DocBook pdf transformation: broken SVG graphics

[dcowan]

When performing the standard pdf translation on a DocBook document, everything works beautifully except my svg format graphics are garbled and partially missing in the pdf document. Pixel format graphics such as png or jpg do not suffer this problem. Is there perhaps something wrong with my svg files?

[sorin_ristache]

Hello,

The FO processor that comes with Oxygen should render a SVG image in the PDF result without problems if the image is included in the DocBook document with an imagedata element that has the attribute format="SVG". Are your SVG files valid? You can check them with this SVG schema.


Regards,
Sorin

[dcowan]

The SVG files validate with the supplied schema - if I use the relax ng schema that you linked to above, I get the following error message:

SystemID: C:\Program Files\Oxygen XML Editor 9\frameworks\svg\dtd\Full-1.2.rng
Description: org.xml.sax.SAXParseException-no implementation available for schema language with namespace URI "http://www.w3.org/1999/xhtml"

The SVG rendered to a PDF is missing most of the text, colours are wrong and various of the lines are drawn in the incorrect weight or are dashed instead of solid. It displays perfectly in Author and all other applications.

[dcowan]

This does not occur when using the RenderX XEP transformation to PDF - using XEP the SVG graphic is rendered perfectly.

[sorin_ristache]

Hello,

It could be a problem in the SVG renderer included in the FO processor that comes with Oxygen and is used by default for generating PDF files. Can you send us one or more SVG images that are not rendered correctly to see what is wrong? The SVG images that we tested are rendered correctly in PDF results of the transformations executed in Oxygen.

You can set up XEP as external FO processor using the Browse button of the FO processor preferences panel. For using it in transformations that generate PDF results just select XEP instead of the default FO processor in the FO Processor tab of the dialog for editing a transformation scenario.


Regards,
Sorin