<div dir="ltr"><div>Dear Pitinan,<br></div><div>Thanks for the corrections.</div><div>I have seen the latest lgr and looks now alright and agreement with</div><div>other similar script languages. I have just made one minor correction</div><div>in the section 7. the existing Rule 5. stands deleted and the next rule 6. </div><div>will be renamed or replaced by the Rule 5.</div><div>Thanks for everything.</div><div>best regards,</div><div>Uma MaheshwarRao</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 11, 2019 at 9:28 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">Dear NBGP members, <br>
<br>
Thank you for confirming the updated version of the Telugu LGR. Based on the confirmed updates, accept all changes and finalize the package. <br>
Please find the final package of version 2.8, dated 7 June 2019 as attached. <br>
<br>
1. Telugu LGR proposal (proposal-telugu-lgr-07Jun19-en.docx)<br>
2. Telugu LGR XML (proposal-telugu-lgr-07jun19-en.xml)<br>
3. Telugu Test Label (telugu-test-labels-07jun19-en.txt)<br>
<br>
This package is being forward to the IP for consideration to integration. <br>
<br>
Regards,<br>
Pitinan<br>
<br>
-----Original Message-----<br>
From: Neobrahmigp <<a href="mailto:neobrahmigp-bounces@icann.org" target="_blank">neobrahmigp-bounces@icann.org</a>> on behalf of Pitinan Kooarmornpatana <<a href="mailto:pitinan.koo@icann.org" target="_blank">pitinan.koo@icann.org</a>><br>
Date: Tuesday, June 11, 2019 at 23:21<br>
To: "office@babul.ngo" <office@babul.ngo><br>
Cc: "<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>
Subject: Re: [Neobrahmigp] FW: [Ext] lgrtelugucomments-modified<br>
<br>
Dear NBGP team, <br>
<br>
Kindly note that Ganga planned to post this message to the public comment of LGR-3 as well, but due to the problem on his machine, he gave me the consent to post to the PC on his behalf. <br>
<br>
Best Regards,<br>
Pitinan<br>
<br>
-----Original Message-----<br>
From: Babul Films Society n-p NGO ICT for Ecoawareness <office@babul.ngo><br>
Organization: Babul Films Society non profit NGO <br>
Reply-To: "office@babul.ngo" <office@babul.ngo><br>
Date: Tuesday, June 11, 2019 at 21:12<br>
To: Pitinan Kooarmornpatana <<a href="mailto:pitinan.koo@icann.org" target="_blank">pitinan.koo@icann.org</a>><br>
Cc: "<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>
Subject: Re: [Neobrahmigp] FW: [Ext] lgrtelugucomments-modified<br>
<br>
Dear NBGP team,<br>
Thanks for attending the call and arriving at a consensus.<br>
<br>
Follow up on the previous comment to Telugu LGR in LGR-3, the NBGP had <br>
reconsidered the restriction<br>
of Halant following Nasal-C and decided to drop the rule to accommodate <br>
the general usage of labels<br>
in Telugu e.g names.<br>
Also the homophonic variant issue will be handled outside of the LGR, <br>
the same way as other Neo-Brahmi script proposals.<br>
<br>
Example of Telugu labels which become valid in the updated Telugu LGR:<br>
<br>
1. చంపా champaa - flower name<br>
2. గంప gampa - basket [made of bamboo]<br>
3. తంటా tantaa - difficulty<br>
4. పండు pandu - fruit<br>
<br>
<br>
The main motivation is to make general usage of labels more clear and <br>
remove ambiguity.<br>
<br>
Thanks to Prof Rao, Pavanaja, Akshat and others for the healthy <br>
discussion.<br>
<br>
With best wishes<br>
<br>
Gangadhar Panday<br>
<br>
On 06.06.2019 11:26, Pitinan Kooarmornpatana wrote:<br>
> Dear NBGP members,<br>
> <br>
> Please find attached the IP note to NBGP public comment on Telugu and<br>
> Kannada (lgr-3-public-comment-issue-Telugu-Kannada-2019-06-05.docx)<br>
> <br>
> This note response to NBGP comment as attached<br>
> (lgrtelugucomments-modifed-again.docx).<br>
> <br>
> This is for your discussion and finalize how to proceed _WHETHER A<br>
> CHANGE TO EITHER LGR IS CALLED FOR, AND WHETHER THAT CHANGE INVOLVES<br>
> ACTUAL CHANGE IN THE PROPOSED RULES AND OR AN IMPROVEMENT IN THE<br>
> EXPLANATION OF THE FEATURES OF THE EXISTING LGRS AND WHY THEY WERE<br>
> ADOPTED._<br>
> <br>
> Please note that time is of the essence. The deadline for reaction to<br>
> public comments on the LGR-3 drafts is JUNE 18.<br>
> <br>
> Regards,<br>
> <br>
> Pitinan<br>
> <br>
> -------------------------<br>
> <br>
> To: NeoB GP<br>
> From: Integration Panel<br>
> Subject: Recent public comment on LGR-3 regarding Telugu and Kannada<br>
> <br>
> The IP would like to direct the GP's attention to the following public<br>
> comment received about a potential discrepancy between the treatment<br>
> of Halant nasal consonant conjuncts in Kannada and Telugu.<br>
> <br>
> The following repeats the comment and then proceeds to an analysis<br>
> identifying several possible outcomes. It should be noted that while<br>
> the IP has a general preference for treating parallel facts in a<br>
> parallel way, this does not mean that some exceptions aren't possible<br>
> if documented and justified.<br>
> <br>
> Also, following the Procedure, the IP has a general preference for a<br>
> conservative approach, limited to modern practice. If nasal consonant<br>
> conjuncts are effectively limited to Sanskrit, and the GP decided that<br>
> Sanskrit transcription is inappropriate or out of scope for TLD labels<br>
> in a particular script, or that they represent an unnecessary<br>
> duplication in light of the modern practice of using Anusvara, that<br>
> could constitute a justifiable rationale for restricting them.<br>
> <br>
> In the existing Telugu LGR that rationale is hinted at, but not made<br>
> explicit. The Kannada LGR is silent on the issue, although it is our<br>
> (non-expert) understanding that a similar issue exists in that script.<br>
> <br>
> The IP would like to request the GP to review this issue and suggest<br>
> whether a change to either LGR is called for, and whether that change<br>
> involves actual change in the proposed rules and or an improvement in<br>
> the explanation of the features of the existing LGRs and why they were<br>
> adopted.<br>
> <br>
> In closing, we would like to note that time is of the essence. The<br>
> deadline for reaction to public comments on the LGR-3 drafts is June<br>
> 19. The deadline for being able to publish LGR-3 in the current fiscal<br>
> year is June 18.<br>
> <br>
> --- Integration Panel<br>
> <br>
> === Message from prof. Rao ===<br>
> <br>
> PROBLEM:<br>
> <br>
> The sequence of a Nasal Consonant {m, n, ṇ, ɲ, ŋ} + C is<br>
> represented as 1. {m, n, ṇ, ɲ, ŋ} + H+C = {<br>
> म्प,न्त,ण्ट,ञ्च, ङ्क} or 2. {ंप,<br>
> ंत, ंट ंच, ंक}.<br>
> <br>
> Only one of the two representations is popularly followed in each of<br>
> the languages (except for Tamil) that use Brahmi derived scripts. Now<br>
> you need a common solution whether to block one of the two in each of<br>
> these languages or just simply leave it.<br>
> <br>
> In the Telugu script lgr currently we have blocked one variant<br>
> (representation 1.). But I have not come across similar thing in other<br>
> languages. If I am right, then should we assume that both variant<br>
> representations are valid? If that is so, then we have same problem<br>
> but followed different solutions.<br>
> <br>
> SOLUTION:<br>
> <br>
> 1. Drop blocking* in Telugu;<br>
> <br>
> 2. Introduce blocking in other languages.<br>
> <br>
> === End of Message ===<br>
> <br>
> *Please note that the blocking in this context means having a WLE to<br>
> disallow the H to follow nasal-C.<br>
> <br>
>> <br>
> _______________________________________________<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<br>
> your personal data for purposes of subscribing to this mailing list<br>
> accordance with the ICANN Privacy Policy<br>
> (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=qAs-z5lsx1qg4ORlIggZJ8rKxoygReIR_xCeVaO37qo&m=yR92l3cvlbmoP6vH34C1i97uVtJQntHR2Hjl27b2aPI&s=LOsqaPIn8zVOjlZVGWg8JnYQvkUgTxVawyvTRBPFHBE&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=qAs-z5lsx1qg4ORlIggZJ8rKxoygReIR_xCeVaO37qo&m=yR92l3cvlbmoP6vH34C1i97uVtJQntHR2Hjl27b2aPI&s=LOsqaPIn8zVOjlZVGWg8JnYQvkUgTxVawyvTRBPFHBE&e=</a> ) and the website Terms of<br>
> Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=qAs-z5lsx1qg4ORlIggZJ8rKxoygReIR_xCeVaO37qo&m=yR92l3cvlbmoP6vH34C1i97uVtJQntHR2Hjl27b2aPI&s=I81-gVcWwLsZg8sL9vmtVSrZ3JzYBKM4J7VX5W8AtC0&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=qAs-z5lsx1qg4ORlIggZJ8rKxoygReIR_xCeVaO37qo&m=yR92l3cvlbmoP6vH34C1i97uVtJQntHR2Hjl27b2aPI&s=I81-gVcWwLsZg8sL9vmtVSrZ3JzYBKM4J7VX5W8AtC0&e=</a> ). You can visit the Mailman<br>
> link above to change your membership status or configuration,<br>
> including unsubscribing, setting digest-style delivery or disabling<br>
> delivery altogether (e.g., for a vacation), and so on.<br>
<br>
-- <br>
Babul Films Society NGO np [regd]<br>
S-4, Saregama Apts, Shaikpetnala,<br>
GOLCONDA Post, HYDERABAD,<br>
Telangana State, INDIA<br>
<br>
ICT 4 Ecoawareness<br>
+91 9618082288<br>
<br>
<br>
<br>
_______________________________________________<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>