Hi Tobias, On Montag, 1. Oktober 2007, Tobias Wehrum wrote: > Thomas Schraitle wrote: > > This is definitly NOT XSLT 1.0. ;) > > > > For me, it smells like if you are applying a XSLT 2.0 stylesheet to > > an XSLT 1.0 processor. As far as I know, Xalan can only use XSLT 1.0, > > not XSLT 2.0. Maybe switch to Saxon 8? > > well, of course you are right: It isn't. It is listed in W3Cs "XQuery > 1.0 and XPath 2.0 Functions and Operators". > But since Altova StyleVision uses FOP to generate the PDF documents > (when you want to do this, you have to enter the path to the FOP.bat, > so I assume it uses it), I hoped that there is a way that I may do this > too.
I don't know Altova nor do I use it, so I cannot comment on it. :) > However after reading what you wrote, it seems likely that it uses > FOP only for "fo to pdf", and not Xalan for "xslt to fo". > Please correct me if my thoughts are wrong. I am not very familiar with all the Java stuff, so I can only make wild guesses. I might be wrong. Generally, from what I've saw it looks like your assumptions are correct. Normally your tool chain looks like this: XML ---[XSLT processor]---> FO ---[FOP]---> PDF FOP doesn't know and actually doesn't care if your FO file comes from an XSLT 1.0 or XSLT 2.0 transformation. It just renders your FO into a PDF. However, you can generate your PDF also in one step: XML --[FOP]--> PDF Internally, there are two steps but from a user perspective it looks like as one step. Maybe your Altova calls FOP in such a way? I would recommend to have a deeper look into your Altova configuration. You wrote, that you have to enter the path to the FOP.bat file. Probably you can find some options or the like. It would be also very interesting *how* Altova calls the XSLT transformation (if at all). Good luck, Tom -- Thomas Schraitle --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
