Author: gadams
Date: Tue Jul 3 15:36:44 2012
New Revision: 1356792
URL: http://svn.apache.org/viewvc?rev=1356792&view=rev
Log:
Fix broken link to permit documentation deployment.
Modified:
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/fo.xml
Modified:
xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/fo.xml
URL:
http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/fo.xml?rev=1356792&r1=1356791&r2=1356792&view=diff
==============================================================================
--- xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/fo.xml
(original)
+++ xmlgraphics/fop/branches/fop-1_1/src/documentation/content/xdocs/fo.xml Tue
Jul 3 15:36:44 2012
@@ -66,7 +66,7 @@ The following hexadecimal example will r
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 <link href="fo/fonts.fo.pdf">Base-14 Font Character
Mapping</link> is a very useful resource in sorting these issues out for the
Base-14 fonts.
+The FOP example file <link href="fo/fonts.pdf">Base-14 Font Character
Mapping</link> 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.
</p>
<p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
