Page references - i.e. page-number-citation objects - are converted to PageRef fields. The values of these fields are not automatically updated when loading an RTF/WML/OOXML document in MS-Word. The easiest way to update all field values is to force a repagination of the document, for instance by switching to the Page Layout view. This will work fine for fields in the body of the document, but not for those in the header/footer. To update fields in the header or footer of a document, proceed as follows:
Switch to the Page Layout view.
Double-click on an odd page header/footer outline.
Type Ctrl-A (Select all) and F9 (Update fields).
Double-click on an even page header/footer outline and repeat step #3.
If applicable, double-click on the title page header/footer outline and repeat step #3.
For lack of a corresponding element in the output formats, leader objects are implemented by means of tab stops. This is not very convenient given the leader object specification, since there is no way for XFC to derive the tab position from the property values. Though XFC will usually set the tab position to a reasonable value by default, this arbitrary position is unlikely to result in the intended layout.
However, the actual tab position may be specified to XFC by setting an additional property on the leader object. This property is named tab-position and must be defined in the XFC namespace (http://www.xmlmind.com/foconverter/xsl/extensions). The property value is a <length> as defined in section 5.11 of the Recommendation. A positive value specifies the tab position relative to the left margin, whereas a negative value specifies the position relative to the right margin.
The code samples below are excerpts from file $XFC_HOME/xsl/docbook/fo/autotoc.xsl. They illustrate a typical use of the tab-position property in an XSL stylesheet.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:xfc="http://www.xmlmind.com/foconverter/xsl/extensions"
version='1.0'><fo:leader leader-pattern="dots"
leader-pattern-width="3pt"
leader-alignment="reference-area"
xfc:tab-position="-5mm"
keep-with-next.within-line="always"/>Handling of characters that cannot be represented in the output encoding depends on the version of the Java runtime in use. With JRE 1.3 no special processing takes place so these characters are replaced with question marks. (This is the standard Java streams behaviour.) With JRE 1.4 XFC uses a character set encoder - an instance of the java.nio.charset.CharsetEncoder class - to determine if a given character can be represented in the output encoding. Characters that cannot be encoded are then represented using a Unicode control word (RTF output) or an XML character reference (WML, Open XML and OpenDocument output). However, not all charset encoders are available on all platforms. (For instance, encoders for the windows-1250 and windows-1251 charsets are not available in Linux JRE 1.4.0.)
XFC uses an instance of the System.Text.Encoding class to determine if a given character can be represented in the output encoding. Characters that cannot be encoded are then represented using a Unicode control word (RTF output) or an XML character reference (WML, Open XML and OpenDocument output).
XFC supports all conditional-page-master-reference element combinations that can be accommodated by a single RTF section. This means the following page sequence layouts are supported:
Single-sided layout.
Header page + single-sided layout.
Double-sided layout.
Header page + double-sided layout.
This applies to all output formats. Also, note that a single RTF section can handle different headers/footers on left/right/first pages, but does not allow page geometry changes, except for switching left and right margins on facing pages. This restriction does not apply to OpenDocument output.
Note: By default RTF, WML and Open XML output documents are given a double-sided page layout regardless of the input document properties. This results in all sections having separate headers/footers for odd and even pages, even though the content of both headers/footers may be identical. It may also result in blank pages being inserted in the document in order for every section to start on an odd page.
Use of expressions for property values specification is supported, subject to the following restrictions:
The proportional-column-width function may not be part of an arithmetic expression, i.e. it must be used as a single primary expression.
The rgb-icc, system-color, system-font and merge-property-values are not supported.