For Latin-based languages, your point is well taken. For non-latin, its all about character sets. 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... if I understand things correctly, full support for Mandarin Chinese-based domains in not far off (speaking in terms of DNS support and such).
Actually, the only reason for writing this response was to point out the fact that we are entering a world in which China will continue to play a dominant role in both our online and offline worlds, so beginning to learn as much as possible in terms of how to properly handle URI's and email adresses encoded as mentioned seems like it would be a pretty good idea. Couldnt hurt. :) On 3/14/06, Martin Duerst <[EMAIL PROTECTED]> wrote: > > At 08:42 06/03/15, David Powell wrote: > > > > > >Not sure if this is a known bug, but I just noticed that the RelaxNG > >grammar doesn't accept "atomCommonAttributes" (eg xml:lang) on the > >"atom:name" and "atom:uri" and "atom:email" elements used within > >Person constructs. > > For atom:uri and atom:email at least, not having xml:lang may > be seen as a feature. While these often contain pieces from one > language or another, they are not really in a language. > > Regards, Martin. > > -- <M:D/> M. David Peterson http://www.xsltblog.com/