<processFO
processor = Non empty token
file = Path
to = Path
>
Content: [ parameter ]* [ processFO ]?
</processFO>
<parameter
name = Non empty token
url = boolean
>
Content: Parameter value
</parameter>
<parameterGroup
name = Non empty token
/>Converts a XSL-FO file to another format, typically a page description language such as PDF.
Attributes:
Specifies which FO processor to use.
Unlike the XSLT engine used by a transform element, the FO processor used to perform this conversion is not built-in into XXE. A FO processor plug-in having a name equals the value of the processor attribute (case-insensitive) must have been registered with XXE.
Input file.
Output file.
Parameter child elements are passed to the XSL-FO processor in order to parametrize its behavior. These parameters are described in the documentation of the XSL-FO processors.
If the url attribute of a parameter child element is specified and its value is true, the parameter value must be a relative or absolute URL (properly escaped like all URLs). In such case, the value of the parameter is the fully resolved URL.
XFC example:
<parameter name="outputEncoding">Cp1252</parameter>
XEP example:
<parameter name="PS.LANGUAGE_LEVEL">2</parameter>
In addition to actual parameters, some XSL-FO processors may also support a number of pseudo-parameters. The documentation of these pseudo-parameters is displayed in the documentation pane of the dialog box of → .
The processFO optional child element:
This optional child element specifies which FO processor to use when the FO processor specified by the parent processFO element is not available.
Example: try to use FOP when XEP is not available:
<processFO processor="XEP" file="__doc.fo" to="__doc.pdf">
<parameter name="OUTPUT_FORMAT">pdf</parameter>
<processFO processor="FOP" file="__doc.fo" to="__doc.pdf">
<parameter name="renderer">pdf</parameter>
<parameter name="configuration" url="true">fop.xconf</parameter>
</processFO>
</processFO>