<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Georgia">Correction: </font>I was <b>*not*</b>
aware of the sensitivities involved.</p>
<br>
<div class="moz-cite-prefix">On 08-08-2017 18:12, Akshat Joshi
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:58cd2c81-cf49-eab8-cb68-f46810625852@cdac.in">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p><font face="Georgia">Hello Dr. Bal,</font></p>
<p><font face="Georgia">My replies inline below:</font><br>
</p>
<br>
<div class="moz-cite-prefix">On 08-08-2017 17:48, Bal Krishna Bal
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALR54873jrWAHw2Wg0nF_K4vDFKAQMzV7L7FyFDYw3mJDCviXA@mail.gmail.com">
<div dir="ltr">Thanks Akshat for the comprehensive document.
<div>I have passed my comments on some of potential queries
from the Nepali/Newar language perspective as a response to
your recent email.</div>
<div><br>
</div>
<div>I just wanted to add here a few of my comments:</div>
<div><br>
</div>
<div>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.</div>
</div>
</blockquote>
I was aware of the sensitivities involved. It was unintentional.
Thanks for pointing it out. I have changed it in the document
right away. <br>
<blockquote type="cite"
cite="mid:CALR54873jrWAHw2Wg0nF_K4vDFKAQMzV7L7FyFDYw3mJDCviXA@mail.gmail.com">
<div dir="ltr">
<div>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:</div>
<div> Could you add the following note towards the end of
Section 3 "Background on Script and Principal Languages
Using it" ?</div>
<div> <b>"Nepali is the official language of Nepal
spoken by over 30 million people."</b> <br>
</div>
</div>
</blockquote>
I do recall you saying this before. My apologies that I missed. I
have added it now. :)<br>
<blockquote type="cite"
cite="mid:CALR54873jrWAHw2Wg0nF_K4vDFKAQMzV7L7FyFDYw3mJDCviXA@mail.gmail.com">
<div dir="ltr">
<div>3. On "Variants" in Section 6:</div>
<div> I might have raised this issue in my email response but
just wanted to reiterate it here just to not miss it:</div>
<div> 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?</div>
</div>
</blockquote>
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. <br>
<blockquote type="cite"
cite="mid:CALR54873jrWAHw2Wg0nF_K4vDFKAQMzV7L7FyFDYw3mJDCviXA@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>Regards,</div>
<div>Bal Krishna </div>
<div><br>
</div>
</div>
</blockquote>
Regards,<br>
Akshat Joshi<br>
<br>
<blockquote type="cite"
cite="mid:CALR54873jrWAHw2Wg0nF_K4vDFKAQMzV7L7FyFDYw3mJDCviXA@mail.gmail.com">
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div style="font-size:small">---</div>
<div style="font-size:small">Bal Krishna Bal,PhD</div>
<div style="font-size:small">Assistant Professor </div>
<div style="font-size:small">Lead Researcher -
Information and Language Processing Research Lab</div>
<div style="font-size:small">Department of Computer
Science and Engineering</div>
<div style="font-size:small">Kathmandu, University</div>
<div style="font-size:small">Dhulikhel, Kavre</div>
<div style="font-size:small">Nepal</div>
<div style="font-size:small">Homepage: <a
href="http://ku.edu.np/cse/faculty/bal"
target="_blank" moz-do-not-send="true">http://ku.edu.np/cse/faculty/bal</a>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">On Fri, Aug 4, 2017 at 6:12 PM,
Akshat Joshi <span dir="ltr"><<a
href="mailto:akshatj@cdac.in" target="_blank"
moz-do-not-send="true">akshatj@cdac.in</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> <font
face="Georgia">Dear All,<br>
<br>
Please find attached, draft LGR document for
Devanagari. <br>
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. <br>
<br>
There are two things that I have marked in red in the
document. <br>
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.<br>
2. Some of the languages which are yet to be taken
into account <br>
<br>
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, </font><font face="Georgia"><font
face="Georgia">some such cases</font></font><font
face="Georgia"><font face="Georgia"><font
face="Georgia"><font face="Georgia"> pertaining to
Santhali</font></font> have been added to the
Variant table. </font>We can discuss the same over
the mails. If required, will make further changes if
needed. <br>
<br>
Major changes done to the document are:<br>
1. Akshar formation rules have been simplified and
inapplicable cases have been removed e.g. Avagraha and
Digits<br>
2. Anusvara and Chandrabindu have been made separate
categories as discussed in the Kathmandu F2F meet. <br>
3. Santhali nukta requirements have been incorporated
and the WLE section has been modified accordingly. <br>
4. List of languages has been modified as per the
EGIDS scale 1 to 4<br>
5. Guiding principles have been added for code-point
selection<br>
6. Code-points as required by Sindhi and Kashmiri have
been added<br>
<br>
<br>
-- <br>
Regards,<br>
Akshat Joshi<br>
<br>
</font> <br>
------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-------
<br>
[ C-DAC is on Social-Media too. Kindly follow us at: <br>
Facebook: <a href="https://www.facebook.com/CDACINDIA"
target="_blank" moz-do-not-send="true">https://www.facebook.com/<wbr>CDACINDIA</a>
& Twitter: @cdacindia ] <br>
<br>
This e-mail is for the sole use of the intended
recipient(s) and may <br>
contain confidential and privileged information. If you
are not the <br>
intended recipient, please contact the sender by reply
e-mail and destroy <br>
all copies and the original message. Any unauthorized
review, use, <br>
disclosure, dissemination, forwarding, printing or
copying of this email <br>
is strictly prohibited and appropriate legal action will
be taken. <br>
------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-------
</div>
<br>
______________________________<wbr>_________________<br>
Neobrahmigp mailing list<br>
<a href="mailto:Neobrahmigp@icann.org"
moz-do-not-send="true">Neobrahmigp@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/neobrahmigp"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/<wbr>listinfo/neobrahmigp</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Regards,
Akshat Joshi
C-DAC GIST</pre>
<br>
-------------------------------------------------------------------------------------------------------------------------------
<br>
[ C-DAC is on Social-Media too. Kindly follow us at: <br>
Facebook: <a class="moz-txt-link-freetext" href="https://www.facebook.com/CDACINDIA">https://www.facebook.com/CDACINDIA</a> & Twitter:
@cdacindia ]
<br>
<br>
This e-mail is for the sole use of the intended recipient(s) and
may
<br>
contain confidential and privileged information. If you are not
the
<br>
intended recipient, please contact the sender by reply e-mail and
destroy
<br>
all copies and the original message. Any unauthorized review, use,
<br>
disclosure, dissemination, forwarding, printing or copying of this
email
<br>
is strictly prohibited and appropriate legal action will be taken.
<br>
-------------------------------------------------------------------------------------------------------------------------------
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Neobrahmigp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Neobrahmigp@icann.org">Neobrahmigp@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/neobrahmigp">https://mm.icann.org/mailman/listinfo/neobrahmigp</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Regards,
Akshat Joshi
C-DAC GIST</pre>
<br />-------------------------------------------------------------------------------------------------------------------------------
<br />[ C-DAC is on Social-Media too. Kindly follow us at:
<br />Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
<br />
<br />This e-mail is for the sole use of the intended recipient(s) and may
<br />contain confidential and privileged information. If you are not the
<br />intended recipient, please contact the sender by reply e-mail and destroy
<br />all copies and the original message. Any unauthorized review, use,
<br />disclosure, dissemination, forwarding, printing or copying of this email
<br />is strictly prohibited and appropriate legal action will be taken.
<br />-------------------------------------------------------------------------------------------------------------------------------
</body>
</html>