[Latingp] [Ext] new character to be included in MSR

[Sarmad Hussain]

Dear Michael,

A quick clarification question - would you want to forward the following email to the IP or share just the specific comments 1 and 2 ? 

Regards,
Sarmad

-----Original Message-----
From: Michael Bauland <Michael.Bauland at knipp.de> 
Sent: Monday, February 11, 2019 1:29 PM
To: Sarmad Hussain <sarmad.hussain at icann.org>
Cc: latingp at icann.org; Pitinan Kooarmornpatana <pitinan.koo at icann.org>
Subject: Re: [Ext] new character to be included in MSR

Dear Sarmad,

thank you for forwarding the reply from the IP. I would like to add the following two comments for the IP:

1. The section the IP refers to is about "Creating the Variant Rules", we just want to extend our repertoire, not define variants, but that's probably just a formality.

What I find much more important is:
2. The reasoning for the exclusion in Section B.3.4.2 is "because those context rules are not simple enough to be appropriate for the root zone."

I find this reasoning far too general. In case of the Middle Dot the context rules would state that it must be preceded and followed by a regular lowercase L (as stated in Appendix A.3 of RFC 5892). Whenever Catalan people use the middle dot, they *always* have it surrounded by an L. So the context rule would automatically be followed, without any Catalan even thinking about it. If that isn't simple enough, I don't know.

For Catalan people, not allowing the middle dot is similar as if you would tell English people, they may not use the "x" (or any other
letter) for root zone labels. You take away a regular letter for 10 million people.

Finally, let me add some argument from a native speaker:
Contrary to umlauts, or eszett, to cite examples of “IDNs” in a well-known language, there is no alternative for ela geminada (not only from a grammatical point of view, which also happens with diacritical accents or other “special” characters) but even not “visually” (as it happens with, say, é, and e which are not the same but are accepted to look very similar and practical equivalents in DNS.


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 at knipp.de
     Software Development        E-mail: Michael.Bauland at knipp.de

                                 Register Court:
                                 Amtsgericht Dortmund, HRB 13728

                                 Chief Executive Officers:
                                 Dietmar Knipp, Elmar Knipp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5026 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/latingp/attachments/20190211/cc113b4d/smime.p7s>