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 [16/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/trunk/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfencryption.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> » <a href="/fop/trunk/">Trunk</a></div> -->
<div class="section-content"><h1 id="apachewzxhzdk0-fop-pdf-encryption">Apache™ FOP: PDF encryption.</h1>
<p><version>$Revision: 1298724 $</version><authors><person email="pietsch@apache.org" name="J.Pietschmann"></person><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
-<h2 id="overview-wzxhzdk9wzxhzdk10">Overview <a id="Overview"></a></h2>
+<h2 id="overview-wzxhzdk9wzxhzdk10">Overview <a id="Overview"></a></h2>
<p>Apache™ FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited.</p>
<p>For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.</p>
-<h2 id="usage-command-line-wzxhzdk12wzxhzdk13">Usage (command line) <a id="Usage+%28command+line%29"></a></h2>
+<h2 id="usage-command-line-wzxhzdk12wzxhzdk13">Usage (command line) <a id="Usage+%28command+line%29"></a></h2>
<p>Encryption is enabled by supplying any of the encryption related options.</p>
<p>An owner password is set with the <code>-o</code> option. This password is actually used as encryption key. Many tools for PDF processing ask for this password to disregard any restriction imposed on the PDF document.</p>
<p>If no owner password has been supplied but FOP was asked to apply some restrictions, a random password is used. In this case it is obviously impossiible to disregard restrictions in PDF processing tools.</p>
@@ -351,7 +351,7 @@ $(document).ready(function () {
| <code>-noaccesscontent</code> | disable text and graphics extraction for accessibility purposes |
| <code>-noassembledoc</code> | disable assembling documents |
| <code>-noprinthq</code> | disable high quality printing |</p>
-<h2 id="usage-embedded-wzxhzdk14wzxhzdk15">Usage (embedded) <a id="Usage+%28embedded%29"></a></h2>
+<h2 id="usage-embedded-wzxhzdk14wzxhzdk15">Usage (embedded) <a id="Usage+%28embedded%29"></a></h2>
<p>When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:</p>
<table>
<thead>
@@ -515,13 +515,13 @@ Fop fop = fopFactory.newFop(MimeConstant
<p>noprinthq: Boolean or "true"/"false"</p>
</li>
</ol>
-<h2 id="environment-wzxhzdk16wzxhzdk17">Environment <a id="Environment"></a></h2>
+<h2 id="environment-wzxhzdk16wzxhzdk17">Environment <a id="Environment"></a></h2>
<p>In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html">JCE</a> is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.</p>
<p>Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does <strong>not</strong> provide RC4. If you get a message saying
"Cannot find any provider supporting RC4"
then you don't have the needed infrastructure.</p>
<p>There are several commercial and a few Open Source packages which provide RC4. A pure Java implementation is produced by <a href="http://www.bouncycastle.org/">The Legion of the Bouncy Castle</a> . <a href="http://www.mozilla.org/projects/security/pki/jss/">Mozilla JSS</a> is an interface to a native implementation.</p>
-<h2 id="installing-a-crypto-provider-wzxhzdk18wzxhzdk19">Installing a crypto provider <a id="install_crypto"></a></h2>
+<h2 id="installing-a-crypto-provider-wzxhzdk18wzxhzdk19">Installing a crypto provider <a id="install_crypto"></a></h2>
<p>The pure Java implementation from <a href="http://www.bouncycastle.org/">Bouncy Castle</a> is easy to install.</p>
<ol>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfx.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfx.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfx.html Wed Oct 24 04:26:06 2012
@@ -332,22 +332,22 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/trunk/">Trunk</a></div> -->
<div class="section-content"><h1 id="apachewzxhzdk0-fop-pdfx-iso-15930">Apache™ FOP: PDF/X (ISO 15930)</h1>
<p><version>$Revision: 1298724 $</version><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
-<h2 id="overview-wzxhzdk7wzxhzdk8">Overview <a id="overview"></a></h2>
+<h2 id="overview-wzxhzdk7wzxhzdk8">Overview <a id="overview"></a></h2>
<p><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 <a href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&ICS1=37&ICS2=100&ICS3=99">ISO 15930-6:2003(E)</a> . More info on PDF/X can be found on the <a href="http://www.pdfx.info/">PDF/X info site</a> .</p>
-<h2 id="implementation-status-wzxhzdk11wzxhzdk12">Implementation Status <a id="status"></a></h2>
+<h2 id="implementation-status-wzxhzdk11wzxhzdk12">Implementation Status <a id="status"></a></h2>
<p><strong>PDF/X-3:2003</strong> is implemented to the degree that FOP supports the creation of the elements described in ISO 15930-6.</p>
<p>An important restriction of the current implementation is that all normal RGB colors specified in XSL-FO and SVG are left unchanged in the sRGB color space (XSL-FO and SVG both use sRGB as their default color space). There's no conversion to a CMYK color space. Although sRGB is a calibrated color space, its color space has a different size than a CMYK color space which makes the conversion a lossy conversion and can lead to unwanted results. Although the use of the calibrated sRGB has been promoted for years, print shops usually prefer to convert an sRGB PDF to CMYK prior to production. Until there's full CMYK support in FOP you will have to work closely with your print service provider to make sure you get the intended result.</p>
<p>Tests have been performed against Adobe Acrobat 7.0.7 (Preflight function). Note that there are bugs in Adobe Acrobat which cause false alarms if both PDF/A-1b and PDF/X-3:2003 are activated at the same time.</p>
-<h2 id="usage-command-line-wzxhzdk13wzxhzdk14">Usage (command line) <a id="command-line"></a></h2>
+<h2 id="usage-command-line-wzxhzdk13wzxhzdk14">Usage (command line) <a id="command-line"></a></h2>
<p>To activate PDF/X-3:2003 from the command-line, specify "-pdfprofile PDF/X-3:2003" as a parameter. If there is a violation of one of the validation rules for PDF/X, an error message is presented and the processing stops.</p>
-<h2 id="usage-embedded-wzxhzdk15wzxhzdk16">Usage (embedded) <a id="embedded"></a></h2>
+<h2 id="usage-embedded-wzxhzdk15wzxhzdk16">Usage (embedded) <a id="embedded"></a></h2>
<p>When FOP is embedded in another Java application you can set a special option on the renderer options in the user agent to activate the PDF/A-1b profile. Here's an example:</p>
<p class=".">FOUserAgent userAgent = fopFactory.newFOUserAgent();
userAgent.getRendererOptions().put("pdf-x-mode", "PDF/X-3:2003");
Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent);
</p>
-<h2 id="pdfx-in-action-wzxhzdk17wzxhzdk18">PDF/X in Action <a id="rules"></a></h2>
+<h2 id="pdfx-in-action-wzxhzdk17wzxhzdk18">PDF/X in Action <a id="rules"></a></h2>
<p>There are a number of things that must be looked after if you activate a PDF/X profile. If you receive a PDFConformanceException, have a look at the following list (not necessarily comprehensive):</p>
<ul>
<li>
@@ -369,7 +369,7 @@ Fop fop = fopFactory.newFop(MimeConstant
<p>PDF is forced to version 1.4 if PDF/X-3:2003 is activated.</p>
</li>
</ul>
-<h2 id="pdf-profile-compatibility-wzxhzdk19wzxhzdk20">PDF profile compatibility <a id="profile-compatibility"></a></h2>
+<h2 id="pdf-profile-compatibility-wzxhzdk19wzxhzdk20">PDF profile compatibility <a id="profile-compatibility"></a></h2>
<p>The PDF profiles "PDF/X-3:2003" and "PDF/A-1b" are compatible and can both be activated at the same time.</p></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/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/trunk/">Trunk</a></div> -->
<div class="section-content"><h1 id="running-apachewzxhzdk0-fop">Running Apache™ FOP</h1>
<p><version>$Revision: 1308679 $</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/trunk/servlets.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/servlets.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/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/trunk/">Trunk</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/trunk/upgrading.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/upgrading.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/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/trunk/">Trunk</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: 1298724 $</version></p>
-<h2 id="important-wzxhzdk3wzxhzdk4">Important! <a id="important"></a></h2>
+<h2 id="important-wzxhzdk3wzxhzdk4">Important! <a id="important"></a></h2>
<p>If you're planning to upgrade to the latest Apache™ FOP version there are a few very important things to consider:</p>
<ul>
<li>
@@ -358,7 +358,7 @@ While FOP 0.20.5 allowed you to have emp
<p>The SVG Renderer and the MIF Handler have not been resurrected, yet! They are currently non-functional and hope for someone to step up and reimplement them.</p>
</li>
</ul>
-<h2 id="what-you-need-to-know-when-you-upgrade-wzxhzdk6wzxhzdk7">What you need to know when you upgrade! <a id="issues"></a></h2>
+<h2 id="what-you-need-to-know-when-you-upgrade-wzxhzdk6wzxhzdk7">What you need to know when you upgrade! <a id="issues"></a></h2>
<p>When you use your existing FO files or XML/XSL files which work fine with FOP version 0.20.5 against this FOP version some things may not work as expected. The following list will hopefully help you to identify and correct those problems.</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/legal.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/legal.html (original)
+++ websites/staging/xmlgraphics/trunk/content/legal.html Wed Oct 24 04:26:06 2012
@@ -130,7 +130,7 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a></div> -->
<div class="section-content"><h1 id="the-apachewzxhzdk0-xml-graphics-project-legal-stuff">The Apache™ XML Graphics Project - Legal Stuff</h1>
<p><notice></notice><abstract></abstract></p>
-<h2 id="legal-stuff-wzxhzdk5wzxhzdk6">Legal Stuff <a id="Legal"></a></h2>
+<h2 id="legal-stuff-wzxhzdk5wzxhzdk6">Legal Stuff <a id="Legal"></a></h2>
<ul>
<li><a href="/">Home</a></li>
<li><a href="/team.html">Who We Are</a></li>
@@ -141,7 +141,7 @@ $(document).ready(function () {
</ul>
<p>All software and material on this website is licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License V2.0</a> .</p>
<p>For more details, please see the <a href="http://www.apache.org/licenses/">licenses page of The Apache Software Foundation</a> .</p>
-<h2 id="trademarks-wzxhzdk7wzxhzdk8">Trademarks <a id="Trademarks"></a></h2>
+<h2 id="trademarks-wzxhzdk7wzxhzdk8">Trademarks <a id="Trademarks"></a></h2>
<p>Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are trademarks of The Apache Software Foundation.</p>
<p>IBM is a trademark of International Business Systems, Inc. Lotus is a trademark of Lotus Development Corporation. Sun and Sun Microsystems are trademarks or registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. Windows, WindowsNT, and Win32 are registered trademarks of Microsoft Corp. Mac OS X and Macintosh are registered trademarks of Apple Computer, Inc.</p>
<p>All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p></div>
Modified: websites/staging/xmlgraphics/trunk/content/mail.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/mail.html (original)
+++ websites/staging/xmlgraphics/trunk/content/mail.html Wed Oct 24 04:26:06 2012
@@ -132,7 +132,7 @@ $(document).ready(function () {
<h2 id="mailing-lists">Mailing Lists</h2>
<p>Every volunteer project obtains its strength from the people involved in it. Mailing lists provide a simple and effective communication mechanism.</p>
<p>You are welcome to join any of these mailing lists (or all of them if you wish). You can choose to lurk, or actively participate. It's up to you. Before you join these lists, you should look over the resources in the Reference Library section. As with any mailing list, you should probably read any FAQ postings or simply read a sampling of postings on the list before posting your first question.</p>
-<h2 id="usage-notes-wzxhzdk1wzxhzdk2">Usage Notes <a id="usage"></a></h2>
+<h2 id="usage-notes-wzxhzdk1wzxhzdk2">Usage Notes <a id="usage"></a></h2>
<p>Archives are generally named after the project they're about (duh!) with a suffix that denotes the subjects covered. Common suffixes are:</p>
<ul>
<li>
@@ -158,7 +158,7 @@ $(document).ready(function () {
If you want to unsubscribe from the XML Graphics General mailing list you send an empty mail to <code>general-unsubscribe@xmlgraphics.apache.org</code> .</p>
</li>
</ul>
-<h1 id="public-archives-wzxhzdk3wzxhzdk4">Public Archives <a id="public_archives"></a></h1>
+<h1 id="public-archives-wzxhzdk3wzxhzdk4">Public Archives <a id="public_archives"></a></h1>
<p>Archives of all public mailing lists can be found here:</p>
<ul>
<li>
@@ -171,7 +171,7 @@ If you want to unsubscribe from the XML
<p>Some lists are also available from <a href="http://marc.theaimsgroup.com/">http://marc.theaimsgroup.com/</a> , <a href="http://www.mail-archive.com/">The Mail Archive</a> , <a href="http://www.gmane.com/">GMANE</a> , <a href="http://www.nabble.com/Xml-Graphics-f307.html">Nabble</a> and <a href="http://xmlgraphics.markmail.org/">MarkMail</a> .</p>
</li>
</ul>
-<h2 id="xml-graphics-general-mailing-list-wzxhzdk5wzxhzdk6">XML Graphics General Mailing List <a id="xmlgraphics-general"></a></h2>
+<h2 id="xml-graphics-general-mailing-list-wzxhzdk5wzxhzdk6">XML Graphics General Mailing List <a id="xmlgraphics-general"></a></h2>
<p><em>Low Traffic</em> <a href="mailto:general-subscribe@xmlgraphics.apache.org">Subscribe</a> <a href="mailto:general-unsubscribe@xmlgraphics.apache.org">Unsubscribe</a> </p>
<p>This list is for issues that span across all xmlgraphics.apache.org projects, whether technical or organizational. Discussions about specific code bases should be redirected to one of the codebase-specific lists below, except for XML Graphics Commons which is discussed here.</p>
<p><strong>Archives:</strong> </p>
@@ -183,7 +183,7 @@ If you want to unsubscribe from the XML
<p><a href="http://xmlgraphics.apache.org/mail/general/">http://xmlgraphics.apache.org/mail/general/</a> (gzipped mbox files)</p>
</li>
</ul>
-<h2 id="xml-graphics-commits-mailing-list-wzxhzdk7wzxhzdk8">XML Graphics Commits Mailing List <a id="xmlgraphics-commits"></a></h2>
+<h2 id="xml-graphics-commits-mailing-list-wzxhzdk7wzxhzdk8">XML Graphics Commits Mailing List <a id="xmlgraphics-commits"></a></h2>
<p><em>Low Traffic</em> <a href="mailto:commits-subscribe@xmlgraphics.apache.org">Subscribe</a> <a href="mailto:commits-unsubscribe@xmlgraphics.apache.org">Unsubscribe</a> </p>
<p>This is a read-only list that sends out email with details of all commits to the Apache XML Graphics Commons subproject, the Apache XML Graphics project website repository and to its Wiki.</p>
<p><strong>Archives:</strong> </p>
@@ -195,7 +195,7 @@ If you want to unsubscribe from the XML
<p><a href="http://xmlgraphics.apache.org/mail/commits/">http://xmlgraphics.apache.org/mail/commits/</a> (gzipped mbox files)</p>
</li>
</ul>
-<h2 id="batik-users-mailing-list-wzxhzdk9wzxhzdk10">Batik Users Mailing List <a id="batik-users"></a></h2>
+<h2 id="batik-users-mailing-list-wzxhzdk9wzxhzdk10">Batik Users Mailing List <a id="batik-users"></a></h2>
<p><em>Medium Traffic</em> <a href="mailto:batik-users-subscribe@xmlgraphics.apache.org">Subscribe</a> <a href="mailto:batik-users-unsubscribe@xmlgraphics.apache.org">Unsubscribe</a> </p>
<p>This is the list for active users of the Batik project, where issues regarding installation and use of Batik are discussed. Also code changes and new releases are announced on this list.</p>
<p><strong>Archives:</strong> </p>
@@ -207,7 +207,7 @@ If you want to unsubscribe from the XML
<p><a href="http://xmlgraphics.apache.org/mail/batik-users/">http://xmlgraphics.apache.org/mail/batik-users/</a> (gzipped mbox files)</p>
</li>
</ul>
-<h2 id="batik-developers-mailing-list-wzxhzdk11wzxhzdk12">Batik Developers Mailing List <a id="batik-dev"></a></h2>
+<h2 id="batik-developers-mailing-list-wzxhzdk11wzxhzdk12">Batik Developers Mailing List <a id="batik-dev"></a></h2>
<p><em>Medium Traffic</em> <a href="mailto:batik-dev-subscribe@xmlgraphics.apache.org">Subscribe</a> <a href="mailto:batik-dev-unsubscribe@xmlgraphics.apache.org">Unsubscribe</a> </p>
<p>This is the list for everyone interested and involved with the active development of Batik.</p>
<p><strong>Archives:</strong> </p>
@@ -219,7 +219,7 @@ If you want to unsubscribe from the XML
<p><a href="http://xmlgraphics.apache.org/mail/batik-dev/">http://xmlgraphics.apache.org/mail/batik-dev/</a> (gzipped mbox files)</p>
</li>
</ul>
-<h2 id="batik-commits-mailing-list-wzxhzdk13wzxhzdk14">Batik Commits Mailing List <a id="batik-commits"></a></h2>
+<h2 id="batik-commits-mailing-list-wzxhzdk13wzxhzdk14">Batik Commits Mailing List <a id="batik-commits"></a></h2>
<p><em>Medium Traffic</em> <a href="mailto:batik-commits-subscribe@xmlgraphics.apache.org">Subscribe</a> <a href="mailto:batik-commits-unsubscribe@xmlgraphics.apache.org">Unsubscribe</a> </p>
<p>This is a read-only list that sends out email with details of all commits to the Apache Batik subproject code repository and to its Wiki.</p>
<p><strong>Archives:</strong> </p>
@@ -231,7 +231,7 @@ If you want to unsubscribe from the XML
<p><a href="http://xmlgraphics.apache.org/mail/batik-commits/">http://xmlgraphics.apache.org/mail/batik-commits/</a> (gzipped mbox files)</p>
</li>
</ul>
-<h2 id="fop-users-mailing-list-wzxhzdk15wzxhzdk16">FOP Users Mailing List <a id="fop-users"></a></h2>
+<h2 id="fop-users-mailing-list-wzxhzdk15wzxhzdk16">FOP Users Mailing List <a id="fop-users"></a></h2>
<p><em>Medium Traffic</em> <a href="mailto:fop-users-subscribe@xmlgraphics.apache.org">Subscribe</a> <a href="mailto:fop-users-unsubscribe@xmlgraphics.apache.org">Unsubscribe</a> </p>
<p>This is the list for active users of the FOP project, where issues regarding installation and use of FOP are discussed. Also code changes and new releases are announced on this list.</p>
<p><strong>Archives:</strong> </p>
@@ -244,7 +244,7 @@ If you want to unsubscribe from the XML
It is usually a good idea to state the FOP & JDK/JRE version and the operating system you are using. Also, if you are attaching large binary files (PDF, JPG, etc.), please consider attaching a minimal, appropriate B&W GIF, JPG or PNG that conveys the necessary information instead. A good alternative is to put the files on a web server.</p>
</li>
</ul>
-<h1 id="fop-developers-mailing-list-wzxhzdk17wzxhzdk18">FOP Developers Mailing List <a id="fop-dev"></a></h1>
+<h1 id="fop-developers-mailing-list-wzxhzdk17wzxhzdk18">FOP Developers Mailing List <a id="fop-dev"></a></h1>
<p><em>Medium Traffic</em> <a href="mailto:fop-dev-subscribe@xmlgraphics.apache.org">Subscribe</a> <a href="mailto:fop-dev-unsubscribe@xmlgraphics.apache.org">Unsubscribe</a> </p>
<p>This is the list for everyone interested and involved with the active development of FOP.</p>
<p><strong>Archives:</strong> </p>
@@ -256,7 +256,7 @@ It is usually a good idea to state the F
<p><a href="http://xmlgraphics.apache.org/mail/fop-dev/">http://xmlgraphics.apache.org/mail/fop-dev/</a> (gzipped mbox files)</p>
</li>
</ul>
-<h2 id="fop-commits-mailing-list-wzxhzdk19wzxhzdk20">FOP Commits Mailing List <a id="fop-commits"></a></h2>
+<h2 id="fop-commits-mailing-list-wzxhzdk19wzxhzdk20">FOP Commits Mailing List <a id="fop-commits"></a></h2>
<p><em>Medium Traffic</em> <a href="mailto:fop-commits-subscribe@xmlgraphics.apache.org">Subscribe</a> <a href="mailto:fop-commits-unsubscribe@xmlgraphics.apache.org">Unsubscribe</a> </p>
<p>This is a read-only list that sends out email with details of all commits to the Apache FOP subproject code repository and to its Wiki.</p>
<p><strong>Archives:</strong> </p>
Modified: websites/staging/xmlgraphics/trunk/content/repo.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/repo.html (original)
+++ websites/staging/xmlgraphics/trunk/content/repo.html Wed Oct 24 04:26:06 2012
@@ -129,7 +129,7 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a></div> -->
<div class="section-content"><h1 id="the-apachewzxhzdk0-xml-graphics-project-code-repositories">The Apache™ XML Graphics Project - Code Repositories</h1>
-<h2 id="web-access-to-the-repositories-wzxhzdk1wzxhzdk2">Web Access to the Repositories <a id="web-access"></a></h2>
+<h2 id="web-access-to-the-repositories-wzxhzdk1wzxhzdk2">Web Access to the Repositories <a id="web-access"></a></h2>
<p>The Apache™ XML Graphics project uses Subversion (SVN) as version control tool.</p>
<p>You can browse the repositories belonging to the XML Graphics project via the web:</p>
<ul>
@@ -146,9 +146,9 @@ $(document).ready(function () {
<p>Apache™ XML Graphics Site: <a href="http://svn.apache.org/viewvc/xmlgraphics/site/">http://svn.apache.org/viewvc/xmlgraphics/site/</a> (SVN repository)</p>
</li>
</ul>
-<h2 id="access-the-source-tree-wzxhzdk4wzxhzdk5">Access the Source Tree <a id="Access+the+Source+Tree"></a></h2>
+<h2 id="access-the-source-tree-wzxhzdk4wzxhzdk5">Access the Source Tree <a id="Access+the+Source+Tree"></a></h2>
<p>So, you've decided that you need access to the source tree to see the latest and greatest code. There're two different forms of SVN access. The first is <code>anonymous</code> and anybody can use it. The second requires that you have a login to the development server. If you don't know what this means, join the mailing list and find out.</p>
-<h3 id="anonymous-read-only-svn-access-wzxhzdk6wzxhzdk7">Anonymous (read-only) SVN access # <a id="Anonymous+%28read-only%29+SVN+access"></a></h3>
+<h3 id="anonymous-read-only-svn-access-wzxhzdk6wzxhzdk7">Anonymous (read-only) SVN access <a id="Anonymous+%28read-only%29+SVN+access"></a></h3>
<p>Anyone can checkout source code from our anonymous SVN server. To do so, simply use the following commands (if you are using a GUI SVN client, configure it appropriately):</p>
<p>For <strong>Apache Batik</strong> :
svn co http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk
Modified: websites/staging/xmlgraphics/trunk/content/team.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/team.html (original)
+++ websites/staging/xmlgraphics/trunk/content/team.html Wed Oct 24 04:26:06 2012
@@ -129,9 +129,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a></div> -->
<div class="section-content"><h1 id="the-apachewzxhzdk0-xml-graphics-project-community">The Apache™ XML Graphics Project - Community</h1>
-<h2 id="who-we-are-wzxhzdk1wzxhzdk2">Who We Are <a id="WhoWeAre"></a></h2>
+<h2 id="who-we-are-wzxhzdk1wzxhzdk2">Who We Are <a id="WhoWeAre"></a></h2>
<p>The <em>Apache™ XML Graphics Project</em> operates on a meritocracy: the more you do, the more responsibility you can obtain. This page lists all of the people who have gone the extra mile and are Committers or members of the Project Management Committee. If you would like to get involved, the first step is to join the <a href="mail.html">community mailing lists</a> for the project(s) which interest you.</p>
-<h2 id="apachewzxhzdk6-xml-graphics-project-project-management-committee-wzxhzdk4wzxhzdk5">Apache™ XML Graphics Project - Project Management Committee <a id="PMC"></a></h2>
+<h2 id="apachewzxhzdk6-xml-graphics-project-project-management-committee-wzxhzdk4wzxhzdk5">Apache™ XML Graphics Project - Project Management Committee <a id="PMC"></a></h2>
<ul>
<li>
<p><a href="mailto:bowditch_chris@hotmail.com">Chris Bowditch</a> </p>
@@ -161,7 +161,7 @@ $(document).ready(function () {
<p><a href="mailto:pietsch@apache.org">Jörg Pietschmann</a> </p>
</li>
</ul>
-<h3 id="emeritus-project-management-committee-members-wzxhzdk7wzxhzdk8">Emeritus Project Management Committee Members # <a id="PMC-emeritus"></a></h3>
+<h3 id="emeritus-project-management-committee-members-wzxhzdk7wzxhzdk8">Emeritus Project Management Committee Members <a id="PMC-emeritus"></a></h3>
<ul>
<li>
<p><a href="mailto:chrisg@apache.org">Christian Geisert</a> </p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org