No subject

roddey at roddey at
Mon Jan 3 23:31:05 GMT 2000

>    SAXString(const char* p)
>    : basic_string<SAXChar>(p)
>    {
>    // do UTF-8 to UTF-16 decoding here
>    }
>and then:
>void DocumentHandler::startElement (
>     const SAXString& name, const AttributeList& atts)
>     if (name == SAXString("Paragraph")) ...

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.

Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
roddey at

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo at the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list