You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2012/10/24 06:26:12 UTC
svn commit: r835978 [10/16] - in
/websites/staging/xmlgraphics/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/
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html Wed Oct 24 04:26:06 2012
@@ -331,9 +331,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/1.1/">1.1</a></div> -->
<div class="section-content"><h1 id="release-notes-for-apache-fop-11">Release Notes for Apache FOP 1.1</h1>
-<h2 id="major-changes-in-version-11-wzxhzdk0wzxhzdk1">Major Changes in Version 1.1 <a id="version_1.1"></a></h2>
+<h2 id="major-changes-in-version-11-wzxhzdk0wzxhzdk1">Major Changes in Version 1.1 <a id="version_1.1"></a></h2>
<p>This is not a complete list of changes, just some of the more important ones. A full list of changes in this release <a href="changes_1.1.html">is available</a> .</p>
-<h2 id="changes-to-the-code-base-wzxhzdk2wzxhzdk3">Changes to the Code Base # <a id="Changes+to+the+Code+Base"></a></h2>
+<h2 id="changes-to-the-code-base-wzxhzdk2wzxhzdk3">Changes to the Code Base <a id="Changes+to+the+Code+Base"></a></h2>
<ul>
<li>
<p><icon alt="fix" src="../images/fix.jpg"></icon>Update to use of checkstyle-5.5 as default configuration. Remove checkstyle-4.0 configuration. Also, import environment build properties before local properties, so that latter can refer to former. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53083">53083</a> .</p>
@@ -375,11 +375,11 @@ $(document).ready(function () {
<p><icon alt="add" src="../images/add.jpg"></icon>Added support for resolution of relative URIs against a specified xml:base during property refinement. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=48334">48334</a> .</p>
</li>
</ul>
-<h3 id="changes-to-the-user-configuration-wzxhzdk4wzxhzdk5">Changes to the User Configuration # <a id="Changes+to+the+User+Configuration"></a></h3>
+<h3 id="changes-to-the-user-configuration-wzxhzdk4wzxhzdk5">Changes to the User Configuration <a id="Changes+to+the+User+Configuration"></a></h3>
<ul>
<li><icon alt="add" src="../images/add.jpg"></icon>Added configuration option to set the version of the output PDF document. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51385">51385</a> .</li>
</ul>
-<h3 id="changes-to-the-font-subsystem-wzxhzdk6wzxhzdk7">Changes to the Font Subsystem # <a id="Changes+to+the+Font+Subsystem"></a></h3>
+<h3 id="changes-to-the-font-subsystem-wzxhzdk6wzxhzdk7">Changes to the Font Subsystem <a id="Changes+to+the+Font+Subsystem"></a></h3>
<ul>
<li>
<p><icon alt="add" src="../images/add.jpg"></icon>Add support for OpenType advanced typographic tables (GDEF, GSUB, GPOS). Committed by GA.</p>
@@ -397,11 +397,11 @@ $(document).ready(function () {
<p><icon alt="add" src="../images/add.jpg"></icon>Added convenience support for the flushing of the Fop font cache file from the command line. Committed by AC.</p>
</li>
</ul>
-<h3 id="changes-to-the-image-support-wzxhzdk8wzxhzdk9">Changes to the Image Support # <a id="Changes+to+the+Image+Support"></a></h3>
+<h3 id="changes-to-the-image-support-wzxhzdk8wzxhzdk9">Changes to the Image Support <a id="Changes+to+the+Image+Support"></a></h3>
<ul>
<li><icon alt="fix" src="../images/fix.jpg"></icon>Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecssary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40676">40676</a> .</li>
</ul>
-<h3 id="changes-to-the-layout-engine-wzxhzdk10wzxhzdk11">Changes to the Layout Engine # <a id="Changes+to+the+Layout+Engine"></a></h3>
+<h3 id="changes-to-the-layout-engine-wzxhzdk10wzxhzdk11">Changes to the Layout Engine <a id="Changes+to+the+Layout+Engine"></a></h3>
<ul>
<li>
<p><icon alt="fix" src="../images/fix.jpg"></icon>Fix for break before (break-before) not respected on blocks nested in inlines. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45715">45715</a> .</p>
@@ -428,7 +428,7 @@ $(document).ready(function () {
<p><icon alt="fix" src="../images/fix.jpg"></icon>Fix for correct behavior of keep-together.within-line in case there are nested inlines Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49848">49848</a> .</p>
</li>
</ul>
-<h3 id="changes-to-renderers-output-formats-wzxhzdk12wzxhzdk13">Changes to Renderers (Output Formats) # <a id="Changes+to+Renderers+%28Output+Formats%29"></a></h3>
+<h3 id="changes-to-renderers-output-formats-wzxhzdk12wzxhzdk13">Changes to Renderers (Output Formats) <a id="Changes+to+Renderers+%28Output+Formats%29"></a></h3>
<ul>
<li>
<p><icon alt="add" src="../images/add.jpg"></icon>Added possibility to embed TrueType fonts in PostScript. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52338">52338</a> .</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html Wed Oct 24 04:26:06 2012
@@ -332,7 +332,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/1.1/">1.1</a></div> -->
<div class="section-content"><h1 id="running-apachewzxhzdk0-fop">Running Apache™ FOP</h1>
<p><version>$Revision$</version></p>
-<h2 id="system-requirements-wzxhzdk3wzxhzdk4">System Requirements <a id="require"></a></h2>
+<h2 id="system-requirements-wzxhzdk3wzxhzdk4">System Requirements <a id="require"></a></h2>
<p>The following software must be installed:</p>
<ul>
<li>
@@ -375,13 +375,13 @@ $(document).ready(function () {
<ul>
<li>If you will be using FOP to process SVG, you must do so in a graphical environment. See <a href="graphics.html#batik">FOP: Graphics (Batik)</a> for details.</li>
</ul>
-<h2 id="installation-wzxhzdk5wzxhzdk6">Installation <a id="install"></a></h2>
-<h3 id="instructions-wzxhzdk7wzxhzdk8">Instructions # <a id="install-instruct"></a></h3>
+<h2 id="installation-wzxhzdk5wzxhzdk6">Installation <a id="install"></a></h2>
+<h3 id="instructions-wzxhzdk7wzxhzdk8">Instructions <a id="install-instruct"></a></h3>
<p>Basic FOP installation consists of first unzipping the <code>.gz</code> file that is the distribution medium, then unarchiving the resulting <code>.tar</code> file in a directory/folder that is convenient on your system. Please consult your operating system documentation or Zip application software documentation for instructions specific to your site.</p>
-<h3 id="problems-wzxhzdk9wzxhzdk10">Problems # <a id="install-problems"></a></h3>
+<h3 id="problems-wzxhzdk9wzxhzdk10">Problems <a id="install-problems"></a></h3>
<p>Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users have recommended that Mac OSX users use the shell command <code>tar -xzf</code> instead.</p>
-<h2 id="starting-fop-as-a-standalone-application-wzxhzdk11wzxhzdk12">Starting FOP as a Standalone Application <a id="standalone-start"></a></h2>
-<h3 id="using-the-fop-script-or-batch-file-wzxhzdk13wzxhzdk14">Using the fop script or batch file # <a id="fop-script"></a></h3>
+<h2 id="starting-fop-as-a-standalone-application-wzxhzdk11wzxhzdk12">Starting FOP as a Standalone Application <a id="standalone-start"></a></h2>
+<h3 id="using-the-fop-script-or-batch-file-wzxhzdk13wzxhzdk14">Using the fop script or batch file <a id="fop-script"></a></h3>
<p>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 <code>/Library/Java/Home</code> . <strong>Caveat:</strong> 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 <a href="http://developer.apple.com/java/faq">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
<p>USAGE
Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] <outfile>
@@ -467,20 +467,20 @@ Fop [options] [-fo|-xml] infile [-xsl fi
fop foo.fo -print
fop foo.fo -awt
PDF encryption is only available if FOP was compiled with encryption support <strong>and</strong> if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the <a href="pdfencryption.html">Details</a> .</p>
-<h3 id="writing-your-own-script-wzxhzdk18wzxhzdk19">Writing your own script # <a id="your-own-script"></a></h3>
+<h3 id="writing-your-own-script-wzxhzdk18wzxhzdk19">Writing your own script <a id="your-own-script"></a></h3>
<p>FOP's entry point for your own scripts is the class <code>org.apache.fop.cli.Main</code> . The general pattern for the command line is: <code>java -classpath <CLASSPATH>
org.apache.fop.cli.Main <arguments></code> . 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.</p>
-<h3 id="running-with-javas-jar-option-wzxhzdk20wzxhzdk21">Running with java's -jar option # <a id="jar-option"></a></h3>
+<h3 id="running-with-javas-jar-option-wzxhzdk20wzxhzdk21">Running with java's -jar option <a id="jar-option"></a></h3>
<p>As an alternative to the start scripts you can run <code>java
-jar path/to/build/fop.jar <arguments></code> , relying on FOP to build the classpath for running FOP dynamically, see <a href="#dynamical-classpath">below</a> . If you use hyphenation, you must put <code>fop-hyph.jar</code> in the <code>lib</code> directory.</p>
<p>You can also run <code>java -jar path/to/fop.jar
<arguments></code> , relying on the <code>Class-Path</code> entry in the manifest file. This works if you put <code>fop.jar</code> and all jar files from the <code>lib</code> directory in a single directory. If you use hyphenation, you must also put <code>fop-hyph.jar</code> in that directory.</p>
<p>In both cases the arguments consist of the options and infile and outfile specifications as shown above for the standard scripts.</p>
-<h3 id="fops-dynamical-classpath-construction-wzxhzdk22wzxhzdk23">FOP's dynamical classpath construction # <a id="dynamical-classpath"></a></h3>
+<h3 id="fops-dynamical-classpath-construction-wzxhzdk22wzxhzdk23">FOP's dynamical classpath construction <a id="dynamical-classpath"></a></h3>
<p>If FOP is started without a proper classpath, it tries to add its dependencies dynamically. If the system property <code>fop.home</code> 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 <code>build</code> , then its parent directory becomes the base directory.</p>
<p>FOP expects to find <code>fop.jar</code> in the <code>build</code> subdirectory of the base directory, and adds it to the classpath. Subsequently FOP adds all <code>jar</code> files in the lib directory to the classpath. The lib directory is either the <code>lib</code> subdirectory of the base directory, or, if that does not exist, the base directory itself.</p>
<p>If the system property <code>fop.optional.lib</code> contains the name of a directory, then all <code>jar</code> files in that directory are also added to the classpath. See the methods <code>getJARList</code> and <code>checkDependencies</code> in <code>org.apache.fop.cli.Main</code> .</p>
-<h2 id="using-xalan-to-check-xsl-fo-input-wzxhzdk24wzxhzdk25">Using Xalan to Check XSL-FO Input <a id="check-input"></a></h2>
+<h2 id="using-xalan-to-check-xsl-fo-input-wzxhzdk24wzxhzdk25">Using Xalan to Check XSL-FO Input <a id="check-input"></a></h2>
<p>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 <a href="../resources.html#specs">Specifications</a> and <a href="../resources.html#articles">Books/Articles</a> . 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)
@@ -488,7 +488,7 @@ When asking for help on the FOP mailing
The -foout option works the same way as if you would call the <a href="http://xml.apache.org/xalan-j/commandline.html">Xalan command-line</a> :</p>
<p><code>java org.apache.xalan.xslt.Process -IN xmlfile -XSL file -OUT outfile</code> </p>
<p>Note that there are some subtle differences between the FOP and Xalan command-lines.</p>
-<h2 id="memory-usage-wzxhzdk26wzxhzdk27">Memory Usage <a id="memory"></a></h2>
+<h2 id="memory-usage-wzxhzdk26wzxhzdk27">Memory Usage <a id="memory"></a></h2>
<p>FOP can consume quite a bit of memory, even though this has been continually improved. This is partly inherent to the formatting process and partly caused by implementation choices. All FO processors currently on the market have memory problems with certain layouts.</p>
<p>If you are running out of memory when using FOP, here are some ideas that may help:</p>
<ul>
@@ -505,7 +505,7 @@ The -foout option works the same way as
<p>Use multiple page sequences. FOP starts rendering after the end of a page sequence is encountered. While the actual rendering is done page-by-page, some additional memory is freed after the page sequence has been rendered. This can be substantial if the page sequence contains lots of FO elements.</p>
</li>
</ul>
-<h2 id="problems-wzxhzdk28wzxhzdk29">Problems <a id="problems"></a></h2>
+<h2 id="problems-wzxhzdk28wzxhzdk29">Problems <a id="problems"></a></h2>
<p>If you have problems running FOP, please see the <a href="../gethelp.html">"How to get Help" page</a> .</p></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html Wed Oct 24 04:26:06 2012
@@ -332,9 +332,9 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/1.1/">1.1</a></div> -->
<div class="section-content"><h1 id="apachewzxhzdk2-fop-servlets">Apache™ FOP: Servlets</h1>
<p><subtitle>How to use Apache™ FOP in a Servlet</subtitle><version>$Revision: 1298724 $</version></p>
-<h2 id="overview-wzxhzdk8wzxhzdk9">Overview <a id="overview"></a></h2>
+<h2 id="overview-wzxhzdk8wzxhzdk9">Overview <a id="overview"></a></h2>
<p>This page discusses topic all around using Apache™ FOP in a servlet environment.</p>
-<h2 id="example-servlets-in-the-fop-distribution-wzxhzdk11wzxhzdk12">Example Servlets in the FOP distribution <a id="example-servlets"></a></h2>
+<h2 id="example-servlets-in-the-fop-distribution-wzxhzdk11wzxhzdk12">Example Servlets in the FOP distribution <a id="example-servlets"></a></h2>
<p>In the directory {fop-dir}/src/java/org/apache/fop/servlet, you'll find a working example of a FOP-enabled servlet.</p>
<p>The servlet is automatically built when you build Apache FOP using the supplied Ant script. After building the servlet, drop fop.war into the webapps directory of Apache Tomcat (or any other web container). Then, you can use URLs like the following to generate PDF files:</p>
<ul>
@@ -347,9 +347,9 @@ $(document).ready(function () {
</ul>
<p>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.</p>
-<h1 id="create-your-own-servlet-wzxhzdk13wzxhzdk14">Create your own Servlet <a id="servlet"></a></h1>
+<h1 id="create-your-own-servlet-wzxhzdk13wzxhzdk14">Create your own Servlet <a id="servlet"></a></h1>
<p>This section assumes you are familiar with <a href="embedding.html">embedding FOP</a> .</p>
-<h2 id="a-minimal-servlet-wzxhzdk15wzxhzdk16">A minimal Servlet # <a id="minimal-servlet"></a></h2>
+<h2 id="a-minimal-servlet-wzxhzdk15wzxhzdk16">A minimal Servlet <a id="minimal-servlet"></a></h2>
<p>Here is a minimal code snippet to demonstrate the basics:
private FopFactory fopFactory = FopFactory.newInstance();
private TransformerFactory tFactory = TransformerFactory.newInstance();</p>
@@ -366,7 +366,7 @@ private TransformerFactory tFactory = Tr
throw new ServletException(ex);
}
}There are numerous problems with the code snippet above. Its purpose is only to demonstrate the basic concepts. See below for details.</p>
-<h2 id="adding-xsl-tranformation-xslt-wzxhzdk17wzxhzdk18">Adding XSL tranformation (XSLT) # <a id="xslt"></a></h2>
+<h2 id="adding-xsl-tranformation-xslt-wzxhzdk17wzxhzdk18">Adding XSL tranformation (XSLT) <a id="xslt"></a></h2>
<p>A common requirement is to transform an XML source to XSL-FO using an XSL transformation. It is recommended to use JAXP for this task. The following snippet shows the basic code:
private FopFactory fopFactory = FopFactory.newInstance();
private TransformerFactory tFactory = TransformerFactory.newInstance();</p>
@@ -406,9 +406,9 @@ private TransformerFactory tFactory = Tr
<p>The <code>Source</code> instance used above is simply an example. If you have to read the XML from a string, supply a <code>new StreamSource(new
StringReader(xmlstring))</code> . 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.</p>
<p>Because you have an explicit <code>Transformer</code> object, you can also use it to explicitely set parameters for the transformation run.</p>
-<h3 id="custom-configuration-wzxhzdk19wzxhzdk20">Custom configuration # <a id="cfg"></a></h3>
+<h3 id="custom-configuration-wzxhzdk19wzxhzdk20">Custom configuration <a id="cfg"></a></h3>
<p>You can easily set up your own FOUserAgent as demonstrated on the <a href="embedding.html">Embedding page</a> .</p>
-<h3 id="improving-performance-wzxhzdk21wzxhzdk22">Improving performance # <a id="performance"></a></h3>
+<h3 id="improving-performance-wzxhzdk21wzxhzdk22">Improving performance <a id="performance"></a></h3>
<p>There are several options to consider:</p>
<ul>
<li>
@@ -419,7 +419,7 @@ private TransformerFactory tFactory = Tr
</li>
</ul>
<p>Of course, the <a href="embedding.html#performance">performance hints from the Embedding page</a> apply here, too.</p>
-<h3 id="accessing-resources-in-your-web-application-wzxhzdk23wzxhzdk24">Accessing resources in your web application # <a id="uriresolver"></a></h3>
+<h3 id="accessing-resources-in-your-web-application-wzxhzdk23wzxhzdk24">Accessing resources in your web application <a id="uriresolver"></a></h3>
<p>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 <code>org.apache.fop.servlet.ServletContextURIResolver</code> .</p>
<p>Here's how to set it up in your servlet. Instantiate a new instance in the servlet's init() method:</p>
<div class="codehilite"><pre><span class="sr">/** URIResolver for use by this servlet */</span>
@@ -459,7 +459,7 @@ Source xsltSrc = this.uriResolver.resolv
"servlet-context:/xslt/mystylesheet.xsl", null);
Transformer transformer = this.transFactory.newTransformer(xsltSrc);
transformer.setURIResolver(this.uriResolver);</p>
-<h1 id="notes-on-microsoft-internet-explorer-wzxhzdk25wzxhzdk26">Notes on Microsoft Internet Explorer <a id="ie"></a></h1>
+<h1 id="notes-on-microsoft-internet-explorer-wzxhzdk25wzxhzdk26">Notes on Microsoft Internet Explorer <a id="ie"></a></h1>
<p>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:</p>
<ul>
<li>
@@ -474,13 +474,13 @@ transformer.setURIResolver(this.uriResol
<p>Cache in the server. It may help to include a parameter in the URL which has a timestamp as the value min order to decide whether a request is repeated. IEx is reported to retrieve a document up to three times, but never more often.</p>
</li>
</ul>
-<h2 id="servlet-engines-wzxhzdk27wzxhzdk28">Servlet Engines <a id="servlet-engine"></a></h2>
+<h2 id="servlet-engines-wzxhzdk27wzxhzdk28">Servlet Engines <a id="servlet-engine"></a></h2>
<p>When using a servlet engine, there are potential CLASSPATH issues, and potential conflicts with existing XML/XSLT libraries. Servlet containers also often use their own classloaders for loading webapps, which can cause bugs and security problems.</p>
-<h3 id="tomcat-wzxhzdk29wzxhzdk30">Tomcat # <a id="tomcat"></a></h3>
+<h3 id="tomcat-wzxhzdk29wzxhzdk30">Tomcat <a id="tomcat"></a></h3>
<p>Check Tomcat's documentation for detailed instructions about installing FOP and Cocoon. There are known bugs that must be addressed, particularly for Tomcat 4.0.3.</p>
-<h3 id="websphere-35-wzxhzdk31wzxhzdk32">WebSphere 3.5 # <a id="websphere"></a></h3>
+<h3 id="websphere-35-wzxhzdk31wzxhzdk32">WebSphere 3.5 <a id="websphere"></a></h3>
<p>Put a copy of a working parser in some directory where WebSphere can access it. For example, if /usr/webapps/yourapp/servlets is the CLASSPATH for your servlets, copy the Xerces jar into it (any other directory would also be fine). Do not add the jar to the servlet CLASSPATH, but add it to the CLASSPATH of the application server which contains your web application. In the WebSphere administration console, click on the "environment" button in the "general" tab. In the "variable name" box, enter "CLASSPATH". In the "value" box, enter the correct path to the parser jar file (/usr/webapps/yourapp/servlets/Xerces.jar in our example here). Press "OK", then apply the change and restart the application server.</p>
-<h2 id="handling-complex-use-cases-wzxhzdk33wzxhzdk34">Handling complex use cases <a id="complex-usecases"></a></h2>
+<h2 id="handling-complex-use-cases-wzxhzdk33wzxhzdk34">Handling complex use cases <a id="complex-usecases"></a></h2>
<p>Sometimes the requirements for a servlet get quite sophisticated: SQL data sources, multiple XSL transformations, merging of several datasources etc. In such a case consider using <a href="http://cocoon.apache.org/">Apache Cocoon</a> instead of a custom servlet to accomplish your goal.</p></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/upgrading.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/upgrading.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/upgrading.html Wed Oct 24 04:26:06 2012
@@ -332,7 +332,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/1.1/">1.1</a></div> -->
<div class="section-content"><h1 id="upgrading-from-an-earlier-version-of-apachewzxhzdk0-fop">Upgrading from an Earlier Version of Apache™ FOP</h1>
<p><version>$Revision$</version></p>
-<h2 id="upgrading-from-version-10-wzxhzdk3wzxhzdk4">Upgrading from Version 1.0 <a id="fop-1.0"></a></h2>
+<h2 id="upgrading-from-version-10-wzxhzdk3wzxhzdk4">Upgrading from Version 1.0 <a id="fop-1.0"></a></h2>
<p>You should encounter very few issues in upgrading from FOP 1.0, except as noted in the following:</p>
<ul>
<li>
@@ -370,7 +370,7 @@ $(document).ready(function () {
<p>Because complex script features are now enabled by default, it is possible that different font specific data will be used for kerning than was previously used. This may be the case if a font supports a traditional TrueType <code>kern</code> table and also supports the advanced typographic <code>kern</code> feature with a <code>GPOS</code> table. In FOP 1.0, the former is used for kerning, while in FOP 1.1 with complex script features enabled, the latter is used. If it is desired to explicitly use the <code>kern</code> table (rather than the <code>GPOS</code> table) in such a case, then the <code>-nocs</code> command line option may be used when invoking FOP in order to disable complex script features.</p>
</li>
</ul>
-<h2 id="upgrading-from-pre-10-versions-wzxhzdk5wzxhzdk6">Upgrading from Pre-1.0 Versions <a id="pre-1.0"></a></h2>
+<h2 id="upgrading-from-pre-10-versions-wzxhzdk5wzxhzdk6">Upgrading from Pre-1.0 Versions <a id="pre-1.0"></a></h2>
<p>If you're planning to upgrade to the latest Apache™ FOP version from a pre-1.0 version, there are a few very important things to consider:</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/bugs.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/bugs.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/bugs.html Wed Oct 24 04:26:06 2012
@@ -333,7 +333,7 @@ $(document).ready(function () {
<div class="section-content"><h1 id="apachewzxhzdk0-fop-bugs-and-other-trackable-issues">Apache™ FOP: Bugs and Other Trackable Issues</h1>
<p><version>$Revision: 1298724 $</version></p>
<p>Information on this page applies to enhancement requests and other trackable issues as well as bugs.</p>
-<h2 id="reported-issues-wzxhzdk3wzxhzdk4">Reported Issues <a id="issues_existing"></a></h2>
+<h2 id="reported-issues-wzxhzdk3wzxhzdk4">Reported Issues <a id="issues_existing"></a></h2>
<p>A list of unresolved reported bugs can be found at <a href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Fop&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=">FOP Open Bugs (Bugzilla)</a> . If you have an interest in an issue already reported, please consider the following:</p>
<ul>
<li>
@@ -343,7 +343,7 @@ $(document).ready(function () {
<p>If you would like to track the status of the issue, consider adding your email address to the list of "CC" recipients, so that you will receive an email as changes are made to the issue.</p>
</li>
</ul>
-<h2 id="unreported-issues-reporting-new-issues-wzxhzdk5wzxhzdk6">Unreported Issues (Reporting New Issues) <a id="issues_new"></a></h2>
+<h2 id="unreported-issues-reporting-new-issues-wzxhzdk5wzxhzdk6">Unreported Issues (Reporting New Issues) <a id="issues_new"></a></h2>
<p>User reports of bugs and requests for enhancements are extremely important parts of FOP development, and we appreciate the time you take to help us track these issues down.</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/changes.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/changes.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/changes.html Wed Oct 24 04:26:06 2012
@@ -332,10 +332,10 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
<div class="section-content"><h1 id="history-of-changes">History of Changes</h1>
<p><a href="changes.rss"></a> </p>
-<h2 id="introduction-and-explanation-of-symbols-wzxhzdk0wzxhzdk1">Introduction and explanation of symbols <a id="introduction"></a></h2>
+<h2 id="introduction-and-explanation-of-symbols-wzxhzdk0wzxhzdk1">Introduction and explanation of symbols <a id="introduction"></a></h2>
<p>Changes are sorted by "type" and then chronologically with the most recent at the top. These symbols denote the various action types:<icon alt="add" src="images/add.jpg"></icon>=add,<icon alt="fix" src="images/fix.jpg"></icon>=fix,<icon alt="remove" src="images/remove.jpg"></icon>=remove,<icon alt="update" src="images/update.jpg"></icon>=update</p>
-<h2 id="version-fop-trunk-tbd-wzxhzdk10wzxhzdk11">Version FOP Trunk (TBD) <a id="version_FOP Trunk"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk12wzxhzdk13">Changes to the Code Base # <a id="Code_FOP Trunk"></a></h3>
+<h2 id="version-fop-trunk-tbd-wzxhzdk10wzxhzdk11">Version FOP Trunk (TBD) <a id="version_FOP Trunk"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk12wzxhzdk13">Changes to the Code Base <a id="Code_FOP Trunk"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>A global setting to wrap F11 images in page segments. Committed by PH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49893">49893</a> .</p>
@@ -497,11 +497,11 @@ $(document).ready(function () {
<p><icon alt="update" src="images/update.jpg"></icon>Add run target for embedded examples. Add increased JVM memory heap flag for example8 in case font cache is rebuilt. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51617">51617</a> .</p>
</li>
</ul>
-<h3 id="changes-to-the-user-configuration-wzxhzdk14wzxhzdk15">Changes to the User Configuration # <a id="Config_FOP Trunk"></a></h3>
+<h3 id="changes-to-the-user-configuration-wzxhzdk14wzxhzdk15">Changes to the User Configuration <a id="Config_FOP Trunk"></a></h3>
<ul>
<li><icon alt="fix" src="images/fix.jpg"></icon>Bugfix: relative URIs in the configuration file (base, font-base, hyphenation-base) are evaluated relative to the base URI of the configuration file. Committed by SP.</li>
</ul>
-<h3 id="changes-to-the-font-subsystem-wzxhzdk16wzxhzdk17">Changes to the Font Subsystem # <a id="Fonts_FOP Trunk"></a></h3>
+<h3 id="changes-to-the-font-subsystem-wzxhzdk16wzxhzdk17">Changes to the Font Subsystem <a id="Fonts_FOP Trunk"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Add support for OpenType advanced typographic tables (GDEF, GSUB, GPOS). Committed by GA.</p>
@@ -540,7 +540,7 @@ $(document).ready(function () {
<p><icon alt="fix" src="images/fix.jpg"></icon>Reinstated support for being able to specify a font cache filepath in the fop user configuration. Committed by AC.</p>
</li>
</ul>
-<h3 id="changes-to-the-layout-engine-wzxhzdk18wzxhzdk19">Changes to the Layout Engine # <a id="Layout_FOP Trunk"></a></h3>
+<h3 id="changes-to-the-layout-engine-wzxhzdk18wzxhzdk19">Changes to the Layout Engine <a id="Layout_FOP Trunk"></a></h3>
<ul>
<li>
<p><icon alt="fix" src="images/fix.jpg"></icon>Bugzilla 50965: Fixed a regression in BlockContainerLayoutManager where margins were no longer reset after forced breaks. Committed by AD. Thanks to Martin Koegler. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50965">50965</a> .</p>
@@ -576,7 +576,7 @@ $(document).ready(function () {
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed retrieval of available BPD for cases spanning columns and multiple pages with differing page masters. Committed by JM. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49885">49885</a> .</p>
</li>
</ul>
-<h3 id="changes-to-renderers-output-formats-wzxhzdk20wzxhzdk21">Changes to Renderers (Output Formats) # <a id="Renderers_FOP Trunk"></a></h3>
+<h3 id="changes-to-renderers-output-formats-wzxhzdk20wzxhzdk21">Changes to Renderers (Output Formats) <a id="Renderers_FOP Trunk"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Various bugfixes to make PDFDocumentGraphics2D operational again. Committed by JM.</p>
@@ -678,16 +678,16 @@ $(document).ready(function () {
<p><icon alt="remove" src="images/remove.jpg"></icon>Removed old Renderer implementations for those output formats that have a version based on the new DocumentHandler architecture available (AFP, PCL, PDF, PS). Committed by VH.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk22wzxhzdk23">Contributors to this release # <a id="contributors_FOP Trunk"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk22wzxhzdk23">Contributors to this release <a id="contributors_FOP Trunk"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Andreas Delmelle (AD), Chris Bowditch (CB), Glenn Adams (GA), Jeremias Märki (JM), Mehdi Houshmand (MH), Peter Hancock (PH), (PH,VH), Simon Pepping (SP), Vincent Hennebert (VH).</p>
<p>This is a list of other contributors:<br></br>Adrian Buza, Alberto Simões, Alexandros Papadakis, Alexios Giotis, Alexis Giotis, Andrejus Chaliapinas, Armin Haaf, Carsten Pfeiffer, Georg Datterl, Glenn Adams, JM, Mehdi Houshmand, Joshua Marquart, Julien Aymé, Luis Bernardo, Martin Koegler, Matthias Reischenbacher, Max Aster, Maximilian Aster, Mehdi Houshmand, Melanie Drake, mkoegler.AT.auto.tuwien.ac.at, Pascal Sancho, Patrick Jaromin, Paul Huemer, Peter Hancock, Sergey Vladimirov, Simon Pepping, VH and PH.</p>
-<h2 id="version-10-21-july-2010-wzxhzdk28wzxhzdk29">Version 1.0 (21 July 2010) <a id="version_1.0"></a></h2>
-<h3 id="changes-to-the-end-user-api-wzxhzdk30wzxhzdk31">Changes to the End-User API # <a id="API_1.0"></a></h3>
+<h2 id="version-10-21-july-2010-wzxhzdk28wzxhzdk29">Version 1.0 (21 July 2010) <a id="version_1.0"></a></h2>
+<h3 id="changes-to-the-end-user-api-wzxhzdk30wzxhzdk31">Changes to the End-User API <a id="API_1.0"></a></h3>
<ul>
<li><icon alt="add" src="images/add.jpg"></icon>Added a command-line option '-catalog' to use a catalog resolver for the XML and XSLT files Committed by SP.</li>
</ul>
-<h3 id="changes-to-the-code-base-wzxhzdk32wzxhzdk33">Changes to the Code Base # <a id="Code_1.0"></a></h3>
+<h3 id="changes-to-the-code-base-wzxhzdk32wzxhzdk33">Changes to the Code Base <a id="Code_1.0"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added support for xmlfile and xsltfile parameters in FOP's Ant Task. Committed by AC.</p>
@@ -756,11 +756,11 @@ Committed by AD. Thanks to rogov.AT.deve
<p><icon alt="update" src="images/update.jpg"></icon>Changed FONode.addCharacters() parameter to closer match the signature of the standard SAX characters() event (reduces confusion and computations). <em>!! Implementors of extensions that subclass FONode directly, and offer an implementation for addCharacters() should take care to make similar modifications in their code !!</em> Committed by AD.</p>
</li>
</ul>
-<h3 id="changes-to-the-bundled-extensions-wzxhzdk34wzxhzdk35">Changes to the Bundled Extensions # <a id="Extensions_1.0"></a></h3>
+<h3 id="changes-to-the-bundled-extensions-wzxhzdk34wzxhzdk35">Changes to the Bundled Extensions <a id="Extensions_1.0"></a></h3>
<ul>
<li><icon alt="add" src="images/add.jpg"></icon>Added support for the #CMYK pseudo-profile supported by some commercial XSL implementations on the rgb-icc() function. Committed by JM.</li>
</ul>
-<h3 id="changes-to-the-font-subsystem-wzxhzdk36wzxhzdk37">Changes to the Font Subsystem # <a id="Fonts_1.0"></a></h3>
+<h3 id="changes-to-the-font-subsystem-wzxhzdk36wzxhzdk37">Changes to the Font Subsystem <a id="Fonts_1.0"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added support for TrueType fonts with symbol character maps (like "Wingdings" and "Symbol"). Character for these fonts are usually found in the 0xF020 to 0xF0FF range (a Unicode private use area). Committed by JM.</p>
@@ -814,7 +814,7 @@ Committed by AD. Thanks to rogov.AT.deve
<p><icon alt="fix" src="images/fix.jpg"></icon>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 <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45734">45734</a> .</p>
</li>
</ul>
-<h3 id="changes-to-the-image-support-wzxhzdk38wzxhzdk39">Changes to the Image Support # <a id="Images_1.0"></a></h3>
+<h3 id="changes-to-the-image-support-wzxhzdk38wzxhzdk39">Changes to the Image Support <a id="Images_1.0"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added customization ability for the image loading framework from FOP's configuration file. Committed by JM.</p>
@@ -826,7 +826,7 @@ Committed by AD. Thanks to rogov.AT.deve
<p><icon alt="fix" src="images/fix.jpg"></icon>Bugfix: use the effective color profile supplied by the ImageEncodingHelper, instead of the original one. Committed by JM.</p>
</li>
</ul>
-<h3 id="changes-to-the-layout-engine-wzxhzdk40wzxhzdk41">Changes to the Layout Engine # <a id="Layout_1.0"></a></h3>
+<h3 id="changes-to-the-layout-engine-wzxhzdk40wzxhzdk41">Changes to the Layout Engine <a id="Layout_1.0"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Implement internal character classes if the hyphenation pattern file does not contain them Committed by SP.</p>
@@ -922,7 +922,7 @@ Committed by AD. Thanks to rogov.AT.deve
<p><icon alt="fix" src="images/fix.jpg"></icon>Activated min-height/max-height and min-width/max-width properties. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=43591">43591</a> .</p>
</li>
</ul>
-<h3 id="changes-to-renderers-output-formats-wzxhzdk42wzxhzdk43">Changes to Renderers (Output Formats) # <a id="Renderers_1.0"></a></h3>
+<h3 id="changes-to-renderers-output-formats-wzxhzdk42wzxhzdk43">Changes to Renderers (Output Formats) <a id="Renderers_1.0"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>AFP Output: Added enhanced dithering functionality for images that are converted to bi-level images. Committed by JM.</p>
@@ -1126,20 +1126,20 @@ Committed by AD.</p>
<p><icon alt="update" src="images/update.jpg"></icon>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.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk44wzxhzdk45">Contributors to this release # <a id="contributors_1.0"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk44wzxhzdk45">Contributors to this release <a id="contributors_1.0"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Andreas Delmelle (AD), Chris Bowditch (CB), Jeremias Märki (JM), (JM,VH), Luca Furini (LF), Max Berger (MB), Simon Pepping (SP), Vincent Hennebert (VH).</p>
<p>This is a list of other contributors:<br></br>Alexander Stamenov, Alok Singh, Antti Karanta, Bharat Attaluri, Carsten Siedentop, D.W. Harks, Dario Laera, Emil Maskovsky, Francois Fernandes, Georg Datterl, Harald G. Henne, J. Frantzius, Jason Harrop, Jonathan Levinson, Jost Klopfstein, Martin Edge, Maxim Wirt, Nicolas Peninguy, Pavel Kysilka, Peter Coppens, Peter Hancock, Richard Wheeldon, rogov.AT.devexperts.com, Thomas Stieler, Tow Browder, Venkat Reddy, Yegor Kozlov.</p>
-<h2 id="version-095-05-august-2008-wzxhzdk50wzxhzdk51">Version 0.95 (05 August 2008) <a id="version_0.95"></a></h2>
-<h3 id="changes-to-the-end-user-api-wzxhzdk52wzxhzdk53">Changes to the End-User API # <a id="API_0.95"></a></h3>
+<h2 id="version-095-05-august-2008-wzxhzdk50wzxhzdk51">Version 0.95 (05 August 2008) <a id="version_0.95"></a></h2>
+<h3 id="changes-to-the-end-user-api-wzxhzdk52wzxhzdk53">Changes to the End-User API <a id="API_0.95"></a></h3>
<ul>
<li><icon alt="fix" src="images/fix.jpg"></icon>Fixed the -imagein command-line option. Committed by JM.</li>
</ul>
-<h3 id="changes-to-the-code-base-wzxhzdk54wzxhzdk55">Changes to the Code Base # <a id="Code_0.95"></a></h3>
+<h3 id="changes-to-the-code-base-wzxhzdk54wzxhzdk55">Changes to the Code Base <a id="Code_0.95"></a></h3>
<ul>
<li><icon alt="fix" src="images/fix.jpg"></icon>Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44887">44887</a> .</li>
</ul>
-<h3 id="changes-to-the-font-subsystem-wzxhzdk56wzxhzdk57">Changes to the Font Subsystem # <a id="Fonts_0.95"></a></h3>
+<h3 id="changes-to-the-font-subsystem-wzxhzdk56wzxhzdk57">Changes to the Font Subsystem <a id="Fonts_0.95"></a></h3>
<ul>
<li>
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed text extraction problem with ZapfDingbats and Symbol font in PDF output. Committed by JM.</p>
@@ -1148,7 +1148,7 @@ Committed by AD.</p>
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed NullPointerException when loading a TrueType font using XML font metric files. Committed by JM.</p>
</li>
</ul>
-<h3 id="changes-to-the-image-support-wzxhzdk58wzxhzdk59">Changes to the Image Support # <a id="Images_0.95"></a></h3>
+<h3 id="changes-to-the-image-support-wzxhzdk58wzxhzdk59">Changes to the Image Support <a id="Images_0.95"></a></h3>
<ul>
<li>
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed two bugs concerning resolution handling with SVG images and their conversion to bitmaps for RTF output. Committed by JM.</p>
@@ -1157,7 +1157,7 @@ Committed by AD.</p>
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed a performance problem concerning image serialization. Committed by JM.</p>
</li>
</ul>
-<h3 id="changes-to-the-layout-engine-wzxhzdk60wzxhzdk61">Changes to the Layout Engine # <a id="Layout_0.95"></a></h3>
+<h3 id="changes-to-the-layout-engine-wzxhzdk60wzxhzdk61">Changes to the Layout Engine <a id="Layout_0.95"></a></h3>
<ul>
<li>
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed NullPointerException when page-number-citations are used inside a marker. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45295">45295</a> .</p>
@@ -1169,7 +1169,7 @@ Committed by AD.</p>
<p><icon alt="fix" src="images/fix.jpg"></icon>Various bugfixes for table layout. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44621">44621</a> .</p>
</li>
</ul>
-<h3 id="changes-to-renderers-output-formats-wzxhzdk62wzxhzdk63">Changes to Renderers (Output Formats) # <a id="Renderers_0.95"></a></h3>
+<h3 id="changes-to-renderers-output-formats-wzxhzdk62wzxhzdk63">Changes to Renderers (Output Formats) <a id="Renderers_0.95"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added support for fo:leader for RTF output (no full support!). Fixes problems with empty leaders being used to force empty lines among other issues. Committed by JM. Thanks to Maximilian Aster. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=43825">43825</a> .</p>
@@ -1202,16 +1202,16 @@ Committed by AD.</p>
<p><icon alt="fix" src="images/fix.jpg"></icon>Fixed regression causing bad positioning of block-containers if used as descendant of a table-cell. Committed by JM.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk64wzxhzdk65">Contributors to this release # <a id="contributors_0.95"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk64wzxhzdk65">Contributors to this release <a id="contributors_0.95"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Jeremias Märki (JM), Vincent Hennebert (VH).</p>
<p>This is a list of other contributors:<br></br>Maximilian Aster.</p>
-<h2 id="version-095beta-26-march-2008-wzxhzdk70wzxhzdk71">Version 0.95beta (26 March 2008) <a id="version_0.95beta"></a></h2>
-<h3 id="changes-to-the-end-user-api-wzxhzdk72wzxhzdk73">Changes to the End-User API # <a id="API_0.95beta"></a></h3>
+<h2 id="version-095beta-26-march-2008-wzxhzdk70wzxhzdk71">Version 0.95beta (26 March 2008) <a id="version_0.95beta"></a></h2>
+<h3 id="changes-to-the-end-user-api-wzxhzdk72wzxhzdk73">Changes to the End-User API <a id="API_0.95beta"></a></h3>
<ul>
<li><icon alt="remove" src="images/remove.jpg"></icon>Removed deprecated methods in the "apps" package that were left-overs from the API discussions. Committed by JM.</li>
</ul>
-<h3 id="changes-to-the-code-base-wzxhzdk74wzxhzdk75">Changes to the Code Base # <a id="Code_0.95beta"></a></h3>
+<h3 id="changes-to-the-code-base-wzxhzdk74wzxhzdk75">Changes to the Code Base <a id="Code_0.95beta"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Turned on XInclude processing for the main source given on the command line. Committed by MB.</p>
@@ -1241,7 +1241,7 @@ Committed by AD.</p>
<p><icon alt="fix" src="images/fix.jpg"></icon>Avoid a NullPointerException in AreaTreeHandler.endDocument(). Committed by JM. Thanks to David Delbecq. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=43910">43910</a> .</p>
</li>
</ul>
-<h3 id="changes-to-the-bundled-extensions-wzxhzdk76wzxhzdk77">Changes to the Bundled Extensions # <a id="Extensions_0.95beta"></a></h3>
+<h3 id="changes-to-the-bundled-extensions-wzxhzdk76wzxhzdk77">Changes to the Bundled Extensions <a id="Extensions_0.95beta"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>New extension attribute fox:transform on fo:block-container allows free-form transformation (rotation, scaling etc.) of absolute and fixed block-containers. Supported only for PDF, PS and Java2D-based renderers. Committed by JM.</p>
@@ -1250,7 +1250,7 @@ Committed by AD.</p>
<p><icon alt="add" src="images/add.jpg"></icon>Added new extension element: fox:external-document. It allows to add whole documents such as multi-page TIFF images to be inserted as peers to a page-sequence. Each image will make up an entire page. See the documentation for details. Committed by JM.</p>
</li>
</ul>
-<h3 id="changes-to-the-font-subsystem-wzxhzdk78wzxhzdk79">Changes to the Font Subsystem # <a id="Fonts_0.95beta"></a></h3>
+<h3 id="changes-to-the-font-subsystem-wzxhzdk78wzxhzdk79">Changes to the Font Subsystem <a id="Fonts_0.95beta"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added support for unusual font encodings (like for Symbol or Cyrillic fonts) of Type 1 fonts in PDF and PostScript output. Committed by JM.</p>
@@ -1283,11 +1283,11 @@ Committed by AD.</p>
<p><icon alt="update" src="images/update.jpg"></icon>Improved font auto-detection and handling of AWT-supplied fonts in order to achieve better results when using multiple output formats. Whenever possible, the font names appearing in the operating system can also be used in XSL-FO. Committed by JM.</p>
</li>
</ul>
-<h3 id="changes-to-the-image-support-wzxhzdk80wzxhzdk81">Changes to the Image Support # <a id="Images_0.95beta"></a></h3>
+<h3 id="changes-to-the-image-support-wzxhzdk80wzxhzdk81">Changes to the Image Support <a id="Images_0.95beta"></a></h3>
<ul>
<li><icon alt="fix" src="images/fix.jpg"></icon>A new image loading framework has been introduced to fix various problems with external graphics and improve performance. Committed by JM.</li>
</ul>
-<h3 id="changes-to-the-layout-engine-wzxhzdk82wzxhzdk83">Changes to the Layout Engine # <a id="Layout_0.95beta"></a></h3>
+<h3 id="changes-to-the-layout-engine-wzxhzdk82wzxhzdk83">Changes to the Layout Engine <a id="Layout_0.95beta"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added support for background on fo:table-column and fo:table-header/footer/body elements. Committed by VH.</p>
@@ -1404,7 +1404,7 @@ Committed by AD.</p>
<p><icon alt="update" src="images/update.jpg"></icon>PropertyCache phase 2:<br></br>⢠improvement of the PropertyCache itself should now guarantee acceptable performance of the static caches in multi-session environments, which is a possible problem with synchronizedMap.<br></br>⢠changed CommonFont to use the cache: added CachedCommonFont to contain the properties that are always cacheable CommonFont itself is only cached if the remaining properties are absolutes.<br></br>⢠changed CommonHyphenation, KeepProperty, ColorProperty and FontFamilyProperty to use the cache.<br></br>Committed by AD.</p>
</li>
</ul>
-<h3 id="changes-to-renderers-output-formats-wzxhzdk84wzxhzdk85">Changes to Renderers (Output Formats) # <a id="Renderers_0.95beta"></a></h3>
+<h3 id="changes-to-renderers-output-formats-wzxhzdk84wzxhzdk85">Changes to Renderers (Output Formats) <a id="Renderers_0.95beta"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added an option to disable the default sRGB profile in PDF output for those who don't care about color fidelity, but care about PDF file size. Committed by JM.</p>
@@ -1464,12 +1464,12 @@ Committed by AD.</p>
<p><icon alt="update" src="images/update.jpg"></icon>PDF Transcoder (SVG) text painting has been completely rewritten. Except for some special cases (with filters for example), all text (including flow text) is now painted using PDF text operators. Committed by JM.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk86wzxhzdk87">Contributors to this release # <a id="contributors_0.95beta"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk86wzxhzdk87">Contributors to this release <a id="contributors_0.95beta"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Andreas Delmelle (AD), Jeremias Märki (JM), Max Berger (MB), Vincent Hennebert (VH).</p>
<p>This is a list of other contributors:<br></br>Adrian Cumiskey, Andrejus Chaliapinas, Bruno Feurer, ckohrn.at.tng.de, David Churavy, David Delbecq, Gordon Cooke, Justus Piater, Max Berger, Patrick Jaromin, Stefan Ziel, V. Schappert.</p>
-<h2 id="version-094-24th-august-2007-wzxhzdk92wzxhzdk93">Version 0.94 (24th August 2007) <a id="version_0.94"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk94wzxhzdk95">Changes to the Code Base # <a id="Code_0.94"></a></h3>
+<h2 id="version-094-24th-august-2007-wzxhzdk92wzxhzdk93">Version 0.94 (24th August 2007) <a id="version_0.94"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk94wzxhzdk95">Changes to the Code Base <a id="Code_0.94"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Support for keep-together.within-line="always". Committed by MM.</p>
@@ -1592,12 +1592,12 @@ Committed by AD.</p>
<p><icon alt="update" src="images/update.jpg"></icon>Use source resolution setting for bitmap images which don't provide their own resolution. Committed by JM. Thanks to Hussein Shafie. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=42406">42406</a> .</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk96wzxhzdk97">Contributors to this release # <a id="contributors_0.94"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk96wzxhzdk97">Contributors to this release <a id="contributors_0.94"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Jay Bryant (JB), Jeremias Märki (JM), Luca Furini (LF), Manuel Mall (MM), Simon Pepping (SP), Vincent Hennebert (VH), (VH, JM).</p>
<p>This is a list of other contributors:<br></br>Adrian Cumiskey, Erwin Tratar, Hussein Shafie, Martin Kögler, Max Berger, Paul Vinkenoog, Richard Wheeldon.</p>
-<h2 id="version-093-9-january-2007-wzxhzdk102wzxhzdk103">Version 0.93 (9 January 2007) <a id="version_0.93"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk104wzxhzdk105">Changes to the Code Base # <a id="Code_0.93"></a></h3>
+<h2 id="version-093-9-january-2007-wzxhzdk102wzxhzdk103">Version 0.93 (9 January 2007) <a id="version_0.93"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk104wzxhzdk105">Changes to the Code Base <a id="Code_0.93"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added support for the use of Open Type fonts Committed by BD.</p>
@@ -1777,12 +1777,12 @@ Committed by AD.</p>
<p><icon alt="update" src="images/update.jpg"></icon>Content in block-containers makes better use of shrink to fit content vertically into the available area. This can be used indirectly to justify content vertically in a block-container. Committed by JM.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk106wzxhzdk107">Contributors to this release # <a id="contributors_0.93"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk106wzxhzdk107">Contributors to this release <a id="contributors_0.93"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Bertrand Delacrétaz (BD), Jeremias Märki (JM), Manuel Mall (MM), Simon Pepping (SP).</p>
<p>This is a list of other contributors:<br></br>Adam Strzelecki, Victor Mote, Dominic Brügger, Gary Reed, Gerhard Oettl, Gilles Beaugeais, Igor Istomin, Jeroen Meijer, Julien Aymé, Max Berger, Oliver Hernà ndez Valls, Peter Coppens, Pierre-Henri Kraus, Richard Wheeldon.</p>
-<h2 id="version-092beta-18-apr-2006-wzxhzdk112wzxhzdk113">Version 0.92beta (18 Apr 2006) <a id="version_0.92beta"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk114wzxhzdk115">Changes to the Code Base # <a id="Code_0.92beta"></a></h3>
+<h2 id="version-092beta-18-apr-2006-wzxhzdk112wzxhzdk113">Version 0.92beta (18 Apr 2006) <a id="version_0.92beta"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk114wzxhzdk115">Changes to the Code Base <a id="Code_0.92beta"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Initial support for page-position="last" added. Committed by JM.</p>
@@ -1938,12 +1938,12 @@ Committed by AD.</p>
<p><icon alt="update" src="images/update.jpg"></icon>Revision of refinement white-space handling. Committed by AD.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk116wzxhzdk117">Contributors to this release # <a id="contributors_0.92beta"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk116wzxhzdk117">Contributors to this release <a id="contributors_0.92beta"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Jeremias Märki (JM), Luca Furini (LF), Manuel Mall (MM), Simon Pepping (SP).</p>
<p>This is a list of other contributors:<br></br>Gerhard Oettl, Gerhard Oettl (gerhard.oettl.at.oesoft.at), Jirà Mareš, Max Berger, Richard Wheeldon.</p>
-<h2 id="version-091beta-23-dec-2005-wzxhzdk122wzxhzdk123">Version 0.91beta (23 Dec 2005) <a id="version_0.91beta"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk124wzxhzdk125">Changes to the Code Base # <a id="Code_0.91beta"></a></h3>
+<h2 id="version-091beta-23-dec-2005-wzxhzdk122wzxhzdk123">Version 0.91beta (23 Dec 2005) <a id="version_0.91beta"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk124wzxhzdk125">Changes to the Code Base <a id="Code_0.91beta"></a></h3>
<ul>
<li>
<p><icon alt="add" src="images/add.jpg"></icon>Added checks that warn about tables and block-containers that are wider than the available content area. Committed by JM.</p>
@@ -2054,27 +2054,27 @@ Committed by AD.</p>
<p><icon alt="update" src="images/update.jpg"></icon>Improvements on leader painting in PDF output. Committed by JM.</p>
</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk126wzxhzdk127">Contributors to this release # <a id="contributors_0.91beta"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk126wzxhzdk127">Contributors to this release <a id="contributors_0.91beta"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM), (LF, MM), Manuel Mall (MM).</p>
<p>This is a list of other contributors:<br></br>Tom Craddock.</p>
-<h2 id="version-090alpha1-22-nov-2005-wzxhzdk132wzxhzdk133">Version 0.90alpha1 (22 Nov 2005) <a id="version_0.90alpha1"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk134wzxhzdk135">Changes to the Code Base # <a id="Code_0.90alpha1"></a></h3>
+<h2 id="version-090alpha1-22-nov-2005-wzxhzdk132wzxhzdk133">Version 0.90alpha1 (22 Nov 2005) <a id="version_0.90alpha1"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk134wzxhzdk135">Changes to the Code Base <a id="Code_0.90alpha1"></a></h3>
<ul>
<li><icon alt="update" src="images/update.jpg"></icon> <strong>Complete redesign of the FOP codebase</strong> in the period between Dec 2001 and Nov 2005. There are just too many changes to list here. If you like to know details, run <code>"svn log --verbose http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/"</code> . Committed by all.</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk136wzxhzdk137">Contributors to this release # <a id="contributors_0.90alpha1"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk136wzxhzdk137">Contributors to this release <a id="contributors_0.90alpha1"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>the FOP committers (all).</p>
-<h2 id="version-0205-18-july-2003-wzxhzdk140wzxhzdk141">Version 0.20.5 (18 July 2003) <a id="version_0.20.5"></a></h2>
-<h3 id="changes-to-the-code-base-wzxhzdk142wzxhzdk143">Changes to the Code Base # <a id="Code_0.20.5"></a></h3>
+<h2 id="version-0205-18-july-2003-wzxhzdk140wzxhzdk141">Version 0.20.5 (18 July 2003) <a id="version_0.20.5"></a></h2>
+<h3 id="changes-to-the-code-base-wzxhzdk142wzxhzdk143">Changes to the Code Base <a id="Code_0.20.5"></a></h3>
<ul>
<li><icon alt="update" src="images/update.jpg"></icon>For the change log for the maintenance branch (where FOP 0.20.5 came from), please see the "CHANGES" file in the distribution, or <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/branches/fop-0_20_2-maintain/CHANGES?view=markup">the CHANGES file in the SVN repository</a> . Committed by all.</li>
</ul>
-<h3 id="contributors-to-this-release-wzxhzdk144wzxhzdk145">Contributors to this release # <a id="contributors_0.20.5"></a></h3>
+<h3 id="contributors-to-this-release-wzxhzdk144wzxhzdk145">Contributors to this release <a id="contributors_0.20.5"></a></h3>
<p>We thank the following people for their contributions to this release.</p>
<p>This is a list of all people who participated as committers:<br></br>the FOP committers (all).</p>
-<h2 id="all-committers-wzxhzdk148wzxhzdk149">All Committers <a id="all-committers"></a></h2>
+<h2 id="all-committers-wzxhzdk148wzxhzdk149">All Committers <a id="all-committers"></a></h2>
<p>This is a list of all people who have ever participated as committers on this project.</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html Wed Oct 24 04:26:06 2012
@@ -333,7 +333,7 @@ $(document).ready(function () {
<div class="section-content"><h1 id="apachewzxhzdk0-fop-development-coding-conventions">Apache™ FOP Development: Coding Conventions</h1>
<p><version>$Revision: 1298724 $</version></p>
<p>Acknowledgement: Some content in this guide was adapted from other Apache™ projects such as Avalon, Cactus, Turbine and Velocity.</p>
-<h2 id="subversion-repository-wzxhzdk4wzxhzdk5">Subversion Repository <a id="svn"></a></h2>
+<h2 id="subversion-repository-wzxhzdk4wzxhzdk5">Subversion Repository <a id="svn"></a></h2>
<p>Conventions in this section apply to Repository content, regardless of type:</p>
<ul>
<li>
@@ -346,8 +346,8 @@ $(document).ready(function () {
<p>In order to be able to discern commits from a committer from those where a committer applied a patch from a contributor, the commit message must contain a separate line following this pattern: <strong>"Submitted by: [contributor's name] <[contributor's obfuscated e-mail address]>"</strong> . This also helps doing audits on the repository.</p>
</li>
</ul>
-<h2 id="java-wzxhzdk6wzxhzdk7">Java <a id="java"></a></h2>
-<h3 id="java-style-wzxhzdk8wzxhzdk9">Java Style # <a id="java-style"></a></h3>
+<h2 id="java-wzxhzdk6wzxhzdk7">Java <a id="java"></a></h2>
+<h3 id="java-style-wzxhzdk8wzxhzdk9">Java Style <a id="java-style"></a></h3>
<p>In order to facilitate the human reading of FOP source code, reduce churning in code, and prevent disputes, the FOP developers have agreed on a set of coding conventions. The basis of these coding conventions is documented in the <a href="http://xml.apache.org/source.html">Apache XML Project Guidelines</a> , which requires that <strong>all Java Language source code in the repository must be written in conformance to Sun's</strong> <a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Code Conventions for the Java Programming Language</a> . In addition, the FOP developers have agreed to other conventions, which are summarized in the following table:</p>
<table>
<thead>
@@ -411,11 +411,11 @@ $(document).ready(function () {
</tbody>
</table>
<p>For developers that dislike these conventions, one workaround is to develop using their own style, then use a formatting tool like <a href="http://astyle.sourceforge.net/">astyle</a> (Artistic Style) before committing.</p>
-<h3 id="checkstyle-wzxhzdk10wzxhzdk11">Checkstyle # <a id="java-checkstyle"></a></h3>
+<h3 id="checkstyle-wzxhzdk10wzxhzdk11">Checkstyle <a id="java-checkstyle"></a></h3>
<p>The java syntax checker "<jump href="http://checkstyle.sourceforge.net">Checkstyle</jump>" is used to enforce many of the FOP coding standards. The standards enforced through Checkstyle are documented in its configuration file (xml-fop/checkstyle.cfg). The conventions defined in the configuration file are an integral part of FOP's coding conventions, and should not be changed without common consent. In other words, the configuration file contains additional conventions that are not documented on this page, but are generally accepted as good style within the java community (i.e. they are the default behavior of checkstyle, which the FOP developers have decided to adopt <em>de facto</em> ). Any apparent contradiction between the configuration file and this document should be raised on the fop-dev mailing list so that it can be clarified.</p>
<p>To use the "checkstyle" target in FOP's build process, download the source from the<jump href="http://checkstyle.sourceforge.net">Checkstyle web site</jump>, place checkstyle-all-*.jar in the lib directory and call "build checkstyle". Output (in the build directory) includes checkstyle_report.txt and checkstyle_report.xml. If you copy the file contrib/checkstyle-noframes.xsl from Checkstyle into FOP's root directory, you will also get an HTML report.</p>
<p>Checkstyle is probably most useful when integrated into your IDE. See the Checkstyle web site for more information about IDE plugins.</p>
-<h3 id="java-best-practices-wzxhzdk16wzxhzdk17">Java Best Practices # <a id="java-best-practices"></a></h3>
+<h3 id="java-best-practices-wzxhzdk16wzxhzdk17">Java Best Practices <a id="java-best-practices"></a></h3>
<p>The following general principles are a distillation of best practice expectations on the FOP project.</p>
<ul>
<li>
@@ -449,7 +449,7 @@ $(document).ready(function () {
<p>Try to avoid catching Throwable or Exception and catch specific exceptions instead.</p>
</li>
</ul>
-<h3 id="resources-wzxhzdk18wzxhzdk19">Resources # <a id="java-resources"></a></h3>
+<h3 id="resources-wzxhzdk18wzxhzdk19">Resources <a id="java-resources"></a></h3>
<ul>
<li>
<p>[book on code style] Code Complete by Steve McConnell.</p>
@@ -458,7 +458,7 @@ $(document).ready(function () {
<p>[code formatting software]<jump href="http://jrefactory.sourceforge.net">JRefactory</jump>.</p>
</li>
</ul>
-<h3 id="related-links-wzxhzdk20wzxhzdk21">Related Links # <a id="java-links"></a></h3>
+<h3 id="related-links-wzxhzdk20wzxhzdk21">Related Links <a id="java-links"></a></h3>
<ul>
<li>
<p><jump href="http://xmlgraphics.apache.org/repo.html">Apache XML Graphics Code Repositories</jump></p>
@@ -467,7 +467,7 @@ $(document).ready(function () {
<p><jump href="http://jakarta.apache.org/site/faqs.html#Coding%20Conventions%20and%20Standards">Jakarta Code Conventions and Standards</jump>(see Coding Conventions and Standards section)</p>
</li>
</ul>
-<h2 id="xml-wzxhzdk22wzxhzdk23">XML <a id="xml"></a></h2>
+<h2 id="xml-wzxhzdk22wzxhzdk23">XML <a id="xml"></a></h2>
<table>
<thead>
<tr>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/areas.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/areas.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/areas.html Wed Oct 24 04:26:06 2012
@@ -332,66 +332,66 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a> » <a href="/fop/dev/design/">Design</a></div> -->
<div class="section-content"><h1 id="apachewzxhzdk0-fop-design-area-tree">Apache™ FOP Design: Area Tree</h1>
<p><version>$Revision: 1298724 $</version><authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person></authors></p>
-<h2 id="introduction-wzxhzdk7wzxhzdk8">Introduction <a id="intro"></a></h2>
+<h2 id="introduction-wzxhzdk7wzxhzdk8">Introduction <a id="intro"></a></h2>
<p>The Area Tree is an internal representation of the result document, representing pages and their contents. To make the concepts clearer and easier to understand, the code to implement the area tree matches the areas defined in the XSL-FO specification.</p>
<p>The area tree is created by the layout managers once the layout is decided for a page. Once a completed page is finished it can then be added to the area tree. From that point forward, the area tree model can then handle the new page. The data in the area tree must be minimal and independant. This means that the data uses less memory and can be serialized to an output stream if needed.</p>
<p>The Area Tree consists of a set of pages, which the actual implemenation places in a set of page sequences.</p>
-<h2 id="structure-wzxhzdk9wzxhzdk10">Structure <a id="structure"></a></h2>
+<h2 id="structure-wzxhzdk9wzxhzdk10">Structure <a id="structure"></a></h2>
<p>The area tree is a root element that has a list of page-viewport-areas. Each page viewport has a page-reference-area which holds the contents of the page. To handle the processing better FOP does not maintain a list at the root level but lets the area tree model handle each page as it is added.</p>
-<h2 id="page-wzxhzdk11wzxhzdk12">Page <a id="page"></a></h2>
+<h2 id="page-wzxhzdk11wzxhzdk12">Page <a id="page"></a></h2>
<p>A page consists of a page+viewport pair.</p>
<p>The PageViewPort and Page with the regions is created by the LayoutMasterSet. The contents are then placed by the layout managers. Once the layout of a page is complete then it is added to the Area Tree.</p>
<p>Inside the page is a set of RegionViewport+Region pairs for each region on the page.</p>
<p>A page is made up of five area regions. These are before, start, body, end and after. Each region has a viewport and contains the areas produced from the children in the FO object heirarchy.</p>
<p>For the body area there are more subdivisions for before floats, footnotes and the main reference area. The main reference area is made from span areas which have normal flow reference areas as children. The flow areas are then created inside these normal flow reference areas.</p>
<p>Since the layout is done inside a page, the page is created from the pagemaster with all the appropriate areas. The layout manager then uses the page to add areas into the normal flow reference areas and floats and footnotes. After adding the areas for the body region then the other regions can be done layed out and added.</p>
-<h2 id="block-areas-wzxhzdk13wzxhzdk14">Block Areas <a id="block"></a></h2>
+<h2 id="block-areas-wzxhzdk13wzxhzdk14">Block Areas <a id="block"></a></h2>
<p>Block level areas contain either other blocks or line areas (which is a special block area).</p>
<p>A block is either positoned or stacked with other block areas.</p>
<p>Block areas are created and/or returned by all top level elements in the flow. The spacing between block areas is handled by an empty block area. A block area is stacked with other block areas in a particular direction, it has a size and it contains line areas made from a group of inline areas and/or block areas.</p>
-<h2 id="line-areas-wzxhzdk15wzxhzdk16">Line Areas <a id="line-area"></a></h2>
+<h2 id="line-areas-wzxhzdk15wzxhzdk16">Line Areas <a id="line-area"></a></h2>
<p>A line areas is simply a collection of inline areas that are stacked in the inline progression direction. A line area has a height and a start position. The line area is rendered by handling each inline area.</p>
<p>A line area gets a set of inline areas added until complete then it is justified and vertically alignedi when adding the areas. If the line area contains unresolved areas then there will be a line resolver that retains the justification information until all areas in the line are resolved.</p>
-<h2 id="inline-areas-wzxhzdk17wzxhzdk18">Inline Areas <a id="inline"></a></h2>
+<h2 id="inline-areas-wzxhzdk17wzxhzdk18">Inline Areas <a id="inline"></a></h2>
<p>There are a few different types of inline areas. All inline areas have a height and width.</p>
<p>Unresolved areas can reserve some space to allow for possible sizes once it is resolved. Then the line can be re-justified and finalised.</p>
<p>Inline areas are stacked in a line area. Inline areas are objects such as character, viewport, inline-container, leader and space. A special inline area Word is also used for a group of consecutive characters.</p>
<p>The image and instream foreign object areas are placed inside a viewport. The leader (with use content) and unresolved page number areas are resolved to other inline areas.</p>
<p>Once a LineArea is filled with inline areas then the inline areas need to be aligned and adjusted to fill the line properly.</p>
-<h2 id="repeated-areas-wzxhzdk19wzxhzdk20">Repeated Areas <a id="repeated-area"></a></h2>
+<h2 id="repeated-areas-wzxhzdk19wzxhzdk20">Repeated Areas <a id="repeated-area"></a></h2>
<p>There are cases where the same subtree could be repeated in the area tree. These areas will be returned by the same layout managers. So it is possible to put a flag on the created areas so that the subtree data can be cached in the output. Examples of this are: static areas, table header/footer, svg.</p>
-<h2 id="traits-wzxhzdk21wzxhzdk22">Traits <a id="traits"></a></h2>
+<h2 id="traits-wzxhzdk21wzxhzdk22">Traits <a id="traits"></a></h2>
<p>A trait is information associated with an area. This could be information such as text colour or is-first.</p>
<p>Traits provide information about an area. The traits are derived from properties on the formatting object or are generated during the layout process. Many of the layout traits do not have actual values but can be derived from the Area Tree. Other traits that apply when rendering the areas are set on the area. Since setting the same value on every area would use a lot of memory then the traits are derived from default or parent values.</p>
<p>A dominant trait on a block area is set, for example font colour, so that every line area with the same dominant value can derive it. The text inline areas then get the font colour set on the inline area or from the line area or from the block area.</p>
-<h2 id="classes-wzxhzdk23wzxhzdk24">Classes <a id="classes"></a></h2>
+<h2 id="classes-wzxhzdk23wzxhzdk24">Classes <a id="classes"></a></h2>
<p>The following class structure will be used to represent the area tree.</p>
-<h3 id="page-area-classes-wzxhzdk25wzxhzdk26">Page Area Classes # <a id="classes-page"></a></h3>
+<h3 id="page-area-classes-wzxhzdk25wzxhzdk26">Page Area Classes <a id="classes-page"></a></h3>
<p>The page area classes hold the top level layout of a page. The areas are created by the page master and should be ready to have flow areas added.</p>
-<h3 id="block-area-classes-wzxhzdk27wzxhzdk28">Block Area Classes # <a id="classes-block"></a></h3>
+<h3 id="block-area-classes-wzxhzdk27wzxhzdk28">Block Area Classes <a id="classes-block"></a></h3>
<p>The block areas hold other block areas and/or line areas. The child areas are stacked in a particular direction.</p>
<p>Areas for tables, lists and block container have their child block areas stacked in different ways. These areas a placed with an absolute positioning. The absolute positioning is where the blocks are placed with an offset from the parent reference area.</p>
-<h3 id="inline-area-classes-wzxhzdk29wzxhzdk30">Inline Area Classes # <a id="classes-inline"></a></h3>
+<h3 id="inline-area-classes-wzxhzdk29wzxhzdk30">Inline Area Classes <a id="classes-inline"></a></h3>
<p>The inline areas are used to make up a line area. An inline area typically has a height, width and some content. The inline area is offset from the baseline of the current line area. The content of the inline area can be other inline areas or a simple atomic object.</p>
-<h2 id="forward-references-wzxhzdk31wzxhzdk32">Forward References <a id="forward-references"></a></h2>
+<h2 id="forward-references-wzxhzdk31wzxhzdk32">Forward References <a id="forward-references"></a></h2>
<p>The Area Tree maintains a set of mappings from the reference to pages.</p>
<p>The PageViewPort holds the list of forward references that need resolving so that if a references is resolved during layout the page can be easily found and then fixed. Once all the forward references are resolved then the page is ready to be rendered.</p>
<p>To layout a page any areas that cannot be resolved need to reserve space. Once the inline area is resolved then the complete line should be adjusted to accomodate any change in space used by the area.</p>
-<h2 id="caching-wzxhzdk33wzxhzdk34">Caching <a id="caching"></a></h2>
+<h2 id="caching-wzxhzdk33wzxhzdk34">Caching <a id="caching"></a></h2>
<p>We may need to cache pages due to forward references or when keeping all pages.</p>
<p>This is done by serializing the Page. The PageViewport is retained to be used as a key for page references and backward references. The Page is serialized to an object stream and then all of the page contents are released. The Page is then recoved by reading from the object stream.</p>
<p>The PageViewport retains information about id areas for easy access.</p>
-<h2 id="extensions-wzxhzdk35wzxhzdk36">Extensions <a id="extensions"></a></h2>
+<h2 id="extensions-wzxhzdk35wzxhzdk36">Extensions <a id="extensions"></a></h2>
<p>The Area Tree holds the Output Document extensions. This is information such as pdf bookmarks or other output document specific information that is not handled by XSL:FO.</p>
<p>It is also possible to create custom areas that extend a normal area. The actual data that is rendered could be set in a different way or depend on resolving a forward reference.</p>
-<h2 id="area-tree-handlers-wzxhzdk37wzxhzdk38">Area Tree Handlers <a id="handlers"></a></h2>
+<h2 id="area-tree-handlers-wzxhzdk37wzxhzdk38">Area Tree Handlers <a id="handlers"></a></h2>
<p>To handle different situations the handler for the Area Tree handles each page as it is added.</p>
<p>The RenderPagesModel sends the page directly to the renderer if the page is ready to be rendered. Once a page is rendered it is discarded. The StorePagesModel stores all the pages so that any page can be later accessed.</p>
<p>The Area Tree retains the concept of page sequences (this is not in the area tree in the spec) so that this information can be passed to the renderer. This is useful for setting the title and organising the groups of page sequences.</p>
-<h2 id="status-wzxhzdk39wzxhzdk40">Status <a id="status"></a></h2>
-<h3 id="to-do-wzxhzdk41wzxhzdk42">To Do # <a id="status-todo"></a></h3>
-<h3 id="work-in-progress-wzxhzdk43wzxhzdk44">Work in Progress # <a id="status-wip"></a></h3>
-<h3 id="completed-wzxhzdk45wzxhzdk46">Completed # <a id="status-complete"></a></h3>
+<h2 id="status-wzxhzdk39wzxhzdk40">Status <a id="status"></a></h2>
+<h3 id="to-do-wzxhzdk41wzxhzdk42">To Do <a id="status-todo"></a></h3>
+<h3 id="work-in-progress-wzxhzdk43wzxhzdk44">Work in Progress <a id="status-wip"></a></h3>
+<h3 id="completed-wzxhzdk45wzxhzdk46">Completed <a id="status-complete"></a></h3>
<ul>
<li>
<p>new area tree model</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org