Excellent! Thanks for the info :) I will have to go back and see what exactly the article I read was refering to, but if I remember correctly they seemed to mention that support for the top level domains, specifically .com, .net, and .cn had not been implemented using the Mandarin character set.
Either way, obviously there are a lot of considerations that need to be allowed for when developing from an interanational perspective, something that should be part of the defaul process instead of the exception... of course, I say this mainly because this is really the first time I have put any real thought into this area, and obviously I need to put a lot more. Thanks again for clearing things up and providing the links! On 3/15/06, Stephane Bortzmeyer <[EMAIL PROTECTED]> wrote: > On Tue, Mar 14, 2006 at 10:36:36PM -0700, > M. David Peterson <[EMAIL PROTECTED]> wrote > a message of 43 lines which said: > > > As long as your character set for any given feed is properly set, it > > seems to me then all the information necessary to properly decode > > the email and URI (in which the work continues to integrate support > > for non-latin based languages, such as Mandarin, etc... > > Just to be pedantic, URIs (RFC 3986) are in pure US-ASCII. IRIs (RFC > 3987) are in Unicode and are accepted by Atom (so, Atom's URIs seem to > be actually IRIs). The standard says: > > # Unconstrained; it's not entirely clear how IRI fit into > # xsd:anyURI so let's not try to constrain it here > atomUri = text > > > if I understand things correctly, full support for Mandarin > > Chinese-based domains in not far off (speaking in terms of DNS > > support and such). > > It is quite old, RFC 3490 (issued three years ago and implemented even > before). > > > email adresses encoded as mentioned > > There is not yet any standard for Unicode email addresses (work is > going on, see the very recent IETF Working Group EAI > http://www.ietf.org/html.charters/eai-charter.html). > -- <M:D/> M. David Peterson http://www.xsltblog.com/
