<div dir="ltr">Thanks! Do we have to worry about the sound?</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 7, 2017 at 4:59 PM, Michael Bauland <span dir="ltr"><<a href="mailto:Michael.Bauland@knipp.de" target="_blank">Michael.Bauland@knipp.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Mirjana, hi all,<br>
<br>
thank you very much for the work you already did.<br>
<span class=""><br>
<br>
> GP needs volunteer to check our Latin part of MSR-2 with attestation<br>
> table it seems that some code points are missing. I would ask everyone<br>
> to think about it.<br>
<br>
</span>I started to compare our list of characters as specified in our proposal<br>
with the list of characters defined in MSR-2 (see<br>
<a href="https://www.icann.org/en/system/files/files/msr-2-wle-rules-13apr15-en.xml" rel="noreferrer" target="_blank">https://www.icann.org/en/<wbr>system/files/files/msr-2-wle-<wbr>rules-13apr15-en.xml</a>).<br>
<br>
Our table contains a lot of characters not from MSR-2.<br>
For example, we write that<br>
U+0080 - U+00FF<br>
would be included. However, only<br>
U+00DF - U+00F6<br>
U+00F8 - U+00FF<br>
is included.<br>
<br>
Similarly with the next section, we say Latin Extended-A<br>
U+0100 – U+017F<br>
would be included, whereas in MSR-2 only<br>
U+0101<br>
U+0103<br>
... (every second character)<br>
U+0137<br>
U+013A<br>
U+013C<br>
U+013E<br>
U+0142<br>
U+0144<br>
U+0146<br>
U+0148<br>
U+014B<br>
U+014D<br>
U+014F<br>
U+0151<br>
U+0153<br>
... (every second character)<br>
U+0177<br>
U+017A<br>
U+017C<br>
U+017E<br>
is included.<br>
<br>
The good thing is that our list of characters<br>
LatinPart-MSR2-Attestation.V6<br>
(<a href="https://docs.google.com/spreadsheets/d/1fFe-uo5Gbh6nxf3c8LIoP_UvOpGN9lH-8RoPXAdeq8c" rel="noreferrer" target="_blank">https://docs.google.com/<wbr>spreadsheets/d/1fFe-<wbr>uo5Gbh6nxf3c8LIoP_UvOpGN9lH-<wbr>8RoPXAdeq8c</a>)<br>
contains exactly the list of characters from MSR-2 ... plus the ones we<br>
added in our first run of language processing.<br>
<br>
So I guess we only have to adjust the table in our proposal document.<br>
<br>
Best regards,<br>
<br>
Michael<br>
<br>
--<br>
______________________________<wbr>______________________________<wbr>________<br>
| |<br>
| knipp | Knipp Medien und Kommunikation GmbH<br>
------- Technologiepark<br>
Martin-Schmeisser-Weg 9<br>
44227 Dortmund<br>
Germany<br>
<br>
Dipl.-Informatiker Fon: <a href="tel:%2B49%20231%209703-0" value="+4923197030">+49 231 9703-0</a><br>
Fax: <a href="tel:%2B49%20231%209703-200" value="+492319703200">+49 231 9703-200</a><br>
Dr. Michael Bauland SIP: <a href="mailto:Michael.Bauland@knipp.de">Michael.Bauland@knipp.de</a><br>
Software Development E-mail: <a href="mailto:Michael.Bauland@knipp.de">Michael.Bauland@knipp.de</a><br>
<br>
Register Court:<br>
Amtsgericht Dortmund, HRB 13728<br>
<br>
Chief Executive Officers:<br>
Dietmar Knipp, Elmar Knipp<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
Latingp mailing list<br>
<a href="mailto:Latingp@icann.org">Latingp@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/latingp" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/latingp</a><br>
</div></div></blockquote></div><br></div>