>>A TeXSerializer with a transformer delivering TeX text is not possible.
>>You must have SAX events in a pipe, not text. So the only option is a >>TeXSerializer understanding XSL FO or a XML representation of TeX. But >>this would already be very near to FOP. >>Of course you can encapsulate the XSL FO to TeX transformation in the >>serializer and feed the result directly into a TeXProcessor, but I don't >>know whether this is a good approach. But it really doesn't seem to make >>sense, adding a further transformation step for using legacy processor >>as far you have to code the further transformation step. IMO it's better >>to support developers of XSL FO processors like FOP. Sometimes you can't avoid using "legacy" systems, and sometimes they are even good, but that is unrelated to the question of how a third party processor can be intregrated in a serializer. 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. If your original file is text, you should be able to use a textgenerator to wrap a <text> element around the entire file, so that the entire file is read as a series of character events, although its obviously useless as actual xml content at that point. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
