Announcement: SAX Java Implementation (pre-release)

Tyler Baker tyler at
Fri Apr 10 22:48:11 BST 1998

Lars Marius Garshol wrote:

> I've now done a Python translation of this and put it (also a
> pre-release) at
> <URL:>
> (SAX classes, some convenience classes, xmllib driver and an
> unfinished xmlproc driver.)
> The translation was very straightforward, with one exception:
> overloading. Unless there are protests I think I'll just leave the two
> extra parse methods and the extra exception constructor out of the
> Python translation altogether.
> Also, the distinction between the two new parse methods looks very
> Java-specific to me.

The idea of character streams is for supporting streams which already handle the
byte to UNICODE character translation for you.  I am not familiar with Python,
but I assume there must be some sort of 16 bit wide character set that is Unicode
compliant.  This I feel is all that David is trying to add to SAX, not something
Java specific.  Nevertheless, if a particular language has no Unicode support
whatsoever in the first place, then you are SOL for supporting XML in the first

Readers (or character streams) may have much more efficient byte to character
translation implementations than anything the parser could provide in the first

I think the addition of character streams to SAX is a very good thing.


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as:
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe 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