Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

I receive a different output in StyleVision® 2008 for “FO” (Formating Objects) than when I transform a file in XMLSpy® 2008 with Apache FOP or other FOP engines. Why?

0
Posted

I receive a different output in StyleVision® 2008 for “FO” (Formating Objects) than when I transform a file in XMLSpy® 2008 with Apache FOP or other FOP engines. Why?

0

The currently available version of the FOP processor from Apache implements only a subset of the XSL:FO standard. This subset often doesn’t include functionality which is required to implement the design in StyleVision® 2008. Even though we provide a special compatibility mode for the Apache FOP processor, it still works differently with a more complete implementation. It must be noted that there are different interpretations on how to implement the FO specification and therefore the output of one FO processor may differ from that of another.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123