cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/10/16 07:35:11 Modified:src/documentation/content/xdocs fonts.xml Log: correct doc re: use of custome fonts from the AWT and Print renderers Revision ChangesPath 1.20 +3 -3 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- fonts.xml 15 Sep 2003 20:54:01 - 1.19 +++ fonts.xml 16 Oct 2003 14:35:11 - 1.20 @@ -54,14 +54,14 @@ AWT if available from OS yes - no + yes n/a (display only) Print if available from OS yes - no + yes controlled by OS printer driver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/07/28 16:03:23 Modified:src/documentation/content/xdocs fonts.xml Log: fix some more typos Revision ChangesPath 1.18 +3 -3 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- fonts.xml 28 Jul 2003 18:26:25 - 1.17 +++ fonts.xml 28 Jul 2003 23:03:22 - 1.18 @@ -12,7 +12,7 @@ Summary - The following table summarizes the font capabilites of the various FOP renderers: + The following table summarizes the font capabilities of the various FOP renderers: Renderer @@ -143,7 +143,7 @@ TrueType Font Metrics FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it. Use it in a similar manner to PFMReader. -For example, to create such a metcis file in Windows from the TrueType font at c:\myfonts\cmr10.ttf: +For example, to create such a metrics 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 [options] @@ -185,7 +185,7 @@ Correct. Correct if and only if the font is embedded in the output. (This is possible because, although the underlying characters are encoded incorrectly, the embedded font is -also encoded incorreclty). +also encoded incorrectly). As shown in the above table, regardless of - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/07/28 11:26:25 Modified:src/documentation/content/xdocs fonts.xml Log: fix bad link Revision ChangesPath 1.17 +1 -1 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.16 retrieving revision 1.17 diff -u -r1.16 -r1.17 --- fonts.xml 28 Jul 2003 17:40:47 - 1.16 +++ fonts.xml 28 Jul 2003 18:26:25 - 1.17 @@ -238,7 +238,7 @@ One workaround for this behavior is to use the "-enc ansi" option when generating metrics with TTFReader. This will cause the whole font to be embedded in the pdf document. Characters will be WinAnsi encoded (as specified in the PDF spec), so you lose the ability to use characters from other character sets. -See Table of TTF Encoding Options for more details. +See Table of TTF Encoding Options for more details. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/07/28 10:40:47 Modified:src/documentation/content/xdocs fonts.xml Log: 1. add detail of command-line options for PFMReader and TTFReader 2. add more detail about the encoding issues for TTF metrics Revision ChangesPath 1.16 +62 -8 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.15 retrieving revision 1.16 diff -u -r1.15 -r1.16 --- fonts.xml 10 Jul 2003 16:59:29 - 1.15 +++ fonts.xml 28 Jul 2003 17:40:47 - 1.16 @@ -117,12 +117,20 @@ Windows: 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 [options] pfm-file xml-file Unix: 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. + org.apache.fop.fonts.apps.PFMReader [options] pfm-file xml-file +PFMReader [options]: + + -fnBy default, FOP uses the fontname from the +.pfm file when embedding the font. Use the "-fn" option to override this name with one you have +chosen. This may be useful in some cases to ensure that applications using the output document +(Acrobat Reader for example) use the embedded font instead of a local font with the same +name. + +The classpath in the above example has been simplified for readability. 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. @@ -138,8 +146,53 @@ For example, to create such a metcis 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 + org.apache.fop.fonts.apps.TTFReader [options] C:\myfonts\cmr10.ttf ttfcm.xml +TTFReader [options]: + + -d Sets the debug level (default is +INFO). + -fn Same as for PFMReader. + -ttcname If you're reading data from a +TrueType Collection (.ttc file) you must specify which font from the collection you will read +metrics from. +If you read from a .ttc file without this option, the fontnames will be listed for you. + -enc ansi Creates a WinAnsi-encoded font metrics file. +Without this option, a CID-keyed font metrics file is created. +The table below summarizes the differences between these two encoding options as currently +used within FOP. +Please note that this information only applies to TrueType fonts and TrueType collections: + + + +Issue +WinAnsi +CID-keyed + + +Usable Character Set +Limited to WinAnsi character set, which is roughly equivalent to iso-8889-1. +Limited only by the characters in the font itself. + + +Character Encoding in the Output Document. +Correct. +Never correct. Search, index, and cut-and-paste operations in the output document +will produce incorrect results. + + +Character Display +Correct. +Correct if and only if the font is embedded in the output. (This is possible +because, although the underlying characters are encoded incorrectly, the embedded font is +also encoded incorreclty). + + +As shown in the above table, regardless of +whether the font is embedded or not, text generated from a CID-keyed font metrics file +will never be encoded properly. +Further, if the related font is not embedded, it cannot even be displayed properly. +Obviously, this behavior is not desirable, and we hope to correct it in upcoming releases. TrueType Collections Font Metrics @@ -175,16 +228,17 @@ 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. -W
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/07/10 09:59:29 Modified:src/documentation/content/xdocs fonts.xml Log: 1. move "embedding" section under "custom" 2. some minor cleanup Revision ChangesPath 1.15 +15 -13xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -r1.14 -r1.15 --- fonts.xml 10 Jul 2003 06:47:38 - 1.14 +++ fonts.xml 10 Jul 2003 16:59:29 - 1.15 @@ -19,7 +19,7 @@ Base-14 AWT/OS Custom - Embedding + Custom Embedding PDF @@ -133,7 +133,9 @@ 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: +FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it. +Use it in a similar manner to PFMReader. +For example, to create such a metcis 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 @@ -141,7 +143,7 @@ TrueType Collections Font Metrics -TrueType collections (.ttc files) contains more than one font. +TrueType collections (.ttc files) contain 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. @@ -167,23 +169,23 @@ Cocoon users will need to setup the config, see FOPSerializer for more information. - - - 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. + +Embedding +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. - When FOP embeds a font, it scrambles its fontname by inserting a prefix that ensures that the fontname will not match the fontname of an installed font. +When FOP embeds a font, it scrambles its fontname by inserting a prefix that ensures that the fontname will not match the fontname of an installed font. This is helpful with older versions of Acrobat Reader that preferred installed fonts over embedded fonts. - When embedding PostScript fonts, the entire font is always embedded. - When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a new font, containing only the glyphs used, is created from the original font and embedded in the pdf. +When embedding PostScript fonts, the entire font is always embedded. +When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a new font, containing only the glyphs used, is created from the original font and embedded in the pdf. Currently, this embedded font contains only the minimum data needed to be embedded in a pdf document, and does not contain any codepage information. The PDF document contains indexes to the glyphs in the font instead of to encoded characters. While the document will be displayed correctly, the net effect of this is that searching, indexing, and cut-and-paste will not work properly. - One workaround for this behavior is to use the -ansi option when generating metrics with TTFReader. +One workaround for this behavior is to use the -ansi option when generating metrics with TTFReader. This will cause the whole font to be embedded in the pdf document. Characters will be WinAnsi encoded (as specified in the PDF spec), so you lose the ability to use characters from other character sets. + - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/07/09 12:41:15 Modified:src/documentation/content/xdocs fonts.xml Log: pretty-print changes only. Revision ChangesPath 1.13 +147 -165 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- fonts.xml 9 Jul 2003 19:31:48 - 1.12 +++ fonts.xml 9 Jul 2003 19:41:15 - 1.13 @@ -1,212 +1,194 @@ http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";> - FOP: Fonts - + - - -Summary -The following table summarizes the font capabilites of the various FOP renderers: - - -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 - - - - -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 http://partners.adobe.com/asn/developer/type/ftypes.html";> -Adobe font types. There is also lots more font information -on this http://partners.adobe.com/asn/developer/technotes/fonts.html";>Adobe Font Technote. - - - 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. + + + Summary + The following table summarizes the font capabilites of the various FOP renderers: + + + 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 +
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/07/09 12:31:49 Modified:src/documentation/content/xdocs fonts.xml Log: 1. rearrange some content into a summary table 2. misc cleanup 3. working toward some consolidation Revision ChangesPath 1.12 +132 -113 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.11 retrieving revision 1.12 diff -u -r1.11 -r1.12 --- fonts.xml 9 Jul 2003 18:01:42 - 1.11 +++ fonts.xml 9 Jul 2003 19:31:48 - 1.12 @@ -4,7 +4,7 @@ -Fonts +FOP: Fonts @@ -12,142 +12,160 @@ -Important -The information on this page applies primarily to the PDF renderer. The PostScript renderer -also supports custom fonts but does not yet support font embedding. This page does -not apply to the AWT, PCL, MIF and other renderers. -When using the AWT renderer, font metric information is available to FOP through AWT and the operating system (i.e. there is no need for font metrics files), and the operating system printer driver decides whether a font will be embedded. +Summary +The following table summarizes the font capabilites of the various FOP renderers: + + +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 http://partners.adobe.com/asn/developer/type/ftypes.html";> Adobe font types. There is also lots more font information on this http://partners.adobe.com/asn/developer/technotes/fonts.html";>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 ca
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
vmote 2003/07/09 11:01:42 Modified:src/documentation/content/xdocs fonts.xml Log: minor cleanup Revision ChangesPath 1.11 +4 -6 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- fonts.xml 14 Jun 2003 17:43:09 - 1.10 +++ fonts.xml 9 Jul 2003 18:01:42 - 1.11 @@ -14,16 +14,14 @@ Important The information on this page applies primarily to the PDF renderer. The PostScript renderer -also supports custom fonts but doesn't support font embedding, yet. This page does +also supports custom fonts but does not yet support font embedding. This page does not apply to the AWT, PCL, MIF and other renderers. -The AWT renderer relies upon AWT to provide the available fonts. And it's the printer -driver of your operating system that decides if a font is embedded when using the AWT -renderer. +When using the AWT renderer, font metric information is available to FOP through AWT and the operating system (i.e. there is no need for font metrics files), and the operating system printer driver decides whether a font will be embedded. Status -FOP (building PDF files) normally supports only the base 14 font package defined in the Adobe PDF specification. -That includes the following fonts: Helvetica, Times, Courier, Symbol and ZapfDingbats. +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. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
pietsch 2003/06/14 10:43:09 Modified:src/documentation/content/xdocs fonts.xml Log: Made XML well formed in font config code samples. Submitted by: Johannes Fiala Revision ChangesPath 1.10 +2 -2 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- fonts.xml 1 May 2003 19:47:05 - 1.9 +++ fonts.xml 14 Jun 2003 17:43:09 - 1.10 @@ -79,7 +79,7 @@ Starting from FOP version 0.20.5 you can use URLs for the paths to the font files. Relative URLs are resolved @@ -157,7 +157,7 @@ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
jeremias2003/02/19 01:30:52 Modified:src/documentation/content/xdocs fonts.xml Log: Added note for applicability to PDF and PS renderers only. Revision ChangesPath 1.5 +9 -0 xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- fonts.xml 12 Dec 2002 10:59:33 - 1.4 +++ fonts.xml 19 Feb 2003 09:30:51 - 1.5 @@ -12,6 +12,15 @@ +Important +The information on this page applies primarily to the PDF renderer. The PostScript renderer +also supports custom fonts but doesn't support font embedding, yet. This page does +not apply to the AWT, PCL, MIF and other renderers. +The AWT renderer relies upon AWT to provide the available fonts. And it's the printer +driver of your operating system that decides if a font is embedded when using the AWT +renderer. + + Status FOP (building PDF files) normally supports only the base 14 font package defined in the Adobe PDF specification. That includes the following fonts: Helvetica, Times, Courier, Symbol and ZapfDingbats. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml
jeremias2002/12/02 11:31:00 Modified:src/documentation/content/xdocs fonts.xml Log: Correct classpaths Improve text structure Some notes Revision ChangesPath 1.3 +76 -52xml-fop/src/documentation/content/xdocs/fonts.xml Index: fonts.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/fonts.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- fonts.xml 19 Nov 2002 07:57:27 - 1.2 +++ fonts.xml 2 Dec 2002 19:31:00 - 1.3 @@ -6,23 +6,21 @@ Fonts - + - - Font Support Status FOP (building PDF files) normally supports only the base 14 font package defined in the Adobe PDF specification. That includes the following fonts: Helvetica, Times, Courier, 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. +Type 1 fonts and TrueType fonts. No other font types (Type 3, etc.) are supported at this time. -The Font is simply embedded into the PDF file, it is not converted. +The font is simply embedded into the PDF file, it is not converted. @@ -35,18 +33,26 @@ Run the class org.apache.fop.fonts.apps.PFMReader to generate the XML file. Windows: - - java -cp build\fop.jar;lib\xercesImpl-2.0.1.jar;lib\xml-apis.jar;lib\xalan-2.3.1.jar;lib\batik.jar - org.apache.fop.fonts.apps.PFMReader pfm-file xml-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.PFMReader pfm-file xml-file + + Unix: - -java -cp build/fop.jar:lib/xercesImpl-2.0.1.jar:lib/xml-apis.jar:lib/xalan-2.3.1.jar:lib/batik.jar -org.apache.fop.fonts.apps.PFMReader pfm-file xml-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.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. The PFMReader tool does not yet interpret PFB files, so if you want + 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. @@ -57,30 +63,38 @@ Edit conf/userconfig.xml and add entries for the font if the fonts section, ie: - - - - - - + + + + + + +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. - + Adding additional TrueType -Adding Truetype fonts is almost identical to the process of -adding type 1 fonts. The main difference is in the first +Adding TrueType fonts is almost identical to the process of +adding Type 1 fonts. The main difference is in the first step. @@ -88,17 +102,20 @@ As mentioned above you need an XML file containing
