xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840938 [17/17] - 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/
Date Thu, 06 Dec 2012 14:12:38 GMT
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 Thu Dec  6 14:12:18
2012
@@ -342,7 +342,7 @@ $(document).ready(function () {
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/trunk/">Trunk</a></div>
-->
       	<div class="section-content"><h1 id="running-apachewzxhzdk1-fop">Running
Apache&trade; FOP</h1>
-<h2 id="system-requirements-wzxhzdk2wzxhzdk3">System Requirements <a id="require"></a></h2>
+<h2 id="require">System Requirements</h2>
 <p>The following software must be installed:</p>
 <ul>
 <li>
@@ -385,13 +385,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-wzxhzdk4wzxhzdk5">Installation <a id="install"></a></h2>
-<h3 id="instructions-wzxhzdk6wzxhzdk7">Instructions <a id="install-instruct"></a></h3>
+<h2 id="install">Installation</h2>
+<h3 id="install-instruct">Instructions</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-wzxhzdk8wzxhzdk9">Problems <a id="install-problems"></a></h3>
+<h3 id="install-problems">Problems</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-wzxhzdk10wzxhzdk11">Starting FOP as
a Standalone Application <a id="standalone-start"></a></h2>
-<h3 id="using-the-fop-script-or-batch-file-wzxhzdk12wzxhzdk13">Using the fop script
or batch file <a id="fop-script"></a></h3>
+<h2 id="standalone-start">Starting FOP as a Standalone Application</h2>
+<h3 id="fop-script">Using the fop script or batch file</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>
 <div class="codehilite"><pre><span class="n">USAGE</span>
 <span class="n">Fop</span> <span class="p">[</span><span class="n">options</span><span
class="p">]</span> <span class="p">[</span><span class="o">-</span><span
class="n">fo</span><span class="o">|-</span><span class="n">xml</span><span
class="p">]</span> <span class="n">infile</span> <span class="p">[</span><span
class="o">-</span><span class="n">xsl</span> <span class="n">file</span><span
class="p">]</span> <span class="p">[</span><span class="o">-</span><span
class="n">awt</span><span class="o">|-</span><span class="n">pdf</span><span
class="o">|-</span><span class="n">mif</span><span class="o">|-</span><span
class="n">rtf</span><span class="o">|-</span><span class="n">tiff</span><span
class="o">|-</span><span class="n">png</span><span class="o">|-</span><span
class="n">pcl</span><span class="o">|-</span><span class="n">ps</span><span
class="o">|-</span><span class="n">txt</span><span class="o">|-</span><span
class="n">at</span> <span class="p">[</span><span class="n">mime
 </span><span class="p">]</span><span class="o">|-</span><span
class="k">print</span><span class="p">]</span> <span class="sr">&lt;outfile&gt;</span>
@@ -488,20 +488,20 @@ $(document).ready(function () {
 
 
 <p>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-wzxhzdk14wzxhzdk15">Writing your own script <a id="your-own-script"></a></h3>
+<h3 id="your-own-script">Writing your own script</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 &lt;CLASSPATH&gt;
         org.apache.fop.cli.Main &lt;arguments&gt;</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-wzxhzdk16wzxhzdk17">Running with java's -jar
option <a id="jar-option"></a></h3>
+<h3 id="jar-option">Running with java's -jar option</h3>
 <p>As an alternative to the start scripts you can run <code>java
         -jar path/to/build/fop.jar &lt;arguments&gt;</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
       &lt;arguments&gt;</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-wzxhzdk18wzxhzdk19">FOP's dynamical classpath
construction <a id="dynamical-classpath"></a></h3>
+<h3 id="dynamical-classpath">FOP's dynamical classpath construction</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-wzxhzdk20wzxhzdk21">Using Xalan to Check
XSL-FO Input <a id="check-input"></a></h2>
+<h2 id="check-input">Using Xalan to Check XSL-FO Input</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)
@@ -509,7 +509,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-wzxhzdk22wzxhzdk23">Memory Usage <a id="memory"></a></h2>
+<h2 id="memory">Memory Usage</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>
@@ -526,7 +526,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-wzxhzdk24wzxhzdk25">Problems <a id="problems"></a></h2>
+<h2 id="problems">Problems</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 Thu Dec  6 14:12:18
2012
@@ -343,9 +343,9 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/trunk/">Trunk</a></div>
-->
       	<div class="section-content"><h1 id="apachewzxhzdk4-fop-servlets">Apache&trade;
FOP: Servlets</h1>
 <p><subtitle>How to use Apache&trade; FOP in a Servlet</subtitle></p>
-<h2 id="overview-wzxhzdk8wzxhzdk9">Overview <a id="overview"></a></h2>
+<h2 id="overview">Overview</h2>
 <p>This page discusses topic all around using Apache&trade; 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">Example Servlets in the FOP distribution</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>
@@ -358,9 +358,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>
-<h2 id="create-your-own-servlet-wzxhzdk13wzxhzdk14">Create your own Servlet <a id="servlet"></a></h2>
+<h2 id="servlet">Create your own Servlet</h2>
 <p>This section assumes you are familiar with <a href="embedding.html">embedding
FOP</a>.</p>
-<h3 id="a-minimal-servlet-wzxhzdk15wzxhzdk16">A minimal Servlet <a id="minimal-servlet"></a></h3>
+<h3 id="minimal-servlet">A minimal Servlet</h3>
 <p>Here is a minimal code snippet to demonstrate the basics:</p>
 <div class="codehilite"><pre><span class="kd">private</span> <span
class="n">FopFactory</span> <span class="n">fopFactory</span> <span
class="o">=</span> <span class="n">FopFactory</span><span class="o">.</span><span
class="na">newInstance</span><span class="o">();</span>
 <span class="kd">private</span> <span class="n">TransformerFactory</span>
<span class="n">tFactory</span> <span class="o">=</span> <span
class="n">TransformerFactory</span><span class="o">.</span><span class="na">newInstance</span><span
class="o">();</span>
@@ -382,7 +382,7 @@ This example servlet should not be used 
 
 
 <p>There are numerous problems with the code snippet above. Its purpose is only to
demonstrate the basic concepts. See below for details.</p>
-<h3 id="adding-xsl-tranformation-xslt-wzxhzdk17wzxhzdk18">Adding XSL tranformation
(XSLT) <a id="xslt"></a></h3>
+<h3 id="xslt">Adding XSL tranformation (XSLT)</h3>
 <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:</p>
 <div class="codehilite"><pre><span class="kd">private</span> <span
class="n">FopFactory</span> <span class="n">fopFactory</span> <span
class="o">=</span> <span class="n">FopFactory</span><span class="o">.</span><span
class="na">newInstance</span><span class="o">();</span>
 <span class="kd">private</span> <span class="n">TransformerFactory</span>
<span class="n">tFactory</span> <span class="o">=</span> <span
class="n">TransformerFactory</span><span class="o">.</span><span class="na">newInstance</span><span
class="o">();</span>
@@ -426,9 +426,9 @@ This example servlet should not be used 
 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="cfg">Custom configuration</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="performance">Improving performance</h3>
 <p>There are several options to consider:</p>
 <ul>
 <li>
@@ -439,7 +439,7 @@ The <code>Source</code> instance used ab
 </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="uriresolver">Accessing resources in your web application</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="cm">/** URIResolver for use by
this servlet */</span>
@@ -486,7 +486,7 @@ The <code>Source</code> instance used ab
 </pre></div>
 
 
-<h2 id="notes-on-microsoft-internet-explorer-wzxhzdk25wzxhzdk26">Notes on Microsoft
Internet Explorer <a id="ie"></a></h2>
+<h2 id="ie">Notes on Microsoft Internet Explorer</h2>
 <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>
@@ -501,13 +501,13 @@ The <code>Source</code> instance used ab
 <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-engine">Servlet Engines</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">Tomcat</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">WebSphere 3.5</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="complex-usecases">Handling complex use cases</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 Thu Dec  6 14:12:18
2012
@@ -342,7 +342,7 @@ $(document).ready(function () {
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a
href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<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&trade; FOP</h1>
-<h2 id="important-wzxhzdk1wzxhzdk2">Important! <a id="important"></a></h2>
+<h2 id="important">Important!</h2>
 <p>If you're planning to upgrade to the latest Apache&trade; FOP version there
are a few very important things to consider:</p>
 <ul>
 <li>
@@ -369,7 +369,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-wzxhzdk4wzxhzdk5">What you need to know
when you upgrade! <a id="issues"></a></h2>
+<h2 id="issues">What you need to know when you upgrade!</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 Thu Dec  6 14:12:18 2012
@@ -137,7 +137,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&trade; 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">Legal Stuff</h2>
 <ul>
 <li><a href="/">Home</a></li>
 <li><a href="/team.html">Who We Are</a></li>
@@ -148,7 +148,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">Trademarks</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 Thu Dec  6 14:12:18 2012
@@ -139,7 +139,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">Usage Notes</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>
@@ -165,7 +165,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">Public Archives</h1>
 <p>Archives of all public mailing lists can be found here:</p>
 <ul>
 <li>
@@ -178,7 +178,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="xmlgraphics-general">XML Graphics General Mailing List</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>
@@ -190,7 +190,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="xmlgraphics-commits">XML Graphics Commits Mailing List</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>
@@ -202,7 +202,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">Batik Users Mailing List</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>
@@ -214,7 +214,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-dev">Batik Developers Mailing List</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>
@@ -226,7 +226,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">Batik Commits Mailing List</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>
@@ -238,7 +238,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">FOP Users Mailing List</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>
@@ -251,7 +251,7 @@ If you want to unsubscribe from the XML 
 It is usually a good idea to state the FOP &amp; 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&amp;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-dev">FOP Developers Mailing List</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>
@@ -263,7 +263,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">FOP Commits Mailing List</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 Thu Dec  6 14:12:18 2012
@@ -136,7 +136,7 @@ $(document).ready(function () {
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a></div> -->
       	<div class="section-content"><h1 id="the-apachewzxhzdk0-xml-graphics-project-code-repositories">The
Apache&trade; 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">Web Access to the Repositories</h2>
 <p>The Apache&trade; 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>
@@ -153,9 +153,9 @@ $(document).ready(function () {
 <p>Apache&trade; 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-accessthesourcetree">Access the Source Tree {#Access+the+Source+Tree}</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-anonymous28read-only29svnaccess">Anonymous (read-only)
SVN access {#Anonymous+%28read-only%29+SVN+access}</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 Thu Dec  6 14:12:18 2012
@@ -136,9 +136,9 @@ $(document).ready(function () {
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a></div> -->
       	<div class="section-content"><h1 id="the-apachewzxhzdk0-xml-graphics-project-community">The
Apache&trade; XML Graphics Project - Community</h1>
-<h2 id="who-we-are-wzxhzdk1wzxhzdk2">Who We Are <a id="WhoWeAre"></a></h2>
+<h2 id="WhoWeAre">Who We Are</h2>
 <p>The <em>Apache&trade; 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&trade;
XML Graphics Project - Project Management Committee <a id="PMC"></a></h2>
+<h2 id="PMC">Apache&trade; XML Graphics Project - Project Management Committee</h2>
 <ul>
 <li>
 <p><a href="mailto:bowditch_chris@hotmail.com">Chris Bowditch</a></p>
@@ -168,7 +168,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="PMC-emeritus">Emeritus Project Management Committee Members</h3>
 <ul>
 <li>
 <p><a href="mailto:chrisg@apache.org">Christian Geisert</a></p>
@@ -180,7 +180,7 @@ $(document).ready(function () {
 <p><a href="mailto:spepping@apache.org">Simon Pepping</a></p>
 </li>
 </ul>
-<h2 id="contacting-the-apachewzxhzdk9-xml-graphics-project">Contacting the Apache&trade;
XML Graphics Project</h2>
+<h2 id="contacting-the-apachewzxhzdk3-xml-graphics-project">Contacting the Apache&trade;
XML Graphics Project</h2>
 <p>If you need to get into contact with the Apache&trade; XML Graphics PMC and
require confidentiality, send your mail to <a href="mailto:private@xmlgraphics.apache.org">private@xmlgraphics.apache.org</a>.
Otherwise, please send your mail to <a href="mailto:general@xmlgraphics.apache.org">general@xmlgraphics.apache.org</a>.
If you want to ask a question about one of the XML Graphics projects's products, please send
your mail to the respective <a href="mail.html">user mailing list</a>.</p></div>
       </div>
       



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


Mime
View raw message