Roger wrote: > > If your original file is XML and you have an xslt that > converts it into TEX > > text, the output from the xslt is passed as a series of > character sax > > events, so even though it is technically xml/sax events, > since there are no > > elements or attributes, you can easily treat it as a text > stream which can > > be fed by a serializer to an external processor if desired.
Joerg Heinicke wrote: > NO! Exactly this is not an option. We won't break the sitemap > contract > for having a specialized serializer. After every step in the > sitemap it > must be possible to get well-formed XML - and that's not > possible if you > have text as output of a transformer and as input for a serializer. > > As Bruno and me pointed out the TeXSerializer must be able to read an > XML representation of TeX. Only in the prefered solution he > has another > opinion than me. AFAIU the contract between pipeline components is that just SAX. These SAX events may represent a fragment of a document, with multiple root elements, or whatever. The pipeline processor certainly doesn't check that the SAX streams constitute well-formed XML documents. In any case - isn't TeX a text format? If so then a well-formed XML document like <TeX>blah blah blah ... </TeX> could be serialised to TeX by the TextSerializer, couldn't it? Con --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
