aboutsummaryrefslogtreecommitdiffstats
path: root/src/documentation/content/xdocs/0.20.5
diff options
context:
space:
mode:
Diffstat (limited to 'src/documentation/content/xdocs/0.20.5')
-rw-r--r--src/documentation/content/xdocs/0.20.5/compiling.xml6
-rw-r--r--src/documentation/content/xdocs/0.20.5/embedding.xml4
-rw-r--r--src/documentation/content/xdocs/0.20.5/extensions.xml4
-rw-r--r--src/documentation/content/xdocs/0.20.5/graphics.xml4
-rw-r--r--src/documentation/content/xdocs/0.20.5/hyphenation.xml6
-rw-r--r--src/documentation/content/xdocs/0.20.5/running.xml16
6 files changed, 20 insertions, 20 deletions
diff --git a/src/documentation/content/xdocs/0.20.5/compiling.xml b/src/documentation/content/xdocs/0.20.5/compiling.xml
index 6f66d15d8..6162b0c03 100644
--- a/src/documentation/content/xdocs/0.20.5/compiling.xml
+++ b/src/documentation/content/xdocs/0.20.5/compiling.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" standalone="no"?>
<!--
- Copyright 1999-2004 The Apache Software Foundation
+ Copyright 1999-2005 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -27,7 +27,7 @@
<section id="build-needed">
<title>Do You Need To Build?</title>
<p>FOP distributions are either pre-compiled binary or source.
-If you are using a binary distribution, it is already built and there is no need to build it again. See the <link href="download.html">Download Instructions</link> for information about whether a binary or source distribution is best for your needs.
+If you are using a binary distribution, it is already built and there is no need to build it again. See the <link href="../download.html">Download Instructions</link> for information about whether a binary or source distribution is best for your needs.
</p>
</section>
<section id="env">
@@ -80,7 +80,7 @@ To obtain a complete list of useful build targets:</p>
<li>Run the build with the target of "clean", then rerun the build.</li>
<li>Delete the build directory completely, then rerun the build.</li>
<li>Make sure you do not have a non-FOP version of xerces.jar, xalan.jar, batik.jar, or another dependency product somewhere in your CLASSPATH.</li>
- <li>If the build still fails, see the <link href="gethelp.html">Getting Help</link> page for further help.</li>
+ <li>If the build still fails, see the <link href="../gethelp.html">Getting Help</link> page for further help.</li>
</ul>
</section>
</body>
diff --git a/src/documentation/content/xdocs/0.20.5/embedding.xml b/src/documentation/content/xdocs/0.20.5/embedding.xml
index 5baec0d12..2270df46b 100644
--- a/src/documentation/content/xdocs/0.20.5/embedding.xml
+++ b/src/documentation/content/xdocs/0.20.5/embedding.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" standalone="no"?>
<!--
- Copyright 1999-2004 The Apache Software Foundation
+ Copyright 1999-2005 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -217,7 +217,7 @@ driver.setLogger(new org.apache.avalon.framework.logger.LogKitLogger(log));]]></
<title>Input Sources</title>
<p>
The input XSL-FO document is always handled internally as SAX (see the
- <link href="design/parsing.html">Parsing Design Document</link> for the rationale).
+ <link href="../dev/design/parsing.html">Parsing Design Document</link> for the rationale).
However, the input itself can be provided in a variety of ways to FOP,
which normalizes the input (if necessary) into SAX events:
</p>
diff --git a/src/documentation/content/xdocs/0.20.5/extensions.xml b/src/documentation/content/xdocs/0.20.5/extensions.xml
index 6f286dd46..a89cf9926 100644
--- a/src/documentation/content/xdocs/0.20.5/extensions.xml
+++ b/src/documentation/content/xdocs/0.20.5/extensions.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" standalone="no"?>
<!--
- Copyright 1999-2004 The Apache Software Foundation
+ Copyright 1999-2005 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -26,7 +26,7 @@
<body>
<p>By "extension", we mean any data that can be placed in the input XML document that is not addressed by the XSL-FO standard.
By having a mechanism for supporting extensions, FOP is able to add features that are not covered in the specification.</p>
- <p>The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the <link href="dev/extensions.html">Developers' Extension Page</link>.</p>
+ <p>The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the <link href="../dev/extensions.html">Developers' Extension Page</link>.</p>
<note>All extensions required the correct use of an appropriate namespace in your input document.</note>
<section id="svg">
<title>SVG</title>
diff --git a/src/documentation/content/xdocs/0.20.5/graphics.xml b/src/documentation/content/xdocs/0.20.5/graphics.xml
index ea9774405..6f9e54b67 100644
--- a/src/documentation/content/xdocs/0.20.5/graphics.xml
+++ b/src/documentation/content/xdocs/0.20.5/graphics.xml
@@ -184,8 +184,8 @@ correctly.
<title>Placing SVG Text into PDF</title>
<p>If possible, Batik will use normal PDF text when inserting text. It does
this by checking if the text can be drawn normally and the font is
-supported. This example svg <link href="dev/svg/text.svg">text.svg</link> /
-<!--link href="dev/svg/text.pdf"-->text.pdf<!--/link-->
+supported. This example svg <link href="../dev/svg/text.svg">text.svg</link> /
+<!--link href="../dev/svg/text.pdf"-->text.pdf<!--/link-->
shows how various types and effects with text are handled.
Note that tspan and outlined text are not yet implemented.</p>
<p>
diff --git a/src/documentation/content/xdocs/0.20.5/hyphenation.xml b/src/documentation/content/xdocs/0.20.5/hyphenation.xml
index db82c6362..61c510ce6 100644
--- a/src/documentation/content/xdocs/0.20.5/hyphenation.xml
+++ b/src/documentation/content/xdocs/0.20.5/hyphenation.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" standalone="no"?>
<!--
- Copyright 1999-2004 The Apache Software Foundation
+ Copyright 1999-2005 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -36,7 +36,7 @@
<note>If you have made improvements to an existing FOP hyphenation pattern,
or if you have created one from scratch, please consider contributing these
to OFFO so that they can benefit other FOP users as well.
- Please inquire on the <link href="maillist.html#fop-user">FOP User
+ Please inquire on the <link href="../maillist.html#fop-user">FOP User
mailing list</link>.</note>
</section>
<section id="license-issues">
@@ -141,7 +141,7 @@
tested against actual FOP behavior. It may contain errors or omissions.
Do not rely on these instructions without testing everything stated here.
If you use these instructions, please provide feedback on the
- <link href="maillist.html#fop-user">FOP User mailing list</link>, either
+ <link href="../maillist.html#fop-user">FOP User mailing list</link>, either
confirming their accuracy, or raising specific problems that we can
address.</warning>
<ul>
diff --git a/src/documentation/content/xdocs/0.20.5/running.xml b/src/documentation/content/xdocs/0.20.5/running.xml
index 549444928..f5aad4751 100644
--- a/src/documentation/content/xdocs/0.20.5/running.xml
+++ b/src/documentation/content/xdocs/0.20.5/running.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" standalone="no"?>
<!--
- Copyright 1999-2004 The Apache Software Foundation
+ Copyright 1999-2005 The Apache Software Foundation
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
@@ -30,7 +30,7 @@
<p>The following software must be installed:</p>
<ul>
<li>Java 1.2.x or later Runtime Environment.</li>
- <li>FOP. The <link href="download.html">FOP distribution</link> includes all libraries that you will need to run a basic FOP installation. These can be found in the xml-fop/lib directory. These libraries include the following:
+ <li>FOP. The <link href="../download.html">FOP distribution</link> includes all libraries that you will need to run a basic FOP installation. These can be found in the xml-fop/lib directory. These libraries include the following:
<ul>
<li><jump href="http://xml.apache.org/xerces-j/index.html">Apache Xerces-J</jump> for XML parsing. You can use other XML parsers which support SAX and DOM.</li>
<li><jump href="http://xml.apache.org/xalan-j/index.html">Apache Xalan-J</jump>, an XSLT processor.</li>
@@ -38,7 +38,7 @@
</ul>
</li>
</ul>
- <p>The following sofware is optional, depending on your needs:</p>
+ <p>The following software is optional, depending on your needs:</p>
<ul>
<li>Graphics libraries. Support for some graphics formats requires additional packages. See <link href="graphics.html">FOP: Graphics Formats</link> for details.</li>
<li>PDF encryption. See <link href="pdfencryption.html">FOP: PDF Encryption</link> for details.</li>
@@ -115,7 +115,7 @@ Although FOP controls both of these processes, the first is included merely as a
Only the second is part of FOP's core processing.
If a user has a problem running FOP, it is important to determine which of these two processes is causing the problem.
If the problem is in the first process, the user's stylesheet is likely the cause.
-The FOP development team does not have resources to help with stylesheet issues, although we have included links to some useful <link href="resources.html#specs">Specifications</link> and <link href="resources.html#articles">Books/Articles</link>.
+The FOP development team does not have resources to help with stylesheet issues, although we have included links to some useful <link href="../resources.html#specs">Specifications</link> and <link href="../resources.html#articles">Books/Articles</link>.
If the problem is in the second process, FOP may have a bug or an unimplemented feature that does require attention from the FOP development team.</p>
<note>The user is always responsible to provide correct XSL-FO code to FOP.</note>
<p>In the case of using -xml and -xsl input, although the user is responsible for the XSL-FO code that is FOP's input, it is not visible to the user. To make the intermediate FO file visible, the FOP distribution includes xalan.bat (Windows batch file) and xalan.sh (Unix/Linux script), which run only the first (transformation) step, and write the results to a file.</p>
@@ -150,7 +150,7 @@ Increase memory available to the JVM. See <link href="http://java.sun.com/j2se/1
<li>
Avoid forward references.
Forward references are references to some later part of a document.
-Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (<link href="faq.html#pagenum">"page N of TOTAL"</link>).
+Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (<link href="../faq.html#pagenum">"page N of TOTAL"</link>).
Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered.
Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them.
A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
@@ -172,18 +172,18 @@ This can be substantial if the page sequence contains lots of FO elements.
</ul>
<p>
There are currently some bugs which cause FOP to go into a nonterminating loop, which will also often result in a memory overflow.
-A characteristic symptom is continuous <link href="faq.html#boxoverflow">box overflows</link> in the log.
+A characteristic symptom is continuous <link href="../faq.html#boxoverflow">box overflows</link> in the log.
Most of these loops are triggered by elements that do not fit in the available space, such as big images or an improperly specified width in nested block elements.
The only workaround is to locate such problems and correct them.
</p>
<p>
One of FOP's stated design goals is to be able to process input of arbitrary size.
-Addressing this goal is one of the prime motivations behind the <link href="dev/index.html">FOP Redesign</link>.
+Addressing this goal is one of the prime motivations behind the <link href="../dev/index.html">FOP Redesign</link>.
</p>
</section>
<section id="problems">
<title>Problems</title>
- <p>If you have problems running FOP, please see the <jump href="gethelp.html">"How to get Help" page</jump>.</p>
+ <p>If you have problems running FOP, please see the <jump href="../gethelp.html">"How to get Help" page</jump>.</p>
</section>
</body>
</document>