However, this approach hasn't been implemented, yet. If FOP used the font metrics from its own font subsystem but still used Java2D for text painting in the Java2D-based renderers, this could probably be achieved. Theoretically, there's some potential to make the output of the PDF/PS renderers match the output of the Java2D-based renderers. The net effect is that the layout of a given FO document can be quite different between renderers that do not use the same font information.
This can result in several differences, including actually using different fonts, and having different font metrics for the same font. However, the Java2D/AWT and print renderers use the Java AWT package, which gets its font information from the operating system registration. Most FOP renderers use a FOP-specific system for font registration. The renderers do not all have the same set of capabilities, sometimes because of the output format itself, sometimes because some renderers get more development attention than others. Hope to see you there! ApacheCon Europe ¶Īpache™ FOP supports multiple output formats by using a different renderer for each format. Search Apache XML Graphics ¶ ApacheCon N.
0 kommentar(er)
