[UA-discuss] Ideas for engagement with stakeholders in Germany
asmusf at ix.netcom.com
Sun Nov 24 20:52:21 UTC 2019
What is the context of this discussion of Latin characters?
Is it to discuss recommended practice or to describe actual practice?
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.
For the Root Zone, the Latin Generation Panel is working on a proposed
set of Label Generation Rules. It's key features are:
(1) precomposed letters are limited to those in use in everyday modern
(2) combining marks are limited to the actual combinations used in the
(3) because NFC, there's no duplication between (1) and (2).
(4) the sharp s is allowed, but made a variant of "ss".
Due to the fact that Swiss, when writing German will only use "ss";
the variant is allocatable if "ß" is registered, allowing one
entity to control
both variants. That takes care of issues around fall-back use.
(5) i with and without dot may be defined as variants
(6) many cross-script variants are defined to safely allow
Greek, Cyrillic and Armenian labels to coexist with Latin ones in
(7) the Catalan middle dot is not allowed.
(8) Ducth ij and any other cases of single code points for digraph
letters are not allowed.
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.
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
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.
On 11/24/2019 10:19 AM, Roberto Gaetano wrote:
> Dear Mark,
> This brings another topic to my mind.
> 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?
> 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).
>> On 24.11.2019, at 04:22, Mark W. Datysgeld <mark at governanceprimer.com
>> <mailto:mark at governanceprimer.com>> wrote:
>> Hello everyone,
>> 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.
>> *Special characters:* Eszett (ß) and Umlaut (ü) have fallback options
>> by default:
>> * Eszett becomes "ss".
>> * 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.
>> * Umlaut characters (ä, ö, ü) become "ae", "oe", "ue".
>> * Fallback: the popular cityTLD for "Köln" is run under ".koeln"
>> and ".cologne" to avoid the Umlaut.
>> * ".berlin" is a popular gTLD and is in active use for varied
>> purposes, including local businesses.
>> * Other relevant gTLDs: ".hamburg", ".bayern", ".ruhr", ".nrw" and
>> Hopefully this can help us engage better. Safe journeys to all of
>> those traveling to the IGF!
>> Mark W. Datysgeld from Governance Primer [www.markwd.website]
>> In partnership with AR-TARC and the Brazilian Association of Software Companies (ABES)
>> By submitting your personal data, you consent to the processing of
>> your personal data for purposes of subscribing to this mailing list
>> (https://www.icann.org/privacy/policy) and the website Terms of
>> Service (https://www.icann.org/privacy/tos). 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the UA-discuss