- SinhalaGP - lists.icann.org

Re: [SinhalaGP] [Neobrahmigp] Singleton/Few cross-script variant code points
by veena solomon July 6, 2018

July 6, 2018

Yes, I too agree. I also felt the same yesterday when this was brought into attention. On Fri, Jul 6, 2018, 6:51 PM Dr. Ajay DATA <ajay(a)data.in> wrote: > This is as disucssed.. we shall see all the feedback and discuss this > today on call and finalise the view. > > Thank you. > > On 6 July 2018 15:33:38 GMT+05:30, Akshat Joshi <akshatj(a)cdac.in> wrote: >> >> Dear All, >> >> Here is a brief discussion about this issue. >> >> By and large, we have been including all the cross-script variants in the >> cross-script variant analysis which (or any combination of which) could >> stand as a alone valid character/character sequence. >> >> Recently IP has suggested that we may want to reconsider this where a >> small number of code-points are involved as that is an indicative of very >> small overlap between the scripts. >> >> There are two kinds of such cases: >> >> 1. Cross-script variant set made up of dependent characters *ONLY*: >> >> 2. Cross-script variant sets which do included non-dependent >> characters/sequences: >> >> Let us take a look at each of them individually: >> >> *1. **Cross-script variants made up of dependent characters only:* >> >> This is the case as given in the Example 2 given by Pitinan: >> >> *Telugu ం (0C02) and Malayalam ം (0D02) are NOT variant code points. As >> they are combining marks and cannot form variant labels. The same applies >> or Telugu ః (0C03)and Malayalam ഃ (0D03)* >> >> If dependent characters (e.g. Vowel Signs, Anusvara, Visarga, >> Chandrabindu etc) are the *ONLY* cases of cross-script variants among >> the script involved, it is safe to assume the *NON**E* of the labels >> created entirely of the cross-script variants would be valid ones. Hence we >> did not include them in the cross-script variants of the script pair. >> However, if there is even one non-dependent (e.g. Consonant, Vowel etc) >> character as a part of the cross-script variants, then all such cases >> should mandatorily be included in the cross-script variant table. >> >> *2. **Cross-script variants which do included non-dependent >> characters/sequences:* >> >> This is the case as given in the Example 1 given by Pitinan: >> >> *Oriya ଠ (0B20) and Malayalam ഠ (0D20) are variant code points. * >> >> As both the code-points involved in this pair are non-dependent, even the >> smallest instance (single code-point) i.e. ଠ (Oriya ) and ഠ (Malayalam) >> are valid labels which look exactly alike. If we concatenate instances of >> same variant characters with one another, we, in theory, get infinite >> number labels as given below: >> >> ଠଠ - ഠഠ >> >> ଠଠଠ - ഠഠഠ >> >> ଠଠଠଠ - ഠഠഠഠ >> >> ଠଠଠଠଠ - ഠഠഠഠഠ >> >> ..... >> >> all of these look exactly alike, belong to totally different scripts and >> can gain independent existence if not included in the cross-script variant >> set. This indicates that though seemingly the number of characters is few, >> it can create a large number of labels. Important thing to note here is the >> presence of at least one non-dependent character in the cross-script >> variant set. >> >> Hence, it is proposed that: >> >> If, in any two given scripts, all the potential cross-script variants >> consist of dependent (e.g. Vowel Signs, Anusvara, Visarga, Chandrabindu >> etc) characters *ONLY*, then that entire set can be ignored and no >> cross-script variants be proposed between those two scripts. >> >> If, in any two given scripts, there is *AT LEAST ONE* non-dependent (e.g. >> Consonant, Vowel etc) cross-script variant character/sequence present, >> all the potential cross-script variants be considered and proposed between >> the two scripts. >> >> Regards, >> >> Akshat >> >> On 06-07-2018 12:20, Pitinan Kooarmornpatana wrote: >> >> Dear NBGP members, >> >> >> >> Kindly let me draw you attention to the issue of cross-script variant >> code points where there is only a single code point or there are only a few >> code points. >> >> >> >> 1. >> >> *Background * >> >> Currently NBGP proposals include all cross-script variant code points >> which they can form well-formed cross-script variant labels without >> considering how many cross-script variant code points there are between two >> scripts. >> >> >> >> *Example1:* Oriya ଠ (0B20) and Malayalam ഠ (0D20) *are* variant code >> points. >> >> They are consonants and they can form such ഠഠഠ (0B20 0B20 0B20) and ଠଠଠ (0D20 >> 0D20 0D20) cross-script variant labels >> >> Oriya >> >> Malayalam >> >> ଠ (0B20) >> >> ഠ (0D20) >> >> >> >> *Example2*: Telugu ం (0C02) and Malayalam ം (0D02) *are* *NOT* variant >> code points. As they are combining marks and cannot form variant labels. >> The same applies or Telugu ః (0C03)and Malayalam ഃ (0D03) >> >> Telugu >> >> Malayalam >> >> ం (0C02) >> >> ം (0D02) >> >> ః (0C03) >> >> ഃ (0D03) >> >> >> >> 1. >> >> *IP Feedback * >> >> With only a single consonant (or plus two combining marks) the overlap >> between scripts appears rather limited (case of *Example 1* above) . The >> IP would recommend dropping the variants. This feedback applies for Telugu, >> Kannada, Sinhala, Oriya, Malayalam. However the GP decision will affect all >> NBGP proposals. >> >> >> >> The IP suggest dropping following variant sets: >> >> Telugu >> >> Kannada >> >> Sinhala >> >> ం (0C02) >> >> ಂ (0C82) >> >> ං (0D82) >> >> ః (0C03) >> >> ಃ (0C83) >> >> ඃ (0D83) >> >> ర (0C30) >> >> ರ (0CB0) >> >> ර (0DBB) >> >> >> >> Oriya >> >> Malayalam >> >> ଠ (0B20) >> >> ഠ (0D20) >> >> >> >> 1. >> >> *OPTIONS * >> >> *OPTION 1: *Do nothing. >> >> *OPTION 2: *Drop the suggested variant sets. >> >> >> >> Both options are valid. The final decision depends on NBGP. Whichever >> option selected, the proposals will be published for public comment period >> for 40 days. The community and experts will also have a chance to make a >> comment there. After the public comment period has ended. NBGP will >> consider all feedback and finalize proposals accordingly. >> >> >> >> >> >> We’d like to request the NBGP to consider this issue prior to the >> NBGP-Sinhala call this evening and let’s aim to finalize the option during >> the call. >> >> >> >> Regards, >> >> Pitinan >> >> >> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> Neobrahmigp mailing listNeobrahmigp@icann.orghttps://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. >> ------------------------------------------------------------------------------------------------------------------------------- >> >> >> ------------------------------ >> >> Neobrahmigp mailing list >> Neobrahmigp(a)icann.org >> https://mm.icann.org/mailman/listinfo/neobrahmigp >> >> > -- > Sent from my Android device with XGenPlus. > _______________________________________________ > Neobrahmigp mailing list > Neobrahmigp(a)icann.org > https://mm.icann.org/mailman/listinfo/neobrahmigp >

1 0

NBGP-SinhalaGP Meeting
by Pitinan Kooarmornpatana July 5, 2018

July 5, 2018

Dear Sinhala GP members and NBGP members, Thank you Harsha for agreeing on the time for the call. This is a place holder for NBGP-Sinhala meeting tomorrow Friday, 6 July 2018 at 6.30PM - 7:30PM (India Time - Sri Lanka Time , GMT+5.30) Agenda: 1. NBGP-Sinhala Cross-Script Variant Direction * Case of the singleton or only a few cross-script variant. * Other cases (if any) 2. Finalize LGR based on latest IP feedback for a. Devanagari - Akshat b. Gurmukhi - Lehal c. Gujarati - Akshat d. Telugu - Uma Rao/ Ganga e. Kannada - Pavanaja f. Tamil - Shanmugam g. Bangla - Atiur h. Oriya - Kuldeep i. Malayalam - Veena 3. AOB Regards, Pitinan ---------------------------- Link to Adobe Connect: https://participate.icann.org/idn/ *Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). After joining the call, as a courtesy to others and the presenters, please MUTE your phone. This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. If you are Unable to log into Adobe Connect and can only join via phone: https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=1064158692&num=1-719-… Participant Passcode: 1064158692

1 0

Re: [SinhalaGP] Telugu,Kannada cross scripting variants
by Pathum Egodawatta Jan. 10, 2018

Jan. 10, 2018

Hi all, I did a comparison of the code points in question with popular UI fonts. This is the approach we agreed on last SinhalaGP meeting for evaluation. Based on this I agree with Aruni on both accounts. OC30 / 0CB0 / 0DBB: IMO 0DBB is distinctive enough to not be a varient of the former. But it is close. OC05 / 0C85 / 0DB4 and OC06 / 0C85 / 0DB4 : These are distinctive in smaller sizes as well. Therefore I think they dose not qualify. Hope this helps! Cheers, Pathum On Wed, Jan 10, 2018 at 6:10 PM Aruni K. Goonetilleke <arunniii(a)gmail.com> wrote: > Harsha, I'm going thru this with difficulty using phone: > OC30 looks like a ර only when the font size is small. For larger sizes the > two are distinctly different. > OC05 & OC06 look like a stylized ප. Also, only when it's small. > Regards, > Aruni > > > > On 10 Jan 2018 15:15, "harsha wijayawardhana" <wijayawardhana(a)gmail.com> > wrote: > >> Dear all >> >> Pitinan was in touch with me this morning and Neo Brahmi panel requires >> immediate response from within this week of cross scripting variants >> between Telugu and Kannada since they will be submitting their proposals at >> the end of this week. Please go through the following Google doc: >> https://docs.google.com/spreadsheets/d/1pAbK1kA2DCWd9Dhz_4KFJLTf8jx0g_4nnWz… >> Sinhala is in Column n and Telugu and Kannada team has already marked in >> yellow. Please go through two rows marked in yellow, they look similar to >> 'pa' . Please confirm the others as well. >> >> thanks and regards >> harsha >> >> >> >> >> _______________________________________________ >> SinhalaGP mailing list >> SinhalaGP(a)icann.org >> https://mm.icann.org/mailman/listinfo/sinhalagp >> >> -- ෴ ජය! ෴ පැතුම් එගොඩවත්ත Pathum Egodawatta pathum(a)mooniak.com

1 0

Telugu,Kannada cross scripting variants
by harsha wijayawardhana Jan. 10, 2018

Jan. 10, 2018

Dear all Pitinan was in touch with me this morning and Neo Brahmi panel requires immediate response from within this week of cross scripting variants between Telugu and Kannada since they will be submitting their proposals at the end of this week. Please go through the following Google doc: https://docs.google.com/spreadsheets/d/1pAbK1kA2DCWd9Dhz_4KFJLTf8jx0g_4nnWz… Sinhala is in Column n and Telugu and Kannada team has already marked in yellow. Please go through two rows marked in yellow, they look similar to 'pa' . Please confirm the others as well. thanks and regards harsha

1 0

Khmer LGR - Sample for in-script variant
by Pitinan Kooarmornpatana Jan. 9, 2018

Jan. 9, 2018

Dear Sinhala GP Members, Regards to the sample of in-Script variant. Kindly find attached the Khmer LGR Proposal. Regards, Pitinan

1 0

Update form Varients group
by Pathum Egodawatta Jan. 8, 2018

Jan. 8, 2018

Hi All, Today the variants sub-group met and made the following decisions. - Set up a Google Drive folder for documents and collaboration. It will be the primary source going forward. I will add the SinhalaGP members with write and edit assess. If you would like to contribute and not on SinhalaGP, please observe the mailing list for now. We will post drafts for comments as per schedule. - We will have arrange a call/s before 18th and finlise presentation. - Which scripts to look at for variants is key question that we need to answer immediately. Some discussion happened regarding this. Will be documented on the Google Doc. I can share the drive folder on the list as a view-only, not sure weather it is the best thing to do at this stage. Cheers, -pe -- ෴ ජය! ෴ පැතුම් එගොඩවත්ත Pathum Egodawatta pathum(a)mooniak.com

1 0

Material from the workshop
by Pathum Egodawatta Jan. 8, 2018

Jan. 8, 2018

@Samrad Can you please share the documents and slides from the workshop? Or direct us to where we can get them? -pe -- ෴ ජය! ෴ පැතුම් එගොඩවත්ත Pathum Egodawatta pathum(a)mooniak.com

1 0

FW: [Neobrahmigp] Draft Devanagari LGR
by Pitinan Kooarmornpatana Jan. 7, 2018

Jan. 7, 2018

Dear Sinhala GP members, Please find attached the Devanagari LGR Proposal for your reference. Regards, Pitinan From: Neobrahmigp [mailto:neobrahmigp-bounces@icann.org] On Behalf Of Akshat Joshi Sent: Tuesday, January 2, 2018 6:55 PM To: Mahesh Kulkarni <mdk(a)cdac.in>; unsciil51(a)gmail.com; Udaya Narayana Singh <unsciil(a)yahoo.com>; Dr. AJAY D A T A <ajay(a)data.in>; NeobrahmiGP(a)icann.org Subject: Re: [Neobrahmigp] Draft Devanagari LGR Dear All, As per the discussions in the Colombo meeting, I have added the Nukta Variants in the appendix in the non-normative section in Devanagari LGR. All the files required have been attached. Also, the file containing valid and invalid labels has been split for each category separately. Regards, Akshat Joshi On 07-12-2017 18:47, Akshat Joshi wrote: Dear All, Further to the comments received from Integration Panel on 27th Nov. 2017, Devanagari LGR Drafts (Doc file, XML) have been revised and are attached. In addition, I have also attached sample strings (created by Neha Gupta) that are supposed to be validated and invalidated by the said draft. As discussed in con-call on 30th Nov. 2017, we would be submitting the same to Integration Panel on 16th Dec. 2017 for their final comments. If draft is accepted by them without any changes, it will be considered as a final submission from NBGP to IP and will then undergo public comments process. Request all to provide feedback on the same before 15th Dec. 2017 for any changes sought. As I would be leaving for Sri Lanka F2F on 11th night, comments received before that would enable me to integrate them in the document easily. Still, you may provide the comments by 15th. If there are no comments, request the co-chairs to send all the documents to IP with following remarks: ------------%------------%------------%------------%------------%------------%------------%------------%------------%------------%------------% 1. Devanagari LGR Drafts (Doc file, XML) have been revised as per the comments received from Integration Panel on 27th Nov. 2017 (Attached) 2. Sample Input strings (to be validated and invalidated) have also been provided in an Excel file. (Attached) 3. Almost all the edits and additions (both in Main document as well as in XML) suggested by the IP have been carried out, hence there is no separate document attached with NBGP remarks. There are only two remarks from NBGP as given below. - After due analysis for cross-script variants of Devanagari characters with all other scripts, DV LGR lists cross-script variants only with Gurmukhi script based on "visual confusability". As they are not "exactly similar", they have been added in the Appendix (A) and not made part of normative recommendation. They have also not been added to the XML. NBGP requests IP to advise if these cases are to be made part of proposed variants despite belonging to "visual confusability" case. 2. The edit suggested in "Variant Disposition" has not been taken in toto. The use of the term "mutually exclusive" as used to refer to the variants is not clear hence that line is dropped. NBGP can add the same if the wording is an absolute must, after due consultation with the IP. Request the IP feedback on the same. ------------%------------%------------%------------%------------%------------%------------%------------%------------%------------%------------% Regards, Akshat Joshi C-DAC GIST On 17-11-2017 15:18, Akshat Joshi wrote: Dear All, As per the comments received from Dr. Raiomod Doctor and Prof. Uma Maheshwar Rao, please find attached, further refined version of the DV LGR. General nature of changes: - Terminology modification: Anunasika word dropped from Chandrabindu category as it has different connotations - correction in referring B and D categories in one place - Two characters added to valid nukta sequences - Elaboration on the concept of schwa - Minor grammatical corrections In addition to this, have added Devanagari section of MSR chart before the code-point repertoire to give reader of the full picture. Sending this before call in order to solicit comments on these changes as well. Comments on earlier version are also welcome. Regards, Akshat Joshi On 14-11-2017 17:51, Akshat Joshi wrote: Dear All, Please find attached, final revised draft of Devanagari LGR to be submitted to Integration Panel (IP) for their comments/feedback. Both .doc and .pdf versions are given. All of the changes as suggested by the IP in their feedback have been accommodated and our feedback to the same is also attached. Filename: Response to IP Feedback on Devanagari LGR Draft-20171011-4.docx XML file i.e. Normative version of the DV-LGR has also been updated and attached. Filename: Proposed-LGR-Deva-20171114.xml Regards, Akshat Joshi C-DAC GIST On 11-10-2017 16:46, Akshat Joshi wrote: Dear All, Please find attached, Draft Devanagari LGR copy which may be sent to Integration Panel for their detailed review. Only house-keeping changes are still needed which mostly pertain to the non-normative sections of both the documents. In XML, descriptive text needs to be added while in LGR doc file, names of members who all contributed, need to be added. I will soon and share the changes tracked version of the same. As I am out of town till 13th Oct, will do that post 13th. The list of valid and invalid words will also be shared post 13st at the earliest possible time. Most of the changes as suggested by the IP in their feedback have been accommodated. Following is short summary of changes and replies to earlier IP feedback. 1. Halant ending variant has been removed. 2. Nepali corpus words getting invalidated: As rightly pointed by IP, all the below words are invalid as per Nepali writing norms, hence they did not pass the test. Wrong construct ऒ् i.e. V + H शऒ्ढया‎ (0936 0912 094D 0922 092F 093E) शऒ्ढयाका‎ (0936 0912 094D 0922 092F 093E 0915 093E) शऒ्ढयाको‎ (0936 0912 094D 0922 092F 093E 0915 094B) शऒ्ढयालगायत‎ (0936 0912 094D 0922 092F 093E 0932 0917 093E 092F 0924) ‎शैऒ्ढयाको‎ (0936 0948 0912 094D 0922 092F 093E 0915 094B) 3. "अफगानिस्तान" should have passed the test. In this XML version it does. Not sure what must have went wrong. 4. Hindi Corpus: सू़जन‎ (0938 0942 093C 091C 0928) - Wrong sequence Cons+Matra+Nukta अरब़‎ (0905 0930 092C 093C) - Ba+Nukta is not permissible. Maybe a typo. 5. All the references pertaining to INSCRIPT standard have been withdrawn as it is not available online, being a paid resource. Instead, omniglot references have been added. 6. Rationale for excluded code-points could not be added. Will be added soon. In my opinion, Dr. Sarmad you may please take this to the IP if there are no immediate substantial comments on the mailing list. Regards, Akshat Joshi C-DAC GIST On 08-09-2017 00:29, Akshat Joshi wrote: Dear All, Please find attached, copy of the Devanagari LGR which can be submitted to Integration Panel for their early comments. The Devanagari LGR document is also accompanied with the XML file of the same. Dr. Data you may please take this to the IP with following points: 1. In the XML, framing of the rule "follows-only-C-or-CN" has been done as per our understanding. It may need corrections. Request IP to suggest. 2. Variants: - As per reciprocity of variants, the variant sequences have been reproduced in the <data> section. It may need corrections. Request IP to suggest. - The "Halant ending" variants mentioned in section 6.2 in LGR document is a case of conditional and null variant. It was not clear how to put that in XML. It has not been done. Request IP to suggest. 3. Some of the language's data is expected to be received in few days. Once received, that too will be incorporated into this. Those have been marked in red. Regards, Akshat Joshi On 28-08-2017 17:58, Akshat Joshi wrote: Dear All, Please find attached, most recent version of the Devangari LGR with all the suggestions/changes incorporated till date. We are still in process of getting information on the languages which use Devanagari, fall within EGIDS scale 1 to 4 and are yet to be covered by the NBGP. If we can complete that by end of August, we will release the final version of the Devanagari LGR document which can be sent to Integration Panel for their review. I hope this pre-final draft will act as a good basis for tomorrow's call. 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 Major changes done to the document are: 1. Changes suggested by Dr. Bal regarding name change to Newar and Nepali being official language of Nepal 2. Additional Halanta ending variant has been added (up for discussion) 3. Principles for inclusion of characters have been added in Guiding Principles section (up for discussion) 4. The case of V preceded by an H has been explicitly mentioned under the WLE section (up for discussion) Regards, Akshat Joshi On 04-08-2017 17:57, Akshat Joshi 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[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_CDACI…> & 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(a)icann.org<mailto:Neobrahmigp@icann.org> https://mm.icann.org/mailman/listinfo/neobrahmigp -- Regards, Akshat Joshi C-DAC GIST -- Regards, Akshat Joshi C-DAC GIST ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_CDACI…> & 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(a)icann.org<mailto:Neobrahmigp@icann.org> https://mm.icann.org/mailman/listinfo/neobrahmigp -- Regards, Akshat Joshi C-DAC GIST -- Regards, Akshat Joshi C-DAC GIST -- Regards, Akshat Joshi C-DAC GIST -- Regards, Akshat Joshi C-DAC GIST ------------------------------------------------------------------------------------------------------------------------------- [ C-DAC is on Social-Media too. Kindly follow us at: Facebook: https://www.facebook.com/CDACINDIA[facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_CDACI…> & 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(a)icann.org<mailto:Neobrahmigp@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. -------------------------------------------------------------------------------------------------------------------------------

1 0

Welcome to Sinhala GP list and wiki page
by Sarmad Hussain Jan. 3, 2018

Jan. 3, 2018

Dear Sinhala GP members, We would like to thank you for agreeing to contribute to the Sinahala GP. It was great to meet up with all of you in Colombo recently. Kindly note that the SinahalaGP(a)icann.org<mailto:SinahalaGP@icann.org> list has now been created and Pitinan has subscribed all of us on this email list. You can email to this list to communicate with the Sinhala GP members. However, please note that all the emails to this list are publicly archived at http://mm.icann.org/pipermail/sinhalagp/. We will also be posting the updates by the Sinhala GP at the newly created wiki page for the GP: https://community.icann.org/display/croscomlgrprocedure/Sinhala+GP. Kindly check your information on this page and we would welcome any suggestions to improve this page. We look forward to working with all of you towards the development of the Sinhala Label Generation Rules for the Internet's Root Zone. Regards, Sarmad

2 2

FW: [Ext] ICANN News Alert -- Sri Lankan Community Preparing for a Multilingual Internet Using Local Scripts
by Sarmad Hussain Dec. 13, 2017

Dec. 13, 2017

Dear Sinhala GP members, FYI. Regards, Sarmad From: ICANN News Alert [mailto:no-reply@external.icann.org] Sent: Wednesday, December 13, 2017 7:49 AM To: Sarmad Hussain <sarmad.hussain(a)icann.org> Subject: [Ext] ICANN News Alert -- Sri Lankan Community Preparing for a Multilingual Internet Using Local Scripts [Image removed by sender. ICANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/resources/press-material/release-2-2017-12-12-en[ican…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> ________________________________ Sri Lankan Community Preparing for a Multilingual Internet Using Local Scripts Work commences on enabling Sinhala and Tamil scripts for top-level domain names 12 December 2017 Colombo, Sri Lanka… The Internet Corporation for Assigned Names and Numbers (ICANN) and local experts in policy, technical and linguistic fields convened in Colombo today to introduce the Internationalized Domain Name (IDN) program and launch the Sinhala Generation Panel (GP). The launch signifies an exciting future where the local community contributes towards developing secure and stable access to the Internet in Sinhala. The Asia Pacific region is linguistically diverse. Of the 6,800 languages in the world, about half of them or 3,500 are spoken in APAC. 21 of the top 30 most spoken languages in the world are used in the region. This diversity adds challenges to the Internet domain name space. "IDNs are domain names represented by letters or characters from different scripts and writing systems. They offer the possibility of using the domain names in languages across the globe, including Sinhala, Tamil, Thai, Chinese, Hindi, and others. Thus, providing a truly multilingual Internet with greater flexibility and opportunities for billions of users," said Sarmad Hussain, ICANN's IDN Programs Director. "The ability for Internet users to come online in their native languages and scripts is a significant development for the Internet. As Sinhala is a commonly used language in Sri Lanka, the work by the Sinhala GP will lay the groundwork for allowing complete domain names in the Sinhalese language," added Hussain. The Sinhala GP comprises two Co-Chairs and a number of local community representatives from the policy, linguistic fields, as well as members with technical expertise in Sinhala language computing, Unicode and the Internet's domain name system. Harsha Wijayawardhana, Co-Chair of the Sinhala GP, said, "We are all extremely excited about this new development. The Sinhala GP will work on developing root zone label generation rules for the Sinhala script. There will be significant technical work involved, such as developing the rules for computers to understand how to form correct top-level domain names in Sinhala script. Our efforts will help to form the basis for allowing complete domain names in the Sinhala language." Earlier this week, members of the Sinhala GP attended a workshop to discuss the work plan and next steps. The Neo-Brahmi GP is also in Colombo this week. They are developing label generation rules for nine Neo-Brahmi scripts including Tamil, the other commonly used language in Sri Lanka. When both the Sinhala and Neo-Brahmi GPs' work are completed, Sri Lankans can look forward to accessing the Internet's domain name system using domain names in their scripts and languages. Work has been completed by the respective GPs for the Arabic, Armenian, Cyrillic, Ethiopic, Georgian, Khmer, Lao and Thai scripts, and is underway for many more, including Chinese, Japanese, Greek, Korean, and Latin scripts. ICANN is currently calling for volunteers to form GPs for these four scripts: Hebrew, Myanmar, Tibetan and Thaana. Enabling a Multilingual Internet – Additional Information In addition to developing rules to form valid top-level domains (TLDs) in the local script, many computing systems need to be upgraded as they do not recognize or appropriately process new domain names, primarily because the TLD or IDN may be more than three characters in length or in an alternate format. The same is true for email addresses that incorporate these new extensions. The Universal Acceptance Steering Group (UASG), supported by ICANN, is a community-led, Internet industry-wide initiative working on creating awareness and identifying and resolving problems associated with the universal acceptance of domain names. To learn more, or report an issue with Universal Acceptance, please visit www.uasg.tech[uasg.tech]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.uasg.tech&d=DwMFaQ&…>. #### For more information on IDNs, please visit here[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. For more information on UA, please visit here[uasg.tech]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.uasg.tech_&d=DwMFaQ…>. Media Contacts ICANN Liana Teo Head of Communications, APAC Tel: +65 6816 1259 Mobile: +65 9796 5500 Email: liana.teo(a)icann.org<mailto:liana.teo@icann.org> Fiona Aw Global Communications Coordinator Tel: +65 6816 1264 Mobile: +65 9113 6621 Email: fiona.aw(a)icann.org<mailto:fiona.aw@icann.org> About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world.

1 0