• To: Rick Jelliffe <ricko@a...>
• Subject: Re: XML 1.1 grinds to halt?
• From: Tim Bray <tbray@t...>
• Date: Tue, 29 Apr 2003 07:42:34 -0700
• Cc: XML Dev <xml-dev@l...>
• In-reply-to: <00b301c30e0f$e9912e10$4bc8a8c0@A...>
• References: <oproc7ephwezizxn@s...> <00b301c30e0f$e9912e10$4bc8a8c0@A...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3) Gecko/20030312

Rick Jelliffe wrote:

> Time is on XML 1.1's side:  even Java is only just reaching Unicode 3.2
> just as Unicode 4 is released. 

Really?  I just looked at a recent set of Java docs, and it's pretty 
clear that a Java char isn't really a character, it's a UTF-16 
codepoint, and the semantics of String are wrong for non-BMP characters, 
and that the attempt at UTF-8 support remains pretty laughably 
nonstandard and wrong.  I'd be *delighted* to hear that I'm looking at 
wrong/obsolete docs.  Pointers anyone? -Tim

• Follow-Ups:
  • Re: XML 1.1 grinds to halt?
    • From: John Cowan <cowan@m...>
  • Re: XML 1.1 grinds to halt?
    • From: "Rick Jelliffe" <ricko@a...>
  • Re: XML 1.1 grinds to halt?
    • From: Elliotte Rusty Harold <elharo@m...>
  • Re: XML 1.1 grinds to halt?
    • From: "Simon St.Laurent" <simonstl@s...>

• References:
  • XML 1.1 grinds to halt?
    • From: Mike Champion <mc@x...>
  • Re: XML 1.1 grinds to halt?
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: how to call two kinds of languages' extension function with Xalan parser?
• Next by Date: Re: XML 1.1 grinds to halt?
• Previous by thread: how to call two kinds of languages' extension function with Xalan parser?
• Next by thread: Re: XML 1.1 grinds to halt?
• Index(es):
  • Date
  • Thread