You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by vh...@apache.org on 2007/08/23 20:30:09 UTC
svn commit: r569104 [3/4] - in /xmlgraphics/fop/trunk: ./ src/documentation/
src/documentation/content/ src/documentation/content/xdocs/
src/documentation/content/xdocs/0.20.5/ src/documentation/content/xdocs/0.93/
src/documentation/content/xdocs/0.94/...
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/design/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/design/configuration.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/design/configuration.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/design/configuration.xml Thu Aug 23 11:30:05 2007
@@ -47,30 +47,30 @@
instructions, including comments which specify the value range. Also,
since the configuration file is XML, be sure to keep it
well-formed.</p>
- </section>
+ </section>
- <section id="general-available">
- <title>Making Configuration Available to FOP</title>
- <p>After creating your configuration file, you must tell FOP how
+ <section id="general-available">
+ <title>Making Configuration Available to FOP</title>
+ <p>After creating your configuration file, you must tell FOP how
to find it.</p>
- <section id="command-line">
- <title>From the Command Line</title>
- <p>When you run FOP from the command-line, use the
+ <section id="command-line">
+ <title>From the Command Line</title>
+ <p>When you run FOP from the command-line, use the
“<code>-c</code>” command-line option with the path to the
configuration file as the option value.</p>
- </section>
+ </section>
- <section id="embedded-file">
- <title>A Configuration File in an Embedded Application</title>
- <p>FOP uses the Avalon framework configuration package
+ <section id="embedded-file">
+ <title>A Configuration File in an Embedded Application</title>
+ <p>FOP uses the Avalon framework configuration package
<code>org.apache.avalon.framework.configuration</code>. For detailed
information, see the documentation of the package.</p>
- <p>If you want to use a user configuration file with your
+ <p>If you want to use a user configuration file with your
embedded program, you need to build an Avalon configuration
object from it, and register that with the user agent:</p>
- <source>FOUserAgent foUserAgent;
+ <source>FOUserAgent foUserAgent;
XMLReader parser;
DefaultConfigurationBuilder configBuilder;
File userConfigFile;
@@ -81,81 +81,81 @@
userConfig = configBuilder.buildFromFile(userConfigFile);
foUserAgent.setUserConfig(userConfig);
</source>
- <p>You can find example code in FOP's
+ <p>You can find example code in FOP's
<code>apps.CommandLine</code> class, method
<code>createUserConfig</code>.</p>
- </section>
+ </section>
- <section id="embedded-build">
- <title>Programmatically Building the Configuration</title>
- <p>You can also build the configuration object programmatically,
+ <section id="embedded-build">
+ <title>Programmatically Building the Configuration</title>
+ <p>You can also build the configuration object programmatically,
instead of building it from an external file. Make sure that the
configuration object is equivalent to a configuration object that
would be obtained from a correct configuration file. Register the
configuration object with the user agent as described above.</p>
- </section>
+ </section>
- </section>
+ </section>
- <section id="config-overview">
- <title>The Configuration File</title>
- <p>The top-level element is arbitrary. You may give it any name
+ <section id="config-overview">
+ <title>The Configuration File</title>
+ <p>The top-level element is arbitrary. You may give it any name
that is useful for you, e.g. <code><fop-configuration
version="2"></code>.</p>
- <p>Inside the top-level element the configuration may contain
+ <p>Inside the top-level element the configuration may contain
three sections: <code>userAgent</code>, <code>renderers</code>,
and <code>hyphenation</code>. At the moment of this writing the
<code>userAgent</code> and <code>hyphenation</code> sections are
not used by FOP.</p>
- <p>The <code>renderers</code> section has subsections called
+ <p>The <code>renderers</code> section has subsections called
<code>renderer</code>. There may be one subsection for each type
of renderer. The renderers are identified by their MIME type,
which is given in the <code>mime</code> attribute. For example:
<code><renderer mime="application/pdf"></code>. The content
of each <code>renderer</code> subsection depends on the type of
renderer.</p>
- <p>The PDF renderer (MIME type <code>application/pdf</code>) has
+ <p>The PDF renderer (MIME type <code>application/pdf</code>) has
several options:</p>
- <dl>
- <dt><code>filterList</code></dt>
- <dd>Contains a number of <code>value</code> elements, whose
+ <dl>
+ <dt><code>filterList</code></dt>
+ <dd>Contains a number of <code>value</code> elements, whose
content specify a filter which should be applied. Possible
filters are: <code>flate</code>, <code>ascii-85</code>,
<code>ascii-hex</code>. The <code>flate</code> filter is on by
default.</dd>
- <dt><code>fonts</code></dt>
- <dd>Contains a number of <code>font</code> elements. Each
+ <dt><code>fonts</code></dt>
+ <dd>Contains a number of <code>font</code> elements. Each
<code>font</code> element represents a font file,
e.g. <code>arial.ttf</code>. It contains a number of
<code>font-triplet</code> elements, defining the font triplets
which are provided by this font file. See the example
configuration file for details.</dd>
- </dl>
- <p>The example configuration file provides for details about the
+ </dl>
+ <p>The example configuration file provides for details about the
other renderers.</p>
- </section>
+ </section>
<section id="hyphenation-dir">
<title>Hyphenation</title>
- <p>When FOP needs to load a hyphenation file for a certain
+ <p>When FOP needs to load a hyphenation file for a certain
language and country combination, it follows these steps.</p>
- <ol>
- <li>FOP searches for the compiled hyphenation file (extension
+ <ol>
+ <li>FOP searches for the compiled hyphenation file (extension
<code>hyp</code> in the directory <code>hyph</code> in the
class path.</li>
- <li>FOP searches for the compiled or the XML hyphenation file
+ <li>FOP searches for the compiled or the XML hyphenation file
in a user directory. At the time of this writing FOP does not
read the configuration file for the user directory. It always
uses the directory <code>/hyph</code>.</li>
- </ol>
- <p>It is possible to add user hyphenation files to FOP's
+ </ol>
+ <p>It is possible to add user hyphenation files to FOP's
hyphenation directory when FOP is built. The directory
containing user hyphenation files must be specified in the
variable <code>user.hyph.dir</code> in the local build
properties file. All hyphenation files in the directory are
compiled, and the compiled files are added to the hyphenation
directory in the build directory.</p>
- <p>See <link href="../hyphenation.html">FOP: Hyphenation</link> for
+ <p>See <link href="../hyphenation.html">FOP: Hyphenation</link> for
more information on creating and modifying hyphenation within FOP.</p>
</section>
@@ -168,24 +168,24 @@
href="../fonts.html#register">Register Fonts with FOP</link>.</p>
</section>
- <section id="logging">
- <title>Logging</title>
- <p>FOP uses the Jakarta Commons logging package
+ <section id="logging">
+ <title>Logging</title>
+ <p>FOP uses the Jakarta Commons logging package
<code>org.apache.commons.logging</code>. For detailed information, see
the documentation of the package.</p>
- <p>Commons logging is entirely configured by the user, using
+ <p>Commons logging is entirely configured by the user, using
Java system properties. Configuration happens in two stages.</p>
- <p>First you configure which logging implementation you want
+ <p>First you configure which logging implementation you want
to use. For example:</p>
- <source>org.apache.commons.logging.Log
+ <source>org.apache.commons.logging.Log
=org.apache.commons.logging.impl.SimpleLog</source>
- <p><code>SimpleLog is the default logging package on most Java
+ <p><code>SimpleLog is the default logging package on most Java
systems. On Java 1.4 systems JDK 1.4 is the default.</code></p>
- <p>Secondly, you configure the selected logging package. How
+ <p>Secondly, you configure the selected logging package. How
this is done depends on the logging package. The most important
feature is the log level. The default is level “info”. An
example configuration file for SimpleLog is:</p>
- <source>
+ <source>
# logging level for all loggers, default info
org.apache.commons.logging.simplelog.defaultlog=info
@@ -193,7 +193,7 @@
org.apache.commons.logging.simplelog.log.xxxxx=debug
org.apache.commons.logging.simplelog.log.org.apache.fop.pdf=trace
</source>
- <p>FOP uses several named loggers. When you set the logging level
+ <p>FOP uses several named loggers. When you set the logging level
for all loggers to “info”, you get a decent small amount
of information
about application progress. The debugging and especially the trace
@@ -201,7 +201,7 @@
it is wise to switch them on for one or several specific loggers. The
names of the loggers can be found in the source files. Many loggers
bear the name of their package, their class or of a superclass.</p>
- </section>
+ </section>
</body>
</document>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/faq.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/faq.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/faq.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/faq.xml Thu Aug 23 11:30:05 2007
@@ -48,9 +48,9 @@
<faq id="doc-mgt">
<question>Where can I learn how the FOP docs and web site are built?</question>
<answer>
- <p>
- See FOP <link href="doc.html">Doc Management</link>. ;-)
- </p>
+ <p>
+ See FOP <link href="doc.html">Doc Management</link>. ;-)
+ </p>
</answer>
</faq>
</part>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/release.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/release.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/release.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/dev/release.xml Thu Aug 23 11:30:05 2007
@@ -37,18 +37,18 @@
<li>Determine whether this is a Release Candidate or a Release.</li>
<li>Determine whether further testing is required.</li>
<li>Commit any outstanding changes</li>
- <li>Create a branch called <code>branches/fop-v_vv</code></li>
- <li>Edit release notes (README and status.xml in the root).</li>
- <li>Update the index.xml and site.xml for the new version.</li>
+ <li>Create a branch called <code>branches/fop-v_vv</code></li>
+ <li>Edit release notes (<code>README</code> and <code>status.xml</code> in the root).</li>
+ <li>Update the <code>index.xml</code> and <code>site.xml</code> for the new version.</li>
<li>Update the version numbers in the release column on the
- compliance page; update the compliance in the release column
+ compliance page (<code>compliance.xml</code>); update the compliance in the release column
to the current state (development column).</li>
- <li>Update version number in build.xml (not to be merged back
+ <li>Update version number in <code>build.xml</code> (not to be merged back
into trunk).</li>
<li>Copy trunk documentation directory to a new directory with
the version number, and update any links and the .htaccess
file for redirections.</li>
- <li>Copy <code>test/fotree/disabled-testcases.xml</code> and
+ <li>Copy <code>test/fotree/disabled-testcases.xml</code> and
<code>test/layoutengine/disabled-testcases.xml</code> to the
new version directory
<code><version>/fotree/disabled-testcases.xml</code> and
@@ -56,40 +56,40 @@
Copy <code>known-issues.xml</code> to the new version
directory. Copy <code>knownissues-overview.xml</code> from the
previous to the new version directory.</li>
- <li>Delete the previous version directory.</li>
- <li>Build the dist files (<code>build[.sh] dist</code>)
+ <li>Delete the previous version directory.</li>
+ <li>Build the dist files (<code>build[.sh] dist</code>)
and upload them to your web directory on
<code>people.apache.org</code></li>
- <li>Ask on fop-dev to check the branch and the generated dist
+ <li>Ask on fop-dev to check the branch and the generated dist
files for errors.</li>
- <li>Tag the source tree with the release ID. For example, if the release is 0.93:
- <code>svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_93 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93</code></li>
+ <li>Tag the source tree with the release ID. For example, if the release is 0.94:
+ <code>svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_94 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_94</code></li>
<li>Make a fresh checkout with the just created tag:
- <code>svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93</code></li>
+ <code>svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_94</code></li>
<li>Copy jimi and jai to lib/ (jimi-1.0.jar, jai_core.jar, jai_codec.jar)</li>
<li>Copy jce-jdk13-119.jar from <link href="http://www.bouncycastle.org/latest_releases.html">
from http://www.bouncycastle.org/latest_releases.html</link> to lib/</li>
- <li>Copy the hyphenation patterns jar file
+ <li>Copy the hyphenation patterns jar file
<code>fop-hyph.jar</code> to lib/ (e.g. from
<code>http://sourceforge.net/projects/offo</code></li>
<li>Alternatively, create a build-local.properties file that points to the above libs.</li>
<li>Run build[.sh] dist. Do this once using Sun JDK 1.3.1_15 or later and once with Sun JDK 1.4.2_08 or later. A Forrest installation is needed.</li>
<li>Create signatures. Don't forget to upload your KEY:
- <code>gpg -a -b --force-v3-sigs fop-0.93-src.tar.gz</code> etc.</li>
+ <code>gpg -a -b --force-v3-sigs fop-0.94-src.tar.gz</code> etc.</li>
<li>Upload the dist and signature files to your web directory
on people.apache.org (An account on minotaur is needed):
- <code>scp fop-0.93*.tar.gz*
+ <code>scp fop-0.94*.tar.gz*
chrisg@people.apache.org:public_html/</code></li>
<li>Check permissions:
<code>chmod 664 ... ; chgrp xmlgraphics ...</code></li>
- <li>Add MD5 sums: <code>md5 fop-0.93-src.tar.gz >
- fop-0.93-src.tar.gz.md5</code> etc.</li>
+ <li>Add MD5 sums: <code>md5 fop-0.94-src.tar.gz >
+ fop-0.94-src.tar.gz.md5</code> etc.</li>
<li>Make a test download.</li>
- <li>Start a vote for the release on
+ <li>Start a vote for the release on
<code>general@xmlgraphics.a.o</code>. The message should point
to the release files and list the MD5 sums (<code>cat
*.md5</code>). The vote is open for 72hrs.</li>
- <li>When the release is accepted, copy the release files,
+ <li>When the release is accepted, copy the release files,
their md5 sum files and the signature files to
/www/www.apache.org/dist/xmlgraphics/fop/ in the
subdirectories <code>source</code> and
@@ -98,10 +98,10 @@
the previous version.</li>
<li>Update HEADER.html and README.html in people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/</li>
<li>Wait 24 hours (for the mirrors to catch up).</li>
- <li>Merge the changes of the subversion release branch back
+ <li>Merge the changes of the subversion release branch back
into trunk (not the version number in the build file) and
delete the branch.</li>
- <li>Deploy the updated documentation to the FOP website.</li>
+ <li>Deploy the updated documentation to the FOP website.</li>
<li>Post announcements on fop-dev and fop-user and other related mailing lists.</li>
<li>Ask a Bugzilla admin (Christian Geisert) to add a bugzilla
entry for the new release id, or create an issue at
@@ -131,7 +131,7 @@
<li>general@xmlgraphics.apache.org</li>
<li>general@xml.apache.org</li>
<li>announce@apache.org (from your apache.org address)</li>
- <li>xsl-list@lists.mulberrytech.com (subscriber-only)</li>
+ <li>xsl-list@lists.mulberrytech.com (subscriber-only)</li>
<li>XSL-FO@yahoogroups.com (subscriber-only)</li>
<li>www-xsl-fo@w3.org</li>
<li>docbook-apps@lists.oasis-open.org (subscriber-only)</li>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/download.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/download.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/download.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/download.xml Thu Aug 23 11:30:05 2007
@@ -56,13 +56,6 @@
<section id="source">
<title>Source Download</title>
<p>
- You must first determine which of the two main development branches you wish
- to download, "maintenance" or "redesign". See
- <link href="dev/index.html">Development Introduction</link> for more details
- on the choices, and for the CVS tags to use when downloading the "maintenance"
- branch.
- </p>
- <p>
There are several ways to obtain a source distribution. Please note that they
are listed from least current to most current:
</p>
@@ -70,8 +63,7 @@
<li>
Download a released version from a
<link href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop">FOP Distribution mirror</link>.
- Source distributions include "-src" in their names. Please note that official
- releases currently are <em>only</em> made from the "maintenance" branch.
+ Source distributions include "-src" in their names.
</li>
<!--li>
Download a CVS snapshot from the cvs files
@@ -92,40 +84,21 @@
<p/>
<table>
<tr>
- <th colspan="2">Old Maintenance Branch (for 0.20.5)</th>
- </tr>
- <tr>
- <td>Repository URL</td>
- <td>
- <link href="http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_20_2-maintain/">
- <code>http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_20_2-maintain/</code>
- </link>
- </td>
- </tr>
- <tr>
- <td>Web view</td>
- <td>
- <link href="http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_20_2-maintain/">
- <code>http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_20_2-maintain/</code>
- </link>
- </td>
- </tr>
- <tr>
<th colspan="2">Latest Release</th>
</tr>
<tr>
<td>Repository URL</td>
<td>
- <link href="http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93/">
- <code>http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_93/</code>
+ <link href="http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_94/">
+ <code>http://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_94/</code>
</link>
</td>
</tr>
<tr>
<td>Web view</td>
<td>
- <link href="http://svn.apache.org/viewvc/xmlgraphics/fop/tags/fop-0_93/">
- <code>http://svn.apache.org/viewvc/xmlgraphics/fop/tags/fop-0_93/</code>
+ <link href="http://svn.apache.org/viewvc/xmlgraphics/fop/tags/fop-0_94/">
+ <code>http://svn.apache.org/viewvc/xmlgraphics/fop/tags/fop-0_94/</code>
</link>
</td>
</tr>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/examples.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/examples.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/examples.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/examples.xml Thu Aug 23 11:30:05 2007
@@ -44,9 +44,9 @@
</tr>
</table>
<p>Other basic examples on the use of XSL-FO can be found in the FOP distribution in
- the subdirectory xml-fop/examples/fo. You can start transformation of all fo files into pdf
- files by starting xml-fop/examples/fo/runtests (only source distribution). The resulting test
- files can be found in xml-fop/examples/fo/tests
+ the subdirectory examples/fo. You can start transformation of all fo files into pdf
+ files by running ant in this directory (only source distribution). The resulting test
+ files can be found in examples/fo/tests
</p>
<p>At the moment the following files are part of the distribution:</p>
<ul>
@@ -85,7 +85,7 @@
Developers will find the first steps to a test suite for all implemented
formatting objects and properties in xml-fop/test/xml/.
</p>
- </section>
+ </section>
<section>
<title>Images Examples</title>
<p>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml Thu Aug 23 11:30:05 2007
@@ -70,9 +70,9 @@
for XSL (FO) documents.
</p>
<p>
- <link href="http://xml.apache.org/batik">Batik</link> can be used with
+ <link href="http://xmlgraphics.apache.org/batik">Batik</link> can be used with
FOP to <link
- href="http://xml.apache.org/batik/svgrasterizer.html">transcode an SVG
+ href="http://xmlgraphics.apache.org/batik/svgrasterizer.html">transcode an SVG
image</link> into a PDF document.
</p>
</answer>
@@ -83,7 +83,7 @@
<p>
XSL is a W3C standard concerned with publishing XML documents. It
consists of two parts: <link href="#XSLT">XSLT</link> and <link
- href="#XSLFO">XSLFO</link>. The acronym expands to
+ href="#XSLFO">XSL-FO</link>. The acronym expands to
e<strong>X</strong>tensible <strong>S</strong>tylesheet
<strong>L</strong>anguage.
</p>
@@ -138,10 +138,10 @@
<p>
When it's ready and the committers have enough time to go through
the time-consuming process of creating a release. We
- released version 0.93 on 9 January 2007, and intend to
- release version 1.0 later in 2007. If you
- want to speed up the process, consider to
- <link href="dev/index.html#involved">contribute</link> to FOP.</p>
+ released version 0.94 on XX August 2007, and intend to
+ release version 1.0 later in late 2007 or early 2008. If you
+ want to speed up the process, consider
+ <link href="dev/index.html#involved">contributing</link> to FOP.</p>
</answer>
</faq>
<faq id="redesign">
@@ -170,13 +170,13 @@
<title>Problems running FOP</title>
<faq id="no-page-master">
<question>I get the error: [ERROR]: 'master-reference' for
- 'fo:page-sequence'matches no 'simple-page-master' or
+ 'fo:page-sequence' matches no 'simple-page-master' or
'page-sequence-master'</question>
<answer>
<p>
FOP was changed to be in accordance with the latest standard (see
- <link href="resources.html#w3-xsl">XSL standard</link>).The page
- master for a fo:page-sequence is now refereced by the
+ <link href="resources.html#specs-xslfo">XSL standard</link>).The page
+ master for a fo:page-sequence is now referenced by the
master-reference attribute. Replace the master-name attributes of
your fo:page-sequence elements by master-reference attributes. You
have to do this also for fo:single-page-master-reference,
@@ -211,7 +211,7 @@
If you run FOP embedded in your servlet, web application or
other Java application, check the classpath of the
application. Check the also the information pertaining to <link
- href="0.93/servlets.html#servlet-engine">servlet engines</link>
+ href="0.94/servlets.html#servlet-engine">servlet engines</link>
for further hints.
</p>
<p>
@@ -241,7 +241,7 @@
<question>I get an OutOfMemoryException.</question>
<answer>
<p>
- See <link href="0.93/running.html#memory">FOP Memory</link>.
+ See <link href="0.94/running.html#memory">FOP Memory</link>.
</p>
</answer>
</faq>
@@ -295,14 +295,14 @@
whether you got them right.
</p>
<p>
- You may find it helpful to use the <link href="#FO-validate">validation tools</link> to validate your
+ You may find it helpful to use the <link href="#fo-validate">validation tools</link> to validate your
FO document. This will catch most problems, but should not be
relied upon to catch all.
</p>
<p>
If you use XSLT, problems in your style sheet and in your
source XML also can produce a NullPointerException. <link
- href="0.93/running.html#check-input">Run the transformation
+ href="0.94/running.html#check-input">Run the transformation
separately</link> to check for this, usually you'll get a
detailed error message from the XSLT processor.
</p>
@@ -336,7 +336,7 @@
</p>
<p>
If you called the FOP command line application from some other
- programm, for example from Java using Runtime.exec(), it may hang
+ program, for example from Java using Runtime.exec(), it may hang
while trying to write log entries to the output pipe. You have to read
the FOP output regularly to empty the pipe buffer. It is best to avoid
exec'ing FOP, use the library interface instead.
@@ -368,8 +368,8 @@
<question>FOP does not find my fonts.</question>
<answer>
<p>
- Did you get: «Failed to read font metrics file C:\foo\arial.xml
- : File "C:\foo\arial.xml" not found»? The value for the
+ Did you get: “Failed to read font metrics file C:\foo\arial.xml
+ : File "C:\foo\arial.xml" not found”? The value for the
metrics-file attribute in the user config file is actually an URL, not
a file name. Use "file:///C:/foo/arial.xml" instead.
</p>
@@ -380,7 +380,7 @@
</p>
<p>
Try also setting the <link
- href="0.93/configuration.html#general-elements">font-base
+ href="0.94/configuration.html#general-elements">font-base
configuration</link>.
</p>
</answer>
@@ -389,7 +389,7 @@
<part id="part-output">
<title>Problems with FOP output</title>
<faq id="leader-expansion">
- <question>Leaders don't work anymore in 0.93. Instead of
+ <question>Leaders don't work anymore in 0.94. Instead of
filling the line, only three dots or a short ruler is
output.</question>
<answer>
@@ -410,7 +410,7 @@
The new implementation uses leader-length.optimum to
determine where to break the line, and expands the leader
only further if the line should be filled, as indicated by
- the text-aling and text-align-last properties.
+ the text-align and text-align-last properties.
</p>
<p>
Actually due to the fuzzyness of the specification both the
@@ -432,7 +432,7 @@
</p>
<p>
The <link
- href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#force-page-count">force-page-count
+ href="http://www.w3.org/TR/xsl11/#force-page-count">force-page-count
property</link> controls how a FO processor pads page sequences in
order to get certain page counts or last page numbers. The default is
"<code>auto</code>". With this setting, if the next page sequence
@@ -470,7 +470,7 @@
<p>Other possibilities:</p>
<ul>
<li>The image format is not supported or not supported completely.
- See <link href="0.93/graphics.html">FOP Graphics Formats</link> for a
+ See <link href="0.94/graphics.html">FOP Graphics Formats</link> for a
list of supported formats and related issues.</li>
<li>The graphic may be too large to fit into the intended space.</li>
<li>There may be something (static content) that is obscuring the
@@ -482,14 +482,14 @@
<faq id="png-fails">
<question>My graphical images do not work properly.</question>
<answer>
- <p>See <link href="0.93/graphics.html">FOP Graphics Formats</link> for a
+ <p>See <link href="0.94/graphics.html">FOP Graphics Formats</link> for a
list of supported graphics formats and related issues.</p>
</answer>
</faq>
<faq id="graphic-resolution">
<question>Why is my graphic rendered at a different resolution than it was created?</question>
<answer>
- <p>See <link href="0.93/graphics.html#resolution">Graphics Resolution</link>.</p>
+ <p>See <link href="0.94/graphics.html#resolution">Graphics Resolution</link>.</p>
</answer>
</faq>
<faq id="keep-with">
@@ -582,9 +582,9 @@
<answer>
<p>
This is usually caused by setting a "height" on a table-row or table-cell and when
- the content is higher that the specified height. By setting "height" (a so-called
+ the content is higher than the specified height. By setting "height" (a so-called
corresponding property) you
- <link href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice5.html#section-N6057-Height,-and-Width-Properties">implicitely set</link>
+ <link href="http://www.w3.org/TR/xsl11/#d0e4413">implicitely set</link>
block-progression-dimension.minimum, block-progression-dimension.optimum and
block-progression-dimension.maximum to the same value. You'll get some information
about that in the warning message. Look for something like:
@@ -592,10 +592,10 @@
</p>
<p>
Assuming you set the height on the table-row to 14pt and your content is 75pt high,
- a constraint (maximum=14pt) is violated. Normally, you just want want to make sure
+ a constraint (maximum=14pt) is violated. Normally, you just want to make sure
with the "height" property that the row has a minimum height. If that is so, the
right solution is to specify block-progression-dimension.minimum="14pt" instead of
- heigth="14pt".
+ height="14pt".
</p>
</answer>
</faq>
@@ -621,7 +621,7 @@
<answer>
<p>Make sure you have set the language and optionally the country attributes for an appropriate XSL-FO element (fo:page-sequence, fo:block or fo:character):</p>
<source><![CDATA[<fo:page-sequence language="fi">]]></source>
- <p>See <link href="0.93/hyphenation.html#support">Hyphenation Support</link> for details and instructions on using hyphenation with FOP.</p>
+ <p>See <link href="0.94/hyphenation.html#support">Hyphenation Support</link> for details and instructions on using hyphenation with FOP.</p>
<p>Explicitly enable hyphenation for an appropriate XSL-FO element (fo:block, fo:character):</p>
<source><![CDATA[<fo:block hyphenate="true">]]></source>
</answer>
@@ -652,7 +652,7 @@
<question>How do I use FOP in a servlet?</question>
<answer>
<p>
- See <link href="0.93/servlets.html">Using FOP in a Servlet</link>.
+ See <link href="0.94/servlets.html">Using FOP in a Servlet</link>.
</p>
</answer>
</faq>
@@ -661,7 +661,7 @@
transformation?</question>
<answer>
<p>
- See <link href="0.93/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
+ See <link href="0.94/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
</p>
</answer>
</faq>
@@ -669,7 +669,7 @@
<question>How do I pass parameters to the XSLT transformation?</question>
<answer>
<p>
- See <link href="0.93/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
+ See <link href="0.94/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</link>.
</p>
</answer>
</faq>
@@ -687,7 +687,7 @@
<question>How do I set the baseDir property in a servlet environment?</question>
<answer>
<p>
- See <link href="0.93/embedding.html#config-internal">Setting the Configuration Programmatically</link>.
+ See <link href="0.94/embedding.html#config-internal">Setting the Configuration Programmatically</link>.
</p>
</answer>
</faq>
@@ -695,7 +695,7 @@
<question>How do I use a user configuration file from a servlet?</question>
<answer>
<p>
- See <link href="0.93/embedding.html#config-external">Using a Configuration File in an Embedded App</link>.
+ See <link href="0.94/embedding.html#config-external">Using a Configuration File in an Embedded App</link>.
</p>
</answer>
</faq>
@@ -704,7 +704,7 @@
get FOP working for various servlet engines?</question>
<answer>
<p>
- See <link href="0.93/servlets.html#servlet-engine">Servlet Engines</link>.
+ See <link href="0.94/servlets.html#servlet-engine">Servlet Engines</link>.
</p>
</answer>
</faq>
@@ -712,7 +712,7 @@
<question>Can FOP be used in multithreaded environments?</question>
<answer>
<p>
- See <link href="0.93/embedding.html#multithreading">Multithreading FOP</link>.
+ See <link href="0.94/embedding.html#multithreading">Multithreading FOP</link>.
</p>
</answer>
</faq>
@@ -723,13 +723,13 @@
<question>The rendering of SVG text in my PDF is of poor quality.
Can I control this?</question>
<answer>
- <p>See <link href="0.93/graphics.html#svg-pdf-text">Placing SVG Text into PDF</link>.</p>
+ <p>See <link href="0.94/graphics.html#svg-pdf-text">Placing SVG Text into PDF</link>.</p>
</answer>
</faq>
<faq id="svg-headless">
<question>How do I use FOP with SVG on headless servers?</question>
<answer>
- <p>See <link href="0.93/graphics.html#batik">FOP: Graphics (Batik)</link>.</p>
+ <p>See <link href="0.94/graphics.html#batik">FOP: Graphics (Batik)</link>.</p>
</answer>
</faq>
<faq id="svghangs">
@@ -792,7 +792,7 @@
<faq id="svg-scaling">
<question>Why is my SVG rendered at a size different from that specified in my fo:external-graphic element?</question>
<answer>
- <p>See <link href="0.93/graphics.html#svg-scaling">SVG Scaling</link>.</p>
+ <p>See <link href="0.94/graphics.html#svg-scaling">SVG Scaling</link>.</p>
</answer>
</faq>
<faq id="svg-attribute-required">
@@ -825,7 +825,7 @@
<question>How do I embed fonts in PDF?</question>
<answer>
<p>
- See the <link href="0.93/fonts.html">Fonts</link> page for information
+ See the <link href="0.94/fonts.html">Fonts</link> page for information
about embedding fonts.
</p>
</answer>
@@ -844,7 +844,7 @@
set. For a variety of reasons, even those are not completely
guaranteed to work, for example you can't use the fi
ligature from the standard serif font. Check the <link
- href="0.93/output.html#pdf-fonts">overview</link> for the default
+ href="0.94/output.html#pdf-fonts">overview</link> for the default
PDF fonts.
</p>
<p>
@@ -852,7 +852,7 @@
the desired character. Furthermore the font must be
available on the machine where the PDF is viewed or it must
have been embedded in the PDF file. See <link
- href="0.93/fonts.html">embedding fonts</link>.
+ href="0.94/fonts.html">embedding fonts</link>.
</p>
<p>
For most symbols, it is better to select the symbol font
@@ -870,7 +870,7 @@
<faq id="pdf-postprocess">
<question>What tools are available for post-processing my PDF document?</question>
<answer>
- <p>See <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
+ <p>See <link href="0.94/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
</answer>
</faq>
<faq id="pdf-security">
@@ -878,8 +878,8 @@
to my PDF document?</question>
<answer>
<p>
- See <link href="0.93/pdfencryption.html">PDF Encryption</link>.
- See also <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.
+ See <link href="0.94/pdfencryption.html">PDF Encryption</link>.
+ See also <link href="0.94/output.html#pdf-postprocess">PDF Post-processing</link>.
</p>
</answer>
</faq>
@@ -887,13 +887,13 @@
<question>How do I add document properties (title, author, etc.) to my
PDF document?</question>
<answer>
- <p>See <link href="0.93/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
+ <p>See <link href="0.94/output.html#pdf-postprocess">PDF Post-processing</link>.</p>
</answer>
</faq>
<faq id="pdf-watermark">
<question>How do I add watermarks to my PDF document?</question>
<answer>
- <p>See <link href="0.93/output.html#pdf-watermark">PDF Watermarks</link>.</p>
+ <p>See <link href="0.94/output.html#pdf-watermark">PDF Watermarks</link>.</p>
</answer>
</faq>
<faq id="pdf-print-contortion">
@@ -912,11 +912,6 @@
<question>How do I control the Acrobat bookmark display?</question>
<answer>
<p>
- FOP 0.20.5 does not support this feature. Possible workarounds
- include those mentioned in the <link href="0.93/output.html#pdf-postprocess">PDF
- Post-Processing FAQ</link>.
- </p>
- <p>
FOP versions 0.93 and later support the starting-state property of the XSL 1.1
<link href="http://www.w3.org/TR/xsl11/#fo_bookmark">fo:bookmark</link>
element which can be used for this. The color, font-style and
@@ -934,7 +929,7 @@
<answer>
<p>
This is a problem of Internet Explorer requesting the content several
- times. Please see the <link href="0.93/servlets.html#ie">notes on Internet Explorer</link>
+ times. Please see the <link href="0.94/servlets.html#ie">notes on Internet Explorer</link>
for more information.
</p>
</answer>
@@ -955,7 +950,7 @@
For the second task, you can use some client side script to start
Acrobat Reader in print mode, or use a Java applet based on the FOP
print servlet. This depends heavily on the client installation and
- should not relied on except in tightly controlled environments.
+ should not be relied on except in tightly controlled environments.
</p>
<p>
See also <link href="http://marc.theaimsgroup.com/?l=fop-dev&m=101065988325115&w=2">http://marc.theaimsgroup.com/?l=fop-dev&m=101065988325115&w=2</link>
@@ -1114,21 +1109,21 @@
<question>Can I use FOP to convert XHTML or HTML files to PDF?</question>
<answer>
<p>
- You will get better results if you transform your source
- XML directly into XSLFO. It is tempting to use the
- XML->XHTML->XSLFO approach, because this apparently means
- there's only one transformation to maintain, but XHTML
- and publishing grade PDF are dissimilar enough that an
- "generic" XHTML->XSLFO(PDF) usually wont cut it, because
- the XHTML already lacks information from the original XML.
- It may be worthwhile to go from the source XML to an
- intermediate custom XML which on one hand is close enough
- to representation to allow simple transformation to either
- XHTML or XSLFO for most of the structure, but on the other
- hand retains enough semantic from the original XML that
- elements which must be handled differently in the two
- representations can be handled differently. Setting this
- up requires experience and most likely extensive prototyping.
+ You will get better results if you transform your source
+ XML directly into XSLFO. It is tempting to use the
+ XML->XHTML->XSLFO approach, because this apparently means
+ there's only one transformation to maintain, but XHTML
+ and publishing grade PDF are dissimilar enough that an
+ "generic" XHTML->XSLFO(PDF) usually wont cut it, because
+ the XHTML already lacks information from the original XML.
+ It may be worthwhile to go from the source XML to an
+ intermediate custom XML which on one hand is close enough
+ to representation to allow simple transformation to either
+ XHTML or XSLFO for most of the structure, but on the other
+ hand retains enough semantic from the original XML that
+ elements which must be handled differently in the two
+ representations can be handled differently. Setting this
+ up requires experience and most likely extensive prototyping.
</p>
</answer>
</faq>
@@ -1136,11 +1131,11 @@
<question>I know it may be a bad idea to use FOP to convert XHTML or HTML files to PDF, but I want to do it anyway. Are there any tools available to help me?</question>
<answer>
<p>
- The <link href="resources.html">FOP Resources page</link> has links
- to a tool called <link href="http://html2fo.sourceforge.net/">html2fo</link>
- which can be used to make such a transformation. In addition, there
- are tools on the Antenna House <link href="http://www.antennahouse.com/XSLsample/XSLsample.htm">XSL-FO Tutorial and Sample</link>
- page.
+ The <link href="resources.html">FOP Resources page</link> has links
+ to a tool called <link href="http://html2fo.sourceforge.net/">html2fo</link>
+ which can be used to make such a transformation. In addition, there
+ are tools on the Antenna House <link href="http://www.antennahouse.com/XSLsample/XSLsample.htm">XSL-FO Tutorial and Sample</link>
+ page.
</p>
</answer>
</faq>
@@ -1150,9 +1145,9 @@
<faq id="doc-mgt">
<question>Where can I learn how the FOP docs and web site are built?</question>
<answer>
- <p>
- See FOP <link href="dev/doc.html">Doc Management</link>. ;-)
- </p>
+ <p>
+ See FOP <link href="dev/doc.html">Doc Management</link>. ;-)
+ </p>
</answer>
</faq>
</part>
@@ -1196,7 +1191,7 @@
<li>
In the case where something works properly with another formatter,
(AntennaHouse, PassiveTex, etc.) but doesn't work with FOP, please
- check the <link href="relnotes.html">Release Notes</link>, the
+ check the <!--link href="relnotes.html"-->Release Notes<!--/link-->, the
<link href="compliance.html">FOP Standards Compliance</link> document,
and the remaining FAQ in this document. If not found there, look at the
list of <link href="bugs.html#issues_existing">Bugs Already Reported</link>.
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/fo.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/fo.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/fo.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/fo.xml Thu Aug 23 11:30:05 2007
@@ -31,7 +31,7 @@
FOP uses XSL-FO as input.
It is the responsibility of the user to make sure that the XSL-FO submitted to FOP is correct.
The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another
-good FAQ is <fork href="http://www.dpawson.co.uk/xsl/xslfaq.html">Dave Pawson's XSL FAQ</fork>.
+good FAQ is <fork href="http://www.dpawson.co.uk/xsl/">Dave Pawson's XSL FAQ</fork>.
</p>
</section>
<section id="xml">
@@ -92,7 +92,7 @@
<section id="xml-encoding">
<title>Encoding Issues</title>
<p>
- If the parser complains about illegal bytes or characters in the input, or there are unexpected characters in the output, this is usually is the result of a character encoding problem.
+ If the parser complains about illegal bytes or characters in the input, or there are unexpected characters in the output, this is usually the result of a character encoding problem.
See the <link href="http://www.dpawson.co.uk/xsl">XSL FAQ</link> for additional information.
Many software packages that produce XML, including XSLT processors, use UTF-8 encoding as a default.
If you view their output with something not aware of the encoding, like Notepad for Win95/98/ME/NT, funny characters are displayed. A Å is a giveaway.
@@ -350,13 +350,14 @@
<section id="fo-preformat">
<title>Preformatting Content</title>
<p>
- Sometimes it is desirable to retain linebreaks and hard spaces, and to get preformatted text to pass through without being changed.
-The XSL-FO specification provides some properties for this: <link href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#white-space-collapse">white-space-collapse</link> and <link href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#linefeed-treatment">linefeed-treatment</link>.
-In FOP, use white-space-collapse="false" on an enclosing block.
+ Sometimes it is desirable to retain linebreaks and hard spaces, and to get
+ preformatted text to pass through without being changed. The XSL-FO
+ specification provides some properties for this: <link
+ href="http://www.w3.org/TR/xsl11/#white-space-collapse">white-space-collapse</link>
+ and <link
+ href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#white-space-collapse">linefeed-treatment</link>.
+ In FOP, use white-space-collapse="false" on an enclosing block.
</p>
- <warning>
- Due to a bug in FOP 0.20.5, setting white-space-collapse="false" will also preserve line breaks in the text. Do not rely on this behavior, as it is non-conformant and has changed in FOP 0.93.
- </warning>
</section>
<section id="fo-total-pages">
<title>Total Document Pages</title>
@@ -447,7 +448,7 @@
</p>
<ul>
<li>
- Horizontal lines can be drawn using <link href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice6.html#fo_leader">fo:leader</link>.
+ Horizontal lines can be drawn using <link href="http://www.w3.org/TR/xsl11/#fo_leader">fo:leader</link>.
</li>
<li>
Use a solid border on a suitable fo:block. This will work for horizontal and vertical lines only.
@@ -463,9 +464,12 @@
<link href="http://www.renderx.com">RenderX</link> has provided an <link href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for FO Documents</link>, which may be helpful in validating general FO issues.
</p>
<p>
- FOP also maintains an <link href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop.xsd?view=co">Unofficial FOP Schema</link> in the FOP CVS Repository.
-This document can be used either to validate against the FO standard, or against the actual FOP implementation.
-See the notes near the beginning of the document for instructions on how to use it.
+ FOP also maintains an <link
+ href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop.xsd?view=co">Unofficial
+ FOP Schema</link> in the FOP Subversion Repository. This document can be used
+ either to validate against the FO standard, or against the actual FOP
+ implementation. See the notes near the beginning of the document for
+ instructions on how to use it.
</p>
</section>
<section id="landscape">
@@ -484,8 +488,8 @@
</section>
<section id="external-resources">
<title>External Resources</title>
- <p>Resources needed by an XSL-FO file that are external to it (graphics, for example), are defined in the XSL-FO standard as being of type "uri-specification". This is defined in the standard at <jump href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice5.html#section-N8794-Property-Datatypes">Section 5.11 Property Datatypes</jump>, which includes a link to the URI standard itself. Refer to the XSL-FO and URI standards themselves for more detailed instructions.</p>
- <p>URIs may be either absolute or relative to a base URI. (See <link href="0.20.5/configuration.html">FOP: Configuration</link> for information on setting the base URI for a FOP session). Here is an example referencing an external-graphic that is relative to the base URI:</p>
+ <p>Resources needed by an XSL-FO file that are external to it (graphics, for example), are defined in the XSL-FO standard as being of type "uri-specification". This is defined in the standard at <jump href="http://www.w3.org/TR/xsl11/#datatype">Section 5.11 Property Datatypes</jump>, which includes a link to the URI standard itself. Refer to the XSL-FO and URI standards themselves for more detailed instructions.</p>
+ <p>URIs may be either absolute or relative to a base URI. (See <link href="0.94/configuration.html">FOP: Configuration</link> for information on setting the base URI for a FOP session). Here is an example referencing an external-graphic that is relative to the base URI:</p>
<source><![CDATA[<fo:external-graphic src="url('images/logo.jpg')"/>]]></source>
<p>Here is an example referencing an external-graphic that is an absolute URI on a local filesystem:</p>
<source><![CDATA[fo:external-graphic src="url('file:d:///images/logo.jpg')"/>]]></source>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/index.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/index.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/index.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/index.xml Thu Aug 23 11:30:05 2007
@@ -26,25 +26,19 @@
<body>
<section id="intro">
<title>Introduction</title>
- <p>Apache FOP (Formatting Objects Processor) is the world's first print formatter driven by XSL formatting
- objects (XSL-FO) and the world's first output independent formatter. It is a
- Java application that reads a formatting object (FO) tree and
- renders the resulting pages to a specified output. <link href="0.20.5/output.html">Output formats</link>
- currently supported include PDF, PCL, PS, SVG, XML (area tree representation),
- Print, AWT, MIF and TXT.
- The primary output target is PDF.
- </p>
+ <p>Apache FOP (Formatting Objects Processor) is a print formatter driven by XSL
+ formatting objects (XSL-FO) and an output independent formatter. It is a Java
+ application that reads a formatting object (FO) tree and renders the resulting
+ pages to a specified output. <link href="0.94/output.html">Output formats</link>
+ currently supported include PDF, PS, PCL, AFP, XML (area tree representation),
+ Print, AWT and PNG, and to a lesser extent, RTF and TXT. The primary output target is PDF.
+ </p>
<figure width="480" height="260" src="images/document.jpg" alt="Render Diagram" />
<p>
- The previous version of FOP (<link href="0.20.5/">0.20.5</link>) is a partial implementation of the
- <link href="http://www.w3.org/TR/2001/REC-xsl-20011015/">XSL-FO Version 1.0
- W3C Recommendation</link>.
- </p>
- <p>
- The latest stable version of FOP (<link href="0.93/">0.93</link>) is the first stable release
- after a large redesign effort and implements a larger subset than 0.20.5 of the
- <link href="http://www.w3.org/TR/2001/REC-xsl-20011015/">XSL-FO Version 1.0 W3C Recommendation</link>
- as well as some parts of the <link href="http://www.w3.org/TR/xsl11">XSL-FO Version 1.1 Working Draft</link>.
+ The latest stable version of FOP (<link href="0.94/">0.94</link>) is the second
+ stable release after a large redesign effort and implements a large subset of the
+ <link href="http://www.w3.org/TR/xsl11/">XSL-FO Version 1.1 W3C
+ Recommendation</link>.
</p>
<p>
Support for each of the standard's objects and properties is detailed in <link href="compliance.html">FOP Compliance</link>.
@@ -63,22 +57,21 @@
</p>
<p>
FOP uses the standard XSL-FO file format as input, lays the content out into pages, then renders it to the requested output.
-One great advantage to using XSL-FO as input is that XSL-FO is itself an XML file, which means that it can be conveniently created from a variety of sources.
+One great advantage of using XSL-FO as input is that XSL-FO is itself an XML file, which means that it can be conveniently created from a variety of sources.
The most common method is to convert semantic XML to XSL-FO, using an XSLT transformation.</p>
</section>
<section id="objectives">
<title>FOP Objectives</title>
- <p>The goals of the Apache FOP project are to deliver an XSL-FO to PDF formatter that is compliant to at least the Basic
- conformance level described in the W3C Recommendation from 15 October 2001, and that complies with the 11 March 1999 Portable Document
- Format Specification (Version 1.3) from Adobe Systems.
+ <p>The goals of the Apache FOP project are to deliver an XSL-FO to PDF formatter that
+ is compliant to at least the Basic conformance level described in the W3C
+ Recommendation from 05 December 2006, and that complies with the November 2001
+ Portable Document Format Specification (Version 1.4) from Adobe Systems.
</p>
<p>Conformance to the XML 1.0 Recommendation, XSLT 1.0 Recommendation and the XML Namespaces Recommendation is
understood. Other relevant documents, such as the XPath and XLink Working Drafts, are referenced as necessary. The FOP
Project will attempt to use the latest version of evolving specifications.
</p>
-
- <p>The FOP layout system is currently being rewritten to better support the XSL-FO standard.</p>
</section>
<note>
The PDF files on this site are created using Apache FOP.
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/maillist.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/maillist.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/maillist.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/maillist.xml Thu Aug 23 11:30:05 2007
@@ -78,7 +78,11 @@
<li>Have you read <link href="#general">Mailing List General Information</link>? If not please do so before proceeding.</li>
<li>Have you stated the version of FOP you are using? Please do so. Usually, it's a good idea to state the JDK/JRE version and the operating system you're using, too.</li>
<li>Have you included any detailed error messages? Please do so.</li>
- <li>Does a proper understanding of your question require inclusion of XSLT code, DocBook source, or other semantic XML? If so, the question is <em>almost certainly not appropriate to this list</em>. In general, the only input documents that are appropriate on this list are XSL-FO snippets. See <link href="0.20.5/running.html#running_xalan">Running Xalan</link> for instructions about capturing the XSL-FO document that is actually submitted to FOP. If you haven't examined the XSL-FO document yourself, then you are not yet prepared to formulate a FOP-specific question.</li>
+ <li>Does a proper understanding of your question require inclusion of XSLT code, DocBook
+ source, or other semantic XML? If so, the question is <em>almost certainly not
+ appropriate to this list</em>. In general, the only input documents that are
+ appropriate on this list are XSL-FO snippets. See <link
+ href="0.94/running.html#check-input">Running Xalan</link> for instructions about capturing the XSL-FO document that is actually submitted to FOP. If you haven't examined the XSL-FO document yourself, then you are not yet prepared to formulate a FOP-specific question.</li>
<li>If you are providing one or more XSL-FO snippets:
<ul>
<li>Have you reduced them to the shortest possible complete, <strong>self-contained</strong> document that demonstrates the problem? Please do so.</li>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/news.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/news.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/news.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/news.xml Thu Aug 23 11:30:05 2007
@@ -26,18 +26,26 @@
</header>
<body>
<section>
+ <title>XX August 2007 - Apache FOP 0.94 Released</title>
+ <p>The Apache FOP team is pleased to present you the second production
+ grade release of the new FOP codebase. This release contains many bug
+ fixes and new features. See the <a
+ href="0.94/releaseNotes_0.94.html">Release Notes</a> for a list of
+ the most important changes.</p>
+ </section>
+ <section>
<title>26 January 2007 - New Committer</title>
<p>Welcome Jay Bryant!</p>
</section>
- <section>
- <title>9 January 2007 - Apache FOP 0.93 released</title>
+ <section>
+ <title>9 January 2007 - Apache FOP 0.93 released</title>
<p>
The Apache FOP team is proud to present to you the first
production grade release of the new FOP codebase. This release
has the new API first introduced in release 0.92 beta. It
contains again many bug fixes and new features.
</p>
- </section>
+ </section>
<section>
<title>16 October 2006 - New Committer</title>
<p>Welcome Vincent Hennebert!</p>
@@ -71,8 +79,8 @@
</p>
<p>
Please see also the
- <link href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/200511.mbox/%3c20051123002157.0EB0.JEREMIAS@apache.org%3e">announcement</link>
- and the <link href="relnotes.html#FOP+0.90+alpha+1">release notes</link>.
+ <link href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/200511.mbox/%3c20051123002157.0EB0.JEREMIAS@apache.org%3e">announcement</link>.
+ <!-- TODO re-enable and the <link href="relnotes.html#FOP+0.90+alpha+1">release notes</link>.-->
</p>
</section>
<section>
@@ -83,7 +91,7 @@
<title>20 October 2004 - Creation of the Apache XML Graphics project</title>
<p>
The Apache Board of Directors agreed to the creation of the
- <link href="http://xmlgrapics.apache.org">Apache XML Graphics</link>
+ <link href="http://xmlgraphics.apache.org">Apache XML Graphics</link>
project which will be comprised of Batik and FOP. Both former
Apache XML subprojects are in this way complying with the Board's desire
to improve project oversight. Both project teams also see additional
@@ -137,7 +145,8 @@
<p>
See also the full text of the
<link href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=fop-dev@xml.apache.org&msgNo=6067">
- announcement</link> and the <link href="relnotes.html#FOP+0.20.5">release notes</link>.
+ announcement</link>.
+ <!-- TODO re-enable and the <link href="relnotes.html#FOP+0.20.5">release notes</link>.-->
</p>
</section>
<section>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/relnotes.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/relnotes.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/relnotes.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/relnotes.xml Thu Aug 23 11:30:05 2007
@@ -44,11 +44,11 @@
</li>
<li>
The API has changed between 0.91beta this release.
- Please consult the <a href="0.93/upgrading.html">"Upgrading"</a> page for details.
+ Please consult the <a href="0.94/upgrading.html">"Upgrading"</a> page for details.
</li>
<li>
You may experience different behaviour compared to version 0.20.5.
- Please consult the <a href="0.93/upgrading.html">"Upgrading"</a> page for details.
+ Please consult the <a href="0.94/upgrading.html">"Upgrading"</a> page for details.
</li>
</ul>
<p>Known Issues:</p>
@@ -177,7 +177,7 @@
</li>
<li>
You may experience different behaviour compared to version 0.20.5.
- Please consult the <a href="0.93/upgrading.html">"Upgrading"</a> page indicated above for details.
+ Please consult the <a href="0.94/upgrading.html">"Upgrading"</a> page indicated above for details.
</li>
</ul>
<p>Known Issues:</p>
@@ -318,7 +318,7 @@
</li>
<li>
You may experience different behaviour compared to version 0.20.5.
- Please consult the <a href="0.93/upgrading.html">"Upgrading"</a> page indicated above for details.
+ Please consult the <a href="0.94/upgrading.html">"Upgrading"</a> page indicated above for details.
</li>
</ul>
<p>Known Issues:</p>
@@ -430,7 +430,7 @@
</section>
<section>
<title>FOP 0.20.5</title>
- <p>This is the last planned release in the 0.20.x series (aka maintenance branch).</p>
+ <p>This was the last release in the 0.20.x series (aka maintenance branch).</p>
<p>Important changes since the last release (0.20.4):</p>
<ul>
<li>Some hyphenation patterns (cs, da, de, de_DR, el, en, en_US, fr, nl,
@@ -461,7 +461,8 @@
<li>Links in PDF won't generate multiple link rectangles anymore. If this causes
a problem you can set the system property "links.merge" to "no".
</li>
- <li>FOP has been compiled with cryptography support. See <a href="0.20.5/pdfencryption.html">
+ <li>FOP has been compiled with cryptography support. See
+ <a href="0.94/pdfencryption.html">
PDF encryption</a> for details about installation and usage.
</li>
<li>The behaviour of leader has changed. See
@@ -496,7 +497,7 @@
support for additional truetype fonts in AWT Viewer.
</li>
<li>Logging has been changed from LogKit to Avalon's Logger Interface.
- (see <a href="0.20.5/embedding.html">Embedding</a> for details).
+ (see <a href="0.94/embedding.html">Embedding</a> for details).
</li>
<li>Building under JDK 1.4:
You need to add a method in
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/resources.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/resources.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/resources.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/resources.xml Thu Aug 23 11:30:05 2007
@@ -30,7 +30,7 @@
<section id="specs-xslfo">
<title>XSL-FO</title>
<ul>
- <li><jump href="http://www.w3.org/TR/2001/REC-xsl-20011015/">XSL-FO Recommendation (15 October 2001)</jump></li>
+ <li><jump href="http://www.w3.org/TR/xsl11/">XSL-FO Recommendation (05 December 2006)</jump></li>
<li><jump href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for the XSL-FO Recommendation</jump> provided by N. Grigoriev from RenderX.</li>
</ul>
</section>
@@ -87,7 +87,6 @@
<li>[online article] <jump href="http://www.xml.com/pub/a/2001/01/17/xsl-fo/index.html">Using XSL Formatting Objects</jump>, by J. David Eisenberg.</li>
<li>[online reference] <jump href="http://zvon.org/xxl/xslfoReference/Output/index.html">XSL FO reference</jump>, by Miloslav Nic.</li>
<li>[online reference] <jump href="http://www.dpawson.co.uk/xsl/sect3/index.html">Dave Pawson's XSL-FO FAQ</jump>.</li>
- <li>[online book] <jump href="http://www.dpawson.co.uk/xsl/sect3/bk/index.html">An introduction to XSL Formatting Objects</jump>, by Dave Pawson. See hardcopy version below.</li>
<li>[book] <jump href="http://www.oreilly.com/catalog/xslfo">XSL-FO</jump>, by Dave Pawson, O'Reilly & Associates, 2002, ISBN 0-596-00355-2. See online version above.</li>
<li>[book] <jump href="http://www.phptr.com/browse/product.asp?product_id={CEA527AF-412D-49DA-8C1F-46E0A519B8D8}">Definitive XSL-FO</jump>, by G. Ken Holman, Prentice Hall PTR, 2003, ISBN 0-131-40374-5.</li>
<li>[book] <jump href="http://www.sams.com/catalog/product.asp?product_id={F7ADFA46-6AF1-497C-9163-0D6337F727B3}">XSL Formatting Objects Developer's Handbook</jump>, by Doug Lovell, Sams, 2002, ISBN 0-672-32281-1.</li>
@@ -101,7 +100,7 @@
<li>[book] <jump href="http://wrox.com/books/1861005067.htm">XSLT Programmer's Reference</jump>, by Michael H. Kay, Wrox Press, ISBN 1-861-00506-7.</li>
<li>[book] <jump href="http://www.oreilly.com/catalog/xslt">XSLT</jump>, by Doug Tidwell, O'Reilly & Associates, 2001, ISBN 0-596-00053-7.</li>
<li>[book] <jump href="http://www.oreilly.com/catalog/xsltckbk">XSLT Cookbook</jump>, by Sal Mangano, O'Reilly & Associates, 2002, ISBN 0-596-00372-2.</li>
- <li>[article] <jump href="http://www.dpawson.co.uk/xsl/xslfaq.html">Dave Pawson's XSL FAQ</jump>.</li>
+ <li>[article] <jump href="http://www.dpawson.co.uk/xsl/index.html">Dave Pawson's XSL FAQ</jump>.</li>
<li>[book] <jump href="http://www.oreilly.com/catalog/xpathpointer">XPath and XPointer: Locating Content in XML Documents</jump>, by John E. Simpson, O'Reilly & Associates, 2002, ISBN 0-596-00291-2.</li>
<li>[book] <jump href="http://www.wiley.com/cda/product/0,,0471416207,00.html">XSL Essentials</jump>, by Michael Fitzgerald, John Wiley & Sons, 2001, ISBN 0-471-41620-7.</li>
<li>[book] <jump href="http://www.oreilly.com/catalog/javaxslt">Java and XSLT</jump>, by Eric M. Burke, O'Reilly & Associates, 2001, ISBN 0-596-00143-6.</li>
@@ -221,7 +220,6 @@
<li>[software] <jump href="http://www.scriptura-xsl.com">Scriptura</jump> by Inventive Designers (commercial)</li>
<li>[software] <jump href="http://www.xslfast.com">XSLfast</jump> by jCatalog Software AG (commercial)</li>
<li>[software] <jump href="http://www.metafocus.no/en/xultation_designer.php">Xultation Designer</jump> by Metafocus (commercial)</li>
- <li>[software] <jump href="http://www.cambridgedocs.com/products/downloads/WordFODesigner.htm">Word FO Designer</jump> by CambridgeDocs (commercial)</li>
<li>[software] <jump href="http://web.assentis.com/products/products.php?navi=Products&product_id=7">Assentis:DocDesign</jump> by Assentis Technologies (commercial)</li>
</ul>
</section>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/site.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/site.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/site.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/site.xml Thu Aug 23 11:30:05 2007
@@ -55,11 +55,15 @@
-->
<!--
- BEGIN Version 0.20.5 tab
+ BEGIN Version 0.93 documentation tab
-->
- <v0205 label="Version 0.20.5" href="0.20.5/" tab="maintenanceversion">
+ <trunk label="FOP 0.93" href="0.93/" tab="oldstableversion">
<about label="About" href="index.html"/>
-
+ <release label="Release Notes" href="releaseNotes_0.93.html"/>
+ <changes label="Changes" href="changes_0.93.html"/>
+ <knownissues label="Known Issues" href="knownissues_overview.html"/>
+ <upgrading label="Upgrading" href="upgrading.html"/>
+
<using label="Using FOP">
<build label="Build" href="compiling.html"/>
<config label="Configure" href="configuration.html"/>
@@ -68,29 +72,31 @@
<servlet label="Servlets" href="servlets.html"/>
<ant label="Ant Task" href="anttask.html"/>
</using>
-
+
<features label="Features">
<output label="Output Targets" href="output.html"/>
+ <if label="Intermediate Format" href="intermediate.html"/>
<pdfencryption label="PDF Encryption" href="pdfencryption.html"/>
+ <pdfa label="PDF/A" href="pdfa.html"/>
+ <pdfx label="PDF/X" href="pdfx.html"/>
<graphics label="Graphics" href="graphics.html"/>
<fonts label="Fonts" href="fonts.html"/>
<hyphenation label="Hyphenation" href="hyphenation.html"/>
<extensions label="Extensions" href="extensions.html"/>
</features>
- </v0205>
-
+ </trunk>
<!--
- END Version 0.20.5 tab
+ END Version 0.93 documentation tab
-->
<!--
- BEGIN Version 0.93 documentation tab
+ BEGIN Version 0.94 documentation tab
-->
- <trunk label="FOP 0.93" href="0.93/" tab="stableversion">
+ <trunk label="FOP 0.94" href="0.94/" tab="stableversion">
<about label="About" href="index.html"/>
- <release label="Release Notes" href="releaseNotes_0.93.html"/>
- <changes label="Changes" href="changes_0.93.html"/>
+ <release label="Release Notes" href="releaseNotes_0.94.html"/>
+ <changes label="Changes" href="changes_0.94.html"/>
<knownissues label="Known Issues" href="knownissues_overview.html"/>
<upgrading label="Upgrading" href="upgrading.html"/>
@@ -117,7 +123,7 @@
</trunk>
<!--
- END Version 0.93 documentation tab
+ END Version 0.94 documentation tab
-->
<!--
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/status.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/status.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/status.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/status.xml Thu Aug 23 11:30:05 2007
@@ -33,21 +33,21 @@
This is the development status of Apache FOP. Development on
the maintenance branch where FOP 0.20.5 came from has been
halted. The code base has been largely redesigned. The new
- code base has reached release 0.93.
+ code base has reached release 0.94.
</p>
</section>
<section>
<title>Development Status</title>
- <p>The FOP code base has been largely rewritten, to address
+ <p>The FOP code base has been largely rewritten, to address
design issues for layout and performance. The new design makes
it better possible to be conformant to the spec and be able to
handle large documents.</p>
<p>The redesign of the code base has largely been completed. The
- new code reached production quality with release 0.93. In the
- course of 2007 we plan to release version 1.0.</p>
+ new code reached production quality with release 0.93. In the
+ course of 2007 we plan to release version 1.0.</p>
<p>
If you're looking for a long-term road-map we have to disappoint you. This is Open
- Source and we're mostly voluteers working in their free time. What we have
+ Source and we're mostly volunteers working in their free time. What we have
is an idea where we want to go. How fast we get there depends on the
available time, on how well our ideas work out while developing and on you!
There's a <a href="http://wiki.apache.org/xmlgraphics-fop/RoadMap">document in the Wiki</a>
@@ -134,11 +134,9 @@
<section>
<title>Maintenance Status</title>
<p>
- The latest release of the maintenance branch is FOP 0.20.5,
- released on July 18th, 2003. See <a
- href="relnotes.html">release notes</a> for more details. The
- maintenance branch has been frozen in 2004 so the team can
- concentrate on the new code base.
+ The latest release of the maintenance branch is FOP 0.20.5, released on July 18th, 2003.
+ The maintenance branch has been frozen in 2004 so the team can concentrate on the new code
+ base.
</p>
</section>
<!--section id="stats">
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/tabs.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/tabs.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/tabs.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/tabs.xml Thu Aug 23 11:30:05 2007
@@ -21,8 +21,8 @@
<tabs software="FOP" title="FOP" copyright="@year@ The Apache Software Foundation" xmlns:xlink="http://www.w3.org/1999/xlink">
<tab label="Home" dir=""/>
- <tab label="Version 0.20.5" dir="0.20.5/"/>
<tab label="Version 0.93" dir="0.93/"/>
+ <tab label="Version 0.94" dir="0.94/"/>
<tab label="FOP Trunk" dir="trunk/"/>
<tab label="Development" dir="dev/"/>
<!--
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/compiling.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/compiling.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/compiling.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/compiling.xml Thu Aug 23 11:30:05 2007
@@ -59,7 +59,7 @@
<p>
The build script uses <a href="ext:ant">Apache Ant</a>, a popular
Java-based build tool, which usually requires that the environment variable JAVA_HOME point to
- your local JDK root directory. This is true even if you use JDK 1.2 or above, which normally
+ your local JDK root directory. This is true even if you use JDK 1.3 or above, which normally
does not need this setting.
</p>
</section>
@@ -103,7 +103,8 @@
needed, but may be helpful if you are having problems with the build process itself.
</li>
<li>
- <strong>javadocs</strong>: Generates javadocs. This creates the FOP API documentation.
+ <strong>javadocs</strong>: Creates the FOP API documentation.
+ <note>A minimum JDK version of 1.4.2 is required for generating the javadocs.</note>
</li>
</ul>
<p>To run the build:</p>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/configuration.xml Thu Aug 23 11:30:05 2007
@@ -78,7 +78,7 @@
<td>URL or directory</td>
<td>Specifies the base URL based on which relative font URLs will be resolved.
</td>
- <td>base URL/directory (above)</td>
+ <td>base URL/directory (above)</td>
</tr>
<tr>
<td>hyphenation-base</td>
@@ -112,10 +112,10 @@
<td>strict-configuration</td>
<td>Boolean (true, false)</td>
<td>
- Setting this option to 'true' will cause FOP to strictly verify the contents of the
- FOP configuration file to ensure that defined resources (such as fonts and base
- URLs/directories) are valid and available to FOP. Any errors found will cause FOP to
- immediately raise an exception.</td>
+ Setting this option to 'true' will cause FOP to strictly verify the contents of the
+ FOP configuration file to ensure that defined resources (such as fonts and base
+ URLs/directories) are valid and available to FOP. Any errors found will cause FOP to
+ immediately raise an exception.</td>
<td>false</td>
</tr>
<tr>
@@ -125,7 +125,7 @@
Setting this option to 'false' causes FOP to be more forgiving about XSL-FO validity,
for example, you're allowed to specify a border on a region-body which is supported
by some FO implementations but is non-standard. Note that such a border would
- currently have no effect in Apache FOP.</td>
+ currently have no effect in Apache FOP.</td>
<td>true</td>
</tr>
<tr>
@@ -173,7 +173,7 @@
<td>renderers</td>
<td>(see text below)</td>
<td>Contains the configuration for each renderer. See below.</td>
- <td>N/A</td>
+ <td>N/A</td>
</tr>
</table>
<p>
@@ -311,7 +311,7 @@
offered by Java.
</p>
<p>
- Additionally, there are certain settings that control who the renderer handles various elements.
+ Additionally, there are certain settings that control how the renderer handles various elements.
</p>
<source><![CDATA[<renderer mime="application/vnd.hp-PCL">
<rendering>quality</rendering>
@@ -333,10 +333,10 @@
</section>
</section>
- <section>
- <title>When it does not work</title>
+ <section>
+ <title>When it does not work</title>
- <p>FOP searches the configuration file for the information it
+ <p>FOP searches the configuration file for the information it
expects, at the position it expects. When that information is not
present, FOP will not complain, it will just continue. When there is
other information in the file, FOP will not complain, it will just
@@ -344,14 +344,14 @@
the file but in a different XML element, or in a different XML path,
than FOP expects, it will be silently ignored.</p>
- <p>Check the following possibilities:</p>
+ <p>Check the following possibilities:</p>
- <ul>
- <li>The format of the configuration file has changed
+ <ul>
+ <li>The format of the configuration file has changed
considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did
you convert your file to the new format?</li>
- <li>The FOP distribution contains a schema for configuration
+ <li>The FOP distribution contains a schema for configuration
files, at src/foschema/fop-configuration.xsd. Did you validate your
configuration file against it? Add the following schema location to
the <code>schema</code> element:
@@ -366,13 +366,13 @@
parser. Note that the schema cannot detect all errors, and that it is
stricter about the order of some elements than FOP itself is.</li>
- <li>Run FOP in debug mode (command line option
+ <li>Run FOP in debug mode (command line option
<code>-d</code>). This makes FOP report which configuration
information it finds. Check if FOP finds what you expect.</li>
- </ul>
+ </ul>
- </section>
+ </section>
</body>
</document>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/extensions.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/extensions.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/extensions.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/extensions.xml Thu Aug 23 11:30:05 2007
@@ -34,7 +34,7 @@
to you. If you wish to add an extension of your own to FOP, please see the
<a href="../dev/extensions.html">Developers' Extension Page</a>.
</p>
- <note>All extensions required the correct use of an appropriate namespace in your input document.</note>
+ <note>All extensions require the correct use of an appropriate namespace in your input document.</note>
<section id="svg">
<title>SVG</title>
<p>
@@ -52,10 +52,6 @@
</p>
<source><![CDATA[<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:fox="http://xmlgraphics.apache.org/fop/extensions">]]></source>
- <note>
- Currently, no extension elements are implemented in FOP Trunk which use the
- FOP extension namespace.
- </note>
</section>
<section id="bookmarks">
<title>PDF Bookmarks</title>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/fonts.xml Thu Aug 23 11:30:05 2007
@@ -262,8 +262,8 @@
See <a href="configuration.html">FOP: Configuration</a> for more information.
</li>
<li>Either an "embed-url" or a "metrics-url" must be specified for font tag configurations.</li>
- <li>The font "kerning" attribute is optional. Kerning is currently not used at all.</li>
- <li>If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
+ <li>The font "kerning" attribute is optional.</li>
+ <li>If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
<li>When setting the "embed-url" attribute for Type 1 fonts, be sure to specify the PFB (actual font data), not PFM (font metrics) file that you used to generate the XML font metrics file.</li>
<li>The fonts "directory" tag can be used to register fonts contained within a single or list of directory paths. The "recursive" attribute can be specified to recursively add fonts from all sub directories.</li>
<li>The fonts "auto-detect" tag can be used to automatically register fonts that are found to be installed on the native operating system.</li>
@@ -291,14 +291,8 @@
<p>When FOP embeds a font, it adds a prefix to the fontname to ensure that the name will not match the fontname of an installed font.
This is helpful with older versions of Acrobat Reader that preferred installed fonts over embedded fonts.</p>
<p>When embedding PostScript fonts, the entire font is always embedded.</p>
- <p>When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document.
-Currently, this embedded font contains only the minimum data needed to be embedded in a pdf document, and does not contain any codepage information.
-The PDF document contains indexes to the glyphs in the font instead of to encoded characters.
-While the document will be displayed correctly, the net effect of this is that searching, indexing, and cut-and-paste will not work properly.</p>
- <p>One workaround for this behavior is to use the "-enc ansi" option when generating metrics with TTFReader.
-This will cause the whole font to be embedded in the pdf document.
-Characters will be WinAnsi encoded (as specified in the PDF spec), so you lose the ability to use characters from other character sets.
-See <a href="#ttf-encoding">Table of TTF Encoding Options</a> for more details.</p>
+ <p>When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the
+ original font, containing only the glyphs used, is embedded in the output document.</p>
</section>
<section id="embedding-base14">
<title>Explicitly embedding the base 14 fonts</title>
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/graphics.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/graphics.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/graphics.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/graphics.xml Thu Aug 23 11:30:05 2007
@@ -155,7 +155,6 @@
</section>
<section id="jai">
<title>JAI (Java Advanced Imaging API)</title>
- <warning>JAI support is available for Release 0.20.5 and later. The comments in this section do not apply to releases earlier than 0.20.5.</warning>
<p>
FOP has been compiled with JAI support, but JAI is not included in the FOP distribution.
To use it, install <a href="http://java.sun.com/products/java-media/jai">JAI</a>, then copy the jai_core.jar and the jai_codec.jar files to {fop-install-dir}/lib.
Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml?rev=569104&r1=569103&r2=569104&view=diff
==============================================================================
--- xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml (original)
+++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/trunk/output.xml Thu Aug 23 11:30:05 2007
@@ -635,6 +635,9 @@
possible. The RTF output follows Microsoft's RTF specifications
and produces best results on Microsoft Word.
</p>
+ <note>RTF output is currently unmaintained and lacks many features compared to other output
+ formats. Using other editable formats like Open Document Format, instead of producing XSL-FO
+ then RTF through FOP, might give better results.</note>
</section>
<section id="xml">
<title>XML (Area Tree XML)</title>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-commits-help@xmlgraphics.apache.org