From 1cd970079ab94fc8e1dee079611f060269b8daf6 Mon Sep 17 00:00:00 2001 From: William Victor Mote Date: Mon, 28 Jul 2003 23:03:22 +0000 Subject: [PATCH] fix some more typos git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196754 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/fonts.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/documentation/content/xdocs/fonts.xml b/src/documentation/content/xdocs/fonts.xml index e97ee46fc..b9e1c2613 100644 --- a/src/documentation/content/xdocs/fonts.xml +++ b/src/documentation/content/xdocs/fonts.xml @@ -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:

@@ -143,7 +143,7 @@ The constructed values however appear to have no visible influence.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 @@ will produce incorrect results. +also encoded incorrectly).
Renderer 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 -- 2.39.5