| Questions |

- Source files for the formatting properties are missing
- Formatting object xxx doesn't work as expected
- Supporting the latest XSL working draft
- Fatal error: Root element must be root
- Char '>' inserted into page number
- Are font properties allowed here
- Supported fonts

| Answers |

| Q: I can't find the source files for the formatting properties. The directories where they should be are empty. Where can I find them? |

| A: They are generated during the build process. So you should use the build script coming with Fop at least once to generate these files.

| Q: Feature xxx of the XSL Working Draft 27 March 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: When will the latest version of the XSL working draft be supported? |

| Basic conformance to the latest XSL working draft is scheduled for fall 2000.

| 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. |

| A: 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.

| Q: I need some additional fonts in FOP. How I can set embedding fonts? |

| A: At present, FOP does not support any fonts other than the built-in fonts Times, Helvetica, Courier, Symbol and ZapfDingbats.

Copyright © 1999 The Apache Software Foundation. All Rights Reserved.