Details
-
Improvement
-
Resolution: Fixed
-
Major
-
8.4
-
None
-
Unknown
-
N/A
-
N/A
-
Description
Right now the process is the following (see http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Configuration#HCustomizingthePDFexportLook26Feel for more details):
- 1) Render the document to export as XHTML --> xmlA
- 2) Apply some pdf CSS using CSS4J to xmlA --> xmlB
- 3) Apply an XSL stylesheet to xmlB to generate XSL-FO (xhtml2fo.xsl) --> xmlC
- 4) Apply another XSL stylesheet to perform some cleanup to xmlC --> xmlD
- 5) Call FOP on xmlD to generate the PDF
One major issue is that FOP requires a valid XSL-FO input and will fail with an exception if that's not the case, and our xhtml2fo.xsl content is transforming XHTML and removing unknown properties but it cannot know all unknown properties.
There can be problems during steps 2 and 3/4.
Example of problem in step 2:
Example of problem in step 3/4:
Attachments
Issue Links
- is duplicated by
-
XWIKI-14276 Error thrown when exporting as PDF/RTF a document imported from Word - '
- Closed
- is related to
-
XWIKI-14271 Error thrown when exporting as PDF/RTF a document imported from Word
- Closed
-
XWIKI-14241 background:white css style breaks css4j in pdf export
- Closed
- relates to
-
XWIKI-14280 Warnings displayed in the logs for some invalid XSL-FO properties
- Closed