- Latingp - lists.icann.org

LATIN GP - Notes from the call on January 2nd, 2020
by Mirjana Tasić Jan. 2, 2020

Jan. 2, 2020

Dear GP members, Please find enclosed short notes from today call. If I missed something please add. Regards Mirjana LATIN GP - Notes from the call on January 2nd, 2020 1. Every member should read the last version of the Report<https://www.dropbox.com/s/jgzt8xyjvse6gnu/2020-01-02-ProposalForLatinScript…>, make his/hers own copy and comment it. Submissions should be made until January 7th, 2020. On January the 8th Pitinan will incorporate the changes, we shall look at the new version, and it is planned to submit new version to IP for comments. 2. Mirjana shall ask Meikal to look at the material in Appendix D produced in December 2019 by four members of GP (MM,HH,BJ and MT) and summarize results of the analysis. 3. Bill will prepare GP feedback to IP on the document 2019-12-20-Partial IP Response to Latin LGR Update-v1.1<https://www.dropbox.com/s/0ogf4vmmut968qn/2019-12-20-Partial%20IP%20Respons…> which will be sent to IP as a separate document. 4. Dennis will try to finalize the ‘ss vs sharp s’ topic. If it could not be finalized until January the 7th, it will be sent to IP as separate document for comments. 5. Somehow Bill’s excel sheets with in-script variant analysis cannot be accessed in Google Docs. It should be somehow reconstructed and included in Appendix D as working material. 6. Agenda for F2F meeting in Brussels should be discussed during next call on January 9th.

1 0

Emailing: Visual Variants - Analysis 20191206.xlsx
by Hazem Hezzah Jan. 2, 2020

Jan. 2, 2020

Your message is ready to be sent with the following file or link attachments: Visual Variants - Analysis 20191206.xlsx Note: To protect against computer viruses, e-mail programs may prevent sending or receiving certain types of file attachments. Check your e-mail security settings to determine how attachments are handled.

1 0

Sharp S
by Bill Jouris Jan. 2, 2020

Jan. 2, 2020

Dear colleagues, It seems to me that we have two options to address the IP's concerns about Sharp S: 1) we can say something like "Sharp S can only occur when used in a valid German word or name. Thus it cannot be the first letter in a TLD, must follow a vowel, etc." At which point we will need to reference an authoritative source on what are valid German words and valid German names. 2) we can say something like "The variant relationship between double S (ss) and Sharp S exists because of different usages in different places where German is the official language. But that relationship is otherwise irrelevant for constructing TLDs. From the beginning, TLDs have existed which were not valid words. That practice has continued as new gTLDs (not to mention ccTLDs) were established. It is not our intention to police German spelling rules. Therefore a Sharp S can occur at the beginning of a TLD, following a consonant (including following another Sharp S), etc." I confess that my initial inclination was to go with option 1. But Michael has convinced me that the second option is more reasonable. If we go with the former, it would clearly need to go in Section 7 WLEs. That may also be the correct place to put the latter text, if that is how we go. Or maybe another location would be better.... Bill Jouris Inside Products bill.jouris(a)insidethestack.com 831-659-8360 925-855-9512 (direct)

3 3

[update zoom link] Latin GP Meeting
by Pitinan Kooarmornpatana Jan. 2, 2020

Jan. 2, 2020

Dear Latin GP members, Greetings 2020! This is a gentle reminder for the Latin GP meeting on Thursday 2 January 2020 at 16:00-17:00 UTC. Please join the meeting at https://icann.zoom.us/j/824530213. AGENDA for the GP call on January the 2nd 2020, 16:00UTC 1. Roll call 2. How to proceed with editing of the Report? (The latest version of the report in Dropbox is at https://www.dropbox.com/home/Latin%20GP/2019-12-05-Report?preview=2020-01-0….) 3. How to proceed with In script variant analysis * Bill's excel table [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spread…> * Appendix D In-script Analysis competed in the last version of the Report * 2019-12-12-TBD-ReportV5-VariantAnalysis [dropbox.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_hh5e…> * 2019-12-20-Partial IP Response to Latin LGR Update-v1.1 [dropbox.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_0ogf…> * Cross-Script-Talking-Points-v2 [dropbox.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dropbox.com_s_62rk…> 4. Next meeting proposal January 9th 2020, , 16:00UTC 5. AOB Kindly be informed that I have limited access to the internet at the meeting time today. Sarmad will host the call. Regards, Pitinan

1 0

Re: [Latingp] [Ext] Status of the Report
by Pitinan Kooarmornpatana Jan. 2, 2020

Jan. 2, 2020

Dear all, I’d like to inform that the file was uploaded to dropbox folder. It is at https://www.dropbox.com/home/Latin%20GP/2019-12-05-Report?preview=2020-01-0…. Regards, Pitinan From: Latingp <latingp-bounces(a)icann.org> on behalf of Pitinan Kooarmornpatana <pitinan.koo(a)icann.org> Date: Thursday, January 2, 2020 at 13:36 To: Mirjana Tasić <Mirjana.Tasic(a)rnids.rs>, Latin GP <latingp(a)icann.org> Subject: Re: [Latingp] [Ext] Status of the Report Dear Mirjana, and all. I have checked all the changes by Meikal, there is only one missing sentence, please see following change log #1. Based on the file 2020-01-02-ProposalForLatinScriptRootZoneLGR.docx in the dropbox, I have merged Appendix D homework submitted by Meikal, Hazzem, Bill. Also move over all editorial reviews in Bill’s version to the latest file. Please see changes log below. The latest file is attached, 2020-01-02-ProposalForLatinScriptRootZoneLGR-PK2.docx. I encountered problem uploading to dropbox, I would have to ask Mirjana to kindly upload the file to dropbox. Regards, Pitinan ### Change log #### Source of change: Meikal’s green highlight file (MM-2019-12-27-New version of revision of Proposal from Dec 18 with all changes in Green for MT.docx) 1. In table “Table D.3. Solution excluding 00DF from the Latin script repertoire“, added last sentence in the table including the footnote. Source of change: Meikal’s email on 28 December 2019 to Mirjana (2019-12-15-Appendix D Homework MM.docx) 2. D.1.14, Merged 3. D.1.9, updated screen captures and finding 4. D.4.4, updated screen captures and finding 5. D.4.11, added screen captures and finding 6. D.4.16, added screen captures and finding (D.4.15 in Meikal’s file) 7. D.4.20, added screen captures and finding (D.4.20 in Meikal’s file) Source of change: Hazzem’s email on 30 December 2019 to Latin GP mailing list (Appendix D Tasks - HH.docx) 8. D.1.7, updated the screen capture 9. D.3.10, added screen captures for Sequence ďɗ , åả, ůủ, and finding 10. D.4.6, updated screen captures for ớ and ứ 11. D.4.14, added screen captures for ấaâá, ếeêé, ốoôó, and finding 12. D.4.18, added screen captures for ỡoõơ, ữuũư, and finding 13. D.4.19, added screen captures for ọ̀oòọ, and finding Source of change: Bill’s email on 30 December 2019 to Latin GP mailing list (BJ - 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR v2.docx) 14. D.2.2, added the screen captures and finding 15. D.3.12, added this new section 16. D.4.12, added the screen capture and finding 17. D.4.17, added the screen capture and finding 18. Added section 6.3.5 - 6.3.7 19. Move over all editing From: Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> Date: Saturday, December 28, 2019 at 05:53 To: Latin GP <latingp(a)icann.org> Cc: Pitinan Kooarmornpatana <pitinan.koo(a)icann.org>, Sarmad Hussain <sarmad.hussain(a)icann.org> Subject: [Ext] Status of the Report Dear GP members, Dear Pitinan, Dear Sarmad, I have tried to incorporate following changes to 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR [dropbox.com] Bill’s contribution sent in an e-mail on Dec 13th BJ - 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR [dropbox.com] Then I incorporated manually changes from 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR-REV MM 2019-12-18-merged with Google Docs and repaired [dropbox.com] sent by Meikal Today Meikal sent the same file as previous (MM-2019-12-27-New version of revision of Proposal from Dec 18 with all changes in Green for MT) [dropbox.com] where changes which should be incorporated in the report are marked green. I hope that Pitinan could check if I have inserted all important changes in our new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] I have added my last contribution for Appendix D in our new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] In the new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] TBDs comments in the text, which are done, have been removed. Pitinan and Sarmad have offered their help for future maintenance of the Report. I want to thank them for their offer. Pitinan, please try to do following with current version of the Report ((2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] Check if I have inserted all changes which Meikal has marked in green in his contribution (MM-2019-12-27-New version of revision of Proposal from Dec 18 with all changes in Green for MT) [dropbox.com] . Add Meikal’s Appendix D contribution from file (2019-12-15-Appendix D Homework MM) We shall discuss how to proceed with changes of the Report during our next call. Best Regards Mirjana

1 0

Re: [Latingp] [Ext] Status of the Report
by Pitinan Kooarmornpatana Jan. 2, 2020

Jan. 2, 2020

Dear Mirjana, and all. I have checked all the changes by Meikal, there is only one missing sentence, please see following change log #1. Based on the file 2020-01-02-ProposalForLatinScriptRootZoneLGR.docx in the dropbox, I have merged Appendix D homework submitted by Meikal, Hazzem, Bill. Also move over all editorial reviews in Bill’s version to the latest file. Please see changes log below. The latest file is attached, 2020-01-02-ProposalForLatinScriptRootZoneLGR-PK2.docx. I encountered problem uploading to dropbox, I would have to ask Mirjana to kindly upload the file to dropbox. Regards, Pitinan ### Change log #### Source of change: Meikal’s green highlight file (MM-2019-12-27-New version of revision of Proposal from Dec 18 with all changes in Green for MT.docx) 1. In table “Table D.3. Solution excluding 00DF from the Latin script repertoire“, added last sentence in the table including the footnote. Source of change: Meikal’s email on 28 December 2019 to Mirjana (2019-12-15-Appendix D Homework MM.docx) 2. D.1.14, Merged 3. D.1.9, updated screen captures and finding 4. D.4.4, updated screen captures and finding 5. D.4.11, added screen captures and finding 6. D.4.16, added screen captures and finding (D.4.15 in Meikal’s file) 7. D.4.20, added screen captures and finding (D.4.20 in Meikal’s file) Source of change: Hazzem’s email on 30 December 2019 to Latin GP mailing list (Appendix D Tasks - HH.docx) 8. D.1.7, updated the screen capture 9. D.3.10, added screen captures for Sequence ďɗ , åả, ůủ, and finding 10. D.4.6, updated screen captures for ớ and ứ 11. D.4.14, added screen captures for ấaâá, ếeêé, ốoôó, and finding 12. D.4.18, added screen captures for ỡoõơ, ữuũư, and finding 13. D.4.19, added screen captures for ọ̀oòọ, and finding Source of change: Bill’s email on 30 December 2019 to Latin GP mailing list (BJ - 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR v2.docx) 14. D.2.2, added the screen captures and finding 15. D.3.12, added this new section 16. D.4.12, added the screen capture and finding 17. D.4.17, added the screen capture and finding 18. Added section 6.3.5 - 6.3.7 19. Move over all editing From: Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> Date: Saturday, December 28, 2019 at 05:53 To: Latin GP <latingp(a)icann.org> Cc: Pitinan Kooarmornpatana <pitinan.koo(a)icann.org>, Sarmad Hussain <sarmad.hussain(a)icann.org> Subject: [Ext] Status of the Report Dear GP members, Dear Pitinan, Dear Sarmad, I have tried to incorporate following changes to 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR [dropbox.com] Bill’s contribution sent in an e-mail on Dec 13th BJ - 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR [dropbox.com] Then I incorporated manually changes from 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR-REV MM 2019-12-18-merged with Google Docs and repaired [dropbox.com] sent by Meikal Today Meikal sent the same file as previous (MM-2019-12-27-New version of revision of Proposal from Dec 18 with all changes in Green for MT) [dropbox.com] where changes which should be incorporated in the report are marked green. I hope that Pitinan could check if I have inserted all important changes in our new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] I have added my last contribution for Appendix D in our new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] In the new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] TBDs comments in the text, which are done, have been removed. Pitinan and Sarmad have offered their help for future maintenance of the Report. I want to thank them for their offer. Pitinan, please try to do following with current version of the Report ((2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] Check if I have inserted all changes which Meikal has marked in green in his contribution (MM-2019-12-27-New version of revision of Proposal from Dec 18 with all changes in Green for MT) [dropbox.com] . Add Meikal’s Appendix D contribution from file (2019-12-15-Appendix D Homework MM) We shall discuss how to proceed with changes of the Report during our next call. Best Regards Mirjana

1 0

AGENDA for the GP call on January the 2nd 2020, 16:00UTC
by Mirjana Tasić Jan. 1, 2020

Jan. 1, 2020

Dear GP members. Please find enclosed the Agenda proposal for our next telephone conference. As I have been informed by Pitinan, who is on holiday, there is the possibility to have the new version of the Report before the call. The new version wii be in our Dropbox folder. Any comments are welcome. Regards Mirjana ___________________________________________ AGENDA for the GP call on January the 2nd 2020, 16:00UTC 1. Roll call 2. How to proceed with editing of the Report? 3. How to proceed with In script variant analysis * Bill’s excel table<https://docs.google.com/spreadsheets/d/19pjUuhNwDcxHGKJq-7R_LmkZTrobTmQG/ed…> * Appendix D In-script Analysis competed in the last version of the Report * 2019-12-12-TBD-ReportV5-VariantAnalysis<https://www.dropbox.com/s/hh5e7jh8rdrkixg/2019-12-12-TBD-ReportV5-VariantAn…> * 2019-12-20-Partial IP Response to Latin LGR Update-v1.1<https://www.dropbox.com/s/0ogf4vmmut968qn/2019-12-20-Partial%20IP%20Respons…> * Cross-Script-Talking-Points-v2<https://www.dropbox.com/s/62rkjkb6slob3g0/Cross-Script-Talking-Points-v2.do…> 4. Next meeting proposal January 9th 2020, , 16:00UTC 5. AOB

1 0

Summary of Latin GP Meeting on 19 December 2019
by Pitinan Kooarmornpatana Jan. 1, 2020

Jan. 1, 2020

Dear Latin GP members, Please find attached the summary of the Latin GP meeting on 19 December 2019. Please let us know if you would like to suggest any edits or additions Action Items S. No.Action ItemsOwner 1Reallocate the task list for Appendix D MT 2Conduct and finalize the Appendix D tasks as assignedBJ, HH, MM, MT The recording for this meeting and the note are posted at Latin GP wiki page at https://community.icann.org/display/croscomlgrprocedure/Latin+GP. Regards, Pitinan

1 0

Task distribution for Appendix D
by Mirjana Tasić Dec. 29, 2019

Dec. 29, 2019

Dear GP members, Here is task distribution for Appendix D. The same file could be found in our DROPBOX folder 2019-12-05-Report<https://www.dropbox.com/sh/zfkwsxg3gfk8sv0/AAC3Ts7KPbF76l7l2D4-iWzsa?dl=0> Please do it ASAP. Please send your contributions to the list as word files, Sarmad, Pitinan or me will put your contributions in the Report. Report file is too large to use it for this updates by everyone. When all texts would be in the Report, I hope Bill will find some time to check the language. Regards Mirjana

3 3

Re: [Latingp] [Ext] Status of the Report
by Pitinan Kooarmornpatana Dec. 27, 2019

Dec. 27, 2019

Dear Mirjana, and All, Sure, I’ll check the report as instructed. Happy holidays to you all. Talk to you in 2020! Regards, Pitinan From: Mirjana Tasić <Mirjana.Tasic(a)rnids.rs> Date: Saturday, December 28, 2019 at 05:53 To: Latin GP <latingp(a)icann.org> Cc: Pitinan Kooarmornpatana <pitinan.koo(a)icann.org>, Sarmad Hussain <sarmad.hussain(a)icann.org> Subject: [Ext] Status of the Report Dear GP members, Dear Pitinan, Dear Sarmad, I have tried to incorporate following changes to 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR [dropbox.com] Bill’s contribution sent in an e-mail on Dec 13th BJ - 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR [dropbox.com] Then I incorporated manually changes from 2019-12-05-IP-Proposal for a Latin Script Root Zone LGR-REV MM 2019-12-18-merged with Google Docs and repaired [dropbox.com] sent by Meikal Today Meikal sent the same file as previous (MM-2019-12-27-New version of revision of Proposal from Dec 18 with all changes in Green for MT) [dropbox.com] where changes which should be incorporated in the report are marked green. I hope that Pitinan could check if I have inserted all important changes in our new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] I have added my last contribution for Appendix D in our new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] In the new Report file (2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] TBDs comments in the text, which are done, have been removed. Pitinan and Sarmad have offered their help for future maintenance of the Report. I want to thank them for their offer. Pitinan, please try to do following with current version of the Report ((2020-01-02-ProposalForLatinScriptRootZoneLGR [dropbox.com] Check if I have inserted all changes which Meikal has marked in green in his contribution (MM-2019-12-27-New version of revision of Proposal from Dec 18 with all changes in Green for MT) [dropbox.com] . Add Meikal’s Appendix D contribution from file (2019-12-15-Appendix D Homework MM) We shall discuss how to proceed with changes of the Report during our next call. Best Regards Mirjana

1 0