xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From psan...@apache.org
Subject svn commit: r1417307 [5/14] - in /xmlgraphics/site/trunk/content: ./ batik/ batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Wed, 05 Dec 2012 08:19:31 GMT
Modified: xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext Wed Dec  5 08:19:09 2012
@@ -19,7 +19,7 @@ If no owner password has been supplied b
 
 A user password, supplied with the `-u` option, will cause the PDF display software to ask the reader for this password in order to view the contents of the document. If no user password was supplied, viewing the content is not restricted.
 
-Further restrictions can be imposed by using the `-noprint` , `-nocopy` , `-noedit` and `-noannotations` options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.
+Further restrictions can be imposed by using the `-noprint`, `-nocopy`, `-noedit` and `-noannotations` options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.
 
 ## Usage (embedded) <a id="Usage+%28embedded%29"></a>
 
@@ -85,15 +85,15 @@ Cryptography support must also be presen
 "Cannot find any provider supporting RC4"
 then you don't have the needed infrastructure.
 
-There are several commercial and a few Open Source packages which provide RC4. A pure Java implementation is produced by [The Legion of the Bouncy Castle](http://www.bouncycastle.org/) . [Mozilla JSS](http://www.mozilla.org/projects/security/pki/jss/) is an interface to a native implementation.
+There are several commercial and a few Open Source packages which provide RC4. A pure Java implementation is produced by [The Legion of the Bouncy Castle](http://www.bouncycastle.org/). [Mozilla JSS](http://www.mozilla.org/projects/security/pki/jss/) is an interface to a native implementation.
 
 ## Installing a crypto provider <a id="install_crypto"></a>
 
 The pure Java implementation from [Bouncy Castle](http://www.bouncycastle.org/) is easy to install.
 
 
-1. Unpack the distribution. Add the jar file to your classpath. A convenient way to use the jar on Linux is to simply drop it into the FOP lib directory, it will be automatically picked up by `fop.sh` .
+1. Unpack the distribution. Add the jar file to your classpath. A convenient way to use the jar on Linux is to simply drop it into the FOP lib directory, it will be automatically picked up by `fop.sh`.
 
-1. Open the `java.security` file and add<br></br> `security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider` ,<br></br>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider) .
+1. Open the `java.security` file and add<br></br> `security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider`,<br></br>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on [Sun's web site](http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider).
 
 If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.

Modified: xmlgraphics/site/trunk/content/fop/0.95/pdfx.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/pdfx.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/pdfx.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/pdfx.mdtext Wed Dec  5 08:19:09 2012
@@ -5,7 +5,7 @@ Title: Apache(tm) FOP: PDF/X (ISO 15930)
 
 ## Overview <a id="overview"></a>
 <warning>Support for PDF/X is available beginning with version 0.93. This feature is new and may not be 100% complete, yet. Feedback is welcome.</warning>
-PDF/X is a standard which faciliates prepress digital data exchange using PDF. Currently, only PDF/X-3:2003 is implemented out of the many different flavours of PDF/X profiles. PDF/X-3:2003 is documented in [ISO 15930-6:2003(E)](http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&ICS1=37&ICS2=100&ICS3=99) . More info on PDF/X can be found on the [PDF/X info site](http://www.pdfx.info/) .
+PDF/X is a standard which faciliates prepress digital data exchange using PDF. Currently, only PDF/X-3:2003 is implemented out of the many different flavours of PDF/X profiles. PDF/X-3:2003 is documented in [ISO 15930-6:2003(E)](http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&ICS1=37&ICS2=100&ICS3=99). More info on PDF/X can be found on the [PDF/X info site](http://www.pdfx.info/).
 
 ## Implementation Status <a id="status"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext Wed Dec  5 08:19:09 2012
@@ -12,13 +12,13 @@ Besides the important changes listed bel
 
 - Performance improvements and memory optimizations for the property handling in the FO tree.
 
-Please note that with this release, we've dropped support for Java 1.3. FOP will, from now on, **require at least Java 1.4** .
+Please note that with this release, we've dropped support for Java 1.3. FOP will, from now on, **require at least Java 1.4**.
 
 There have been a few changes in tables that make FOP both more strict and more compliant to the Recommendation:
 
 - XSL-FO 1.1 explicitly states that a row-spanning fo:table-cell element is not allowed to span further than its enclosing fo:table-header/footer/body element (see bottom of [section 6.7.3](http://www.w3.org/TR/xsl11/#fo_table) ). From now on FOP will give a validation error if a document contains such an erroneous cell.
 
-- 
+-
 If an fo:table element contains explicit fo:table-column children, then those elements set the total number of columns in the table. This means that a validation error will now occur if a row contains more cells than available columns. This change allows to improve performance, since the rendering of the table may start as soon as the table-column elements have been parsed.
 
 If more flexibility is needed, then the fo:table-column elements may be just omitted. The final number of columns will then be set by the row that has the most cells.
@@ -26,18 +26,18 @@ If more flexibility is needed, then the 
 
 
 The image libraries Jimi and JAI are no longer needed (and used) for image loading. Instead we rely completely on the Image I/O API that has been introduced with Java 1.4. If you still need support for bitmap image formats that do not work out-of-the-box, we recommend adding [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) (an Image I/O compatible image codec package) to the classpath. JAI is still required for building the FOP distribution but it is optional for normal builds and at run-time.
-This final 0.95 release also includes all of the [changes made for Apache FOP 0.95beta](changes_0.95beta.html) .</section></notes>
+This final 0.95 release also includes all of the [changes made for Apache FOP 0.95beta](changes_0.95beta.html).</section></notes>
 # Major Changes in Version 0.95 <a id="version_0.95"></a>
-This is not a complete list of changes, just some of the more important ones. A full list of changes in this release [is available](changes_0.95.html) .
+This is not a complete list of changes, just some of the more important ones. A full list of changes in this release [is available](changes_0.95.html).
 ## Changes to the Code Base <a id="Changes+to+the+Code+Base"></a>
 
 
-- ![fix](/images/fix.jpg)Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue [44887](http://issues.apache.org/bugzilla/show_bug.cgi?id=44887) .
+- ![fix](/images/fix.jpg)Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue [44887](http://issues.apache.org/bugzilla/show_bug.cgi?id=44887).
 
 ### Changes to the Layout Engine <a id="Changes+to+the+Layout+Engine"></a>
 
 
-- ![fix](/images/fix.jpg)Various bugfixes for table layout. Committed by VH. See Issue [44621](http://issues.apache.org/bugzilla/show_bug.cgi?id=44621) .
+- ![fix](/images/fix.jpg)Various bugfixes for table layout. Committed by VH. See Issue [44621](http://issues.apache.org/bugzilla/show_bug.cgi?id=44621).
 
 ### Changes to Renderers (Output Formats) <a id="Changes+to+Renderers+%28Output+Formats%29"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/running.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/running.mdtext Wed Dec  5 08:19:09 2012
@@ -15,15 +15,15 @@ The following software must be installed
 
 - Apache&trade; FOP. The [FOP distribution](../download.html) includes all libraries that you will need to run a basic FOP installation. These can be found in the [fop-root]/lib directory. These libraries include the following:
 
-    -  [Apache XML Graphics Commons](http://xmlgraphics.apache.org/commons/) , an shared library for Batik and FOP.
+    -  [Apache XML Graphics Commons](http://xmlgraphics.apache.org/commons/), an shared library for Batik and FOP.
 
-    -  [Apache Batik](http://xmlgraphics.apache.org/batik/) , an SVG library.
+    -  [Apache Batik](http://xmlgraphics.apache.org/batik/), an SVG library.
 
-    -  [Apache Commons Logging](http://commons.apache.org/logging/) , a logger abstraction kit.
+    -  [Apache Commons Logging](http://commons.apache.org/logging/), a logger abstraction kit.
 
-    -  [Apache Commons IO](http://commons.apache.org/io/) , a library with I/O utilities.
+    -  [Apache Commons IO](http://commons.apache.org/io/), a library with I/O utilities.
 
-    -  [Apache Excalibur/Avalon Framework](http://excalibur.apache.org/framework/) , for XML configuration handling.
+    -  [Apache Excalibur/Avalon Framework](http://excalibur.apache.org/framework/), for XML configuration handling.
 
 
 The following software is optional, depending on your needs:
@@ -52,7 +52,7 @@ Some Mac OSX users have experienced file
 
 ### Using the fop script or batch file <a id="fop-script"></a>
 
-The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is `/Library/Java/Home` . **Caveat:** We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see [Java on Mac OSX FAQ](http://developer.apple.com/java/faq) for information as it becomes available.
+The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is `/Library/Java/Home`. **Caveat:** We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see [Java on Mac OSX FAQ](http://developer.apple.com/java/faq) for information as it becomes available.
 
     USAGE
     Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] <outfile>
@@ -127,38 +127,38 @@ The usual and recommended practice for s
       Fop foo.fo -print or Fop -print foo.fo
       Fop foo.fo -awt
 
-PDF encryption is only available if FOP was compiled with encryption support **and** if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the [Details](pdfencryption.html) .
+PDF encryption is only available if FOP was compiled with encryption support **and** if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the [Details](pdfencryption.html).
 
 ### Writing your own script <a id="your-own-script"></a>
 
-FOP's entry point for your own scripts is the class `org.apache.fop.cli.Main` . The general pattern for the command line is: `java -classpath <CLASSPATH>
-        org.apache.fop.cli.Main <arguments>` . The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that you get your environment properly configured.
+FOP's entry point for your own scripts is the class `org.apache.fop.cli.Main`. The general pattern for the command line is: `java -classpath <CLASSPATH>
+        org.apache.fop.cli.Main <arguments>`. The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that you get your environment properly configured.
 
 ### Running with java's -jar option <a id="jar-option"></a>
 
 As an alternative to the start scripts you can run `java
-        -jar path/to/build/fop.jar <arguments>` , relying on FOP to build the classpath for running FOP dynamically, see [below](#dynamical-classpath) . If you use hyphenation, you must put `fop-hyph.jar` in the `lib` directory.
+        -jar path/to/build/fop.jar <arguments>`, relying on FOP to build the classpath for running FOP dynamically, see [below](#dynamical-classpath). If you use hyphenation, you must put `fop-hyph.jar` in the `lib` directory.
 
 You can also run `java -jar path/to/fop.jar
-      <arguments>` , relying on the `Class-Path` entry in the manifest file. This works if you put `fop.jar` and all jar files from the `lib` directory in a single directory. If you use hyphenation, you must also put `fop-hyph.jar` in that directory.
+      <arguments>`, relying on the `Class-Path` entry in the manifest file. This works if you put `fop.jar` and all jar files from the `lib` directory in a single directory. If you use hyphenation, you must also put `fop-hyph.jar` in that directory.
 
 In both cases the arguments consist of the options and infile and outfile specifications as shown above for the standard scripts.
 
 ### FOP's dynamical classpath construction <a id="dynamical-classpath"></a>
 
-If FOP is started without a proper classpath, it tries to add its dependencies dynamically. If the system property `fop.home` contains the name of a directory, then FOP uses that directory as the base directory for its search. Otherwise the current working directory is the base directory. If the base directory is called `build` , then its parent directory becomes the base directory.
+If FOP is started without a proper classpath, it tries to add its dependencies dynamically. If the system property `fop.home` contains the name of a directory, then FOP uses that directory as the base directory for its search. Otherwise the current working directory is the base directory. If the base directory is called `build`, then its parent directory becomes the base directory.
 
 FOP expects to find `fop.jar` in the `build` subdirectory of the base directory, and adds it to the classpath. Subsequently FOP adds all `jar` files in the lib directory to the classpath. The lib directory is either the `lib` subdirectory of the base directory, or, if that does not exist, the base directory itself.
 
-If the system property `fop.optional.lib` contains the name of a directory, then all `jar` files in that directory are also added to the classpath. See the methods `getJARList` and `checkDependencies` in `org.apache.fop.cli.Main` .
+If the system property `fop.optional.lib` contains the name of a directory, then all `jar` files in that directory are also added to the classpath. See the methods `getJARList` and `checkDependencies` in `org.apache.fop.cli.Main`.
 
 ## Using Xalan to Check XSL-FO Input <a id="check-input"></a>
 
-FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Tranforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. 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 [Specifications](../resources.html#specs) and [Books/Articles](../resources.html#articles) . 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.
+FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Tranforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. 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 [Specifications](../resources.html#specs) and [Books/Articles](../resources.html#articles). 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.
 The user is always responsible to provide correct XSL-FO code to FOP.
 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 the "-foout" option which causes FOP to run only the first (transformation) step, and write the results to a file. (See also the Xalan command-line below)
 When asking for help on the FOP mailing lists, *never* attach XML and XSL to illustrate the issue. Always run the XSLT step (-foout) and send the resulting XSL-FO file instead. Of course, be sure that the XSL-FO file is correct before sending it.
-The -foout option works the same way as if you would call the [Xalan command-line](http://xml.apache.org/xalan-j/commandline.html) :
+The -foout option works the same way as if you would call the [Xalan command-line](http://xml.apache.org/xalan-j/commandline.html):
 
  `java org.apache.xalan.xslt.Process -IN xmlfile -XSL file -OUT outfile`
 
@@ -181,4 +181,4 @@ If you are running out of memory when us
 
 ## Problems <a id="problems"></a>
 
-If you have problems running FOP, please see the ["How to get Help" page](../gethelp.html) .
+If you have problems running FOP, please see the ["How to get Help" page](../gethelp.html).

Modified: xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext Wed Dec  5 08:19:09 2012
@@ -23,7 +23,7 @@ The servlet is automatically built when 
 The source code for the servlet can be found under {fop-dir}/src/java/org/apache/fop/servlet/FopServlet.java.
 This example servlet should not be used on a public web server connected to the Internet as it does not contain any measures to prevent Denial-of-Service-Attacks. It is provided as an example and as a starting point for your own servlet.
 ## Create your own Servlet <a id="servlet"></a>
-This section assumes you are familiar with [embedding FOP](embedding.html) .
+This section assumes you are familiar with [embedding FOP](embedding.html).
 ### A minimal Servlet <a id="minimal-servlet"></a>
 
 Here is a minimal code snippet to demonstrate the basics:
@@ -91,13 +91,13 @@ A common requirement is to transform an 
 
 Buffering the generated PDF in a ByteArrayOutputStream is done to avoid potential problems with the Acrobat Reader Plug-in in Microsoft Internet Explorer.
 The `Source` instance used above is simply an example. If you have to read the XML from a string, supply a `new StreamSource(new
-          StringReader(xmlstring))` . Constructing and reparsing an XML string is generally less desirable than using a SAXSource if you generate your XML. You can alternatively supply a DOMSource as well. You may also use dynamically generated XSL if you like.
+          StringReader(xmlstring))`. Constructing and reparsing an XML string is generally less desirable than using a SAXSource if you generate your XML. You can alternatively supply a DOMSource as well. You may also use dynamically generated XSL if you like.
 
 Because you have an explicit `Transformer` object, you can also use it to explicitely set parameters for the transformation run.
 
 ### Custom configuration <a id="cfg"></a>
 
-You can easily set up your own FOUserAgent as demonstrated on the [Embedding page](embedding.html) .
+You can easily set up your own FOUserAgent as demonstrated on the [Embedding page](embedding.html).
 
 ### Improving performance <a id="performance"></a>
 
@@ -112,7 +112,7 @@ Of course, the [performance hints from t
 
 ### Accessing resources in your web application <a id="uriresolver"></a>
 
-Often, you will want to use resources (stylesheets, images etc.) which are bundled with your web application. FOP provides a URIResolver implementation that lets you access files via the Servlet's ServletContext. The class is called `org.apache.fop.servlet.ServletContextURIResolver` .
+Often, you will want to use resources (stylesheets, images etc.) which are bundled with your web application. FOP provides a URIResolver implementation that lets you access files via the Servlet's ServletContext. The class is called `org.apache.fop.servlet.ServletContextURIResolver`.
 
 Here's how to set it up in your servlet. Instantiate a new instance in the servlet's init() method:
 
@@ -162,7 +162,7 @@ Here are some example snippets:
 Some versions of Internet Explorer will not automatically show the PDF or call the servlet multiple times. These are well-known limitations of Internet Explorer and are not a problem of the servlet. However, Internet Explorer can still be used to download the PDF so that it can be viewed later. Here are some suggestions in this context:
 
 
-- Use an URL ending in `.pdf` , like `http://myserver/servlet/stuff.pdf` . Yes, the servlet can be configured to handle this. If the URL has to contain parameters, try to have **both** the base URL as well as the last parameter end in `.pdf` , if necessary append a dummy parameter, like `http://myserver/servlet/stuff.pdf?par1=a&par2=b&d=.pdf` . The effect may depend on IEx version.
+- Use an URL ending in `.pdf`, like `http://myserver/servlet/stuff.pdf`. Yes, the servlet can be configured to handle this. If the URL has to contain parameters, try to have **both** the base URL as well as the last parameter end in `.pdf`, if necessary append a dummy parameter, like `http://myserver/servlet/stuff.pdf?par1=a&par2=b&d=.pdf`. The effect may depend on IEx version.
 
 - Give IEx the opportunity to cache. In particular, ensure the server does not set any headers causing IEx not to cache the content. This may be a real problem if the document is sent over HTTPS, because most IEx installations will by default *not* cache any content retrieved over HTTPS. Setting the `Expires` header entry may help in this case:<br></br> `response.setDateHeader("Expires",
           System.currentTimeMillis() + cacheExpiringDuration *

Modified: xmlgraphics/site/trunk/content/fop/0.95/upgrading.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/upgrading.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/upgrading.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/upgrading.mdtext Wed Dec  5 08:19:09 2012
@@ -8,9 +8,9 @@ Title: Upgrading from an Earlier Version
 If you're planning to upgrade to the latest Apache&trade; FOP version there are a few very important things to consider:
 
 
-- More than half of the codebase has been rewritten over the last four years. With version 0.93 the code has reached **production level** , and continues to improve with version 0.94 and 0.95.
+- More than half of the codebase has been rewritten over the last four years. With version 0.93 the code has reached **production level**, and continues to improve with version 0.94 and 0.95.
 
-- The API of FOP has changed considerably and is not backwards-compatible with versions 0.20.5 and 0.91beta. Version 0.92 introduced the **new stable API** .
+- The API of FOP has changed considerably and is not backwards-compatible with versions 0.20.5 and 0.91beta. Version 0.92 introduced the **new stable API**.
 
 - Since version 0.92 some deprecated methods which were part of the old API have been removed. If you upgrade from 0.91 beta, you will need to adjust your Java code. Similarly if you upgrade from 0.92 and use deprecated methods.
 
@@ -18,9 +18,9 @@ If you're planning to upgrade to the lat
 
 - Beginning with version 0.94 you can skip the generation of font metric files and remove the "font-metrics" attribute in the font configuration. The font metrics files are, for the moment, still required if you use a TrueType Collection (*.ttc) and in that case you need to regenerate the font metrics file if yours are from a FOP version before 0.93.
 
-- 
+-
 The new code is much more strict about the interpretation of the XSL-FO 1.1 specification. Things that worked fine in version 0.20.5 might start to produce warnings or even errors now. FOP 0.20.5 contains many bugs which have been corrected in the new code.
-While FOP 0.20.5 allowed you to have empty `fo:table-cell` elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element ( `(%block;)+` , see [XSL-FO 1.1, 6.7.10](http://www.w3.org/TR/xsl/#fo_table-cell) ) inside an `fo:table-cell` element.
+While FOP 0.20.5 allowed you to have empty `fo:table-cell` elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element ( `(%block;)+`, see [XSL-FO 1.1, 6.7.10](http://www.w3.org/TR/xsl/#fo_table-cell) ) inside an `fo:table-cell` element.
 
 - Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP extension for [Barcode4J](http://barcode4j.sourceforge.net) is available since January 2007.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext Wed Dec  5 08:19:09 2012
@@ -61,7 +61,7 @@ Accessibility support in Apache FOP is r
 
 - It's currently not possible to specify the expanded form of an abbreviation or acronym.
 
-- SVG graphics (or images in general) are treated as a single figure. Text contained in SVGs is not accessible. It's only possible to work with `fox:alt-text` .
+- SVG graphics (or images in general) are treated as a single figure. Text contained in SVGs is not accessible. It's only possible to work with `fox:alt-text`.
 
 - The side regions (region-before, region-after etc.) are currently not specially identified. Screen readers may read their content at page changes.
 
@@ -70,14 +70,14 @@ Accessibility support in Apache FOP is r
 Many resources providing guidance about creating accessible documents can be found on the web. Here are a few links, along with additional resources around the topic:
 
 
--  [US Government - Website on Section 508](http://www.section508.gov/) 
+-  [US Government - Website on Section 508](http://www.section508.gov/)
 
--  [Wikipedia on Accessibility in general](http://en.wikipedia.org/wiki/Accessibility) 
+-  [Wikipedia on Accessibility in general](http://en.wikipedia.org/wiki/Accessibility)
 
--  [Wikipedia on Accessibility in PDF](http://en.wikipedia.org/wiki/Portable_Document_Format#Accessibility) 
+-  [Wikipedia on Accessibility in PDF](http://en.wikipedia.org/wiki/Portable_Document_Format#Accessibility)
 
 -  [PDF Reference 1.4](http://partners.adobe.com/public/developer/en/pdf/PDFReference.pdf) (look up chapters 9.7 "Tagged PDF" and 9.8 "Accessibility Support")
 
--  [PDF/A support in Apache FOP](pdfa.html) 
+-  [PDF/A support in Apache FOP](pdfa.html)
 
--  [Developer-oriented details on the accessibility features (on the Wiki)](http://wiki.apache.org/xmlgraphics-fop/PDF_Accessibility) 
+-  [Developer-oriented details on the accessibility features (on the Wiki)](http://wiki.apache.org/xmlgraphics-fop/PDF_Accessibility)

Modified: xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext Wed Dec  5 08:19:09 2012
@@ -39,13 +39,13 @@ Then create FOP tasks within your Ant bu
 | xmlfile | XML input file | Yes, if no fofile is specified |
 | xsltfile | XSLT input file | Yes, if no fofile is specified |
 | outfile | Output filename | Yes, when fofile is used. (This attribute is not valid for filesets.) |
-| format | Possible output formats:<br></br> `application/X-fop-awt-preview` <br></br> `application/X-fop-print` <br></br> `application/X-fop-areatree` <br></br> `application/pdf` <br></br> `application/postscript` <br></br> `application/mif` <br></br> `application/rtf` , `text/richtext` , `text/rtf` <br></br> `application/x-pcl` , `application/vnd.hp-PCL` <br></br> `application/x-afp` , `application/vnd.ibm.modcap` <br></br> `text/plain` <br></br> `image/svg+xml` <br></br> `image/gif` <br></br> `image/png` <br></br> `image/tiff` <br></br> | No, defaults to `application/pdf`  |
+| format | Possible output formats:<br></br> `application/X-fop-awt-preview` <br></br> `application/X-fop-print` <br></br> `application/X-fop-areatree` <br></br> `application/pdf` <br></br> `application/postscript` <br></br> `application/mif` <br></br> `application/rtf`, `text/richtext`, `text/rtf` <br></br> `application/x-pcl`, `application/vnd.hp-PCL` <br></br> `application/x-afp`, `application/vnd.ibm.modcap` <br></br> `text/plain` <br></br> `image/svg+xml` <br></br> `image/gif` <br></br> `image/png` <br></br> `image/tiff` <br></br> | No, defaults to `application/pdf`  |
 | outdir | Output directory | Required if a fileset is used to specify the files to render; optional for fofile. (Can alternatively specify the full path in the fofile value.) |
 | force | Recreate target files, even if they are newer than their corresponding source files. Note: This attribute is available in post-0.20.5 versions (0.20.x nightly build and 1.0dev) only; target files are always generated (i.e., force=true) in 0.20.5 release. | No, default is `false`  |
 | basedir | Base directory to resolve relative references (e.g., graphics files) within the FO document. | No, for single FO File entry, default is to use the location of that FO file. |
-| relativebase | For fileset usage only. A value of `true` specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of `false` specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified. | No, default is `false` . |
+| relativebase | For fileset usage only. A value of `true` specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of `false` specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified. | No, default is `false`. |
 | userconfig | User configuration file (same as the FOP "-c" command line option). | No |
-| messagelevel | Logging level<br></br>Possible values: `error` , `warn` , `info` , `verbose` , `debug` . **Currently doesn't work in FOP Trunk!!!**  | No, defaults to `verbose`  |
+| messagelevel | Logging level<br></br>Possible values: `error`, `warn`, `info`, `verbose`, `debug`. **Currently doesn't work in FOP Trunk!!!**  | No, defaults to `verbose`  |
 | logFiles | Controls whether the names of the files that are processed are logged ( `true` ) or not ( `false` ). **Currently doesn't work in FOP Trunk!!!**  | No, default is `true`  |
 | throwexceptions | Controls whether or not an exception is thrown if an error occurs during rendering. | Default is `true`  |
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/changes_1.0.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/changes_1.0.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/changes_1.0.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/changes_1.0.mdtext Wed Dec  5 08:19:09 2012
@@ -3,7 +3,7 @@ Title: History of Changes 1.0
 #History of Changes 1.0
 
 
- [changes_1.0.rss](changes_1.0.rss) 
+ [changes_1.0.rss](changes_1.0.rss)
 
 ## Introduction and explanation of symbols <a id="introduction"></a>
 
@@ -21,21 +21,21 @@ Changes are sorted by "type" and then ch
 
 - ![add](/images/add.jpg) Added support for xmlfile and xsltfile parameters in FOP's Ant Task. Committed by AC.
 
-- ![add](/images/add.jpg) Added the possibility to use CachedRenderPagesModel, to conserve memory in case of large documents with a lot of cross-references (area tree will be serialized to disk to avoid keeping it entirely in memory). Committed by AD. Thanks to Dario Laera. See Issue [46828](http://issues.apache.org/bugzilla/show_bug.cgi?id=46828) .
+- ![add](/images/add.jpg) Added the possibility to use CachedRenderPagesModel, to conserve memory in case of large documents with a lot of cross-references (area tree will be serialized to disk to avoid keeping it entirely in memory). Committed by AD. Thanks to Dario Laera. See Issue [46828](http://issues.apache.org/bugzilla/show_bug.cgi?id=46828).
 
 - ![add](/images/add.jpg) Added an event handling framework which allows to get better feedback from within FOP with the ability to customize problem management. Committed by JM.
 
-- ![fix](/images/fix.jpg) Bugfix: when #CMYK pseudo-profile was used in the rgb-icc() function, always the fallback RGB colors were used instead. Committed by VH. Thanks to Venkat Reddy. See Issue [48167](http://issues.apache.org/bugzilla/show_bug.cgi?id=48167) .
+- ![fix](/images/fix.jpg) Bugfix: when #CMYK pseudo-profile was used in the rgb-icc() function, always the fallback RGB colors were used instead. Committed by VH. Thanks to Venkat Reddy. See Issue [48167](http://issues.apache.org/bugzilla/show_bug.cgi?id=48167).
 
-- ![fix](/images/fix.jpg) White-space handling in markers with inline-content throws a NullPointerException in some cases. Committed by AD. See Issue [47710](http://issues.apache.org/bugzilla/show_bug.cgi?id=47710) .
+- ![fix](/images/fix.jpg) White-space handling in markers with inline-content throws a NullPointerException in some cases. Committed by AD. See Issue [47710](http://issues.apache.org/bugzilla/show_bug.cgi?id=47710).
 
-- ![fix](/images/fix.jpg) Bugfix: previously retrieved markers were not cleared if the new marker was empty. Committed by AD. See Issue [46960](http://issues.apache.org/bugzilla/show_bug.cgi?id=46960) .
+- ![fix](/images/fix.jpg) Bugfix: previously retrieved markers were not cleared if the new marker was empty. Committed by AD. See Issue [46960](http://issues.apache.org/bugzilla/show_bug.cgi?id=46960).
 
 - ![fix](/images/fix.jpg) Changed meaning of ‘-v’ option to ‘verbose’, which will print FOP’s version and proceed. Added a ‘-version’ option to simply print the version then exit, following Java practices. Committed by VH.
 
-- ![fix](/images/fix.jpg) MinOptMaxUtil.toMinOptMax was converting LengthRangeProperty objects into illegal MinOptMax objects (in some cases opt could be inferior to min). Committed by VH. See Issue [46638](http://issues.apache.org/bugzilla/show_bug.cgi?id=46638) .
+- ![fix](/images/fix.jpg) MinOptMaxUtil.toMinOptMax was converting LengthRangeProperty objects into illegal MinOptMax objects (in some cases opt could be inferior to min). Committed by VH. See Issue [46638](http://issues.apache.org/bugzilla/show_bug.cgi?id=46638).
 
-- ![fix](/images/fix.jpg) Fixed a memory-leak in Marker.MarkerAttribute, where an instance was used both as key and value in a WeakHashMap, effectively neutralizing the benefit of using WeakReferences. Solved by extending PropertyCache to work for MarkerAttributes as well. Committed by AD. See Issue [46319](http://issues.apache.org/bugzilla/show_bug.cgi?id=46319) .
+- ![fix](/images/fix.jpg) Fixed a memory-leak in Marker.MarkerAttribute, where an instance was used both as key and value in a WeakHashMap, effectively neutralizing the benefit of using WeakReferences. Solved by extending PropertyCache to work for MarkerAttributes as well. Committed by AD. See Issue [46319](http://issues.apache.org/bugzilla/show_bug.cgi?id=46319).
 
 - ![fix](/images/fix.jpg) Fixed some multi-threading issues in FontCache.java:
 
@@ -44,21 +44,21 @@ Changes are sorted by "type" and then ch
     - make the changeLock member final (initialization-safety + impossible to reassign)
 
     - perform the HashMap check for a failed font inside the synchronized block to avoid a race condition
-Committed by AD. Thanks to rogov.AT.devexperts.com. See Issue [46211](http://issues.apache.org/bugzilla/show_bug.cgi?id=46211) .
+Committed by AD. Thanks to rogov.AT.devexperts.com. See Issue [46211](http://issues.apache.org/bugzilla/show_bug.cgi?id=46211).
 
-- ![fix](/images/fix.jpg) Improved the behaviour of the command line interface. Committed by VH. Thanks to Tow Browder. See Issue [45971](http://issues.apache.org/bugzilla/show_bug.cgi?id=45971) .
+- ![fix](/images/fix.jpg) Improved the behaviour of the command line interface. Committed by VH. Thanks to Tow Browder. See Issue [45971](http://issues.apache.org/bugzilla/show_bug.cgi?id=45971).
 
-- ![fix](/images/fix.jpg) Make fop.bat and fop.cmd use the %FOP_OPTS% environment variable. Committed by AD. Thanks to Carsten Siedentop. See Issue [45842](http://issues.apache.org/bugzilla/show_bug.cgi?id=45842) .
+- ![fix](/images/fix.jpg) Make fop.bat and fop.cmd use the %FOP_OPTS% environment variable. Committed by AD. Thanks to Carsten Siedentop. See Issue [45842](http://issues.apache.org/bugzilla/show_bug.cgi?id=45842).
 
-- ![fix](/images/fix.jpg) Quick-fix to avoid a possible NullPointerException when using empty inlines and hyphenation. Committed by AD. See Issue [45667](http://issues.apache.org/bugzilla/show_bug.cgi?id=45667) .
+- ![fix](/images/fix.jpg) Quick-fix to avoid a possible NullPointerException when using empty inlines and hyphenation. Committed by AD. See Issue [45667](http://issues.apache.org/bugzilla/show_bug.cgi?id=45667).
 
 - ![fix](/images/fix.jpg) Fixed memory leak in property cache (not cleaning stale PropertyCache$CacheEntry instances). Committed by JM.
 
-- ![fix](/images/fix.jpg) Fixed a slight error when resolving non-file URLs: avoid altering the original 'href' if the protocol is other than 'file:' Committed by AD. Thanks to Thomas Stieler. See Issue [45490](http://issues.apache.org/bugzilla/show_bug.cgi?id=45490) .
+- ![fix](/images/fix.jpg) Fixed a slight error when resolving non-file URLs: avoid altering the original 'href' if the protocol is other than 'file:' Committed by AD. Thanks to Thomas Stieler. See Issue [45490](http://issues.apache.org/bugzilla/show_bug.cgi?id=45490).
 
-- ![fix](/images/fix.jpg) Corrected white-space-treatment for situations where an inline-node is the first/last child node of an fo:block, without preceding/following text. Committed by AD. See Issue [45097](http://issues.apache.org/bugzilla/show_bug.cgi?id=45097) .
+- ![fix](/images/fix.jpg) Corrected white-space-treatment for situations where an inline-node is the first/last child node of an fo:block, without preceding/following text. Committed by AD. See Issue [45097](http://issues.apache.org/bugzilla/show_bug.cgi?id=45097).
 
-- ![fix](/images/fix.jpg) Fixed a logic error in Hyphenator.java: If the source had an associated InputStream, an UnsupportedOperationException was triggered. Committed by AD. See Issue [44203](http://issues.apache.org/bugzilla/show_bug.cgi?id=44203) .
+- ![fix](/images/fix.jpg) Fixed a logic error in Hyphenator.java: If the source had an associated InputStream, an UnsupportedOperationException was triggered. Committed by AD. See Issue [44203](http://issues.apache.org/bugzilla/show_bug.cgi?id=44203).
 
 - ![update](/images/update.jpg) Changed FONode.addCharacters() parameter to closer match the signature of the standard SAX characters() event (reduces confusion and computations). *!! Implementors of extensions that subclass FONode directly, and offer an implementation for addCharacters() should take care to make similar modifications in their code !!* Committed by AD.
 
@@ -86,30 +86,30 @@ Committed by AD. Thanks to rogov.AT.deve
 
 - ![add](/images/add.jpg) Add support for font substitution. Committed by AC.
 
-- ![add](/images/add.jpg) Added support for auto-configuring TrueType Collections. XML font metrics files for *.ttc fonts are not required anymore. Committed by JM. Thanks to Jason Harrop. See Issue [44737](http://issues.apache.org/bugzilla/show_bug.cgi?id=44737) .
+- ![add](/images/add.jpg) Added support for auto-configuring TrueType Collections. XML font metrics files for *.ttc fonts are not required anymore. Committed by JM. Thanks to Jason Harrop. See Issue [44737](http://issues.apache.org/bugzilla/show_bug.cgi?id=44737).
 
 - ![add](/images/add.jpg) Added support for addressing all glyphs available in a Type 1 font, not just the ones in the font's primary encoding. Committed by JM.
 
 - ![fix](/images/fix.jpg) Bugfix: Font selection fallbacks did not work in some cases (ex. bold+italic to normal) Committed by JM.
 
-- ![fix](/images/fix.jpg) Fixed generation of CIDSet object in PDF output. Committed by JM. Thanks to Nicolas Peninguy. See Issue [47711](http://issues.apache.org/bugzilla/show_bug.cgi?id=47711) .
+- ![fix](/images/fix.jpg) Fixed generation of CIDSet object in PDF output. Committed by JM. Thanks to Nicolas Peninguy. See Issue [47711](http://issues.apache.org/bugzilla/show_bug.cgi?id=47711).
 
 - ![fix](/images/fix.jpg) Bugfix: support PFM Files with no extent table. Committed by CB.
 
-- ![fix](/images/fix.jpg) Bugfix: for the last character of a Type1 font, always a width of 0 was returned. Committed by VH. Thanks to Maxim Wirt. See Issue [47232](http://issues.apache.org/bugzilla/show_bug.cgi?id=47232) .
+- ![fix](/images/fix.jpg) Bugfix: for the last character of a Type1 font, always a width of 0 was returned. Committed by VH. Thanks to Maxim Wirt. See Issue [47232](http://issues.apache.org/bugzilla/show_bug.cgi?id=47232).
 
-- ![fix](/images/fix.jpg) Use temporary directory for the font cache if the user home directory is not write-accessible. Committed by JM. Thanks to Alok Singh. See Issue [46686](http://issues.apache.org/bugzilla/show_bug.cgi?id=46686) .
+- ![fix](/images/fix.jpg) Use temporary directory for the font cache if the user home directory is not write-accessible. Committed by JM. Thanks to Alok Singh. See Issue [46686](http://issues.apache.org/bugzilla/show_bug.cgi?id=46686).
 
 - ![fix](/images/fix.jpg) More robust AFP font parsing, although it is still in need of some rework in the future. Committed by AC.
 
-- ![fix](/images/fix.jpg) Fix for PFMReader after bug #43089 changed the behavior of PFMFile. Fixes baseline problems when Type 1 fonts are used in conjunction with XML font metric files. Committed by JM. Thanks to J. Frantzius. See Issue [45734](http://issues.apache.org/bugzilla/show_bug.cgi?id=45734) .
+- ![fix](/images/fix.jpg) Fix for PFMReader after bug #43089 changed the behavior of PFMFile. Fixes baseline problems when Type 1 fonts are used in conjunction with XML font metric files. Committed by JM. Thanks to J. Frantzius. See Issue [45734](http://issues.apache.org/bugzilla/show_bug.cgi?id=45734).
 
 ### Changes to the Image Support <a id="Images_1.0"></a>
 
 
 - ![add](/images/add.jpg) Added customization ability for the image loading framework from FOP's configuration file. Committed by JM.
 
-- ![add](/images/add.jpg) Added support for SVG 1.2 functionality inside fo:instream-foreign-object. Committed by JM. See Issue [41657](http://issues.apache.org/bugzilla/show_bug.cgi?id=41657) .
+- ![add](/images/add.jpg) Added support for SVG 1.2 functionality inside fo:instream-foreign-object. Committed by JM. See Issue [41657](http://issues.apache.org/bugzilla/show_bug.cgi?id=41657).
 
 - ![fix](/images/fix.jpg) Bugfix: use the effective color profile supplied by the ImageEncodingHelper, instead of the original one. Committed by JM.
 
@@ -120,9 +120,9 @@ Committed by AD. Thanks to rogov.AT.deve
 
 - ![add](/images/add.jpg) Added limited support for pages of different inline-progression-dimensions within a page-sequence. Committed by VH.
 
-- ![add](/images/add.jpg) Added basic implementation for column-keeps. Committed by AD. See Issue [46905](http://issues.apache.org/bugzilla/show_bug.cgi?id=46905) .
+- ![add](/images/add.jpg) Added basic implementation for column-keeps. Committed by AD. See Issue [46905](http://issues.apache.org/bugzilla/show_bug.cgi?id=46905).
 
-- ![add](/images/add.jpg) Added extension to disable column balancing before blocks spanning the whole page, in multiple-column documents. Committed by VH. Thanks to Georg Datterl. See Issue [46315](http://issues.apache.org/bugzilla/show_bug.cgi?id=46315) .
+- ![add](/images/add.jpg) Added extension to disable column balancing before blocks spanning the whole page, in multiple-column documents. Committed by VH. Thanks to Georg Datterl. See Issue [46315](http://issues.apache.org/bugzilla/show_bug.cgi?id=46315).
 
 - ![add](/images/add.jpg) Added missing generation of areas for empty grid units in tables with collapsing border model. Committed by JM.
 
@@ -134,60 +134,60 @@ Committed by AD. Thanks to rogov.AT.deve
 
 - ![add](/images/add.jpg) Added minimal support for integer keep values on the various keep properties on block-level FOs. For now, all integer values are treated the same (i.e. without strength distinction). Using integers allows to avoid overflows that can happen when "always" is used extensively. Committed by JM.
 
-- ![fix](/images/fix.jpg) Bugfix: having a special page-master for the last page caused loss of content when normal blocks were mixed with blocks spanning all columns. Committed by VH. See Issue [46486](http://issues.apache.org/bugzilla/show_bug.cgi?id=46486) .
+- ![fix](/images/fix.jpg) Bugfix: having a special page-master for the last page caused loss of content when normal blocks were mixed with blocks spanning all columns. Committed by VH. See Issue [46486](http://issues.apache.org/bugzilla/show_bug.cgi?id=46486).
 
-- ![fix](/images/fix.jpg) Bugfix: value of conditional space not always taken into account in the calculation of a table’s height. Committed by VH. See Issue [48082](http://issues.apache.org/bugzilla/show_bug.cgi?id=48082) .
+- ![fix](/images/fix.jpg) Bugfix: value of conditional space not always taken into account in the calculation of a table’s height. Committed by VH. See Issue [48082](http://issues.apache.org/bugzilla/show_bug.cgi?id=48082).
 
 - ![fix](/images/fix.jpg) Fixed handling of percentage values for provisional-label-separation. Committed by VH.
 
-- ![fix](/images/fix.jpg) Fixed handling of percentage values for provisional-distance-between-starts. Committed by VH. Thanks to Jonathan Levinson. See Issue [47835](http://issues.apache.org/bugzilla/show_bug.cgi?id=47835) .
+- ![fix](/images/fix.jpg) Fixed handling of percentage values for provisional-distance-between-starts. Committed by VH. Thanks to Jonathan Levinson. See Issue [47835](http://issues.apache.org/bugzilla/show_bug.cgi?id=47835).
 
-- ![fix](/images/fix.jpg) Bugfix: The cells of a table inside a marker were duplicated at every marker retrieval. Committed by VH. See Issue [47101](http://issues.apache.org/bugzilla/show_bug.cgi?id=47101) .
+- ![fix](/images/fix.jpg) Bugfix: The cells of a table inside a marker were duplicated at every marker retrieval. Committed by VH. See Issue [47101](http://issues.apache.org/bugzilla/show_bug.cgi?id=47101).
 
 - ![fix](/images/fix.jpg) Bugfix: footnotes occurring within the forced height of a table row did not appear on the output Committed by VH.
 
-- ![fix](/images/fix.jpg) Fixed a bug when combining a forced break with a "last" page-master. The restart of the algorithm would start at the index of the penalty corresponding to the last page-break. This has been changed to the index of the first element after the last page-break. Committed by AD. See Issue [46489](http://issues.apache.org/bugzilla/show_bug.cgi?id=46489) .
+- ![fix](/images/fix.jpg) Fixed a bug when combining a forced break with a "last" page-master. The restart of the algorithm would start at the index of the penalty corresponding to the last page-break. This has been changed to the index of the first element after the last page-break. Committed by AD. See Issue [46489](http://issues.apache.org/bugzilla/show_bug.cgi?id=46489).
 
 - ![fix](/images/fix.jpg) Fixed BPD trait and border painting for leaders with leader-pattern="space" (and similar cases). Committed by JM.
 
-- ![fix](/images/fix.jpg) Fixed fo:instream-foreign-object inside fo:marker. Committed by JM. See Issue [45306](http://issues.apache.org/bugzilla/show_bug.cgi?id=45306) .
+- ![fix](/images/fix.jpg) Fixed fo:instream-foreign-object inside fo:marker. Committed by JM. See Issue [45306](http://issues.apache.org/bugzilla/show_bug.cgi?id=45306).
 
-- ![fix](/images/fix.jpg) Fixed a bug when combining break-before with a span change. Committed by AD. See Issue [46240](http://issues.apache.org/bugzilla/show_bug.cgi?id=46240) .
+- ![fix](/images/fix.jpg) Fixed a bug when combining break-before with a span change. Committed by AD. See Issue [46240](http://issues.apache.org/bugzilla/show_bug.cgi?id=46240).
 
 - ![fix](/images/fix.jpg) Fixed a problem where the BPD or a block area could be wrong if there is a nested, absolutely positioned area (for example a block-container). Committed by JM.
 
-- ![fix](/images/fix.jpg) Bugzilla 40798: A conditional-page-master-reference with page-position="last" qualifies for a first page, if it is also the last. Additionally: also added support for page-position="only". Committed by AD. See Issue [40798](http://issues.apache.org/bugzilla/show_bug.cgi?id=40798) .
+- ![fix](/images/fix.jpg) Bugzilla 40798: A conditional-page-master-reference with page-position="last" qualifies for a first page, if it is also the last. Additionally: also added support for page-position="only". Committed by AD. See Issue [40798](http://issues.apache.org/bugzilla/show_bug.cgi?id=40798).
 
 - ![fix](/images/fix.jpg) Fixed the source for a division by zero when the content of an fo:leader with leader-pattern="use-content" collapses to zero width during layout. Committed by JM.
 
 - ![fix](/images/fix.jpg) Fixed ID resolution for nested bookmarks with duplicated IDs. Committed by JM.
 
-- ![fix](/images/fix.jpg) Added LayoutManagerMapping.registerMaker() to make registration of custom layout managers easier. Committed by JM. See Issue [45470](http://issues.apache.org/bugzilla/show_bug.cgi?id=45470) .
+- ![fix](/images/fix.jpg) Added LayoutManagerMapping.registerMaker() to make registration of custom layout managers easier. Committed by JM. See Issue [45470](http://issues.apache.org/bugzilla/show_bug.cgi?id=45470).
 
 - ![fix](/images/fix.jpg) Fixed absolute positioning of block-containers when specified using right and bottom instead of left and top. Committed by LF.
 
 - ![fix](/images/fix.jpg) Fixed an inconsistency in footnote handling that led to unnecessary empty areas in pages whose last normal line contains footnotes when the page bpd is not the same for all pages. Committed by LF.
 
-- ![fix](/images/fix.jpg) Added support for page-number-citation and page-number-citation-last of fo:inline. Corrected behavior for page-number-citation-last of fo:block: forward references now properly resolved. Committed by AD. See Issue [44794](http://issues.apache.org/bugzilla/show_bug.cgi?id=44794) .
+- ![fix](/images/fix.jpg) Added support for page-number-citation and page-number-citation-last of fo:inline. Corrected behavior for page-number-citation-last of fo:block: forward references now properly resolved. Committed by AD. See Issue [44794](http://issues.apache.org/bugzilla/show_bug.cgi?id=44794).
 
-- ![fix](/images/fix.jpg) Added support for the "id" attribute on fo:wrappers when used as a child of the fo:flow. Committed by AD. See Issue [42423](http://issues.apache.org/bugzilla/show_bug.cgi?id=42423) .
+- ![fix](/images/fix.jpg) Added support for the "id" attribute on fo:wrappers when used as a child of the fo:flow. Committed by AD. See Issue [42423](http://issues.apache.org/bugzilla/show_bug.cgi?id=42423).
 
-- ![fix](/images/fix.jpg) Fixed a ClassCastException when using an fo:wrapper as a child of an fo:block-container. Committed by AD. See Issue [41500](http://issues.apache.org/bugzilla/show_bug.cgi?id=41500) .
+- ![fix](/images/fix.jpg) Fixed a ClassCastException when using an fo:wrapper as a child of an fo:block-container. Committed by AD. See Issue [41500](http://issues.apache.org/bugzilla/show_bug.cgi?id=41500).
 
-- ![fix](/images/fix.jpg) Fixed a regression introduced by the fix for [Bugzilla 44286](https://issues.apache.org/bugzilla/show_bug.cgi?id=44286) . Committed by AD. See Issue [42703](http://issues.apache.org/bugzilla/show_bug.cgi?id=42703) .
+- ![fix](/images/fix.jpg) Fixed a regression introduced by the fix for [Bugzilla 44286](https://issues.apache.org/bugzilla/show_bug.cgi?id=44286). Committed by AD. See Issue [42703](http://issues.apache.org/bugzilla/show_bug.cgi?id=42703).
 
-- ![fix](/images/fix.jpg) Activated min-height/max-height and min-width/max-width properties. Committed by AD. See Issue [43591](http://issues.apache.org/bugzilla/show_bug.cgi?id=43591) .
+- ![fix](/images/fix.jpg) Activated min-height/max-height and min-width/max-width properties. Committed by AD. See Issue [43591](http://issues.apache.org/bugzilla/show_bug.cgi?id=43591).
 
 ### Changes to Renderers (Output Formats) <a id="Renderers_1.0"></a>
 
 
 - ![add](/images/add.jpg) AFP Output: Added enhanced dithering functionality for images that are converted to bi-level images. Committed by JM.
 
-- ![add](/images/add.jpg) Initial support for CID-keyed double-byte fonts (Type 0) in AFP output. Committed by JM. Thanks to Peter Hancock. See Issue [48567](http://issues.apache.org/bugzilla/show_bug.cgi?id=48567) .
+- ![add](/images/add.jpg) Initial support for CID-keyed double-byte fonts (Type 0) in AFP output. Committed by JM. Thanks to Peter Hancock. See Issue [48567](http://issues.apache.org/bugzilla/show_bug.cgi?id=48567).
 
 - ![add](/images/add.jpg) Added possibility to customize PDF tagging via the ‘role’ property. Committed by VH.
 
-- ![add](/images/add.jpg) Added basic accessibility and Tagged PDF support. Committed by JM,VH. Thanks to Jost Klopfstein. See Issue [46705](http://issues.apache.org/bugzilla/show_bug.cgi?id=46705) .
+- ![add](/images/add.jpg) Added basic accessibility and Tagged PDF support. Committed by JM,VH. Thanks to Jost Klopfstein. See Issue [46705](http://issues.apache.org/bugzilla/show_bug.cgi?id=46705).
 
 - ![add](/images/add.jpg) Added support for encoding CMYK bitmap images (IOCA FS45) and TIFF images as embedded objects. Committed by JM.
 
@@ -197,7 +197,7 @@ Committed by AD. Thanks to rogov.AT.deve
 
 - ![add](/images/add.jpg) AFP Output: Added support for IMM Extension on fo:simple-page-master. Committed by CB.
 
-- ![add](/images/add.jpg) Added an initial set of extensions for prepress support (fox:bleed, fox:crop-offset, fox:crop-box and fox:scale). This is currently supported only by PDF and Java2D renderers. Committed by JM. Thanks to Peter Coppens. See Issue [47311](http://issues.apache.org/bugzilla/show_bug.cgi?id=47311) .
+- ![add](/images/add.jpg) Added an initial set of extensions for prepress support (fox:bleed, fox:crop-offset, fox:crop-box and fox:scale). This is currently supported only by PDF and Java2D renderers. Committed by JM. Thanks to Peter Coppens. See Issue [47311](http://issues.apache.org/bugzilla/show_bug.cgi?id=47311).
 
 - ![add](/images/add.jpg) PCL Output: Added support for specifying the output bin. Committed by JM.
 
@@ -214,7 +214,7 @@ Committed by AD.
 
 - ![add](/images/add.jpg) Added setting to enable dithered painting of filled rectangles in AFP and PCL. Committed by JM.
 
-- ![add](/images/add.jpg) Added a custom text painter for rendering SVG text using text operators when rendering to PostScript or EPS. Text is no longer painted as shapes, thus creating much smaller files. Committed by JM. See Issue [47000](http://issues.apache.org/bugzilla/show_bug.cgi?id=47000) .
+- ![add](/images/add.jpg) Added a custom text painter for rendering SVG text using text operators when rendering to PostScript or EPS. Text is no longer painted as shapes, thus creating much smaller files. Committed by JM. See Issue [47000](http://issues.apache.org/bugzilla/show_bug.cgi?id=47000).
 
 - ![add](/images/add.jpg) AFP Output: Tag Logical Element (TLE) is now also allowed on fo:page-sequence (page group level). Committed by JM.
 
@@ -232,55 +232,55 @@ Committed by AD.
 
 - ![add](/images/add.jpg) AFP Output: Native image embedding support (e.g. JPEG, GIF, TIFF) using ObjectContainer and a MOD:CA Registry implementation. Committed by AC.
 
-- ![add](/images/add.jpg) Added PDF /Launch action: references to URIs using the file:// protocol will now generate a /Launch action as opposed to a more general /URI (which doesn't yield the expected result for this protocol). Committed by AD. Thanks to Alexander Stamenov. See Issue [45113](http://issues.apache.org/bugzilla/show_bug.cgi?id=45113) .
+- ![add](/images/add.jpg) Added PDF /Launch action: references to URIs using the file:// protocol will now generate a /Launch action as opposed to a more general /URI (which doesn't yield the expected result for this protocol). Committed by AD. Thanks to Alexander Stamenov. See Issue [45113](http://issues.apache.org/bugzilla/show_bug.cgi?id=45113).
 
-- ![add](/images/add.jpg) PDF Output: Added support for handling 16-bit alpha channel. They are currently converted to 8 bits. Committed by JM. See Issue [45795](http://issues.apache.org/bugzilla/show_bug.cgi?id=45795) .
+- ![add](/images/add.jpg) PDF Output: Added support for handling 16-bit alpha channel. They are currently converted to 8 bits. Committed by JM. See Issue [45795](http://issues.apache.org/bugzilla/show_bug.cgi?id=45795).
 
 - ![add](/images/add.jpg) Added PDF encryption parameter support in configuration. Committed by AC.
 
-- ![add](/images/add.jpg) Added a PCL-specific extension attribute on simple-page-master for controlling the simplex/duplex mode. Committed by JM. Thanks to Martin Edge. See Issue [45115](http://issues.apache.org/bugzilla/show_bug.cgi?id=45115) .
+- ![add](/images/add.jpg) Added a PCL-specific extension attribute on simple-page-master for controlling the simplex/duplex mode. Committed by JM. Thanks to Martin Edge. See Issue [45115](http://issues.apache.org/bugzilla/show_bug.cgi?id=45115).
 
-- ![add](/images/add.jpg) Add partial support for the "show-destination" property on fo:basic-link (PDF output only; see limitations on the compliance page) Committed by AD. See Issue [44634](http://issues.apache.org/bugzilla/show_bug.cgi?id=44634) .
+- ![add](/images/add.jpg) Add partial support for the "show-destination" property on fo:basic-link (PDF output only; see limitations on the compliance page) Committed by AD. See Issue [44634](http://issues.apache.org/bugzilla/show_bug.cgi?id=44634).
 
 - ![add](/images/add.jpg) Added support for rendering pages using JPS (Java Printing System). See new example: examples/embedding/java/ExamplesFO2JPSPrint.java Committed by JM.
 
-- ![add](/images/add.jpg) Restored ability to specify from/to and odd/even pages as well as the number of copies for printing from the command-line. Committed by JM. See Issue [41687](http://issues.apache.org/bugzilla/show_bug.cgi?id=41687) .
+- ![add](/images/add.jpg) Restored ability to specify from/to and odd/even pages as well as the number of copies for printing from the command-line. Committed by JM. See Issue [41687](http://issues.apache.org/bugzilla/show_bug.cgi?id=41687).
 
-- ![add](/images/add.jpg) Added ability to pass a preconfigured PrinterJob instance to the PrintRenderer via the rendering options map. Committed by JM. Thanks to Antti Karanta. See Issue [44678](http://issues.apache.org/bugzilla/show_bug.cgi?id=44678) .
+- ![add](/images/add.jpg) Added ability to pass a preconfigured PrinterJob instance to the PrintRenderer via the rendering options map. Committed by JM. Thanks to Antti Karanta. See Issue [44678](http://issues.apache.org/bugzilla/show_bug.cgi?id=44678).
 
-- ![add](/images/add.jpg) Added a public accessor for reference to the current page to PDFGraphics2D. Committed by JM. Thanks to Yegor Kozlov. See Issue [44743](http://issues.apache.org/bugzilla/show_bug.cgi?id=44743) .
+- ![add](/images/add.jpg) Added a public accessor for reference to the current page to PDFGraphics2D. Committed by JM. Thanks to Yegor Kozlov. See Issue [44743](http://issues.apache.org/bugzilla/show_bug.cgi?id=44743).
 
 - ![fix](/images/fix.jpg) AFP Output: Fixed positioning of Java2D-based images (when GOCA is enabled). Committed by JM.
 
 - ![fix](/images/fix.jpg) AFP Output: Fix for bitmap images inside an SVG or G2D graphic (printer errors) and positioning fix for bitmaps from G2D graphics. Committed by JM.
 
-- ![fix](/images/fix.jpg) Fix for AWT viewer to correctly track page numbers in continuous display mode. Committed by JM. Thanks to Richard Wheeldon. See Issue [42306](http://issues.apache.org/bugzilla/show_bug.cgi?id=42306) .
+- ![fix](/images/fix.jpg) Fix for AWT viewer to correctly track page numbers in continuous display mode. Committed by JM. Thanks to Richard Wheeldon. See Issue [42306](http://issues.apache.org/bugzilla/show_bug.cgi?id=42306).
 
 - ![fix](/images/fix.jpg) Bugfix for formatting of floating point numbers which could lead to invalid PDFs. Committed by JM.
 
 - ![fix](/images/fix.jpg) Added a save/restoreGraphicsState pair for the initial coordinate system in PDF output for easier post-processing. Committed by JM.
 
-- ![fix](/images/fix.jpg) Bugfix for color model in IOCA IDE structure parameter for 4- and 8-bit grayscale images. Committed by JM. Thanks to Peter Hancock. See Issue [48696](http://issues.apache.org/bugzilla/show_bug.cgi?id=48696) .
+- ![fix](/images/fix.jpg) Bugfix for color model in IOCA IDE structure parameter for 4- and 8-bit grayscale images. Committed by JM. Thanks to Peter Hancock. See Issue [48696](http://issues.apache.org/bugzilla/show_bug.cgi?id=48696).
 
-- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: Respect image color settings for svg Committed by CB. Thanks to Peter Hancock. See Issue [48237](http://issues.apache.org/bugzilla/show_bug.cgi?id=48237) .
+- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: Respect image color settings for svg Committed by CB. Thanks to Peter Hancock. See Issue [48237](http://issues.apache.org/bugzilla/show_bug.cgi?id=48237).
 
-- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: Page Overlays not generated when using Intermediate Format Committed by CB. Thanks to Venkat Reddy. See Issue [48376](http://issues.apache.org/bugzilla/show_bug.cgi?id=48376) .
+- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: Page Overlays not generated when using Intermediate Format Committed by CB. Thanks to Venkat Reddy. See Issue [48376](http://issues.apache.org/bugzilla/show_bug.cgi?id=48376).
 
-- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: Underline is incorrectly placed when reference-orientation != 0 Committed by CB. See Issue [48456](http://issues.apache.org/bugzilla/show_bug.cgi?id=48456) .
+- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: Underline is incorrectly placed when reference-orientation != 0 Committed by CB. See Issue [48456](http://issues.apache.org/bugzilla/show_bug.cgi?id=48456).
 
-- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: Page Segments not positioned correctly when reference-orientation != 0 Committed by CB. See Issue [48453](http://issues.apache.org/bugzilla/show_bug.cgi?id=48453) .
+- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: Page Segments not positioned correctly when reference-orientation != 0 Committed by CB. See Issue [48453](http://issues.apache.org/bugzilla/show_bug.cgi?id=48453).
 
-- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: AttributeQualifier Triplet occurs before TLE Value. Committed by CB. See Issue [48290](http://issues.apache.org/bugzilla/show_bug.cgi?id=48290) .
+- ![fix](/images/fix.jpg) Bugfix: AFP Renderer: AttributeQualifier Triplet occurs before TLE Value. Committed by CB. See Issue [48290](http://issues.apache.org/bugzilla/show_bug.cgi?id=48290).
 
-- ![fix](/images/fix.jpg) Bugfix in AFP output: fixed flags in GOCA GBAR order. Committed by JM. Thanks to D.W. Harks. See Issue [48048](http://issues.apache.org/bugzilla/show_bug.cgi?id=48048) .
+- ![fix](/images/fix.jpg) Bugfix in AFP output: fixed flags in GOCA GBAR order. Committed by JM. Thanks to D.W. Harks. See Issue [48048](http://issues.apache.org/bugzilla/show_bug.cgi?id=48048).
 
-- ![fix](/images/fix.jpg) Bugfix in AFP output: rounding error when computing the CMYK components of a color. Committed by VH. Thanks to Harald G. Henne. See Issue [48185](http://issues.apache.org/bugzilla/show_bug.cgi?id=48185) .
+- ![fix](/images/fix.jpg) Bugfix in AFP output: rounding error when computing the CMYK components of a color. Committed by VH. Thanks to Harald G. Henne. See Issue [48185](http://issues.apache.org/bugzilla/show_bug.cgi?id=48185).
 
-- ![fix](/images/fix.jpg) BugFix: Maintain valid AFP by providing TLE truncation on Attribute Value Triplet values that are greater than 250 chars in length. Committed by AC. See Issue [47941](http://issues.apache.org/bugzilla/show_bug.cgi?id=47941) .
+- ![fix](/images/fix.jpg) BugFix: Maintain valid AFP by providing TLE truncation on Attribute Value Triplet values that are greater than 250 chars in length. Committed by AC. See Issue [47941](http://issues.apache.org/bugzilla/show_bug.cgi?id=47941).
 
-- ![fix](/images/fix.jpg) Dithered Background Shading can produce illegal AFP if objects are very small Committed by CB. See Issue [47694](http://issues.apache.org/bugzilla/show_bug.cgi?id=47694) .
+- ![fix](/images/fix.jpg) Dithered Background Shading can produce illegal AFP if objects are very small Committed by CB. See Issue [47694](http://issues.apache.org/bugzilla/show_bug.cgi?id=47694).
 
-- ![fix](/images/fix.jpg) Bugfix: Error while writing TLE's attribute qualifier in the output. Committed by AD. Thanks to Bharat Attaluri. See Issue [47508](http://issues.apache.org/bugzilla/show_bug.cgi?id=47508) .
+- ![fix](/images/fix.jpg) Bugfix: Error while writing TLE's attribute qualifier in the output. Committed by AD. Thanks to Bharat Attaluri. See Issue [47508](http://issues.apache.org/bugzilla/show_bug.cgi?id=47508).
 
 - ![fix](/images/fix.jpg) Bugfix: support justified text in AFP Renderer (already working in AFP Painter) Committed by CB.
 
@@ -288,29 +288,29 @@ Committed by AD.
 
 - ![fix](/images/fix.jpg) Fixed a bug that left the PrintRenderer unconfigured even if a configuration was specified for "application/X-fop-print". Committed by JM.
 
-- ![fix](/images/fix.jpg) Fixed the handling of CMYK colors in PDFGraphics2D. Committed by JM. Thanks to Yegor Kozlov. See Issue [46882](http://issues.apache.org/bugzilla/show_bug.cgi?id=46882) .
+- ![fix](/images/fix.jpg) Fixed the handling of CMYK colors in PDFGraphics2D. Committed by JM. Thanks to Yegor Kozlov. See Issue [46882](http://issues.apache.org/bugzilla/show_bug.cgi?id=46882).
 
-- ![fix](/images/fix.jpg) AFP Fonts: Fixed interpretation of metric for fonts with fixed metrics and made sure all repeating groups in FNP (Font Position) are processed. Committed by JM. Thanks to Emil Maskovsky. See Issue [45342](http://issues.apache.org/bugzilla/show_bug.cgi?id=45342) .
+- ![fix](/images/fix.jpg) AFP Fonts: Fixed interpretation of metric for fonts with fixed metrics and made sure all repeating groups in FNP (Font Position) are processed. Committed by JM. Thanks to Emil Maskovsky. See Issue [45342](http://issues.apache.org/bugzilla/show_bug.cgi?id=45342).
 
 - ![fix](/images/fix.jpg) Fixed black backgrounds occurring for transparent images in PCL output. Committed by JM.
 
-- ![fix](/images/fix.jpg) Fixed bug that caused AFP Renderer Extensions to be ignored. Committed by CB. See Issue [46369](http://issues.apache.org/bugzilla/show_bug.cgi?id=46369) .
+- ![fix](/images/fix.jpg) Fixed bug that caused AFP Renderer Extensions to be ignored. Committed by CB. See Issue [46369](http://issues.apache.org/bugzilla/show_bug.cgi?id=46369).
 
 - ![fix](/images/fix.jpg) Fixed a multi-threading issue when rendering SVG. Committed by JM.
 
 - ![fix](/images/fix.jpg) PDF Output: Made sure the XMP Metadata stream is never compressed. Committed by JM.
 
-- ![fix](/images/fix.jpg) Fix for table handling in RTF output, so the output works with OpenOffice and AbiWord, too. Committed by JM. Thanks to Pavel Kysilka. See Issue [45616](http://issues.apache.org/bugzilla/show_bug.cgi?id=45616) .
+- ![fix](/images/fix.jpg) Fix for table handling in RTF output, so the output works with OpenOffice and AbiWord, too. Committed by JM. Thanks to Pavel Kysilka. See Issue [45616](http://issues.apache.org/bugzilla/show_bug.cgi?id=45616).
 
 - ![fix](/images/fix.jpg) Fixed text stroking in SVG when the stroke-width is zero. Committed by JM.
 
 - ![fix](/images/fix.jpg) Fixed border trait parsing for the area tree XML when CMYK or ICC colors were used. Committed by JM.
 
-- ![fix](/images/fix.jpg) Fixed generation of "fonttbl" for RTF output to fix loading problem with AbiWord. Committed by JM. Thanks to Pavel Kysilka. See Issue [45606](http://issues.apache.org/bugzilla/show_bug.cgi?id=45606) .
+- ![fix](/images/fix.jpg) Fixed generation of "fonttbl" for RTF output to fix loading problem with AbiWord. Committed by JM. Thanks to Pavel Kysilka. See Issue [45606](http://issues.apache.org/bugzilla/show_bug.cgi?id=45606).
 
-- ![fix](/images/fix.jpg) PCL Renderer: Improved page format selection so it doesn't interfere with duplex printing. Committed by JM. See Issue [43650](http://issues.apache.org/bugzilla/show_bug.cgi?id=43650) .
+- ![fix](/images/fix.jpg) PCL Renderer: Improved page format selection so it doesn't interfere with duplex printing. Committed by JM. See Issue [43650](http://issues.apache.org/bugzilla/show_bug.cgi?id=43650).
 
-- ![update](/images/update.jpg) PDFGraphics2D.writeClip doesn't generate a clip command anymore when the clip path is empty. Committed by JM. Thanks to Francois Fernandes. See Issue [47031](http://issues.apache.org/bugzilla/show_bug.cgi?id=47031) .
+- ![update](/images/update.jpg) PDFGraphics2D.writeClip doesn't generate a clip command anymore when the clip path is empty. Committed by JM. Thanks to Francois Fernandes. See Issue [47031](http://issues.apache.org/bugzilla/show_bug.cgi?id=47031).
 
 - ![update](/images/update.jpg) When a JPEG image is embedded, an optionally embedded color profile is filtered out as it's already embedded separately in the PDF file. Committed by JM.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/compiling.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/compiling.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/compiling.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/compiling.mdtext Wed Dec  5 08:19:09 2012
@@ -21,7 +21,7 @@ There is generally no need to setup a cl
 
 ### JAVA_HOME <a id="env-java-home"></a>
 
-The build script uses [Apache Ant](http://ant.apache.org/) , 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.4 or above, which normally does not need this setting.
+The build script uses [Apache Ant](http://ant.apache.org/), 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.4 or above, which normally does not need this setting.
 
 ### Apache Ant <a id="env-ant"></a>
 
@@ -36,11 +36,11 @@ ant -projecthelp
 The most useful targets are:
 
 
--  **package** : Generates the JAR files (default). This is the normal build that produces a jar file usable for running FOP.
+-  **package**: Generates the JAR files (default). This is the normal build that produces a jar file usable for running FOP.
 
--  **clean** : Cleans the build directory. This is useful for making sure that any build errors are cleaned up before starting a new build. It should not ordinarily be needed, but may be helpful if you are having problems with the build process itself.
+-  **clean**: Cleans the build directory. This is useful for making sure that any build errors are cleaned up before starting a new build. It should not ordinarily be needed, but may be helpful if you are having problems with the build process itself.
 
--  **javadocs** : Creates the FOP API documentation.A minimum JDK version of 1.4.2 is required for generating the javadocs.
+-  **javadocs**: Creates the FOP API documentation.A minimum JDK version of 1.4.2 is required for generating the javadocs.
 
 To run the build:
 ant [target ...]

Modified: xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext Wed Dec  5 08:19:09 2012
@@ -14,9 +14,9 @@ The easiest way to get started using a F
 After creating your configuration file, you must tell FOP how to find it:
 
 
-- If running FOP from the command-line, see the "-c" command-line option in [Running FOP](running.html) .
+- If running FOP from the command-line, see the "-c" command-line option in [Running FOP](running.html).
 
-- If running FOP as an embedded application, see [Embedding, Using a Configuration File](embedding.html#config-external) .
+- If running FOP as an embedded application, see [Embedding, Using a Configuration File](embedding.html#config-external).
 
 See [Setting the Configuration Programmatically](embedding.html#config-internal) for instructions on how to do so in an embedded environment.
 
@@ -117,7 +117,7 @@ The configuration for the PDF Renderer c
       <renderer mime="application/postscript">
       <!-- etc. etc..... -->
 
-The details on the font configuration can be found on the separate [Fonts](fonts.html) page. Note especially the section entitled [Register Fonts with FOP](fonts.html#register) .
+The details on the font configuration can be found on the separate [Fonts](fonts.html) page. Note especially the section entitled [Register Fonts with FOP](fonts.html#register).
 
 ### Special Settings for the PDF Renderer <a id="pdf-renderer"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext?rev=1417307&r1=1417306&r2=1417307&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext Wed Dec  5 08:19:09 2012
@@ -74,7 +74,7 @@ This may look complicated at first, but 
 
 ### Logging <a id="basic-logging"></a>
 
-Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to [Jakarta Commons Logging](http://commons.apache.org/logging/) . While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.
+Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to [Jakarta Commons Logging](http://commons.apache.org/logging/). While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.
 
 By default, [Jakarta Commons Logging](http://commons.apache.org/logging/) uses JDK logging (available in JDKs 1.4 or higher) as its backend. You can configure Commons Logging to use an alternative backend, for example Log4J. Please consult the [documentation for Jakarta Commons Logging](http://commons.apache.org/logging/) on how to configure alternative backends.
 
@@ -85,7 +85,7 @@ As a result of the above we differentiat
 
 -  [User/Integrator-oriented feedback](events.html) (NEW!)
 
-The use of "feedback" instead of "logging" is intentional. Most people were using log output as a means to get feedback from events within FOP. Therefore, FOP now includes an `event` package which can be used to receive feedback from the layout engine and other components within FOP **per rendering run** . This feedback is not just some text but event objects with parameters so these events can be interpreted by code. Of course, there is a facility to turn these events into normal human-readable messages. For details, please read on on the [Events page](events.html) . This leaves normal logging to be mostly a thing used by the FOP developers although anyone can surely activate certain logging categories but the feedback from the loggers won't be separated by processing runs. If this is required, the [Events subsystem](events.html) is the right approach.
+The use of "feedback" instead of "logging" is intentional. Most people were using log output as a means to get feedback from events within FOP. Therefore, FOP now includes an `event` package which can be used to receive feedback from the layout engine and other components within FOP **per rendering run**. This feedback is not just some text but event objects with parameters so these events can be interpreted by code. Of course, there is a facility to turn these events into normal human-readable messages. For details, please read on on the [Events page](events.html). This leaves normal logging to be mostly a thing used by the FOP developers although anyone can surely activate certain logging categories but the feedback from the loggers won't be separated by processing runs. If this is required, the [Events subsystem](events.html) is the right approach.
 
 ### Processing XSL-FO <a id="render"></a>
 
@@ -123,7 +123,7 @@ However, you may not always have your in
 
 -  **Java Objects:** Please have a look at the [Embedding examples](#examples) which contain an example for this.
 
-There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in [Xalan Basic Usage Patterns](http://xml.apache.org/xalan-j/usagepatterns.html) .
+There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in [Xalan Basic Usage Patterns](http://xml.apache.org/xalan-j/usagepatterns.html).
 
 ## Configuring Apache FOP Programmatically <a id="config-internal"></a>
 
@@ -147,7 +147,7 @@ The **hyphenation base URL** to use when
     `fopFactory.setHyphenBaseURL("file:///C:/Temp/hyph");`
 
 -
-Disable **strict validation** . When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:
+Disable **strict validation**. When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:
 
     `fopFactory.setStrictValidation(false);`
 
@@ -162,7 +162,7 @@ Set the **source resolution** for the do
     `fopFactory.setSourceResolution(96); // =96dpi (dots/pixels per Inch)`
 
 -
-Manually add an **ElementMapping instance** . If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:
+Manually add an **ElementMapping instance**. If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:
 
     `fopFactory.addElementMapping(myElementMapping); // myElementMapping is a org.apache.fop.fo.ElementMapping`
 
@@ -228,12 +228,12 @@ Set the **target resolution** for the do
     `userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)`
 
 -
-Set **your own Renderer instance** . If you want to supply your own renderer or configure a Renderer in a special way you can give the instance to the FOUserAgent. Normally, the Renderer instance is created by FOP. Example:
+Set **your own Renderer instance**. If you want to supply your own renderer or configure a Renderer in a special way you can give the instance to the FOUserAgent. Normally, the Renderer instance is created by FOP. Example:
 
     `userAgent.setRendererOverride(myRenderer); // myRenderer is an org.apache.fop.render.Renderer`
 
 -
-Set **your own FOEventHandler instance** . If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:
+Set **your own FOEventHandler instance**. If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:
 
     `userAgent.setFOEventHandlerOverride(myFOEventHandler); // myFOEventHandler is an org.apache.fop.fo.FOEventHandler`
 
@@ -261,7 +261,7 @@ Instead of setting the parameters manual
 
     fopFactory.setUserConfig(new File("C:/Temp/mycfg.xml"));
 
-The layout of the configuration file is described on the [Configuration page](configuration.html) .
+The layout of the configuration file is described on the [Configuration page](configuration.html).
 
 ## Hints <a id="hints"></a>
 
@@ -273,13 +273,13 @@ Fop instances shouldn't (and can't) be r
 
 If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is initialised it uses certain classes in `java.awt` that intialise the Java AWT classes. This means that a daemon thread is created by the JVM and on Unix it will need to connect to a DISPLAY.
 
-The thread means that the Java application may not automatically quit when finished, you will need to call `System.exit()` . These issues should be fixed in the JDK 1.4.
+The thread means that the Java application may not automatically quit when finished, you will need to call `System.exit()`. These issues should be fixed in the JDK 1.4.
 
-If you run into trouble running FOP on a head-less server, please see the [notes on Batik](graphics.html#batik) .
+If you run into trouble running FOP on a head-less server, please see the [notes on Batik](graphics.html#batik).
 
 ### Getting information on the rendering process <a id="render-info"></a>
 
-To get the number of pages that were rendered by FOP you can call `Fop.getResults()` . This returns a `FormattingResults` object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.
+To get the number of pages that were rendered by FOP you can call `Fop.getResults()`. This returns a `FormattingResults` object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.
 
 ## Improving performance <a id="performance"></a>
 
@@ -290,13 +290,13 @@ There are several options to consider:
 
 - Depending on the target OutputStream (in case of a FileOutputStream, but not for a ByteArrayOutputStream, for example) it may improve performance considerably if you buffer the OutputStream using a BufferedOutputStream: `out = new java.io.BufferedOutputStream(out);` <br></br>Make sure you properly close the OutputStream when FOP is finished.
 
-- Cache the stylesheet. If you use the same stylesheet multiple times you can set up a JAXP `Templates` object and reuse it each time you do the XSL transformation. (More information can be found [here](http://www.javaworld.com/javaworld/jw-05-2003/jw-0502-xsl.html) .)
+- Cache the stylesheet. If you use the same stylesheet multiple times you can set up a JAXP `Templates` object and reuse it each time you do the XSL transformation. (More information can be found [here](http://www.javaworld.com/javaworld/jw-05-2003/jw-0502-xsl.html).)
 
 - Use an XSLT compiler like [XSLTC](http://xml.apache.org/xalan-j/xsltc_usage.html) that comes with Xalan-J.
 
 - Fine-tune your stylesheet to make the XSLT process more efficient and to create XSL-FO that can be processed by FOP more efficiently. Less is more: Try to make use of property inheritance where possible.
 
-- You may also wish to consider trying to reduce [memory usage](http://xmlgraphics.apache.org/fop/trunk/running.html#memory) .
+- You may also wish to consider trying to reduce [memory usage](http://xmlgraphics.apache.org/fop/trunk/running.html#memory).
 
 ## Multithreading FOP <a id="multithreading"></a>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message