From f2a4f59f3adf8fc4a85587ad60915b1022cef665 Mon Sep 17 00:00:00 2001
From: Glenn Adams
Date: Tue, 3 Jul 2012 15:33:44 +0000
Subject: [PATCH] Revert change in tag, moving change to fop-1_1 branch.
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_1rc1@1356791 13f79535-47bb-0310-9956-ffa450edef68
---
src/documentation/content/xdocs/fo.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/documentation/content/xdocs/fo.xml b/src/documentation/content/xdocs/fo.xml
index c668eecfd..f0781ec50 100644
--- a/src/documentation/content/xdocs/fo.xml
+++ b/src/documentation/content/xdocs/fo.xml
@@ -66,7 +66,7 @@ The following hexadecimal example will result in a Euro sign:
Getting your XML correctly encoded is only part of the job.
If you want the character to display or print correctly (and you probably do), then the selected font must contain the necessary glyph.
Because of differences between font encoding methods, and limitations in some font technologies, this can be a troublesome issue, especially for symbol characters.
-The FOP example file Base-14 Font Character Mapping is a very useful resource in sorting these issues out for the Base-14 fonts.
+The FOP example file Base-14 Font Character Mapping is a very useful resource in sorting these issues out for the Base-14 fonts.
For other fonts, use font editing sofware or operating system utilities (such as the Character Map in most Windows platforms) to determine what characters the font supports.