Hello Tom!

I think I am beginning to understand the process XSLT to PDF, and that's a marvelous feeling! And what makes me even more happy: I just sucessfully switched the XSLT processor to Saxon, and everything works fine now! This may seem like a little step to you, but to somebody being new to this topic, it seems like a great (and unexpected!) success. :)

Thomas Schraitle wrote:
  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).
Pity, there are no options at all. Only the path to an XSL processor (they seem to recommend FOP) - and an option whether you want FOP (0.93) compatibility mode or to make full use of the XSL-FO standard. (That was one more thing that irritated me: Why do they promise "compatibility with FOP" when I can't use the resulting XSLT with FOP? Now that I understood the two-step-process it's clearer: I think they speak about the resulting FO document which you can generate too.)

I now took a deeper look in the documentation and they say the arguments they pass to the FOP.bat are "-fo filename.fo -pdf fileame.pdf" - so the FO must've been build before this step.
The only other information about that I can get from the Altova FAQ:

Q: Are XSLT 2.0 and XPATH 2.0 supported in StyleVision® 2008?
A: As of StyleVision® 2008 XSLT 2.0 and XPATH 2.0 are both supported.

...ah well, built-in support, no FOP involved. To learn how exactly they are doing it, I think I would've to contact them, but now that everything runs fine with Saxon-B, there is no need to.

Thanks to you Tom, and thanks to everyone else who helped me here. Great mailing list!

Regards from a content
Tobias

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to