Fix broken link to permit documentation deployment.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-1_1@1356792 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/src/documentation/content/xdocs/fo.xml b/src/documentation/content/xdocs/fo.xml
index f0781ec5044884f730a9f2b2f9b0bec2af04f425..c668eecfd6ddf767a05c2e6b3eb59ad47823b850 100644 (file)
--- 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 <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>