XF Rendering Server offers support for different page properties regarding the .pdf output file through xf:page-settings extension.

In the example below you can see how it can be used:

 

<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"

       xmlns:xf="http://www.ecrion.com/xf/1.0">

 <xf:page-settings blending-color-space="DeviceRGB"

       pdf-conformance="PDF/A-1b:2005">

 </xf:page-settings>

 <fo:layout-master-set>

  ...

</fo:root>

 

 

You may notice that PDF documents that contain transparent RGB images may not print correctly on CMYK printers. This happens because the mathematics of the blending are occurring the color space of the output device. If you are sending in elements in RGB, and the calculation is occurring in CMYK (the default of most printers), you will be getting poor results.

To correct this, you set the blending-color-space attribute to one of the available values : "DeviceNative" | "DeviceRGB" | "DeviceCMYK" | "DeviceGray".

 

pdf-overprint-black-text is an option for printing and supports a boolean value.

If the overprint parameter is "false" (the default value), painting a color in any color space causes the corresponding areas of unspecified colorants to be erased (painted with a tint value of 0.0). The effect is that the color at any position on the page is whatever was painted there last, which is consistent with the normal painting behavior of the opaque imaging model.

If the overprint parameter is "true" and the output device supports overprinting, no such erasing actions are performed; anything previously painted in other colorants

is left undisturbed. Consequently, the color at a given position on the page may be a combined result of several painting operations in different colorants. The effect produced by such overprinting is device-dependent and is not defined by the PDF language.

 

pdf-embed-true-type-fonts can be set on: "true" | "false" | "subset".

This attribute is used to embed document characters; difference between "true" and "subset" is that set on "subset" will be embedded only once each character.

 

pdf-conformance set the type of PDf file from: "PDF/X-1a" | "PDF/A-1a" | "PDF/A-1b".

The difference between the last two is that "PDF/A-1a" is tagged. That means that the following lines are equivalent:

 

 

<xf:page-settings pdf-conformance="PDF/A-1b:2005"

       tagged-pdf="true"></xf:page-settings>

<xf:page-settings pdf-conformance="PDF/A-1a:2005">

</xf:page-settings>

 

 

PDF/A is a standard that defines a format  for the long-term archiving of electronic documents and is based on the PDF Reference Version 1.4. while the purpose of PDF/X is to facilitate graphics exchange.

 

tagged-pdf can have the value "true" | "false".

In PDF files, structure is expressed via "tags". Tags may be generated automatically for any PDF file using Acrobat 6.0 Professional, but unless the document is very simple indeed, automated tagging alone is unlikely to produce satisfactory results, and is certainly not a quick-fix for compliance with Section 508.

A PDF file equipped with well-formed tags may be "reflowed" to fit different page or screen widths, and will display well on handheld devices.

Tagged PDF files also work better with the screen-reader devices used by many blind and other disabled users.

In most cases, tags are necessary in order to make a PDF file comply with Section 508.

 

pdf-version can be set to one of the available versions: "1.3" | "1.4".