Q: Feature xxx of the XSL Working Draft 12 January 2000 does not work as it should. Why?
A: First: Only a small subset of formatting objects and properties is
implemented at the moment. Please have a look at the section "Features",
which lists the supported fo and properties. Second: At the moment only
Working Draft 21 Apr 1999 is supported.
Q: Running FOP I get the following messages or something similar:
"WARNING: Unknown formatting object http://www.w3.org/XSL/Format/1.0^root"
and then a FATAL Error "Root element must be root, not default FO".
A: Make sure that you have specified as the namespace for fo the
following string: "http://www.w3.org/1999/XSL/Format". It is analogous
to the xslt namespace "http://www.w3.org/1999/XSL/Transform"
Q: The char ">" is inserted into the page number display like this
"formatting FOs into areas [1] [2] [3>>>>]". Is this a bug?
A: No, a feature. It simply means that on that page an area
overflowed (ie there was not enough room to fit the text in).
Q: It looks like FOP must be honoring font properties when it shouldn't be?
Example: According to the dtd coming with the xsl-fo spec inline-sequence
shouldn't have any attributes, but FOP doesn't reject them.
Font properties are inherited down to individual characters. You can
specify font properties on any formatting object you like and any textual content
will inherit those properties (unless overriden by a closer ancestor).
The dtd coming with the xsl-fo spec isn't correct in this respect.
I need some additional fonts in FOP. How I can set embedding fonts?
At present, FOP does not support any fonts other than the in-built fonts
Times, Helvetica and Courier.
