Here is the list of major changes in version 1.0
- Added support for addressing all glyphs available in a Type 1 font
- Added support for auto-configuring TrueType Collections. XML font metrics files for *.ttc fonts are not required anymore.
- Added support for rendering pages using Java Printing System.
- Support character-by-character font-selection strategy on fo:character element.
- Implemented word-by-ford font-selection strategy on text.
- AFP Output: Various enhancements
- FOP now creates ToUnicode CMaps for single-byte fonts that don't use built-in encodings
- Introduced a new, additional intermediate format optimized for performance. See the intermediate format documentation for details.
- Added an initial set of extensions for prepress support.
- Added limited support for different page widths within a page-sequence.
- Added support for TrueType fonts with symbol character maps (like "Wingdings" and "Symbol").
- Added an event handling framework which allows to get better feedback from within FOP with the ability to customize problem management.
FOP converts XSL-FO files to PDF, PostScript, SVG, RTF, or XML. It is the default implementation bundled in XML editors such as XSLfast, Oxygen, and XMLSpy.
The FOP project is already in widespread use by companies like Accenture, BNP Paribas, FedEx, the European Patent Office, Ford, HP, IBM, Siemens, the US Army, and the US House of Representatives. "FOP's popularity is undisputed," said Apache XML Graphics PMC Chair Simon Pepping. However, the developers still consider it a work in progress with more features yet to be implemented. "Some 'overnight successes' take ten years or more," said James Governor, Analyst and Founder of RedMonk. "Apache FOP seems to be one of them."