Fonts

Renderer	Base-14	AWT/OS	Custom	Embedding
PDF	yes	no	yes	yes
PostScript	yes	no	yes	no
PCL	yes (modified)	no	no	no
TXT	yes (used for layout but not for output)	no	yes (used for layout but not for output)	no
AWT	if available from OS	yes	no	n/a (display only)
Print	if available from OS	yes	no	controlled by OS printer driver
RTF	n/a (font metrics not needed)	n/a	n/a	n/a
MIF	n/a (font metrics not needed)	n/a	n/a	n/a
SVG	if available from OS	yes	no	no
XML	yes	no	yes	n/a

- Status -

When building PDF files, FOP normally supports only the base-14 fonts defined in the Adobe PDF specification. -These include: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats. -

Font support in FOP can be extended by the addition of font metric files (written in XML) created from Adobe - Type 1 fonts and TrueType fonts. No other font types (Type 3, etc.) are supported at this time. +

+ Base-14 Fonts +

The Adobe PDF Specification specifies a set of 14 fonts that must be available to every PDF reader: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats.

+ AWT/Operating System Fonts +

The AWT family of renderers (AWT, Print, SVG), use the Java AWT libraries for font metric information. Through operating system registration, the AWT libraries know what fonts are available on the system, and the font metrics for each one.

+ Custom Fonts +

Support for custom fonts is added by creating font metric files (written in XML) from the actual font files, and registering them with FOP. Currently only Type 1 and TrueType fonts can be added. More information about font types can be found at the Adobe font types. There is also lots more font information on this Adobe Font Technote.

- - The font is simply embedded into the PDF file, it is not converted. - -

- Adding Type 1 fonts -

As mentioned above you need an XML file containing font metrics to be able to use an additional font. FOP - contains a tool that can generate such a font metrics file from a PFM file, which normally comes with the font file. -

- Generating a font metrics file -

Run the class org.apache.fop.fonts.apps.PFMReader to generate the XML file. -

+ Create Type 1 Font Metrics +

FOP includes a tool that can generate an appropriate font metrics file from the PFM file that normally comes with the Type 1 font file. +To use it, run the class org.apache.fop.fonts.apps.PFMReader:

Windows:

- -java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; + java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; lib\xercesImpl.jar;lib\xalan.jar - org.apache.fop.fonts.apps.PFMReader pfm-file xml-file - + org.apache.fop.fonts.apps.PFMReader pfm-file xml-file

Unix:

- -java -cp build/fop.jar:lib/avalon-framework.jar:lib/xml-apis.jar: + java -cp build/fop.jar:lib/avalon-framework.jar:lib/xml-apis.jar: lib/xercesImpl.jar:lib/xalan.jar - org.apache.fop.fonts.apps.PFMReader pfm-file xml-file - - - The classpath in the above example has been simplified for readibity. - You will have to adjust the classpath to the names of the actual JAR files in the lib directory. - avalon-framework.jar is necessary only for versions 0.20.5 or later. - xml-apis.jar, xercesImpl.jar and xalan.jar are not necessary for JDK version 1.4 or later. - - The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and - calculations which are only an approximation to the real values. FontBBox and Italic Angle can be found in - the human-readable part of the PFB file or in the AFM file. The PFMReader tool does not yet interpret PFB or AFM files, so if you want - to be correct, you may have to adjust the values in the XML file manually. The constructed values however - appear to have no visible influence. - + org.apache.fop.fonts.apps.PFMReader pfm-file xml-file + The classpath in the above example has been simplified for readibity. +You will have to adjust the classpath to the names of the actual JAR files in the lib directory. +avalon-framework.jar is necessary only for versions 0.20.5 or later. +xml-apis.jar, xercesImpl.jar and xalan.jar are not necessary for JDK version 1.4 or later. + The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and calculations which are only an approximation to the real values. +FontBBox and Italic Angle can be found in the human-readable part of the PFB file or in the AFM file. +The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually. +The constructed values however appear to have no visible influence.

- Register the fonts within FOP -

- Edit conf/userconfig.xml and add entries for the font - if the fonts section, - ie: -

-Register Type 1 Font Metrics with FOP +

Edit conf/userconfig.xml and add entries for the font in the fonts section, e.g.:

]]> - - Starting from FOP version 0.20.5 you can use URLs for the paths to the font files. Relative URLs are resolved - relative to the fontBaseDir property (or baseDir) if available. - - - Make sure you specify the PFB file in the embed-file attribute - and not the PFM you used to generate the XML font metrics file. - - - If you do not want the font embedded in the PDF then remove the - "embed-file" attribute. The PDF will then contain text using - the font with the font metrics and to view it properly the - font will need to be installed where it is being viewed. - - - Cocoon users will need to setup the config, see FOPSerializer - for more information. - + Starting with FOP version 0.20.5 you can use URLs for the paths to the font files. +Relative URLs are resolved relative to the fontBaseDir property (or baseDir) if available. + Make sure you specify the PFB file in the embed-file attribute and not the PFM you used to generate the XML font metrics file. + If you do not want the font embedded in the PDF then remove the "embed-file" attribute. +The PDF will then contain text using the font with the font metrics and to view it properly the font will need to be installed where it is being viewed. + Cocoon users will need to setup the config, see FOPSerializer for more information.

- Adding TrueType Fonts -

Adding TrueType fonts is almost identical to the process of - adding Type 1 fonts. The main difference is in the first - step.

- Generating a font metrics file -

As mentioned above you need an XML file containing font - metrics to be able to use an additional font. FOP contains - a tool that can generate such a font metrics file from - your TrueType font file. -

- Create metrics for the fontfile (we assume the file has - the name cmr10.ttf and exists in c:\myfonts\): -

- -java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; + Creating TrueType Font Metrics +

FOP includes a tool that can generate an appropriate font metrics file from your TrueType font file. To create such a file in Windows from the TrueType font at c:\myfonts\cmr10.ttf:

+ java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; lib\xercesImpl.jar;lib\xalan.jar org.apache.fop.fonts.apps.TTFReader - C:\myfonts\cmr10.ttf ttfcm.xml - + C:\myfonts\cmr10.ttf ttfcm.xml

- TrueType collections -

- TrueType collections (.ttc files) contains more than one - font. To create metrics for a ttc file you must specify - the font in the collection with the -ttcname option to - TTFReader. -

- To get a list of the fonts in a collection, just start the - TTFReader as if it were a normal TrueType file (without - the -ttcname option). It will then display all the font - names and exit with an Exception... -

- Example on generating metrics for a .ttc file: -

- -java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; +

+ Creating TrueType Collections Font Metrics +

TrueType collections (.ttc files) contains more than one font. +To create metrics files for these fonts, you must specify which font in the collection should be generated, by using the "-ttcname" option with the TTFReader:

To get a list of the fonts in a collection, just start the TTFReader as if it were a normal TrueType file (without the -ttcname option). +It will display all of the font names and exit with an Exception.

Example on generating metrics for a .ttc file:

+ java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; lib\xercesImpl.jar;lib\xalan.jar org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho" - msmincho.ttc msminch.xml - + msmincho.ttc msminch.xml

@@ -158,10 +176,11 @@ java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar; ]]>

Embedding fonts + The PostScript renderer does not yet support font embedding. + The font is simply embedded into the PDF file, it is not converted.

Font embedding is enabled in the userconfig.xml file and controlled by the embed-file attribute. If you don't specify the embed-file attribute the font will not be embedded, but will only be referenced. -- 2.39.5