Esszett, Final Sigma, ZWJ and ZWNJ

[Vint Cerf]

LB,

not as I understand the UNICODE definition of the term.

v

Vint Cerf
Google
1818 Library Street, Suite 400
Reston, VA 20190
202-370-5637
vint at google.com




On Feb 21, 2009, at 6:12 PM, LB wrote:

> Are not cuneiforms also symbols?
> --
> LB
>
>
> 2009/2/21 Vint Cerf <vint at google.com>:
>> these are not permitted to be registered as they are symbols, not
>> letters/digits.
>>
>>
>>
>> Vint Cerf
>> Google
>> 1818 Library Street, Suite 400
>> Reston, VA 20190
>> 202-370-5637
>> vint at google.com
>>
>>
>>
>>
>> On Feb 21, 2009, at 4:59 PM, LB wrote:
>>
>>> this is a matter of user. I would register "$£€. tld". Are we sure
>>> that I will not have a problem, or these characters should not  
>>> they be
>>> protected, in case  "$" results  to "USD", "£" to "GBP", etc.
>>>
>>> Thank you.
>>> --
>>> LB
>>>
>>> 2009/2/21 Vint Cerf <vint at google.com>:
>>>>
>>>> Folks,
>>>>
>>>> My reading of the consensus is that the WG has discussed and  
>>>> generally
>>>> accepted that Esszett, Final Sigma, ZWJ and ZWNJ can be made  
>>>> PVALID.
>>>> For registries that formerly mapped Esszett or Final Sigma, the
>>>> solutions are:
>>>>
>>>> 1. block registration of Esszett and Final Sigma at the registry  
>>>> level
>>>> (in which case any former registration forms are still valid but  
>>>> will
>>>> not be found by entering the newly PVALID characters)
>>>>
>>>> 2. Bundle Esszett with "ss" and Final Sigma with lower case  
>>>> ("sigma")
>>>> (and do so retrospectively for all prior registrations of the  
>>>> mapped
>>>> forms).
>>>>
>>>> With regard to ZWJ and ZWNJ, these would be PVALID but  
>>>> constrained by
>>>> CONTEXTJ rules as to their valid usage.
>>>>
>>>> As I read the charter, the WG has the latitude to adopt these
>>>> recommendations.
>>>>
>>>> It has been pointed out that there are consequences of not mapping
>>>> characters per IDNA2003. One example relates to the appearance of,
>>>> e.g., Esszett in a URL. A side-effect of the mapping under  
>>>> IDNA2003 is
>>>> that the Esszett character would be converted to "ss" and this  
>>>> would
>>>> match a registration of a domain name that contained Esszett  
>>>> since the
>>>> registered form would have been mapped prior to registration into  
>>>> the
>>>> "ss" form. It seems beneficial to articulate to the best of our
>>>> ability such side-effects as an aid to users, software writers,
>>>> registries and registrars who may need to define policies for
>>>> registration limitations or adopt other compensating practices.
>>>>
>>>> Vint
>>>>
>>>>
>>>> Vint Cerf
>>>> Google
>>>> 1818 Library Street, Suite 400
>>>> Reston, VA 20190
>>>> 202-370-5637
>>>> vint at google.com
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Idna-update mailing list
>>>> Idna-update at alvestrand.no
>>>> http://www.alvestrand.no/mailman/listinfo/idna-update
>>>>