vmote 2003/07/28 16:03:23
Modified: src/documentation/content/xdocs fonts.xml
Log:
fix some more typos
Revision Changes Path
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 -0000 1.17
+++ fonts.xml 28 Jul 2003 23:03:22 -0000 1.18
@@ -12,7 +12,7 @@
<body>
<section id="intro">
<title>Summary</title>
- <p>The following table summarizes the font capabilites of the various FOP
renderers:</p>
+ <p>The following table summarizes the font capabilities of the various FOP
renderers:</p>
<table>
<tr>
<th>Renderer</th>
@@ -143,7 +143,7 @@
<title>TrueType Font Metrics</title>
<p>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:</p>
+For example, to create such a metrics file in Windows from the TrueType font at
c:\myfonts\cmr10.ttf:</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.TTFReader [options]
@@ -185,7 +185,7 @@
<td>Correct.</td>
<td>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).</td>
+also encoded incorrectly).</td>
</tr>
</table>
<warning id="cid-keyed-encoding-ttf">As shown in the above table,
regardless of
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
