addison at yahoo-inc.com
Thu May 3 17:01:12 CEST 2007
Michael Everson wrote:
>> RFC 4646 specifies that non-ASCII characters be represented using
>> these ugly hex NCRs. There are pros and cons to using UTF-8 for the
>> Registry, and even though I an a huge fan of UTF-8, there are valid
>> points to be made on both sides (i.e. many e-mail systems, even today,
>> mangle UTF-8). Again, this list is not empowered to disregard or
>> overturn what RFC 4646 says. We have had the debate in LTRU probably
>> three or four times now, and the hex NCRs appear likely to stay.
> Must they be represented using NCRs? Is that obligatory? Is ASCII
> fallback forbidden?
If you include non-ASCII characters, they must be NCRs. Of course, you
can use an ASCII transliteration to avoid them altogether. The RFC
doesn't require anything in particular about the content of a comment.
Globalization Architect -- Yahoo! Inc.
Internationalization is an architecture.
It is not a feature.
More information about the Ietf-languages