<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><font face="Georgia">Dear Dr. Sarmad,</font></p>
    <p><font face="Georgia">Please find attached, the Devanagari LGR
        package with all the edits incorporated as suggested by the IP.
        Would like to thank Pitinan for the edits.</font></p>
    <p><font face="Georgia">If there are no further comments on the same
        from the NBGP list, would like to submit this for publishing on
        the <a moz-do-not-send="true"
          href="https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en">proposal's
          webpage</a>  for IP evaluation.</font></p>
    <p><font face="Georgia">Regards,</font></p>
    <p><font face="Georgia">Akshat Joshi</font><br>
    </p>
    <div class="moz-cite-prefix">On 04-03-2019 09:11, Sarmad Hussain
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:9cb657f811c042c0b21ae19103bbc4b2@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
      <style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;
        color:black;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p><span style="color:windowtext">Dear Akshat and NBGP members,<o:p></o:p></span></p>
        <p><span style="color:windowtext">IP has suggested some edits to
            consider before final submission of the proposal, listed in
            their message below.  <o:p></o:p></span></p>
        <p><span style="color:windowtext">As next steps, once these
            edits are incorporated, the proposal will be published at
            the <a
              href="https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en"
              moz-do-not-send="true">proposals’ webpage</a> as the final
            version after public comment, and then IP will undertake its
            evaluation.<o:p></o:p></span></p>
        <p><span style="color:windowtext">Regards,<br>
            Sarmad</span><o:p></o:p></p>
        <div class="MsoNormal" style="text-align:center" align="center">
          <hr width="100%" size="2" align="center"></div>
        <p>To: NeoBrahmi Generation Panel<br>
          From: Integration Panel<o:p></o:p></p>
        <div>
          <div>
            <div>
              <p class="MsoNormal"><o:p> </o:p></p>
            </div>
            <div>
              <p class="MsoNormal">We reviewed the 20feb19 version of
                the Devanagari proposal and found one showstopper which
                should be easy to correct and several editorial items in
                the XML file.<o:p></o:p></p>
            </div>
            <div>
              <p class="MsoNormal"><br>
                - Integration Panel<o:p></o:p></p>
            </div>
            <div>
              <p class="MsoNormal"><o:p> </o:p></p>
            </div>
            <div>
              <p class="MsoNormal"><b><u>Detailed Feedback:</u></b><o:p></o:p></p>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>DOCX</b><o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">no
                  issues<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>XML</b><o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>proposal-devanagari-lgr-20feb19-en.xml
                  </b><o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>SHOWSTOPPER:</b><o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">(1)
                  when processing the XML, our tool complains about
                  missing symmetric variants (for fix, see next item)<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">(2)
                  the XML has<o:p></o:p></p>
              </div>
              <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
                <div>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">for
                    cp="0901":<br>
                          <var cp="0945 0902" type="blocked" when="<b><span
                        style="color:red">follows-only-C-or-CN</span></b>"/><o:p></o:p></p>
                  <p class="MsoNormal"
                    style="mso-margin-top-alt:auto;margin-bottom:12.0pt">for
                    cp="0945 0902":<br>
                          <var cp="0901" type="blocked" when="<b><span
                        style="color:red">follows-only-V-or-C-or-N-or-M</span></b>"/><o:p></o:p></p>
                </div>
              </blockquote>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
                  issue may have arisen from an incomplete understanding
                  what makes a variant mapping definition "symmetric".
                  As written, the two definitions aren't symmetric. For
                  variant definitions to be symmetric, the <u>context
                    condition must be the same for both</u> (or both
                  absent) and the mappings must have matching source and
                  target, except one is the inverse of the other. In
                  other words, both highlighted context should be <u>the
                    same</u> (and should be the more restrictive one).<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">In
                  this case, the confusion stems from the fact that the
                  two code points have context rules on the <char>
                  level; In this kind of situation, the context rule on
                  the <u>variant level</u> should be the more
                  restrictive of the the two, or, where that is not
                  possible, the intersection. In this case, both
                  <var> should have: <b><span style="color:red">follows-only-C-or-CN</span></b>.<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
                  requires the entry for <var cp="0901 ....> to be
                  updated to <b><span style="color:red">follows-only-C-or-CN</span></b>.<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>Editorial
                    issues in XML</b><o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">(1)
                  In "Variant Disposition" in the <description>:
                  change "the other one label" --> "any other
                  equivalent label"<br>
                  <br>
                  <o:p></o:p></p>
              </div>
              <div>
                <p> (2) To provide necessary explanation about context
                  rules for variants and sequences used with variants
                  add a subsection at then end of "Variants" section in
                  the <description>:<o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">    <p>Context Rules for
                  Variants: some of the variants defined in this LGR are
                  "effective null variants", that is,<br>
                      both some  code points in the source map to
                  "nothing" in the target with all other code points
                  unchanged. <br>
                      (Because mappings are symmetric, it does not
                  matter whether it is the forward or reverse mapping
                  that <br>
                      maps to "null"). Such variants require a context
                  rule to keep the variant well behaved. Symmetry
                  requires <br>
                      the same context rule for both forward and reverse
                  mappings.</p><br>
                      <br>
                      <p>In other cases, the sequences or code
                  points making up source and target are constrained by
                  context <br>
                      rules on the code points.  In such a case, any
                  variants require context rules that match the
                  intersection<br>
                      between the contexts for both source and target;
                  otherwise a sequence might be considered valid in some
                  <br>
                      variant label when it would not be valid in an
                  equivalent context in an original label.</p> <o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">(3)
                  In "Character Classes" change: "The writing system of
                  Devanagari could be summed up as composed of
                  Consonants, Implicit Vowel Killer: Halant, Vowels,
                  Anusvara, Candrabindu, Nukta and a Visarga." to "The
                  writing system of Devanagari could be summed up as
                  composed of Consonants,  Halant, Vowels, Anusvara,
                  Candrabindu, Nukta and  Visarga."<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
                  changes the unwieldy "Implicit Vowel Killer:Halant" to
                  the actual name of the character class being
                  enumerated, that is simply "Halant". There's also an
                  extra "a" near the end of the sentence.<o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">(4)
                  At the end of WLE Rules section, add:<o:p></o:p></p>
                <p class="MsoNormal">    <p>An additional rule is
                  used only for variants where a Nukta maps to a
                  "null":</p><br>
                      <ul><br>
                          <li>Variant is not defined if followed
                  by a Nukta</li><br>
                      </ul> <o:p></o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
                <p class="MsoNormal"
                  style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>TXT</b><o:p></o:p></p>
              </div>
              <div>
                <p class="MsoNormal">  <o:p></o:p></p>
              </div>
              <p class="MsoNormal">We found no change other than
                internal file date. Did not repeat test, particularly as
                the normative definition of the XML still has an error.<o:p></o:p></p>
            </div>
            <div>
              <div class="MsoNormal" style="text-align:center"
                align="center">
                <hr width="100%" size="2" align="center"></div>
              <p class="MsoNormal"><o:p> </o:p></p>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Regards,
Akshat Joshi
C-DAC GIST</pre>
  <img alt="150th Anniversary Mahatma Gandhi" src="cid:signature.jpg">
<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>