August 2018 - Latingp - lists.icann.org

AGENDA for the GP call on August the 16th, 2018, 16:00UTC
by Mirjana Tasić Aug. 13, 2018

Aug. 13, 2018

Dear GP members. Please find enclosed the Agenda proposal for our next telephone conference. Regards Mirjana AGENDA for the GP call on August the 16th, 2018, 16:00UTC 1. Roll call 2. IP comments on repertoire - final discussion * Document with list of tasks to be fulfilled, and some comments https://docs.google.com/document/d/1DhK_YyksaKbNtJ-vN_Q4gsucIpCUt80o2b01Ecc… * New version of the Report with almost all comments from IP resolved https://docs.google.com/document/d/1rXd6ffnbD2BQa3HRvtJcNJDqZ58vaCPr5jzj47S… 1. Latin/Cyrillic cross-script Variants finalization -STATUS 1. Finalization of the Report with Repertoire and Variants * Finalization of the Repertoire * Checking the final Repertoire * Finalization of all variants table * Updating references * Production of test label file 2. Next telephone conference August the 30th 3. AOB

1 0

Variants Meetings
by Bill Jouris Aug. 9, 2018

Aug. 9, 2018

I have a small confusion. Mirjana has made it very clear that she would like us to have a draft on Variants ready by the end of September. And yet, we are currently only meeting every second week, rather than every week. Why the leisurely pace? Bill Jouris Inside Products bill.jouris(a)insidethestack.com 831-659-8360 925-855-9512 (direct)

2 1

[lgr] Fwd: [Ext] Fwd: ICANN News Alert -- Proposals for Kannada, Oriya and Telugu Scripts' Root Zone Label Generation Rules
by Pitinan Kooarmornpatana Aug. 9, 2018

Aug. 9, 2018

Dear All, We are pleased to announce that the Neo-Brahmi GP has finalized and published Root Zone LGR proposals for three scripts: Kannada, Telugu and Oriya. See below for further details (see the complete list of proposals published here<https://www.icann.org/resources/pages/lgr-proposals-2015-12-01-en>). We look forward to the comments and feedback from the community. Regards, Sarmad [ICANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2018-08-08-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Proposals for Kannada, Oriya and Telugu Scripts' Root Zone Label Generation Rules 8 August 2018 Open Date: 8 August 2018 Close Date: 20 September 2018 Originating Organization: Global Domains Division Categories/Tags: Top-Level Domains Brief Overview: The Neo-Brahmi Script Generation Panel (NBGP) was formed by nine communities that use scripts derived from the Brahmi script. NBGP is developing Root Zone Label Generation Rules (LGR) for Bengali, Devanagari, Gujarati, Gurmukhi, Kannada, Malayalam, Oriya, Tamil and Telugu scripts. The GP is publishing the proposals for the LGRs of these nine scripts in three sets, releasing proposals for the scripts which share cross-script variant code points together to the extent possible. The first set is already undergoing public comment and the second set, being released now, includes the following proposals: (1) Proposal for the Kannada Script Label Generation Rules for the Root Zone, (2) Proposal for the Oriya Script Label Generation Rules for the Root Zone, and (3) Proposal for the Telugu Script Label Generation Rules for the Root Zone. As per the LGR Procedure [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>, these proposals are being posted for public comments to allow those who have not participated in the NBGP to make their views known. Based on the feedback, the NBGP will finalize each proposal for its evaluation and integration into the Label Generation Rules for the Root Zone. Link: https://www.icann.org/public-comments/kannada-oriya-telugu-lgr-2018-08-08-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

Variants for LATIN SMALL LETTER U WITH DOT BELOW and friends
by Mats Dufberg Aug. 3, 2018

Aug. 3, 2018

On the conference call last night I was asked to create one email on LATIN SMALL LETTER U WITH DOT BELOW and friends. In this email three code points are considered: * U+045F CYRILLIC SMALL LETTER DZHE * U+1EF1 LATIN SMALL LETTER U WITH HORN AND DOT BELOW * U+1EE5 LATIN SMALL LETTER U WITH DOT BELOW 1. In the Latin-Cyrillic variant material, a comparison is done between U+045F and U+1EF1. As I have noted U+1EE5 is even closer to U+045F, but no comparison has been done between U+045F and U+1EE5, which I now propose should be done. 2. If the workgroup decides that both comparisons should result in between-script variant pairs, then as a consequence U+1EE5 and U+1EF1 must constitute a within-script variant pair. First displayed as text in the mail: 1EF1 045F 1EE5 Times: ự џ ụ Helvetica: ự џ ụ Courier new: ự џ ụ Here as a picture: [cid:image001.png@01D42803.2604AAC0] Yours, Mats --- Mats Dufberg DNS Specialist, IIS Mobile: +46 73 065 3899 https://www.iis.se/en/ -----Original Message----- From: Latingp <latingp-bounces(a)icann.org> on behalf of ICANN Latin GP <latingp(a)icann.org> Reply-To: "Tan Tanaka, Dennis" <dtantanaka(a)verisign.com> Date: Monday, 30 July 2018 at 04:57 To: "Michael.Bauland(a)knipp.de" <Michael.Bauland(a)knipp.de>, ICANN Latin GP <latingp(a)icann.org> Subject: Re: [Latingp] Latin-Cyrillic cross-script analysis Latin GP, Based on Michael's and Bill's input I have resolved all the pending cases. These are highlighted as <green>include</green> or <red>excluded</red> in each of the sets. Review the comments for context as well. Please review the revised doc and provide any other comments you may have. Thanks, Dennis On 7/27/18, 11:30 AM, "Latingp on behalf of Michael Bauland" <latingp-bounces(a)icann.org on behalf of Michael.Bauland(a)knipp.de> wrote: Hi all, On 26.07.2018 21:12, Bill Jouris wrote: > I have reviewed these. In several cases, I believe it is possible to > resolve the issue using the same principle: > When both inspectors have the same rating for the highest ranked font, > and the only difference is between fonts, there seems no reason to look > further. Just take the agreed highest rating (for example 2) and move on. I agree with Bill. We decided to look at several fonts in order to find more cases for possible variants (not to find less cases). Therefore it makes sense to always take the rating from the highest ranked font. In case both inspectors agree, there is nothing more to do. > I also noticed a couple of cases where the first inspector had a rating > of 5 (i.e. no candidate found) while the second inspector had something > else. Perhaps the first inspector could go back and consider the > candidate which, apparently, arose after his initial inspection. Even > if that results in a rating of 4 (different), it would at least give us > someplace to start discussion. Done. Those were my cases and I changed my original 5 to the rating referring to the newly found candidate. Furthermore I added my vote to the occasions were first and second inspector disagreed (and Bill's suggestion from above does not work). If the others could do the same, we could probably apply some majority vote. Have a nice weekend Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: Michael.Bauland(a)knipp.de Software Development E-mail: Michael.Bauland(a)knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp _______________________________________________ Latingp mailing list Latingp(a)icann.org https://mm.icann.org/mailman/listinfo/latingp _______________________________________________ Latingp mailing list Latingp(a)icann.org https://mm.icann.org/mailman/listinfo/latingp

1 0

[lgr] FW: ICANN News Alert -- Study on Technical Use of Root Zone Label Generation Rules
by Sarmad Hussain Aug. 3, 2018

Aug. 3, 2018

Dear All, The scope of an ongoing study on technical use of RZ-LGR has been published for public comment. We look forward to your input on the proposed scope. See below for further details. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2018-08-02-en [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> _____ Study on Technical Use of Root Zone Label Generation Rules 2 August 2018 Open Date: 2 August 2018 Close Date: 11 September 2018 Originating Organization: Global Domains Division Categories/Tags: Top-Level Domains Brief Overview: Second version of the Root Zone Label Generation Rules (RZ-LGR-2) was released in August 2017, integrating six script proposals, as other LGR script proposals are being finalized. The Root Zone Label Generation Rules Study Group (RZ-LGR-SG) has been constituted to study and make recommendations for the technical use of RZ-LGR in a harmonized way across Internationalized Domain Name (IDN) Top-Level Domains (TLDs). RZ-LGR-SG has identified its scope of work [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 128 KB], which is being shared with the community. The SG seeks feedback from the community on whether the questions identified are all relevant for this study and whether there are any other issues it should also consider. RZ-LGR-SG will take into account the community input to finalize the scope of its work, develop the related recommendations and share these recommendations with the community before finalization. Link: https://www.icann.org/public-comments/technical-rz-lgr-2018-08-02-en [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> _______________________________________________ lgr mailing list lgr(a)icann.org https://mm.icann.org/mailman/listinfo/lgr

1 0

Latin-Cyrillic cross-script analysis
by Tan Tanaka, Dennis Aug. 2, 2018

Aug. 2, 2018

Latin GP, As a follow up to our meeting last week, here is the revised document https://docs.google.com/document/d/1Ontc-amdQ_dFCRCc9oHBvotjwIhYc8xEM1OBn5y…. However, there are still 9 cases that need to be resolve. These are the cases where there is a mixed of visual scores. Please use the comment boxes to propose a method for resolution, that is consistent with our inclusion principles. While we solve for the Latin/Cyrillic cases I will start looking at the Greek and Armenian worksheets and apply the same framework to determine inclusion/exclusion of variant candidates. Best, Dennis

5 6

[Update agenda] Latin GP Meeting
by Pitinan Kooarmornpatana Aug. 1, 2018

Aug. 1, 2018

Dear Latin GP members , Please find the agenda for Latin GP meeting on Thursday, August the 2nd, 2018, 16:00UTC UPDATED AGENDA for the GP call on August the 2nd, 2018, 16:00UTC 1. Roll call 2. Face to face meeting in September or October- final dates 3. IP comments on repertoire – discussion • Working table https://docs.google.com/document/d/1ucbOomIbJys4l4bUQyKuyrg8bP3QXFdEngxeA0d… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> • Table with code points which should be included or excluded as proposed by IP https://docs.google.com/document/d/10j6CT7j3QbVzJo_wLZ9uk4Gqx5A6sX0oxksiRIJ… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 4. Latin/Cyrillic cross-script Variants finalization https://docs.google.com/document/d/1Ontc-amdQ_dFCRCc9oHBvotjwIhYc8xEM1OBn5y… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 5. Finalization of Report with Repertoire and Variants * Finalization of the Repertoire * Checking the final Repertoire * Finalization of all variants table * Updating the references as requested by IP (Need full citations, not just URLs. Author /Org, Site name, Page name/Page title, Date published /or accessed, URL) * Ref (UCD) IP says: For UCD, the “latest” link is fine – however, you do need to give the date accessed as it will tell which version that link was pointing to – alternatively use a versioned link, and then you don’t need the date accessed, because Unicode keeps each version “frozen” once published * Production of test label file 6. Next telephone conference August the 16th , 16:00UTC 7. 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

UPDATED AGENDA for the GP call on August the 2nd, 2018, 16:00UTC
by Mirjana Tasić Aug. 1, 2018

Aug. 1, 2018

Dear GP members. Please find enclosed the UPDATED Agenda proposal for our next telephone conference. Regards Mirjana UPDATED AGENDA for the GP call on August the 2nd, 2018, 16:00UTC 1. Roll call 2. Face to face meeting in September or October- final dates 3. IP comments on repertoire – discussion * Working table https://docs.google.com/document/d/1ucbOomIbJys4l4bUQyKuyrg8bP3QXFdEngxeA0d… * Table with code points which should be included or excluded as proposed by IP https://docs.google.com/document/d/10j6CT7j3QbVzJo_wLZ9uk4Gqx5A6sX0oxksiRIJ… 1. Latin/Cyrillic cross-script Variants finalization https://docs.google.com/document/d/1Ontc-amdQ_dFCRCc9oHBvotjwIhYc8xEM1OBn5y… 1. Finalization of Report with Repertoire and Variants * Finalization of the Repertoire * Checking the final Repertoire * Finalization of all variants table * Updating the references as requested by IP (Need full citations, not just URLs. Author /Org, Site name, Page name/Page title, Date published /or accessed, URL) * Ref (UCD) IP says: For UCD, the “latest” link is fine – however, you do need to give the date accessed as it will tell which version that link was pointing to – alternatively use a versioned link, and then you don’t need the date accessed, because Unicode keeps each version “frozen” once published * Production of test label file 2. Next telephone conference August the 16th , 16:00UTC 3. AOB

1 0