<div dir="ltr">Thank you Pitinan. I have gone the documents and test labels and approve the changes. <div><br></div><div>Regards<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font color="#0b5394" face="garamond, times new roman, serif" size="4"><br></font></blockquote><h1 style="white-space:nowrap;line-height:1;margin:0px 0px 8px"><font color="#0b5394" face="garamond, times new roman, serif" size="4">Veena Solomon<br></font></h1><h1 style="font-family:Helvetica,Arial;white-space:nowrap;font-size:14px;color:rgb(0,127,170);line-height:1;margin:0px 0px 8px"><a href="https://www.instagram.com/vinazol" style="color:rgb(17,85,204);font-weight:normal;display:inline-block" target="_blank"><img src="https://cdn3.iconfinder.com/data/icons/free-social-icons/67/instagram_circle_color-24.png"></a><span style="color:rgb(0,0,0);font-weight:normal"> </span><a href="https://www.facebook.com/vinazol" style="color:rgb(17,85,204);font-weight:normal;display:inline-block" target="_blank"><img src="https://cdn3.iconfinder.com/data/icons/free-social-icons/67/facebook_circle_color-24.png"></a><span style="color:rgb(0,0,0);font-weight:normal"> </span><a href="https://twitter.com/vinazol" style="color:rgb(17,85,204);font-weight:normal;display:inline-block" target="_blank"><img src="https://cdn3.iconfinder.com/data/icons/free-social-icons/67/twitter_circle_color-24.png"></a><span style="color:rgb(0,0,0);font-weight:normal"> </span><a href="https://www.linkedin.com/in/vinazol" style="color:rgb(17,85,204);font-weight:normal;display:inline-block" target="_blank"><img src="https://cdn3.iconfinder.com/data/icons/free-social-icons/67/linkedin_circle_color-24.png"></a></h1></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 26, 2019 at 4:55 PM Pitinan Kooarmornpatana <<a href="mailto:pitinan.koo@icann.org">pitinan.koo@icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div class="gmail-m_-3059642316941626123WordSection1"><p class="MsoNormal">Dear Veena and all NBGP members, <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Please find below the additional information from the IP on the previous message on Malayalam LGR defect issues. <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In consultation with Veena, we have updated the Malayalam LGR comment accordingly. <u></u><u></u></p><p class="MsoNormal">Please find attached the updated package version 2.2 dated 26 October 2019. <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Updates in this version:<u></u><u></u></p><ol style="margin-top:0in" start="1" type="1"><li class="gmail-m_-3059642316941626123MsoListParagraph" style="margin-left:0in">Update Rule #1 in docx to match the XML, allowing H to follow 0D7B<u></u><u></u></li><li class="gmail-m_-3059642316941626123MsoListParagraph" style="margin-left:0in">Add necessary variant member into the set due to the rule change<u></u><u></u></li></ol><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Kindly review and finalize. Please let us know if the package is ready to be shared with the IP.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Regards,<u></u><u></u></p><p class="MsoNormal">Pitinan<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><div class="MsoNormal" align="center" style="text-align:center"><span style="color:black"><hr size="2" width="100%" align="center"></span></div><p class="MsoNormal"><span style="color:black">From: Integration Panel<br>To: NeoBrahmi Generation Panel<br>Re: Issue in Root Zone LGR for Malayalam<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">We earlier sent you a request for input on an issue discovered with the Malayalam Root Zone LGR. We have not received a response. In the meantime, as anticipated (see the PS:) the underlying issue of how to encode the Malayalam "nta" has been taken up in the Unicode Technical Committee. Several documents have been filed and links to publicly available ones have been added to the "Update:" at the end.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"><br>We are looking forward to your response,<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">---IP<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><u><span style="color:black">Earlier message:</span></u><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Candara;color:black">The IP has become aware of an<span class="gmail-m_-3059642316941626123apple-converted-space"> </span><u>issue in the published version of the RZ-LGR for Malayalam.</u></span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Candara;color:black">The RZ-LGR-3 version of the Malayalam LGR uses formulation of WLE Rule 1 that (while matching the XML file in the Malayalam LGR proposal) is more permissive than what the proposal document calls for in Section 7.<span class="gmail-m_-3059642316941626123apple-converted-space"> </span></span><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:Candara;color:black">The XML files allow 0D7B to precede Halant, while the text of the proposal document does not, and furthermore, the text gives one example of a sequence that should not be allowed by WLE Rule 1.<span class="gmail-m_-3059642316941626123apple-converted-space"> </span></span><span style="color:black"><u></u><u></u></span></p><p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="font-family:Candara;color:black">At issue is sequence 1b from section 6.1, which the proposal text says should be disallowed because it doesn't render consistently. WLE Rule 1 for H (until the April version of the proposal) did allow the sequence, because VIRAMA was allowed to follow 0D7B.</span><span style="font-family:-webkit-standard,serif;color:black"><u></u><u></u></span></p><p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="font-family:Candara;color:black">This provision was removed in the April version for the DOCx but not in the XML version of the proposal, and the RZ-LGR-3 version of the XML has been published with the more permissive rule.</span><span style="font-family:-webkit-standard,serif;color:black"><u></u><u></u></span></p><p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="font-family:Candara;color:black">One effect is that sequence 1b, which, if permitted, should have been a variant, is now permitted without being a variant, a situation that constitutes a "loophole" that would allow variant labels to be allocated as if unrelated.</span><span style="font-family:-webkit-standard,serif;color:black"><u></u><u></u></span></p><p style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="font-family:Candara;color:black">The WLE rule in question was first changed in response to public comment (it did not allow 0D7B in the 2018-09-25 version). Here's a comment on sequence 1b:</span><span style="font-family:-webkit-standard,serif;color:black"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"><img width="649" height="309" style="width: 6.7604in; height: 3.2187in;" id="gmail-m_-3059642316941626123Picture_x0020_4" src="cid:16e07ef46034cff311" alt="cidimage001.png@01D58056.B96A4570"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">Normally, with the proposal clearly worded one way and the XML different, this could have been a "clerical error" and handled accordingly. However, given that the public comment response and the final proposal are different, it is not possible to unambiguously determine the underlying intent.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal" style="font-variant-caps:normal;text-align:start;word-spacing:0px"><span style="color:black">As it stands, if we leave the Root-Zone's XML version of the rule as is, that XML would be missing a variant definition; Section 6.1 makes it clear that a variant would have been required for sequence 1b if not disallowed. If we change the rule to match the proposal document, then the proposal XML file and response to public comment would need to be revised.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">We have further received reports that question the analysis of the three sequences in Section 6.1 and that come to different conclusions on which ones are unambiguously supported (and which ones should be supported). In particular it is claimed that sequence 1b is not supported by Windows' shaping engine (and neither is 1a).<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">We therefore request the GP to revisit this issue and to resolve how to address this going forward.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">In particular, we would also like the GP to confirm which software platforms support which sequences.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"><br>--IP<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">PS: we are aware that some parties are planning to approach Unicode to request a change to table 12-38. While no such proposal has been received by Unicode today, there is the possibility, but not a certainty, that Unicode's position on the status of that sequence could change in the future.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">Update:<span class="gmail-m_-3059642316941626123apple-converted-space"> </span><b>For background information:</b><span class="gmail-m_-3059642316941626123apple-converted-space"> </span>since the first transmission of the above issue report, the following documents have been submitted to the Unicode Technical Committee or drafted in response.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.unicode.org_cgi-2Dbin_GetMatchingDocs.pl-3FL2_19-2D345&d=DwMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=z4Yh3bolzeekM73LjIua_QhM7_uLjlsqLNy4QfR9NwU&s=qTfIS69iws_kROgkn-X1Be2NGghMO_WYnNXd7LebgUY&e=" title="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.unicode.org_cgi-2Dbin_GetMatchingDocs.pl-3FL2_19-2D345&d=DwMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=z4Yh3bolzeekM73LjIua_QhM7_uLjlsqLNy4QfR9N" target="_blank"><span style="color:purple">L2/19-345 [unicode.org]</span></a><u></u><u></u></span></p><p class="MsoNormal"><b><span style="color:black">Alternative encodings for Malayalam "nta"</span></b><span style="color:black"><u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">Liang Hai<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">2019-10-06<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">and a<span class="gmail-m_-3059642316941626123apple-converted-space"> </span><b>response</b><span class="gmail-m_-3059642316941626123apple-converted-space"> </span>from Cibu<span class="gmail-m_-3059642316941626123apple-converted-space"> </span><u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:"Source Sans Pro",sans-serif;color:rgb(67,67,67)">C Johny</span><span class="gmail-m_-3059642316941626123apple-converted-space"><span style="color:black"> </span></span><span style="color:black"><a href="mailto:cibucj@gmail.com" target="_blank"><span style="color:purple"><cibucj@gmail.com></span></a><u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1K6L82VRmCGc9Fb4AOitNk4MT7Nu4V8aKUJo-5F1mW5X1o_&d=DwMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=z4Yh3bolzeekM73LjIua_QhM7_uLjlsqLNy4QfR9NwU&s=O_s6vEdnHxWBdnoe6_fEW2LUiH0raMTT0ldDTo3sVyM&e=" title="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1K6L82VRmCGc9Fb4AOitNk4MT7Nu4V8aKUJo-5F1mW5X1o_&d=DwMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=z4Yh3bolzeekM73LjIua_QhM" target="_blank"><span style="color:purple">https://docs.google.com/document/d/1K6L82VRmCGc9Fb4AOitNk4MT7Nu4V8aKUJo_1mW5X1o/ [docs.google.com]</span></a><u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><span style="color:black">The UTC met on 2019-10-07 and discussed these documents. The conclusion was to retain the recommended sequence in the current version of the standard as the preferred one, but to better acknowledge the existence of the legacy sequences. The treatment in the Unicode Standard would therefore be somewhat similar to that of Tamil sequences for SHRII.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><div class="MsoNormal" align="center" style="text-align:center"><span style="color:black"><hr size="2" width="100%" align="center"></span></div><p class="MsoNormal"><span style="color:black"> <u></u><u></u></span></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in"><p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Pitinan Kooarmornpatana <<a href="mailto:pitinan.koo@icann.org" target="_blank">pitinan.koo@icann.org</a>><br><b>Date: </b>Tuesday, August 6, 2019 at 17:24<br><b>To: </b>"<a href="mailto:Neobrahmigp@icann.org" target="_blank">Neobrahmigp@icann.org</a>" <<a href="mailto:Neobrahmigp@icann.org" target="_blank">Neobrahmigp@icann.org</a>><br><b>Subject: </b>FW: Defect in the Root Zone LGR for Malayalam?<u></u><u></u></span></p></div><div><p class="MsoNormal"><u></u> <u></u></p></div><p class="MsoNormal">Dear Veena, <u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><div><div><p class="MsoNormal">Please find below a message from the IP to NBGP regarding an issue in the integrated Malayalam LGR. <u></u><u></u></p><p class="MsoNormal">The IP found the discrepancy of rule #1 in three places : XML , proposal, and the response to public comment. <u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Kindly review and let us know your feedback. <u></u><u></u></p><p class="MsoNormal"> <u></u><u></u></p><p class="MsoNormal">Regards,<u></u><u></u></p><p class="MsoNormal">Pitinan<u></u><u></u></p></div><div><div class="MsoNormal" align="center" style="text-align:center"><hr size="2" width="100%" align="center"></div></div><div><p class="MsoNormal">From: Integration Panel<br>To: NeoBrahmi Generation Panel<br>Re: Issue in Root Zone LGR for Malayalam<br><br><span style="font-family:Candara">The IP has become aware of an <u>issue in the published version of the RZ-LGR for Malayalam.</u></span><u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:Candara">The RZ-LGR-3 version of the Malayalam LGR uses formulation of WLE Rule 1 that (while matching the XML file in the Malayalam LGR proposal) is more permissive than what the proposal document calls for in Section 7. </span><u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal"><span style="font-family:Candara">The XML files allow 0D7B to precede Halant, while the text of the proposal document does not, and furthermore, the text gives one example of a sequence that should not be allowed by WLE Rule 1. </span><u></u><u></u></p></div><p><span style="font-family:Candara">At issue is sequence 1b from section 6.1, which the proposal text says should be disallowed because it doesn't render consistently. WLE Rule 1 for H (until the April version of the proposal) did allow the sequence, because VIRAMA was allowed to follow 0D7B.</span><u></u><u></u></p><p><span style="font-family:Candara">This provision was removed in the April version for the DOCx but not in the XML version of the proposal, and the RZ-LGR-3 version of the XML has been published with the more permissive rule.</span><u></u><u></u></p><p><span style="font-family:Candara">One effect is that sequence 1b, which, if permitted, should have been a variant, is now permitted without being a variant, a situation that constitutes a "loophole" that would allow variant labels to be allocated as if unrelated.</span><u></u><u></u></p><p><span style="font-family:Candara">The WLE rule in question was first changed in response to public comment (it did not allow 0D7B in the 2018-09-25 version). Here's a comment on sequence 1b:</span><u></u><u></u></p><div><p class="MsoNormal"><img border="0" width="649" height="309" style="width: 6.7604in; height: 3.2187in;" id="gmail-m_-3059642316941626123_x0000_i1026" src="cid:16e07ef46035b16b22" alt="cid:image001.png@01D54C39.30724660"><u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">Normally, with the proposal clearly worded one way and the XML different, this could have been a "clerical error" and handled accordingly. However, given that the public comment response and the final proposal are different, it is not possible to unambiguously determine the underlying intent.<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><p class="MsoNormal">As it stands, if we leave the Root-Zone's XML version of the rule as is, that XML would be missing a variant definition; Section 6.1 makes it clear that a variant would have been required for sequence 1b if not disallowed. If we change the rule to match the proposal document, then the proposal XML file and response to public comment would need to be revised. <u></u><u></u></p><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">We have further received reports that question the analysis of the three sequences in Section 6.1 and that come to different conclusions on which ones are unambiguously supported (and which ones should be supported). In particular it is claimed that sequence 1b is not supported by Windows' shaping engine (and neither is 1a).<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">We therefore request the GP to revisit this issue and to resolve how to address this going forward. <u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">In particular, we would also like the GP to confirm which software platforms support which sequences.<u></u><u></u></p></div><div><p class="MsoNormal"><br>--IP<u></u><u></u></p></div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal">PS: we are aware that some parties are planning to approach Unicode to request a change to table 12-38. While no such proposal has been received by Unicode today, there is the possibility, but not a certainty, that Unicode's position on the status of that sequence could change in the future.<u></u><u></u></p></div><div><div class="MsoNormal" align="center" style="text-align:center"><hr size="2" width="100%" align="center"></div><p class="MsoNormal"> <u></u><u></u></p></div></div><p class="MsoNormal"> <u></u><u></u></p></div></div>
_______________________________________________<br>
Neobrahmigp mailing list<br>
<a href="mailto:Neobrahmigp@icann.org" target="_blank">Neobrahmigp@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/neobrahmigp" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/neobrahmigp</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div>