About Arbortext Styler > General Reference Information > Differences in Output Support > Print/PDF Output via FOSI
Print/PDF Output via FOSI
The FOSI and XSL-FO print engines are on sustained support and do not receive enhancements or maintenance fixes. PTC ALD is the recommended engine for print/PDF output.
For information on how to set the print engine for your environment, see Logic for Print/Preview Engine Selection.
Area in UI
Text category
If font properties are not specifically set for the font used in a header or footer, headers and footers use system default font properties.
It is suggested that you apply font properties to the _sfe:HeaderOrFooter element if the system defaults do not meet your requirements
A value set in the Offset field will have no effect on content consisting of an inline graphic.
Indent category
Non-left (e.g., centered, right, and preformatted) alignment for numbered elements will not work properly unless the alignment is also specified within the same condition and/or output-specific property that specifies the numbering details.
In the same situation, the Align at (tab to) details are ignored, and the number is separated from the text by an em-space.
Generated text category
If a numbered object is centered or right aligned, any Align at and Follow with settings in the numbering details dialog are ignored. The number is automatically followed by an em-space.
Generated text configured for a property set will be resolved to the contexts/conditions that reference the property set when the stylesheet is exported.
Side by side category
If Placement is Right, the value of Horizontal offset is ignored when determining the left edge of the right aligned element. The FOSI engine uses the left indent and first line indent settings on the Indent category instead.
When Horizontal gap is greater than zero, the position of the following content is determined by adding the values of both Horizontal gap and the indent settings to the adjacent edge of the aligned element.
Values specified in em are not permitted in the Horizontal offset, Width, and Horizontal gap fields. If such a size is used, FOSI will treat 1em as 1pc.
PDF tags category
This is disabled for a stylesheet set to generate PDF via the FOSI engine. You must use the PTC ALD engine to generate tagged PDF output or alternate text for graphics/links.
Elements list
Unpredictable results may occur when a context is processed via FOSI, if its position in the document is defined via an XPath predicate that specifies an explicit level in the document hierarchy. To avoid this situation, use the more general parent and ancestor position options.
Page Sets list
In the Page types category, when the Double sided option is selected, a setting of Same as other pages in the Blank pages field will output the page type specified for even pages.
Unequal column widths are not supported.
Page Regions list
The main content flow region must be the same width for all pages.
The main content flow region may only be rotated by 90 degrees.
Graphics for a region background may not be extracted via XPath.
Region borders will not be output.
An Underlaid regions avoid this region setting will be ignored.
A Clip region at page edge setting will be ignored.
Independent horizontal and vertical scaling of graphics is not supported.
Table of Contents list
With FOSI outputs, XPath expressions specifying navigation that starts from a node in generated text will give unpredictable results (see above). If you define TOC conditions that use XPath tests, any title contexts where the title is generated (i.e. is a UFE) will not appear in the table of contents.
Combined fonts list
Combined fonts are not supported in print output generated via the FOSI engine
The Shrink graphics to fit option is not supported. You must publish via the PTC ALD engine to use this feature.
Rotated content in table cells is always formatted on one line. You may see very tall cells if their content is rotated 90° or 180°.
Publish via the PTC ALD engine if you need your content to break across lines.
When multiple footnotes are encountered with the same text on a page, FOSI will create new footnotes for each use.
PTC ALD will create a single footnote entry for that text and all uses will have the same footnote number.
When footnotes are used within a table header and the table spans two or more pages, FOSI will create a single footnote entry on the first page containing the table. All instances of the header refer to this single footnote.
PTC ALD will create a new footnote entry for each instance of the header. The footnote will appear with a new number on each page.