<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">What is the context of this discussion
of Latin characters?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Is it to discuss recommended practice
or to describe actual practice?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Actual practice is not easy to
determine, because even where Idntables were filed by registries
(in the IANA repository), they don't often provide the complete
story. (Other policies apply as well). Nevertheless, at least some
registries apply minimal restrictions.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">For the Root Zone, the Latin Generation
Panel is working on a proposed set of Label Generation Rules. It's
key features are:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">(1) precomposed letters are limited to
those in use in everyday modern orthographies</div>
<div class="moz-cite-prefix">(2) combining marks are limited to the
actual combinations used in the same orthographies</div>
<div class="moz-cite-prefix">(3) because NFC, there's no duplication
between (1) and (2).</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">(4) the sharp s is allowed, but made a
variant of "ss". <br>
Due to the fact that Swiss, when writing German will only use
"ss"; <br>
the variant is allocatable if "ß" is registered, allowing one
entity to control<br>
both variants. That takes care of issues around fall-back
use.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">(5) i with and without dot may be
defined as variants</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">(6) many cross-script variants are
defined to safely allow <br>
Greek, Cyrillic and Armenian labels to coexist with Latin
ones in the Root.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">(7) the Catalan middle dot is not
allowed. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">(8) Ducth ij and any other cases of
single code points for digraph letters are not allowed. <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Something like that approach could
serve as a basis for "best practice" prescriptions for other
zones, if that's something that is relevant in the UA context.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">However, the UASG would not seem the
appropriate venue to duplicate the full analysis of the Latin
script undertaken by the Latin Generation Panel. That panel spent
several years on this project and analyzed over 200 orthographies.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">A./</div>
<div class="moz-cite-prefix"><br>
PS: a public version of the proposed Latin Root Zone LGR is
expected early next year for those of you who would like to review
that document and its conclusions.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 11/24/2019 10:19 AM, Roberto Gaetano
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:D337B1A6-52B4-4F5C-A3CB-480366A7813C@hotmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
Dear Mark,</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
This brings another topic to my mind.</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
Just for curiosity, do you know what is the situation in the
code tables for the characters that in some languages that use
the “latin” script are the combination of two separate
characters - a bit like the "scharfes S” that you talk about?</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
I am thinking, for instance, about the “rr” or “ll” (that in
spanish are different from two consecutive “l” or “r”), or the
“ij” (that in dutch is not an “i” followed by a “j”, although it
is written that way).</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
Cheers,</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
Roberto</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
<br class="">
</div>
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 24.11.2019, at 04:22, Mark W. Datysgeld
<<a href="mailto:mark@governanceprimer.com" class=""
moz-do-not-send="true">mark@governanceprimer.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">Hello everyone,</p>
<p class="">I exchanged a few messages with Lars earlier
this year, and would like to present below some points
he raised that should be useful both for the IGF next
week and looking towards ICANN meeting C next year,
being tailored towards German stakeholders. In my
view, we can aim to always try gathering such regional
insights moving forward to optimize our engagement.</p>
<br class="">
<p class=""><b class="">Special characters:</b> Eszett
(ß) and Umlaut (ü) have fallback options by default:</p>
<ul class="">
<li class="">Eszett becomes "ss".</li>
<li class="">Capital Eszett (ẞ) has only recently been
introduced officially to the language, meaning that
anything in capital letters used to be written using
"SS" even on the press.</li>
<li class="">Umlaut characters (ä, ö, ü) become "ae",
"oe", "ue".<br class="">
</li>
</ul>
<p class=""><br class="">
</p>
<p class=""><b class="">gTLDs</b></p>
<ul class="">
<li class="">Fallback: the popular cityTLD for "Köln"
is run under ".koeln" and ".cologne" to avoid the
Umlaut.</li>
<li class="">".berlin" is a popular gTLD and is in
active use for varied purposes, including local
businesses.</li>
<li class="">Other relevant gTLDs: ".hamburg",
".bayern", ".ruhr", ".nrw" and ".saarland".<br
class="">
</li>
</ul>
<p class=""><br class="">
</p>
<p class="">Hopefully this can help us engage better.
Safe journeys to all of those traveling to the IGF!</p>
<p class="">Regards,<br class="">
</p>
<pre class="moz-signature" cols="72">--
Mark W. Datysgeld from Governance Primer [<a class="moz-txt-link-abbreviated" href="http://www.markwd.website/" moz-do-not-send="true">www.markwd.website</a>]
In partnership with AR-TARC and the Brazilian Association of Software Companies (ABES)</pre>
</div>
<br class="">
_______________________________________________<br
class="">
By submitting your personal data, you consent to the
processing of your personal data for purposes of
subscribing to this mailing list accordance with the ICANN
Privacy Policy (<a
href="https://www.icann.org/privacy/policy" class=""
moz-do-not-send="true">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://www.icann.org/privacy/tos" class=""
moz-do-not-send="true">https://www.icann.org/privacy/tos</a>).
You can visit the Mailman link above to change your
membership status or configuration, including
unsubscribing, setting digest-style delivery or disabling
delivery altogether (e.g., for a vacation), and so on.</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
</blockquote>
<p><br>
</p>
</body>
</html>