You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by vh...@apache.org on 2014/07/24 18:21:24 UTC
svn commit: r1613173 [15/15] - in /xmlgraphics/site/trunk/content: ./ batik/
batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/
fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Modified: xmlgraphics/site/trunk/content/fop/trunk/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/running.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/running.mdtext Thu Jul 24 16:21:20 2014
@@ -3,7 +3,7 @@ Title: Running Apache™ FOP
#Running Apache™ FOP
-## System Requirements {#require}
+## System Requirements { #require}
The following software must be installed:
@@ -36,19 +36,19 @@ In addition, the following system requir
- If you will be using FOP to process SVG, you must do so in a graphical environment. See [FOP: Graphics (Batik)](graphics.html#batik) for details.
-## Installation {#install}
+## Installation { #install}
-### Instructions {#install-instruct}
+### Instructions { #install-instruct}
Basic FOP installation consists of first unzipping the `.gz` file that is the distribution medium, then unarchiving the resulting `.tar` 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.
-### Problems {#install-problems}
+### Problems { #install-problems}
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 `tar -xzf` instead.
-## Starting FOP as a Standalone Application {#standalone-start}
+## Starting FOP as a Standalone Application { #standalone-start}
-### Using the fop script or batch file {#fop-script}
+### Using the fop script or batch file { #fop-script}
The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is `/Library/Java/Home`. **Caveat:** We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see [Java on Mac OSX FAQ](http://developer.apple.com/java/faq) for information as it becomes available.
@@ -147,12 +147,12 @@ The usual and recommended practice for s
PDF encryption is only available if FOP was compiled with encryption support **and** if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the [Details](pdfencryption.html).
-### Writing your own script {#your-own-script}
+### Writing your own script { #your-own-script}
FOP's entry point for your own scripts is the class `org.apache.fop.cli.Main`. The general pattern for the command line is: `java -classpath <CLASSPATH>
org.apache.fop.cli.Main <arguments>`. The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that you get your environment properly configured.
-### Running with java's -jar option {#jar-option}
+### Running with java's -jar option { #jar-option}
As an alternative to the start scripts you can run `java
-jar path/to/build/fop.jar <arguments>`, relying on FOP to build the classpath for running FOP dynamically, see [below](#dynamical-classpath). If you use hyphenation, you must put `fop-hyph.jar` in the `lib` directory.
@@ -162,7 +162,7 @@ You can also run `java -jar path/to/fop.
In both cases the arguments consist of the options and infile and outfile specifications as shown above for the standard scripts.
-### FOP's dynamical classpath construction {#dynamical-classpath}
+### FOP's dynamical classpath construction { #dynamical-classpath}
If FOP is started without a proper classpath, it tries to add its dependencies dynamically. If the system property `fop.home` contains the name of a directory, then FOP uses that directory as the base directory for its search. Otherwise the current working directory is the base directory. If the base directory is called `build`, then its parent directory becomes the base directory.
@@ -170,7 +170,7 @@ FOP expects to find `fop.jar` in the `bu
If the system property `fop.optional.lib` contains the name of a directory, then all `jar` files in that directory are also added to the classpath. See the methods `getJARList` and `checkDependencies` in `org.apache.fop.cli.Main`.
-## Using Xalan to Check XSL-FO Input {#check-input}
+## Using Xalan to Check XSL-FO Input { #check-input}
FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Tranforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. Only the second is part of FOP's core processing. If a user has a problem running FOP, it is important to determine which of these two processes is causing the problem. If the problem is in the first process, the user's stylesheet is likely the cause. The FOP development team does not have resources to help with stylesheet issues, although we have included links to some useful [Specifications](../resources.html#specs) and [Books/Articles](../resources.html#articles). If the problem is in the second process, FOP may have a bug or an unimplemented feature that does require attention from the FOP development team.
@@ -186,7 +186,7 @@ The -foout option works the same way as
Note that there are some subtle differences between the FOP and Xalan command-lines.
-## Memory Usage {#memory}
+## Memory Usage { #memory}
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.
@@ -201,6 +201,6 @@ If you are running out of memory when us
- 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.
-## Problems {#problems}
+## Problems { #problems}
If you have problems running FOP, please see the ["How to get Help" page](../gethelp.html).
Modified: xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext Thu Jul 24 16:21:20 2014
@@ -3,11 +3,11 @@ Title: Apache(tm) FOP: Servlets
#Apache™ FOP: Servlets
<subtitle>How to use Apache™ FOP in a Servlet</subtitle>
-## Overview {#overview}
+## Overview { #overview}
This page discusses topic all around using Apache™ FOP in a servlet environment.
-## Example Servlets in the FOP distribution {#example-servlets}
+## Example Servlets in the FOP distribution { #example-servlets}
In the directory {fop-dir}/src/java/org/apache/fop/servlet, you'll find a working example of a FOP-enabled servlet.
@@ -24,11 +24,11 @@ The source code for the servlet can be f
<note>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.</note>
-## Create your own Servlet {#servlet}
+## Create your own Servlet { #servlet}
<note>This section assumes you are familiar with [embedding FOP](embedding.html).</note>
-### A minimal Servlet {#minimal-servlet}
+### A minimal Servlet { #minimal-servlet}
Here is a minimal code snippet to demonstrate the basics:
@@ -52,7 +52,7 @@ Here is a minimal code snippet to demons
<note>There are numerous problems with the code snippet above. Its purpose is only to demonstrate the basic concepts. See below for details.</note>
-### Adding XSL tranformation (XSLT) {#xslt}
+### Adding XSL tranformation (XSLT) { #xslt}
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:
@@ -100,11 +100,11 @@ The `Source` instance used above is simp
Because you have an explicit `Transformer` object, you can also use it to explicitely set parameters for the transformation run.
-### Custom configuration {#cfg}
+### Custom configuration { #cfg}
You can easily set up your own FOUserAgent as demonstrated on the [Embedding page](embedding.html).
-### Improving performance {#performance}
+### Improving performance { #performance}
There are several options to consider:
@@ -115,7 +115,7 @@ There are several options to consider:
Of course, the [performance hints from the Embedding page](embedding.html#performance) apply here, too.
-### Accessing resources in your web application {#uriresolver}
+### Accessing resources in your web application { #uriresolver}
Often, you will want to use resources (stylesheets, images etc.) which are bundled with your web application. FOP provides a URIResolver implementation that lets you access files via the Servlet's ServletContext. The class is called `org.apache.fop.servlet.ServletContextURIResolver`.
@@ -162,7 +162,7 @@ Here are some example snippets:
Transformer transformer = this.transFactory.newTransformer(xsltSrc);
transformer.setURIResolver(this.uriResolver);
-## Notes on Microsoft Internet Explorer {#ie}
+## Notes on Microsoft Internet Explorer { #ie}
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:
@@ -178,18 +178,18 @@ Some versions of Internet Explorer will
- 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.
-## Servlet Engines {#servlet-engine}
+## Servlet Engines { #servlet-engine}
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.
-### Tomcat {#tomcat}
+### Tomcat { #tomcat}
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.
-### WebSphere 3.5 {#websphere}
+### WebSphere 3.5 { #websphere}
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.
-## Handling complex use cases {#complex-usecases}
+## Handling complex use cases { #complex-usecases}
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 [Apache Cocoon](http://cocoon.apache.org/) instead of a custom servlet to accomplish your goal.
Modified: xmlgraphics/site/trunk/content/fop/trunk/upgrading.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/upgrading.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/upgrading.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/upgrading.mdtext Thu Jul 24 16:21:20 2014
@@ -2,7 +2,7 @@ Title: Upgrading from an Earlier Version
#Upgrading from an Earlier Version of Apache™ FOP
-## Upgrading from Version 1.0 {#fop-1.0}
+## Upgrading from Version 1.0 { #fop-1.0}
You should encounter very few issues in upgrading from FOP 1.0, except as noted in the following:
@@ -26,7 +26,7 @@ You should encounter very few issues in
- 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 `kern` table and also supports the advanced typographic `kern` feature with a `GPOS` 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 `kern` table (rather than the `GPOS` table) in such a case, then the `-nocs` command line option may be used when invoking FOP in order to disable complex script features.
-## Upgrading from Pre-1.0 Versions {#pre-1.0}
+## Upgrading from Pre-1.0 Versions { #pre-1.0}
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:
Modified: xmlgraphics/site/trunk/content/fop/trunk/whitespacemanagement.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/whitespacemanagement.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/whitespacemanagement.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/whitespacemanagement.mdtext Thu Jul 24 16:21:20 2014
@@ -18,11 +18,11 @@ Notice: Licensed to the Apache Softwa
#Apache™ FOP: Whitespace Management
-## Overview {#overview}
+## Overview { #overview}
This page describes an extension for FOPâs page breaking algorithm that enables the handling of dynamic content. Dynamic content has multiple variants, only one of which will be inserted in the document. Variant selection is done in a First Come First Served manner and the first variant that fits within the remaining space in the current page is chosen. If no appropriate variant is found, the dynamic content will be skipped without affecting the rest of the document layout.
-## Example {#example}
+## Example { #example}
Here is an example of dynamic content with two variants:
@@ -36,7 +36,7 @@ Here is an example of dynamic content wi
</fo:multi-case>
</fo:multi-switch>
-## Limitations {#limitations}
+## Limitations { #limitations}
* Space attributes (space-before, space-after) are not currently supported. This is primarily due to how space resolution is done in FOP, which requires the whole FO content to be known before doing page breaking.
Modified: xmlgraphics/site/trunk/content/legal.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/legal.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/legal.mdtext (original)
+++ xmlgraphics/site/trunk/content/legal.mdtext Thu Jul 24 16:21:20 2014
@@ -4,7 +4,7 @@ Title: The Apache™ XML Graphics Pr
<notice></notice><abstract></abstract>
-## Legal Stuff {#Legal}
+## Legal Stuff { #Legal}
* [Home](/)
* [Who We Are](/team.html)
@@ -17,7 +17,7 @@ All software and material on this websit
For more details, please see the [licenses page of The Apache Software Foundation](http://www.apache.org/licenses/).
-## Trademarks {#Trademarks}
+## Trademarks { #Trademarks}
Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are trademarks of The Apache Software Foundation.
Modified: xmlgraphics/site/trunk/content/mail.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/mail.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/mail.mdtext (original)
+++ xmlgraphics/site/trunk/content/mail.mdtext Thu Jul 24 16:21:20 2014
@@ -8,7 +8,7 @@ Every volunteer project obtains its stre
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.
-## Usage Notes {#usage}
+## Usage Notes { #usage}
Archives are generally named after the project they're about (duh!) with a suffix that denotes the subjects covered. Common suffixes are:
@@ -28,7 +28,7 @@ The ezmlm mailing list controller accept
- `*-help` get Help on mailing list commands
If you want to unsubscribe from the XML Graphics General mailing list you send an empty mail to `general-unsubscribe@xmlgraphics.apache.org`.
-# Public Archives {#public_archives}
+# Public Archives { #public_archives}
Archives of all public mailing lists can be found here:
@@ -39,7 +39,7 @@ Archives of all public mailing lists can
- Some lists are also available from [http://marc.theaimsgroup.com/](http://marc.theaimsgroup.com/), [The Mail Archive](http://www.mail-archive.com/), [GMANE](http://www.gmane.com/), [Nabble](http://www.nabble.com/Xml-Graphics-f307.html) and [MarkMail](http://xmlgraphics.markmail.org/).
-## XML Graphics General Mailing List {#xmlgraphics-general}
+## XML Graphics General Mailing List { #xmlgraphics-general}
*Low Traffic* [Subscribe](mailto:general-subscribe@xmlgraphics.apache.org) [Unsubscribe](mailto:general-unsubscribe@xmlgraphics.apache.org)
@@ -52,7 +52,7 @@ This list is for issues that span across
- [http://xmlgraphics.apache.org/mail/general/](http://xmlgraphics.apache.org/mail/general/) (gzipped mbox files)
-## XML Graphics Commits Mailing List {#xmlgraphics-commits}
+## XML Graphics Commits Mailing List { #xmlgraphics-commits}
*Low Traffic* [Subscribe](mailto:commits-subscribe@xmlgraphics.apache.org) [Unsubscribe](mailto:commits-unsubscribe@xmlgraphics.apache.org)
@@ -65,7 +65,7 @@ This is a read-only list that sends out
- [http://xmlgraphics.apache.org/mail/commits/](http://xmlgraphics.apache.org/mail/commits/) (gzipped mbox files)
-## Batik Users Mailing List {#batik-users}
+## Batik Users Mailing List { #batik-users}
*Medium Traffic* [Subscribe](mailto:batik-users-subscribe@xmlgraphics.apache.org) [Unsubscribe](mailto:batik-users-unsubscribe@xmlgraphics.apache.org)
@@ -78,7 +78,7 @@ This is the list for active users of the
- [http://xmlgraphics.apache.org/mail/batik-users/](http://xmlgraphics.apache.org/mail/batik-users/) (gzipped mbox files)
-## Batik Developers Mailing List {#batik-dev}
+## Batik Developers Mailing List { #batik-dev}
*Medium Traffic* [Subscribe](mailto:batik-dev-subscribe@xmlgraphics.apache.org) [Unsubscribe](mailto:batik-dev-unsubscribe@xmlgraphics.apache.org)
@@ -91,7 +91,7 @@ This is the list for everyone interested
- [http://xmlgraphics.apache.org/mail/batik-dev/](http://xmlgraphics.apache.org/mail/batik-dev/) (gzipped mbox files)
-## Batik Commits Mailing List {#batik-commits}
+## Batik Commits Mailing List { #batik-commits}
*Medium Traffic* [Subscribe](mailto:batik-commits-subscribe@xmlgraphics.apache.org) [Unsubscribe](mailto:batik-commits-unsubscribe@xmlgraphics.apache.org)
@@ -104,7 +104,7 @@ This is a read-only list that sends out
- [http://xmlgraphics.apache.org/mail/batik-commits/](http://xmlgraphics.apache.org/mail/batik-commits/) (gzipped mbox files)
-## FOP Users Mailing List {#fop-users}
+## FOP Users Mailing List { #fop-users}
*Medium Traffic* [Subscribe](mailto:fop-users-subscribe@xmlgraphics.apache.org) [Unsubscribe](mailto:fop-users-unsubscribe@xmlgraphics.apache.org)
@@ -117,7 +117,7 @@ This is the list for active users of the
- [http://xmlgraphics.apache.org/mail/fop-users/](http://xmlgraphics.apache.org/mail/fop-users/) (gzipped mbox files)
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.
-# FOP Developers Mailing List {#fop-dev}
+# FOP Developers Mailing List { #fop-dev}
*Medium Traffic* [Subscribe](mailto:fop-dev-subscribe@xmlgraphics.apache.org) [Unsubscribe](mailto:fop-dev-unsubscribe@xmlgraphics.apache.org)
@@ -130,7 +130,7 @@ This is the list for everyone interested
- [http://xmlgraphics.apache.org/mail/fop-dev/](http://xmlgraphics.apache.org/mail/fop-dev/) (gzipped mbox files)
-## FOP Commits Mailing List {#fop-commits}
+## FOP Commits Mailing List { #fop-commits}
*Medium Traffic* [Subscribe](mailto:fop-commits-subscribe@xmlgraphics.apache.org) [Unsubscribe](mailto:fop-commits-unsubscribe@xmlgraphics.apache.org)
Modified: xmlgraphics/site/trunk/content/repo.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/repo.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/repo.mdtext (original)
+++ xmlgraphics/site/trunk/content/repo.mdtext Thu Jul 24 16:21:20 2014
@@ -2,7 +2,7 @@ Title: The Apache™ XML Graphics Pr
#The Apache™ XML Graphics Project - Code Repositories
-## Web Access to the Repositories {#web-access}
+## Web Access to the Repositories { #web-access}
The Apache™ XML Graphics project uses Subversion (SVN) as version control tool.
@@ -17,11 +17,11 @@ You can browse the repositories belongin
- Apache™ XML Graphics Site: [http://svn.apache.org/viewvc/xmlgraphics/site/](http://svn.apache.org/viewvc/xmlgraphics/site/) (SVN repository)
-## Access the Source Tree {#Access-the-Source-Tree}
+## Access the Source Tree { #Access-the-Source-Tree}
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 `anonymous` 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.
-### Anonymous (read-only) SVN access {#Anonymous-SVN-access}
+### Anonymous (read-only) SVN access { #Anonymous-SVN-access}
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):
Modified: xmlgraphics/site/trunk/content/team.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/team.mdtext?rev=1613173&r1=1613172&r2=1613173&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/team.mdtext (original)
+++ xmlgraphics/site/trunk/content/team.mdtext Thu Jul 24 16:21:20 2014
@@ -2,11 +2,11 @@ Title: The Apache™ XML Graphics Pr
#The Apache™ XML Graphics Project - Community
-## Who We Are {#WhoWeAre}
+## Who We Are { #WhoWeAre}
The *Apache™ XML Graphics Project* 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 [community mailing lists](mail.html) for the project(s) which interest you.
-## Apache™ XML Graphics Project - Project Management Committee {#PMC}
+## Apache™ XML Graphics Project - Project Management Committee { #PMC}
- [Adrian Cumiskey](mailto:acumiskey@apache.org)
@@ -33,7 +33,7 @@ The *Apache™ XML Graphics Project*
- [Vincent Hennebert](mailto:vhennebert@apache.org)
-### Emeritus Project Management Committee Members {#PMC-emeritus}
+### Emeritus Project Management Committee Members { #PMC-emeritus}
- [Christian Geisert](mailto:chrisg@apache.org)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org