Dear GP members, I have worked today on IP comments to our Proposal. https://docs.google.com/document/d/1-b-lpjzhH37Za6-cU0GS09rJ0EnfrTEhBuXES0z5... I have enlightened some parts of text for consideration. Mats has promised to look on 1.2.2 if it could be more acceptable to IP, or we shall remove it. It will be good if Meikal could help Mats with this comment I have updated information in tables 2.1 and 2.2 about new members of GP. I am asking now new members: Bakian, Elvin, Fiammetta, Nebiye and Violet to add relevant information about themselves to the same tables 2.1 and 2.2. I also would ask Sarmad to share their CVs with me, so I can put relevant information in the tables 2.1 and 2.2. I have changed working plan trying to encompass IP comments. Sarmad helped me a lot with this task, thank you Sarmad. GP needs volunteer to check our Latin part of MSR-2 with attestation table it seems that some code points are missing. I would ask everyone to think about it. https://docs.google.com/spreadsheets/d/1fFe-uo5Gbh6nxf3c8LIoP_UvOpGN9lH-8RoP... There should be about 326 code points with diacritics included. I want you all to read the new proposal, to comment it and give suggestions, so we can send another version of the proposal to IP after next conference call. Regards Mirjana
Hi Mirjana, hi all, thank you very much for the work you already did.
GP needs volunteer to check our Latin part of MSR-2 with attestation table it seems that some code points are missing. I would ask everyone to think about it.
I started to compare our list of characters as specified in our proposal with the list of characters defined in MSR-2 (see https://www.icann.org/en/system/files/files/msr-2-wle-rules-13apr15-en.xml). Our table contains a lot of characters not from MSR-2. For example, we write that U+0080 - U+00FF would be included. However, only U+00DF - U+00F6 U+00F8 - U+00FF is included. Similarly with the next section, we say Latin Extended-A U+0100 – U+017F would be included, whereas in MSR-2 only U+0101 U+0103 ... (every second character) U+0137 U+013A U+013C U+013E U+0142 U+0144 U+0146 U+0148 U+014B U+014D U+014F U+0151 U+0153 ... (every second character) U+0177 U+017A U+017C U+017E is included. The good thing is that our list of characters LatinPart-MSR2-Attestation.V6 (https://docs.google.com/spreadsheets/d/1fFe-uo5Gbh6nxf3c8LIoP_UvOpGN9lH-8RoP...) contains exactly the list of characters from MSR-2 ... plus the ones we added in our first run of language processing. So I guess we only have to adjust the table in our proposal document. Best regards, 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@knipp.de Software Development E-mail: Michael.Bauland@knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp
Thanks! Do we have to worry about the sound? On Fri, Apr 7, 2017 at 4:59 PM, Michael Bauland <Michael.Bauland@knipp.de> wrote:
Hi Mirjana, hi all,
thank you very much for the work you already did.
GP needs volunteer to check our Latin part of MSR-2 with attestation table it seems that some code points are missing. I would ask everyone to think about it.
I started to compare our list of characters as specified in our proposal with the list of characters defined in MSR-2 (see https://www.icann.org/en/system/files/files/msr-2-wle-rules-13apr15-en.xml ).
Our table contains a lot of characters not from MSR-2. For example, we write that U+0080 - U+00FF would be included. However, only U+00DF - U+00F6 U+00F8 - U+00FF is included.
Similarly with the next section, we say Latin Extended-A U+0100 – U+017F would be included, whereas in MSR-2 only U+0101 U+0103 ... (every second character) U+0137 U+013A U+013C U+013E U+0142 U+0144 U+0146 U+0148 U+014B U+014D U+014F U+0151 U+0153 ... (every second character) U+0177 U+017A U+017C U+017E is included.
The good thing is that our list of characters LatinPart-MSR2-Attestation.V6 (https://docs.google.com/spreadsheets/d/1fFe-uo5Gbh6nxf3c8LIoP_UvOpGN9lH- 8RoPXAdeq8c) contains exactly the list of characters from MSR-2 ... plus the ones we added in our first run of language processing.
So I guess we only have to adjust the table in our proposal document.
Best regards,
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@knipp.de Software Development E-mail: Michael.Bauland@knipp.de
Register Court: Amtsgericht Dortmund, HRB 13728
Chief Executive Officers: Dietmar Knipp, Elmar Knipp _______________________________________________ Latingp mailing list Latingp@icann.org https://mm.icann.org/mailman/listinfo/latingp
participants (3)
-
Michael Bauland -
Mirjana Tasić -
Textual Solutions