Altova Mailing List Archives

Re: [xml-dev] Re: [Sax-devel] SAX2 r2 ... last call!

From: David Brownell <david-b@-------.--->
To: "Simon St.Laurent" <simonstl@--------.--->
Date: 1/10/2002 10:37:00 PM
> I just suspect the point's worth making a little more strongly, as so
> many of us have been brainwashed to think Java char=Unicode character. 
> Surrogate pairs whacked me a lot harder over the head than I thought,
> and Java doesn't seem to take note.

True for most folk.  XML made me get my hands dirty with
I18N stuff, and that one took a while for me to grok.  I don't
think it'll be intuitive to most folk, who've rarely had to look
at such I18N issues.

> > Point is that anyone working at the "character" level MUST
> > NOT ASSUME that such characters consist only of a single
> > Java "char" value.  And that'd be true even if "char" were
> > to make an incompatible change, and acquire a few extra
> > bits at the left so that surrogates could in some cases be
> > eliminated.
> So could the paragraph above appear in the documentation somewhere?  I
> think that would take of all my concerns.

Yes, I was thinking of doing that.  After I imbibe the other thread
a bit more deeply, to make sure I pick up any other details.  That
should make it into the SAX2 r2 ContentHandler docs, and maybe
also LexicalHandler.comment() if I get ambitious.

- Dave


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.