[Latingp] Draft comments to Cyrillic GP
Mirjana.Tasic at rnids.rs
Sun Dec 3 17:06:35 UTC 2017
Thank you for your contribution. I shall wait two more days for any comment, and I shall send this document oh the 5th of December as our comment to Cyrillic GP.
I ask, again, other members to look at the document, and give their opinion on it.
From: Latingp <latingp-bounces at icann.org> on behalf of Latin GP <latingp at icann.org>
Reply-To: "Tan Tanaka, Dennis" <dtantanaka at verisign.com>
Date: Friday, December 1, 2017 at 17:59
To: Latin GP <latingp at icann.org>
Subject: Re: [Latingp] Draft comments to Cyrillic GP
As a follow-up, I looked up ‘030B’ in our draft repertoire in https://docs.google.com/spreadsheets/d/1Sj2moWEw4YFLFTcvsiRpjsQRyLZJ7SCnlF78OSYQg04/edit#gid=778535057 and didn’t find this code point. So, I’m inclined to remove the sequence 0079+030B from the variant set list, unless someone has a good reason to keep it.
From: Latingp <latingp-bounces at icann.org> on behalf of "Tan Tanaka, Dennis via Latingp" <latingp at icann.org>
Reply-To: Dennis Tan Tanaka <dtantanaka at verisign.com>
Date: Thursday, November 30, 2017 at 2:39 PM
To: Jean Paul NKURUNZIZA via Latingp <latingp at icann.org>
Subject: [EXTERNAL] [Latingp] Draft comments to Cyrillic GP
Please find below Google Docs link to the proposed draft. You have the rights to edit the document.
Bill, Michael, Mats and Meikal please weigh in as well.
There is a special case that depends on the Repertoire team’s input. The case of 0079+030B. The Variant team found that the said sequence is identical to the Cyrillic code point 04F3. However, such sequence 0079+030B does not normalize to a pre-composed form, so unless 030B is allowed to follow 0079, this variant set should be removed from the list.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Latingp