[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Java/Unicode brain damage

• From: Benjamin Franz <snowhare@n...>
• To: xml-dev@l...
• Date: Thu, 26 Jul 2001 10:14:36 -0700 (PDT)

On Thu, 26 Jul 2001, Miles Sabin wrote:

> I wrote,
> > Duane Nickull wrote,
> > > Is anyone aware of Sun or MS working on classes to rectify this?
> >
> > Umm ... _yes_, as I said before.
> 
> I'll try reading the question next time. I'm not aware of anyone at
> Sun working on classes directly representing Unicode characters
> rather than UTF-16 units.

I'm being dense today. When you say 'UTF-16 units' do you mean that in
Java a single character in the surrogate ranges may consist of (correctly
IMHO) a _complete_ 32-bit surrogate pair or (dain bramagedly) of the
individual 'halfs' of the pair (thus making a single character into two
individual 'units' of 16-bits each)? If the latter, the Java's handling of
Unicode is broken-as-designed and must be fixed (most likely via
deprecation of the existing String in favor of a completely new string
type for the sake of backwards compatibility with already deployed apps).

-- 
Benjamin Franz

  Programs must be written for people to read, and only 
  incidentally for machines to execute.
                             ---Abelson and Sussman

• Follow-Ups:
  • RE: Java/Unicode brain damage
    • From: Elliotte Rusty Harold <elharo@m...>
  • RE: Java/Unicode brain damage
    • From: Miles Sabin <msabin@i...>

• References:
  • RE: Java/Unicode brain damage
    • From: Miles Sabin <msabin@i...>

• Prev by Date: Element Order significance in XML
• Next by Date: Re: Element Order significance in XML
• Previous by thread: RE: Java/Unicode brain damage
• Next by thread: RE: Java/Unicode brain damage
• Index(es):
  • Date
  • Thread