Michael,
> > There are several implementations of SAX for C++,
>
> could you point me to them (URL) - and especialy the version you are
> using ?
The one I can recall now is
http://www.jezuk.demon.co.uk/SAX/index.html
As I said, Sablotron does not support SAX (so it does not need any of
these implementations). It does offer a streaming interface which is
similar to one component of the SAX interface.
> > I don't think that the result of an XSLT transformation typically needs
> > any postprocessing before being displayed as HTML: if you use
> > <xsl:output method='html'>, things line <br/> will be treated as the
> > browser expects.
>
> What about UTF8 to ISO-8859-1 conversion? This may be necessary as
> a last step in the chain.
No, you can use <xsl:output encoding='iso-8859-1'/>. (Not in the current
version of Sablotron, though.)
> Sax postprocessing gives more flexibility, perhaps it may become supported
> by a feature of the xsl:output method. SAX postprocessing could be loaded
> dynamicaly by using the QName feature of the xsl:output[@method], to
> produce UN/EDIFACT instead of HTML.
One is free to use a qualified name in the method attribute so this is
an option. You could use an extension element as well. But how do you
identify the SAX handler you want to receive the calls? Is its ID
hard-coded in the stylesheet?
Tom
