cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml

2003-10-16 Thread vmote 
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 @@
 tdAWT/td
 tdif available from OS/td
 tdyes/td
  -  tdno/td
  +  tdyes/td
 tdn/a (display only)/td
   /tr
   tr
 tdPrint/td
 tdif available from OS/td
 tdyes/td
  -  tdno/td
  +  tdyes/td
 tdcontrolled by OS printer driver/td
   /tr
   tr
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml

2003-07-28 Thread vmote 
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 @@
   pOne 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 link href=ttf-encodingTable of TTF Encoding Options/link for more 
details./p
  +See link href=#ttf-encodingTable of TTF Encoding Options/link for more 
details./p
 /section
   /section
 /body
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml

2003-07-28 Thread vmote 
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 @@
 body
   section id=intro
 titleSummary/title
  -  pThe following table summarizes the font capabilites of the various FOP 
renderers:/p
  +  pThe following table summarizes the font capabilities of the various FOP 
renderers:/p
 table
   tr
 thRenderer/th
  @@ -143,7 +143,7 @@
   titleTrueType Font Metrics/title
   pFOP 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:/p
  +For example, to create such a metrics file in Windows from the TrueType font at 
c:\myfonts\cmr10.ttf:/p
   sourcejava -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 @@
   tdCorrect./td
   tdCorrect 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)./td
  +also encoded incorrectly)./td
 /tr
   /table
   warning id=cid-keyed-encoding-ttfAs 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

2003-07-10 Thread vmote 
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 @@
 thBase-14/th
 thAWT/OS/th
 thCustom/th
  -  thEmbedding/th
  +  thCustom Embedding/th
   /tr
   tr
 tdPDF/td
  @@ -133,7 +133,9 @@
 /section
 section id=truetype-metrics
   titleTrueType Font Metrics/title
  -pFOP 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:/p
  +pFOP 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:/p
   sourcejava -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 @@
 /section
 section id=truetype-collections-metrics
   titleTrueType Collections Font Metrics/title
  -pTrueType collections (.ttc files) contains more than one font.
  +pTrueType 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./p
   pTo 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./p
  @@ -167,23 +169,23 @@
   /ul
   noteCocoon users will need to setup the config, see FOPSerializer for 
more information./note
 /section
  -/section
  -section id=embedding
  -  titleEmbedding fonts/title
  -  noteThe PostScript renderer does not yet support font embedding./note
  -  noteThe font is simply embedded into the PDF file, it is not 
converted./note
  -  pFont embedding is enabled in the userconfig.xml file and controlled by the 
embed-file attribute.
  +  section id=embedding
  +titleEmbedding/title
  +noteThe PostScript renderer does not yet support font embedding./note
  +noteThe font is simply embedded into the PDF file, it is not 
converted./note
  +pFont 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./p
  -  pWhen 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.
  +pWhen 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./p
  -  pWhen embedding PostScript fonts, the entire font is always embedded./p
  -  pWhen 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.
  +pWhen embedding PostScript fonts, the entire font is always embedded./p
  +pWhen 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./p
  -  pOne workaround for this behavior is to use the -ansi option when 
generating metrics with TTFReader.
  +pOne 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

cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml

2003-07-09 Thread vmote 
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 @@
   
   document
 header
  -titleFonts/title
  +titleFOP: Fonts/title
   authors
 person name=Jeremias Märki email=/
 person name=Tore Engvig email=/
  @@ -12,142 +12,160 @@
 /header
   body
 section id=intro
  -titleImportant/title
  -pThe 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 
  -strongnot/strong apply to the AWT, PCL, MIF and other renderers./p
  -pWhen 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./p
  +titleSummary/title
  +pThe following table summarizes the font capabilites of the various FOP 
renderers:/p
  +table
  +  tr
  +thRenderer/th
  +thBase-14/th
  +thAWT/OS/th
  +thCustom/th
  +thEmbedding/th
  +  /tr
  +  tr
  +tdPDF/td
  +tdyes/td
  +tdno/td
  +tdyes/td
  +tdyes/td
  +  /tr
  +  tr
  +tdPostScript/td
  +tdyes/td
  +tdno/td
  +tdyes/td
  +tdno/td
  +  /tr
  +  tr
  +tdPCL/td
  +tdyes (modified)/td
  +tdno/td
  +tdno/td
  +tdno/td
  +  /tr
  +  tr
  +tdTXT/td
  +tdyes (used for layout but not for output)/td
  +tdno/td
  +tdyes (used for layout but not for output)/td
  +tdno/td
  +  /tr
  +  tr
  +tdAWT/td
  +tdif available from OS/td
  +tdyes/td
  +tdno/td
  +tdn/a (display only)/td
  +  /tr
  +  tr
  +tdPrint/td
  +tdif available from OS/td
  +tdyes/td
  +tdno/td
  +tdcontrolled by OS printer driver/td
  +  /tr
  +  tr
  +tdRTF/td
  +tdn/a (font metrics not needed)/td
  +tdn/a/td
  +tdn/a/td
  +tdn/a/td
  +  /tr
  +  tr
  +tdMIF/td
  +tdn/a (font metrics not needed)/td
  +tdn/a/td
  +tdn/a/td
  +tdn/a/td
  +  /tr
  +  tr
  +tdSVG/td
  +tdif available from OS/td
  +tdyes/td
  +tdno/td
  +tdno/td
  +  /tr
  +  tr
  +tdXML/td
  +tdyes/td
  +tdno/td
  +tdyes/td
  +tdn/a/td
  +  /tr
  +/table
 /section
  -  section id=status
  -titleStatus/title
  -pWhen 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.
  -/p
  -pFont 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.
  +  section
  +titleBase-14 Fonts/title
  +pThe 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./p
  +  /section
  +  section id=awt
  +titleAWT/Operating System Fonts/title
  +pThe 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./p
  +  /section
  +  section id=custom
  +titleCustom Fonts/title
  +pSupport 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 link href=http://partners.adobe.com/asn/developer/type/ftypes.html;
   Adobe font types/link. There is also lots more font information
   on this link

cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml

2003-07-09 Thread vmote 
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 @@
   ?xml version=1.0 standalone=no?
   !DOCTYPE document PUBLIC -//APACHE//DTD Documentation V1.1//EN
   
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd;
  -
   document
 header
   titleFOP: Fonts/title
   authors
 person name=Jeremias Märki email=/
 person name=Tore Engvig email=/
  - /authors
  +/authors
 /header
  -body
  -  section id=intro
  -titleSummary/title
  -pThe following table summarizes the font capabilites of the various FOP 
renderers:/p
  -table
  -  tr
  -thRenderer/th
  -thBase-14/th
  -thAWT/OS/th
  -thCustom/th
  -thEmbedding/th
  -  /tr
  -  tr
  -tdPDF/td
  -tdyes/td
  -tdno/td
  -tdyes/td
  -tdyes/td
  -  /tr
  -  tr
  -tdPostScript/td
  -tdyes/td
  -tdno/td
  -tdyes/td
  -tdno/td
  -  /tr
  -  tr
  -tdPCL/td
  -tdyes (modified)/td
  -tdno/td
  -tdno/td
  -tdno/td
  -  /tr
  -  tr
  -tdTXT/td
  -tdyes (used for layout but not for output)/td
  -tdno/td
  -tdyes (used for layout but not for output)/td
  -tdno/td
  -  /tr
  -  tr
  -tdAWT/td
  -tdif available from OS/td
  -tdyes/td
  -tdno/td
  -tdn/a (display only)/td
  -  /tr
  -  tr
  -tdPrint/td
  -tdif available from OS/td
  -tdyes/td
  -tdno/td
  -tdcontrolled by OS printer driver/td
  -  /tr
  -  tr
  -tdRTF/td
  -tdn/a (font metrics not needed)/td
  -tdn/a/td
  -tdn/a/td
  -tdn/a/td
  -  /tr
  -  tr
  -tdMIF/td
  -tdn/a (font metrics not needed)/td
  -tdn/a/td
  -tdn/a/td
  -tdn/a/td
  -  /tr
  -  tr
  -tdSVG/td
  -tdif available from OS/td
  -tdyes/td
  -tdno/td
  -tdno/td
  -  /tr
  -  tr
  -tdXML/td
  -tdyes/td
  -tdno/td
  -tdyes/td
  -tdn/a/td
  -  /tr
  -/table
  -  /section
  -  section
  -titleBase-14 Fonts/title
  -pThe 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./p
  -  /section
  -  section id=awt
  -titleAWT/Operating System Fonts/title
  -pThe 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./p
  -  /section
  -  section id=custom
  -titleCustom Fonts/title
  -pSupport 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 link href=http://partners.adobe.com/asn/developer/type/ftypes.html;
  -Adobe font types/link. There is also lots more font information
  -on this link 
href=http://partners.adobe.com/asn/developer/technotes/fonts.html;Adobe Font 
Technote/link.
  -/p
  -section id=type1-metrics
  -  titleCreate Type 1 Font Metrics/title
  -  pFOP includes a tool that can generate an appropriate font metrics file 
from the PFM file that normally comes with the Type 1 font file.
  +  body
  +section id=intro
  +  titleSummary/title
  +  pThe following table summarizes the font capabilites of the various FOP 
renderers:/p
  +  table
  +tr
  +  thRenderer/th
  +  thBase-14/th
  +  thAWT/OS/th
  +  thCustom/th
  +  thEmbedding/th
  +/tr
  +tr
  +  tdPDF/td
  +  tdyes/td
  +  tdno/td
  +  tdyes/td
  +  tdyes/td
  +/tr
  +tr
  +  tdPostScript/td
  +  tdyes/td
  +  tdno/td
  +  tdyes/td
  +  tdno/td
  +/tr
  +tr
  +  tdPCL/td
  +  tdyes (modified)/td
  +

cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml

2003-06-14 Thread pietsch 
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 @@
 /p
   source![CDATA[font metrics-file=FTL_.xml kerning=yes
 embed-file=C:\myfonts\FTL_.pfb
  -  font-triplet name=FrutigerLight style=normal weight=normal
  +  font-triplet name=FrutigerLight style=normal weight=normal/
   /font]]/source
 note
   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 @@
   /p
   source![CDATA[font metrics-file=cyberbit.xml kerning=yes
 embed-file=C:\WINNT\Fonts\Cyberbit.ttf
  -  font-triplet name=Cyberbit style=normal weight=normal
  +  font-triplet name=Cyberbit style=normal weight=normal/
   /font]]/source
 /section
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: xml-fop/src/documentation/content/xdocs fonts.xml

2003-02-19 Thread jeremias 
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 @@
 /header
   body
 section
  +titleImportant/title
  +pThe 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 
  +strongnot/strong apply to the AWT, PCL, MIF and other renderers./p
  +pThe 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./p
  +  /section
  +  section
   titleStatus/title
   pFOP (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

2002-12-02 Thread jeremias 
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 @@
 header
   titleFonts/title
   authors
  -  person name=Jeremias Maerki email=/
  +  person name=Jeremias Märki email=/
 person name=Tore Engvig email=/
/authors
 /header
   body
  -section
  -  titleFont Support/title
 section
   titleStatus/title
   pFOP (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.
   /p
   pFont 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.
   /p
   note
  -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.
   /note
 /section
 section
  @@ -35,18 +33,26 @@
 p Run the class org.apache.fop.fonts.apps.PFMReader to generate the XML 
file.
 /p
 pWindows:/p
  -p
  -  codejava -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/code
  -  /p
  +source
  +
  +  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
  +
  +/source
 pUnix:/p
  -  p
  -codejava -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/code
  -  /p
  +source
  +
  +  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
  +
  +/source
  +  note
  +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.
  +  /note
 noteThe 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.
 /note
  @@ -57,30 +63,38 @@
   Edit conf/userconfig.xml and add entries for the font
   if the fonts section,
   ie:
  -/p
  -p
  -code![CDATA[
  -font metrics-file=cyberbit.xml kerning=yes 
embed-file=C:\WINNT\Fonts\Cyberbit.ttf
  -  font-triplet name=Cyberbit style=normal weight=normal
  -/font]]
  -/code
  -/p
  -note
  +  /p
  +source
  +![CDATA[
  +  font metrics-file=FTL_.xml kerning=yes 
embed-file=C:\myfonts\FTL_.pfb
  +font-triplet name=FrutigerLight style=normal weight=normal
  +  /font]]
  +
  +/source
  +  note
  +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.
  +  /note
  +  note
  +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.
  +  /note
  +  note
   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