[Neobrahmigp] Draft Devanagari LGR

Bal Krishna Bal bal at ku.edu.np
Tue Aug 8 12:51:57 UTC 2017


Thanks Akshat.

---
Bal Krishna Bal,PhD
Assistant Professor
Lead Researcher - Information and Language Processing Research Lab
Department of Computer Science and Engineering
Kathmandu, University
Dhulikhel, Kavre
Nepal
Homepage: http://ku.edu.np/cse/faculty/bal

On Tue, Aug 8, 2017 at 6:27 PM, Akshat Joshi <akshatj at cdac.in> wrote:

> Hello Dr. Bal,
>
> My replies inline below:
>
> On 08-08-2017 17:48, Bal Krishna Bal wrote:
>
> Thanks Akshat for the comprehensive document.
> I have passed my comments on some of potential queries from the
> Nepali/Newar language perspective as a response to your recent email.
>
> I just wanted to add here a few of my comments:
>
> 1. Could you make sure that you type "Newar" as a language rather than
> "Newari" as the latter is taken as an offense by the "Newar" community? I,
> myself often get confused on this, although a native.
>
> I was aware of the sensitivities involved. It was unintentional.  Thanks
> for pointing it out. I have changed it in the document right away.
>
> 2. The other thing is - I had requested this earlier as well in one of the
> early emails before the  Face-to-Face meeting in Kathmandu. I would again
> like to reiterate it here:
>    Could you add the following note towards the end of Section 3
> "Background on Script and Principal Languages Using it" ?
>       *"Nepali is the official language of Nepal spoken by over 30
> million people."*
>
> I do recall you saying this before. My apologies that I missed. I have
> added it now. :)
>
> 3. On "Variants" in Section 6:
>  I might have raised this issue in my email response but just wanted to
> reiterate it here just to not miss it:
>   Are the variants listed in the table going to be treated as
> "allocatable" or "blocked" variants? This is because to the best of my
> understanding from the Kathmandu Face-to-Face meeting, the preference is to
> "blocked". If that is the case, I think that would block genuine domain
> names in other languages. How do we approach this situation?
>
> The nature of almost all the variants that we may propose being
> "confusingly similar looking", those will be "blocked" variants. Yes, agree
> with you that blocking may end up blocking genuine domain names. However,
> as the domain names allocation always works, it is first come first serve
> basis and once a domain gets booked, all it's look alikes better be blocked
> for the overall stability of the system. It is the inevitable consequence
> of opting for a more secured system. That being said, such occurrence
> though theoretically possible, may not end up really blocking many useful
> domains. It is just a hunch on my part.
>
>
> Regards,
> Bal Krishna
>
> Regards,
> Akshat Joshi
>
>
>
> ---
> Bal Krishna Bal,PhD
> Assistant Professor
> Lead Researcher - Information and Language Processing Research Lab
> Department of Computer Science and Engineering
> Kathmandu, University
> Dhulikhel, Kavre
> Nepal
> Homepage: http://ku.edu.np/cse/faculty/bal
>
> On Fri, Aug 4, 2017 at 6:12 PM, Akshat Joshi <akshatj at cdac.in> wrote:
>
>> Dear All,
>>
>> Please find attached, draft LGR document for Devanagari.
>> Request all to give the feedback on the same so that it can be finally
>> modified for sending across to the Integration Panel for comments.
>>
>> There are two things that I have marked in red in the document.
>> 1. The name of the accompanying XML file which we will finalize after the
>> finalization of the LGR rules and repertoire. You may please ignore that
>> for now.
>> 2. Some of the languages which are yet to be taken into account
>>
>> Apart from that, I have taken into consideration the feedback received
>> for Nepali and Newari . Only the Variants have not been taken into account
>> as they conflict with the "No confusingly similar cases as Variants" policy
>> of LGR Procedure. I will separately reply to the proposed variants in
>> Nepali and Newari. However, some such cases pertaining to Santhali have
>> been added to the Variant table. We can discuss the same over the mails.
>> If required, will make further changes if needed.
>>
>> Major changes done to the document are:
>> 1. Akshar formation rules have been simplified and inapplicable cases
>> have been removed e.g. Avagraha and Digits
>> 2. Anusvara and Chandrabindu have been made separate categories as
>> discussed in the Kathmandu F2F meet.
>> 3. Santhali nukta requirements have been incorporated and the WLE section
>> has been modified accordingly.
>> 4. List of languages has been modified as per the EGIDS scale 1 to 4
>> 5. Guiding principles have been added for code-point selection
>> 6. Code-points as required by Sindhi and Kashmiri have been added
>>
>>
>> --
>> Regards,
>> Akshat Joshi
>>
>>
>> ------------------------------------------------------------
>> -------------------------------------------------------------------
>> [ C-DAC is on Social-Media too. Kindly follow us at:
>> Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
>>
>> This e-mail is for the sole use of the intended recipient(s) and may
>> contain confidential and privileged information. If you are not the
>> intended recipient, please contact the sender by reply e-mail and destroy
>> all copies and the original message. Any unauthorized review, use,
>> disclosure, dissemination, forwarding, printing or copying of this email
>> is strictly prohibited and appropriate legal action will be taken.
>> ------------------------------------------------------------
>> -------------------------------------------------------------------
>>
>> _______________________________________________
>> Neobrahmigp mailing list
>> Neobrahmigp at icann.org
>> https://mm.icann.org/mailman/listinfo/neobrahmigp
>>
>>
>
> --
> Regards,
> Akshat Joshi
> C-DAC GIST
>
>
> ------------------------------------------------------------
> -------------------------------------------------------------------
> [ C-DAC is on Social-Media too. Kindly follow us at:
> Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
>
> This e-mail is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies and the original message. Any unauthorized review, use,
> disclosure, dissemination, forwarding, printing or copying of this email
> is strictly prohibited and appropriate legal action will be taken.
> ------------------------------------------------------------
> -------------------------------------------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/neobrahmigp/attachments/20170808/bc1698d8/attachment-0001.html>


More information about the Neobrahmigp mailing list