• From: David Megginson <david@m...>
• To: xml-dev@i...
• Date: 04 Jan 2000 09:02:28 -0500

roddey@u... writes:

> If anything, it should go the other way. Unicode should be the core
> API, and there should be helper API to allow the use of local code
> page chars where necessary. Everything should be set up to optimize
> use of the Unicode API, with local code page use paying the price,
> since Unicode is the more desireable format.

No one's disagreeing with the use of Unicode; we're talking about
which character encoding we'll use to represent it.  You can represent
Unicode in variable-width 8-bit or 16-bit encodings or in fixed-width
32-bit encodings.

Note that Java uses UTF-16, which isn't quite fixed-width, though no
one really notices.


All the best,


David

-- 
David Megginson                 david@m...
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: Unicode confusion
    • From: "Peter S. Housel" <housel@h...>
  • Re: Unicode confusion
    • From: David Brownell <david-b@p...>

• References:
  • No Subject
    • From: roddey@u...

• Prev by Date: RE: SAX2: Parser interface
• Next by Date: Re: sax2: cdata, characters and ignorable whitespace
• Previous by thread: No Subject
• Next by thread: Re: Unicode confusion
• Index(es):
  • Date
  • Thread