xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840938 [14/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/license.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/license.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/license.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></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-license">Apache&trade; FOP License</h1>
-<h2 id="license-wzxhzdk1wzxhzdk2">License <a id="License"></a></h2>
+<h2 id="License">License</h2>
 <p>All new Apache&trade; FOP releases will be licensed under the <strong>Apache&trade; License, version 2.0</strong>. Releases until version 0.20.5 are released unter the Apache&trade; License, version 1.1.</p>
 <p>To inspect the license terms please consult the LICENSE and NOTICE files in the root directory of the distribution. The full license text can also be accessed via the web from the <a href="http://www.apache.org/licenses/">Apache Licenses page</a>.</p>
 <p>Apache FOP comes with a number of libraries all of which are currently coming from within the Apache Software Foundation. These libraries are all licensed under one of the Apache License versions. There is one exception which is "xml-apis.jar" which contains code licensed by the<fork href="http://www.w3.org">W3C</fork>. Please consult the license files included with the libraries in the "lib" directory for details.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/maillist.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/maillist.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/maillist.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></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-mailing-list-resources">Apache&trade; FOP: Mailing List Resources</h1>
-<h2 id="general-information-wzxhzdk1wzxhzdk2">General Information <a id="general"></a></h2>
+<h2 id="general">General Information</h2>
 <p>Before posting questions to any list:</p>
 <ul>
 <li>
@@ -359,9 +359,9 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>For help in understanding email acronyms, see the <a href="http://www.lingo2word.com/lists/acronym_listA.html">Lingo2Word Acronym List</a>, or the <a href="http://www.keno.org/web_design/acronyms.htm">Keno Internet Services Internet Glossary</a>.</p>
-<h2 id="apachewzxhzdk9-fop-users-mailing-list-wzxhzdk7wzxhzdk8">Apache&trade; FOP Users Mailing List <a id="fop-user"></a></h2>
+<h2 id="fop-user">Apache&trade; FOP Users Mailing List</h2>
 <p>Use this forum to discuss topics of interest to FOP users.</p>
-<h3 id="archives-wzxhzdk10wzxhzdk11">Archives <a id="fop-user-archive"></a></h3>
+<h3 id="fop-user-archive">Archives</h3>
 <p>To review the archives, you have several options:</p>
 <ul>
 <li>
@@ -387,7 +387,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>If you don't like mailing lists and prefer a forum-like system, have a look at <a href="http://dir.gmane.org/gmane.text.xml.fop.user">GMANE</a> or <a href="http://www.nabble.com/FOP---Users-f353.html">Nabble</a>. They allow you to post to the mailing list without having to subscribe.</p>
-<h3 id="subscription-information-wzxhzdk16wzxhzdk17">Subscription Information <a id="fop-user-subscribe"></a></h3>
+<h3 id="fop-user-subscribe">Subscription Information</h3>
 <ul>
 <li>
 <p>See <a href="http://xmlgraphics.apache.org/mail.html">Apache XML Graphics Mailing Lists</a> for detailed subscription information.</p>
@@ -406,7 +406,7 @@ $(document).ready(function () {
 You can find the developer mailing list on the <a href="dev/index.html#mail-fop-dev">Development pages</a>.</p>
 </li>
 </ul>
-<h3 id="submitting-a-question-wzxhzdk18wzxhzdk19">Submitting a Question <a id="fop-user-policy"></a></h3>
+<h3 id="fop-user-policy">Submitting a Question</h3>
 <p>FOP support is primarily <em>self-service</em> . The FOP User Mailing List serves as a backup to the self-service documentation for cases where either the documentation is deficient or where users have unusual circumstances. FOP developers and users are happy to help answer questions that are <em>appropriate to the forum</em> (i.e. FOP-specific), and that are <em>submitted after appropriate preparation</em>. To ensure that your question is not <strong>abusive</strong> of this policy, please use the following checklist:</p>
 <ul>
 <li>
@@ -456,7 +456,7 @@ You can find the developer mailing list 
 <p>Are you attaching large PDF files or screen shots to your message? If so, 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>
-<h2 id="xsl-fo-mailing-list-at-w3c-wzxhzdk20wzxhzdk21">XSL-FO Mailing List (at W3C) <a id="w3c-xslfo"></a></h2>
+<h2 id="w3c-xslfo">XSL-FO Mailing List (at W3C)</h2>
 <p>Use this forum to ask general XSL-FO questions.</p>
 <ul>
 <li>
@@ -469,7 +469,7 @@ You can find the developer mailing list 
 <p>Subscription administration information can be found at <a href="http://www.w3.org/Mail/Request">W3C Mailing List Administrativia</a>. After reviewing the instructions there, send your subscribe or unsubscribe request to <a href="mailto:www-xsl-fo-request@w3.org">www-xsl-fo-request@w3.org</a>.</p>
 </li>
 </ul>
-<h2 id="xsl-fo-mailing-list-at-yahoogroups-wzxhzdk22wzxhzdk23">XSL-FO Mailing List (at YahooGroups) <a id="yahoogroups-xslfo"></a></h2>
+<h2 id="yahoogroups-xslfo">XSL-FO Mailing List (at YahooGroups)</h2>
 <p>Use this forum to ask general XSL-FO questions.</p>
 <ul>
 <li>
@@ -479,7 +479,7 @@ You can find the developer mailing list 
 <p>The home page for this groups is <a href="http://groups.yahoo.com/group/XSL-FO">XSL-FO - discussion of XSL Formatting Objects</a>.</p>
 </li>
 </ul>
-<h2 id="xslt-list-mulberry-tech-wzxhzdk24wzxhzdk25">XSLT List (Mulberry Tech) <a id="xslt-mulberry"></a></h2>
+<h2 id="xslt-mulberry">XSLT List (Mulberry Tech)</h2>
 <ul>
 <li>
 <p>Before posting questions to any list, see " <a href="#general">General Information</a> ".</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/news.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/news.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/news.html Thu Dec  6 14:12:18 2012
@@ -343,100 +343,100 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-news">Apache&trade; FOP News</h1>
 <p>RSS Feed: <a href="subproject-news-feed.rss"><img alt="Render Diagram" src="images/feed-icon-14x14.png" /></a></p>
-<h2 id="24-feb-2012-new-committer-wzxhzdk1wzxhzdk2">24 Feb 2012: New committer <a id="news-2012-02-24"></a></h2>
+<h2 id="news-2012-02-24">24 Feb 2012: New committer</h2>
 <p><item date="2012-02-24" title="New committer">
 Welcome Glenn Adams!
 </item></p>
-<h2 id="17-nov-2011-new-committer-wzxhzdk5wzxhzdk6">17 Nov 2011: New committer <a id="news-2011-11-17"></a></h2>
+<h2 id="news-2011-11-17">17 Nov 2011: New committer</h2>
 <p><item date="2011-11-17" title="New committer">
 Welcome Mehdi Houshmand!
 </item></p>
-<h2 id="21-jul-2010-apachewzxhzdk11-fop-10-released-wzxhzdk9wzxhzdk10">21 Jul 2010: Apache&trade; FOP 1.0 Released <a id="news-2010-07-21"></a></h2>
+<h2 id="news-2010-07-21">21 Jul 2010: Apache&trade; FOP 1.0 Released</h2>
 <p><item date="2010-07-21" title="Apache&trade; FOP 1.0 Released">
 The Apache&trade; FOP team is delighted to present you a production grade release of the new FOP codebase. This release contains many bug fixes and new features. See the <a href="1.0/releaseNotes_1.0.html">Release Notes</a> for a list of the most important changes.
 </item></p>
-<h2 id="14-dec-2009-new-committer-wzxhzdk15wzxhzdk16">14 Dec 2009: New committer <a id="news-2009-12-14"></a></h2>
+<h2 id="news-2009-12-14">14 Dec 2009: New committer</h2>
 <p><item date="2009-12-14" title="New committer">
 Welcome Pascal Sancho!
 </item></p>
-<h2 id="5-aug-2008-apachewzxhzdk21-fop-095-released-wzxhzdk19wzxhzdk20">5 Aug 2008: Apache&trade; FOP 0.95 Released <a id="news-2008-08-05"></a></h2>
+<h2 id="news-2008-08-05">5 Aug 2008: Apache&trade; FOP 0.95 Released</h2>
 <p><item date="2008-08-05" title="Apache&trade; FOP 0.95 Released">
 The Apache&trade; FOP team is delighted to present you a production grade release of the new FOP codebase. This release contains many bug fixes and new features. See the <a href="0.95/releaseNotes_0.95.html">Release Notes</a> for a list of the most important changes.
 </item></p>
-<h2 id="16-mar-2008-apachewzxhzdk27-fop-095beta-released-wzxhzdk25wzxhzdk26">16 Mar 2008: Apache&trade; FOP 0.95beta Released <a id="news-2008-03-16"></a></h2>
+<h2 id="news-2008-03-16">16 Mar 2008: Apache&trade; FOP 0.95beta Released</h2>
 <p><item date="2008-03-16" title="Apache&trade; FOP 0.95beta Released">
 The Apache&trade; FOP team is delighted to present you a beta version of the next production grade release of the new FOP codebase. This release contains many bug fixes and new features. See the <a href="0.95/releaseNotes_0.95beta.html">Release Notes</a> for a list of the most important changes.
 </item></p>
-<h2 id="30-oct-2007-new-committer-wzxhzdk31wzxhzdk32">30 Oct 2007: New committer <a id="news-2007-10-30"></a></h2>
+<h2 id="news-2007-10-30">30 Oct 2007: New committer</h2>
 <p><item date="2007-10-30" title="New committer">
 Welcome Max Berger!
 </item></p>
-<h2 id="15-oct-2007-new-committer-wzxhzdk35wzxhzdk36">15 Oct 2007: New Committer <a id="news-2007-10-15"></a></h2>
+<h2 id="news-2007-10-15">15 Oct 2007: New Committer</h2>
 <p><item date="2007-10-15" title="New Committer">
 Welcome Adrian Cumiskey!
 </item></p>
-<h2 id="24-aug-2007-apachewzxhzdk41-fop-094-released-wzxhzdk39wzxhzdk40">24 Aug 2007: Apache&trade; FOP 0.94 Released <a id="news-2007-08-24"></a></h2>
+<h2 id="news-2007-08-24">24 Aug 2007: Apache&trade; FOP 0.94 Released</h2>
 <p><item date="2007-08-24" title="Apache&trade; FOP 0.94 Released">
 The Apache&trade; FOP team is pleased to present you the second production grade release of the new FOP codebase. This release contains many bug fixes and new features. See the Release Notes for a list of the most important changes.
 </item></p>
-<h2 id="26-jan-2007-new-committer-wzxhzdk45wzxhzdk46">26 Jan 2007: New Committer <a id="news-2007-01-26"></a></h2>
+<h2 id="news-2007-01-26">26 Jan 2007: New Committer</h2>
 <p><item date="2007-01-26" title="New Committer">
 Welcome Jay Bryant!
 </item></p>
-<h2 id="9-jan-2007-apachewzxhzdk51-fop-093-released-wzxhzdk49wzxhzdk50">9 Jan 2007: Apache&trade; FOP 0.93 released <a id="news-2007-01-09"></a></h2>
+<h2 id="news-2007-01-09">9 Jan 2007: Apache&trade; FOP 0.93 released</h2>
 <p><item date="2007-01-09" title="Apache&trade; FOP 0.93 released">
 The Apache&trade; FOP team is proud to present to you the first production grade release of the new FOP codebase. This release has the new API first introduced in release 0.92 beta. It contains again many bug fixes and new features.
 </item></p>
-<h2 id="16-oct-2006-new-committer-wzxhzdk55wzxhzdk56">16 Oct 2006: New Committer <a id="news-2006-10-16"></a></h2>
+<h2 id="news-2006-10-16">16 Oct 2006: New Committer</h2>
 <p><item date="2006-10-16" title="New Committer">
 Welcome Vincent Hennebert!
 </item></p>
-<h2 id="18-apr-2006-apachewzxhzdk61-fop-092-beta-released-wzxhzdk59wzxhzdk60">18 Apr 2006: Apache&trade; FOP 0.92 beta released <a id="news-2006-04-18"></a></h2>
+<h2 id="news-2006-04-18">18 Apr 2006: Apache&trade; FOP 0.92 beta released</h2>
 <p><item date="2006-04-18" title="Apache&trade; FOP 0.92 beta released">
 A second "beta" grade release of the new FOP codebase with a modified and now considered stable API. The release contains many bug fixes as well as new features mainly related to even more extensive support of the XSL-FO specification. This is expected to be the last "beta" release before we go to a 1.0 release!
 </item></p>
-<h2 id="23-dec-2005-apachewzxhzdk66-fop-091-beta-released-wzxhzdk64wzxhzdk65">23 Dec 2005: Apache&trade; FOP 0.91 beta released <a id="news-2005-12-23"></a></h2>
+<h2 id="news-2005-12-23">23 Dec 2005: Apache&trade; FOP 0.91 beta released</h2>
 <p><item date="2005-12-23" title="Apache&trade; FOP 0.91 beta released">
 One month after the initial release we're happy present a "beta" grade release of the new FOP codebase. It's mostly a bug fix release but also contains a few new features. Thanks to all those who sent us feedback on the initial release!
 </item></p>
-<h2 id="22-nov-2005-apachewzxhzdk71-fop-090-alpha-1-released-wzxhzdk69wzxhzdk70">22 Nov 2005: Apache&trade; FOP 0.90 alpha 1 released <a id="news-2005-11-22"></a></h2>
+<h2 id="news-2005-11-22">22 Nov 2005: Apache&trade; FOP 0.90 alpha 1 released</h2>
 <p><item date="2005-11-22" title="Apache&trade; FOP 0.90 alpha 1 released">
 The Apache&trade; FOP team is proud to present to you the largely rewritten codebase which is finally in a state where you can start to use it. It has taken over three years to get this far and over two years without a new release from the FOP project.</p>
 <p>Please see also the <a href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/200511.mbox/%3c20051123002157.0EB0.JEREMIAS@apache.org%3e">announcement</a>.
 </item></p>
-<h2 id="8-sep-2005-new-committer-wzxhzdk75wzxhzdk76">8 Sep 2005: New Committer <a id="news-2005-09-08"></a></h2>
+<h2 id="news-2005-09-08">8 Sep 2005: New Committer</h2>
 <p><item date="2005-09-08" title="New Committer">
 Welcome Manuel Mall!
 </item></p>
-<h2 id="20-oct-2004-creation-of-the-apachewzxhzdk81-xml-graphics-project-wzxhzdk79wzxhzdk80">20 Oct 2004: Creation of the Apache&trade; XML Graphics project <a id="news-2004-10-20"></a></h2>
+<h2 id="news-2004-10-20">20 Oct 2004: Creation of the Apache&trade; XML Graphics project</h2>
 <p><item date="2004-10-20" title="Creation of the Apache&trade; XML Graphics project">
 The Apache Board of Directors agreed to the creation of the <a href="http://xmlgraphics.apache.org">Apache&trade; XML Graphics</a> project which will be comprised of Batik and FOP. Both former Apache&trade; XML subprojects are in this way complying with the Board's desire to improve project oversight. Both project teams also see additional benefits of working more closely together.
 </item></p>
-<h2 id="8-oct-2004-new-committer-wzxhzdk86wzxhzdk87">8 Oct 2004: New Committer <a id="news-2004-10-08"></a></h2>
+<h2 id="news-2004-10-08">8 Oct 2004: New Committer</h2>
 <p><item date="2004-10-08" title="New Committer">
 Welcome Luca Furini!
 </item></p>
-<h2 id="24-apr-2004-new-committer-wzxhzdk90wzxhzdk91">24 Apr 2004: New Committer <a id="news-2004-04-24"></a></h2>
+<h2 id="news-2004-04-24">24 Apr 2004: New Committer</h2>
 <p><item date="2004-04-24" title="New Committer">
 Welcome Simon Pepping!
 </item></p>
-<h2 id="7-mar-2004-new-committer-wzxhzdk94wzxhzdk95">7 Mar 2004: New Committer <a id="news-2004-03-07"></a></h2>
+<h2 id="news-2004-03-07">7 Mar 2004: New Committer</h2>
 <p><item date="2004-03-07" title="New Committer">
 Welcome Web Maestro Clay Leeds!
 </item></p>
-<h2 id="10-jan-2004-new-committers-wzxhzdk98wzxhzdk99">10 Jan 2004: New Committers <a id="news-2004-01-10"></a></h2>
+<h2 id="news-2004-01-10">10 Jan 2004: New Committers</h2>
 <p><item date="2004-01-10" title="New Committers">
 Welcome Chris Bowditch and Andreas Delmelle!
 </item></p>
-<h2 id="4-jan-2004-new-committer-wzxhzdk102wzxhzdk103">4 Jan 2004: New Committer <a id="news-2004-01-04"></a></h2>
+<h2 id="news-2004-01-04">4 Jan 2004: New Committer</h2>
 <p><item date="2004-01-04" title="New Committer">
 Welcome Finn Bock!
 </item></p>
-<h2 id="29-nov-2003-new-committer-wzxhzdk106wzxhzdk107">29 Nov 2003: New Committer <a id="news-2003-11-29"></a></h2>
+<h2 id="news-2003-11-29">29 Nov 2003: New Committer</h2>
 <p><item date="2003-11-29" title="New Committer">
 Welcome Peter Herweg!
 </item></p>
-<h2 id="18-jul-2003-apachewzxhzdk112-fop-0205-released-wzxhzdk110wzxhzdk111">18 Jul 2003: Apache&trade; FOP 0.20.5 released <a id="news-2003-07-18"></a></h2>
+<h2 id="news-2003-07-18">18 Jul 2003: Apache&trade; FOP 0.20.5 released</h2>
 <p><item date="2003-07-18" title="Apache&trade; FOP 0.20.5 released">
 Changes since 0.20.4 include:</p>
 <ul>
@@ -488,43 +488,43 @@ Changes since 0.20.4 include:</p>
 </ul>
 <p>See also the full text of the <a href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=fop-dev@xml.apache.org&amp;msgNo=6067">announcement</a>.
 </item></p>
-<h2 id="29-jun-2003-new-committer-wzxhzdk115wzxhzdk116">29 Jun 2003: New Committer <a id="news-2003-06-29"></a></h2>
+<h2 id="news-2003-06-29">29 Jun 2003: New Committer</h2>
 <p><item date="2003-06-29" title="New Committer">
 Welcome Glen Mazza!
 </item></p>
-<h2 id="23-may-2003-apachewzxhzdk121-fop-0205-release-candidate-3-available-wzxhzdk119wzxhzdk120">23 May 2003: Apache&trade; FOP 0.20.5 Release Candidate 3 available <a id="news-2003-05-23"></a></h2>
+<h2 id="news-2003-05-23">23 May 2003: Apache&trade; FOP 0.20.5 Release Candidate 3 available</h2>
 <p><item date="2003-05-23" title="Apache&trade; FOP 0.20.5 Release Candidate 3 available">
 See the full text of the <a href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=fop-dev@xml.apache.org&amp;msgNo=5429">announcement</a>.
 </item></p>
-<h2 id="18-feb-2003-apachewzxhzdk126-fop-0205-release-candidate-2-available-wzxhzdk124wzxhzdk125">18 Feb 2003: Apache&trade; FOP 0.20.5 Release Candidate 2 available <a id="news-2003-02-18"></a></h2>
+<h2 id="news-2003-02-18">18 Feb 2003: Apache&trade; FOP 0.20.5 Release Candidate 2 available</h2>
 <p><item date="2003-02-18" title="Apache&trade; FOP 0.20.5 Release Candidate 2 available">
 See the full text of the <a href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=fop-dev@xml.apache.org&amp;msgNo=4509">announcement</a>.
 </item></p>
-<h2 id="2-feb-2003-new-xml-pmc-wzxhzdk129wzxhzdk130">2 Feb 2003: New XML PMC <a id="news-2003-02-02"></a></h2>
+<h2 id="news-2003-02-02">2 Feb 2003: New XML PMC</h2>
 <p><item date="2003-02-02" title="New XML PMC">
 Jeremias Maerki and Peter B. West are now representing FOP on the XML PMC.
 </item></p>
-<h2 id="28-jan-2003-fop-logo-contest-wzxhzdk133wzxhzdk134">28 Jan 2003: FOP logo contest <a id="news-2003-01-28"></a></h2>
+<h2 id="news-2003-01-28">28 Jan 2003: FOP logo contest</h2>
 <p><item date="2003-01-28" title="FOP logo contest">
 We are looking for a new logo. FOP logo contest is started!
 </item></p>
-<h2 id="23-dec-2002-official-fop-wiki-wzxhzdk137wzxhzdk138">23 Dec 2002: Official FOP Wiki <a id="news-2002-12-23"></a></h2>
+<h2 id="news-2002-12-23">23 Dec 2002: Official FOP Wiki</h2>
 <p><item date="2002-12-23" title="Official FOP Wiki">
 See <a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectPages">FOP project pages</a> at the ApacheWiki.
 </item></p>
-<h2 id="10-dec-2002-fop-0205-release-candidate-available-wzxhzdk141wzxhzdk142">10 Dec 2002: FOP 0.20.5 Release Candidate available <a id="news-2002-12-10"></a></h2>
+<h2 id="news-2002-12-10">10 Dec 2002: FOP 0.20.5 Release Candidate available</h2>
 <p><item date="2002-12-10" title="FOP 0.20.5 Release Candidate available">
 See the full text of the <a href="http://marc.theaimsgroup.com/?l=fop-user&amp;m=103954279712704&amp;w=2">announcement</a>.
 </item></p>
-<h2 id="23-nov-2002-exlsfo-project-has-been-created-wzxhzdk145wzxhzdk146">23 Nov 2002: EXLSFO project has been created <a id="news-2002-11-23"></a></h2>
+<h2 id="news-2002-11-23">23 Nov 2002: EXLSFO project has been created</h2>
 <p><item date="2002-11-23" title="EXLSFO project has been created">
 The EXSLFO project is a community effort to define functional extensions to thet XSL Formatting Objects specification. See the <a href="http://exslfo.sourceforge.net">EXSLFO website</a> for details.
 </item></p>
-<h2 id="22-nov-2002-new-committer-wzxhzdk149wzxhzdk150">22 Nov 2002: New Committer <a id="news-2002-11-22"></a></h2>
+<h2 id="news-2002-11-22">22 Nov 2002: New Committer</h2>
 <p><item date="2002-11-22" title="New Committer">
 Welcome Victor Mote!
 </item></p>
-<h2 id="9-nov-2002-new-committer-wzxhzdk153wzxhzdk154">9 Nov 2002: New Committer <a id="news-2002-11-09"></a></h2>
+<h2 id="news-2002-11-09">9 Nov 2002: New Committer</h2>
 <p><item date="2002-11-09" title="New Committer">
 Welcome Oleg Tkachenko!
 </item></p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/quickstartguide.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/quickstartguide.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/quickstartguide.html Thu Dec  6 14:12:18 2012
@@ -343,7 +343,7 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-quick-start-guide">Apache&trade; FOP: Quick Start Guide</h1>
 <p><subtitle>Everything you need to start using and appreciating Apache&trade; FOP quickly.</subtitle></p>
-<h2 id="apachewzxhzdk6-fop-essentials-wzxhzdk4wzxhzdk5">Apache&trade; FOP Essentials <a id="essentials"></a></h2>
+<h2 id="essentials">Apache&trade; FOP Essentials</h2>
 <p>The goal of this <strong>Quick Start Guide</strong> is to help novice users get Apache FOP up and running quickly. Typically, you'll need to:</p>
 <ol>
 <li>
@@ -384,7 +384,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>Once you've familiarized yourself with the basics, you can get more detailed information, in the detailed FOP <a href="1.0/index.html">product documentation</a>.</p>
-<h2 id="hello-world-with-fop-wzxhzdk7wzxhzdk8">Hello World with FOP <a id="hello-world"></a></h2>
+<h2 id="hello-world">Hello World with FOP</h2>
 <p>This section walks you through a "Hello World!" page with Apache FOP. We're assuming you download the binary distribution and that you have a Java Runtime Environment (version 1.4 or later) installed.</p>
 <ol>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/resources.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/resources.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/resources.html Thu Dec  6 14:12:18 2012
@@ -344,7 +344,7 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-other-resources">Apache&trade; FOP: Other Resources</h1>
 <p><subtitle>Resources useful for developing and using Apache&trade; FOP</subtitle></p>
 <h2 id="specs">Specifications</h2>
-<h3 id="xsl-fo-wzxhzdk4wzxhzdk5">XSL-FO <a id="specs-xslfo"></a></h3>
+<h3 id="specs-xslfo">XSL-FO</h3>
 <ul>
 <li>
 <p><a href="http://www.w3.org/TR/xsl11/">XSL-FO Recommendation (05 December 2006)</a></p>
@@ -353,7 +353,7 @@ $(document).ready(function () {
 <p><a href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for the XSL-FO Recommendation</a> provided by N. Grigoriev from RenderX.</p>
 </li>
 </ul>
-<h3 id="xslt-wzxhzdk6wzxhzdk7">XSLT <a id="specs-xslt"></a></h3>
+<h3 id="specs-xslt">XSLT</h3>
 <ul>
 <li>
 <p><a href="http://www.w3.org/TR/xslt">XSLT 1.0 Recommendation</a></p>
@@ -362,7 +362,7 @@ $(document).ready(function () {
 <p><a href="http://www.w3.org/TR/xslt20">XSLT 2.0 Recommendation</a></p>
 </li>
 </ul>
-<h3 id="xml-wzxhzdk8wzxhzdk9">XML <a id="specs-xml"></a></h3>
+<h3 id="specs-xml">XML</h3>
 <ul>
 <li>
 <p><a href="http://www.w3.org/TR/xml">XML 1.0</a></p>
@@ -389,7 +389,7 @@ $(document).ready(function () {
 <p><a href="http://www.w3.org/TR/xml-names11/">Namespaces in XML 1.1</a></p>
 </li>
 </ul>
-<h3 id="java-wzxhzdk10wzxhzdk11">Java <a id="specs-java"></a></h3>
+<h3 id="specs-java">Java</h3>
 <ul>
 <li>
 <p><a href="http://java.sun.com/j2se/1.4/docs/api/index.html">Java 2 Platform, Standard Edition, v 1.4.2 API Specification</a></p>
@@ -401,20 +401,20 @@ $(document).ready(function () {
 <p><a href="http://java.sun.com/javase/6/docs/api/index.html">Java Platform, Standard Edition 6 API Specification</a></p>
 </li>
 </ul>
-<h3 id="pdf-wzxhzdk12wzxhzdk13">PDF <a id="specs-pdf"></a></h3>
+<h3 id="specs-pdf">PDF</h3>
 <ul>
 <li><a href="http://partners.adobe.com/asn/tech/pdf/specifications.jsp">Portable Document Format (PDF) Reference Manual</a></li>
 </ul>
-<h3 id="unicode-wzxhzdk14wzxhzdk15">Unicode <a id="specs-unicode"></a></h3>
+<h3 id="specs-unicode">Unicode</h3>
 <ul>
 <li><a href="http://www.unicode.org/reports/tr14">UTR-14 (Unicode Standard Annex #14: Line Breaking Properties)</a></li>
 </ul>
-<h3 id="other-wzxhzdk16wzxhzdk17">Other <a id="specs-other"></a></h3>
+<h3 id="specs-other">Other</h3>
 <ul>
 <li><a href="http://www.w3.org/TR/SVG/">Supported SVG Recommendation (04 September 2001)</a></li>
 </ul>
-<h2 id="books-tutorials-articles-wzxhzdk18wzxhzdk19">Books, Tutorials, Articles <a id="documents"></a></h2>
-<h3 id="xsl-fo-wzxhzdk20wzxhzdk21">XSL-FO <a id="documents-xslfo"></a></h3>
+<h2 id="documents">Books, Tutorials, Articles</h2>
+<h3 id="documents-xslfo">XSL-FO</h3>
 <ul>
 <li>
 <p>[online book] <a href="http://www.ibiblio.org/xml/books/bible2/chapters/ch18.html">The XML Bible</a>, by Elliotte Rusty Harold. Chapter 18 of XSL Formatting Objects</p>
@@ -441,7 +441,7 @@ $(document).ready(function () {
 <p>[book] <a href="http://www.cranesoftwrights.com/training/index.htm#pfux">Practical Formatting Using XSLFO</a>, Crane Softwrights Ltd., 2003, ISBN 1-894049-11-X.</p>
 </li>
 </ul>
-<h3 id="xslt-wzxhzdk22wzxhzdk23">XSLT <a id="documents-xslt"></a></h3>
+<h3 id="documents-xslt">XSLT</h3>
 <ul>
 <li>
 <p>[online resource] <a href="http://www.w3.org/Style/XSL/">Extensible Stylesheet Language Family (XSL)</a>, W3C XSL Family page.</p>
@@ -471,7 +471,7 @@ $(document).ready(function () {
 <p>[book] <a href="http://www.oreilly.com/catalog/javaxslt">Java and XSLT</a>, by Eric M. Burke, O'Reilly &amp; Associates, 2001, ISBN 0-596-00143-6.</p>
 </li>
 </ul>
-<h3 id="xml-wzxhzdk24wzxhzdk25">XML <a id="documents-xml"></a></h3>
+<h3 id="documents-xml">XML</h3>
 <ul>
 <li>
 <p>[online book] <a href="http://www.ibiblio.org/xml/books/bible2">The XML Bible</a>, by Elliotte Rusty Harold. See hardcopy version below.</p>
@@ -483,11 +483,11 @@ $(document).ready(function () {
 <p>[online resource] A great number of additional XML-related books and articles can be found at the <a href="http://xml.oreilly.com">O'Reilly XML Site</a>.</p>
 </li>
 </ul>
-<h3 id="java-wzxhzdk26wzxhzdk27">Java <a id="documents-java"></a></h3>
+<h3 id="documents-java">Java</h3>
 <ul>
 <li>[online resource] A great number of Java-related books and articles can be found at the <a href="http://java.oreilly.com">O'Reilly Java Site</a>.</li>
 </ul>
-<h3 id="pdf-wzxhzdk28wzxhzdk29">PDF <a id="documents-pdf"></a></h3>
+<h3 id="documents-pdf">PDF</h3>
 <ul>
 <li>
 <p>[online resource] Links to the various PDF file format specifications and numerous other documents can be found at Adobe Solutions Network, Acrobat Resources, <a href="http://partners.adobe.com/asn/acrobat/docs.jsp#filefmtspecs">Acrobat 5.0 SDK Documentation</a>.</p>
@@ -499,7 +499,7 @@ $(document).ready(function () {
 <p>[online resource] A list of Acrobat and PDF developer resources can be found at Adobe Solutions Network, Acrobat Resources, <a href="http://partners.adobe.com/asn/acrobat">Resources for Developers</a>.</p>
 </li>
 </ul>
-<h3 id="postscript-wzxhzdk30wzxhzdk31">PostScript <a id="documents-ps"></a></h3>
+<h3 id="documents-ps">PostScript</h3>
 <ul>
 <li>
 <p>[online resource] A list of PostScript-related technical resources can be found at Adobe Solutions Network, <a href="http://partners.adobe.com/asn/tech/ps/technotes.jsp">PostScript Language Technical Notes</a></p>
@@ -508,7 +508,7 @@ $(document).ready(function () {
 <p>[online resource] Additional PostScript-related developer resources can be found at Adobe Solutions Network, <a href="http://partners.adobe.com/asn/tech/ps/index.jsp">PostScript SDK Archive</a>.</p>
 </li>
 </ul>
-<h2 id="mailing-lists-wzxhzdk32wzxhzdk33">Mailing Lists <a id="mailing-lists"></a></h2>
+<h2 id="mailing-lists">Mailing Lists</h2>
 <p>Before posting questions to any list:</p>
 <ul>
 <li>
@@ -525,7 +525,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>For help in understanding email acronyms, see the <a href="http://www.lingo2word.com/lists/acronym_listA.html">Lingo2Word Acronym List</a>, or the <a href="http://www.keno.org/web_design/acronyms.htm">Keno Internet Services Internet Glossary</a>.</p>
-<h3 id="apache-fop-mailing-list-wzxhzdk34wzxhzdk35">Apache FOP Mailing List <a id="Apache-FOP"></a></h3>
+<h3 id="Apache-FOP">Apache FOP Mailing List</h3>
 <ul>
 <li>
 <p>[mailing list info] <a href="http://xml.apache.org/fop/maillist.html">http://xml.apache.org/fop/maillist.html</a></p>
@@ -567,7 +567,7 @@ $(document).ready(function () {
 <p>[fop-dev-unsubscribe] <a href="mailto:fop-dev-unsubscribe@xmlgraphics.apache.org">fop-dev-unsubscribe@xmlgraphics.apache.org</a></p>
 </li>
 </ul>
-<h3 id="xsl-fo-mailing-list-at-w3c-wzxhzdk36wzxhzdk37">XSL-FO Mailing List (at W3C) <a id="XSL-FO-at-W3C"></a></h3>
+<h3 id="XSL-FO-at-W3C">XSL-FO Mailing List (at W3C)</h3>
 <ul>
 <li>
 <p>[mailing list info] <a href="http://www.w3.org/Mail/Request">http://www.w3.org/Mail/Request</a></p>
@@ -576,16 +576,16 @@ $(document).ready(function () {
 <p>[mailing list archives] <a href="http://lists.w3.org/Archives/Public/www-xsl-fo/">http://lists.w3.org/Archives/Public/www-xsl-fo/</a></p>
 </li>
 </ul>
-<h3 id="xsl-fo-mailing-list-at-yahoogroups-wzxhzdk38wzxhzdk39">XSL-FO Mailing List (at YahooGroups) <a id="XSL-FO-at-YahooGroups"></a></h3>
+<h3 id="XSL-FO-at-YahooGroups">XSL-FO Mailing List (at YahooGroups)</h3>
 <ul>
 <li>[mailing list info &amp; archives] <a href="http://groups.yahoo.com/group/XSL-FO">http://groups.yahoo.com/group/XSL-FO</a></li>
 </ul>
-<h3 id="xslt-list-mulberry-tech-wzxhzdk40wzxhzdk41">XSLT List (Mulberry Tech) <a id="XSLT-at-Mulberry-Tech"></a></h3>
+<h3 id="XSLT-at-Mulberry-Tech">XSLT List (Mulberry Tech)</h3>
 <ul>
 <li>[mailing list info &amp; archives] <a href="http://www.mulberrytech.com/xsl/xsl-list">http://www.mulberrytech.com/xsl/xsl-list</a></li>
 </ul>
-<h2 id="relateduseful-products-wzxhzdk42wzxhzdk43">Related/Useful Products <a id="products"></a></h2>
-<h3 id="fop-add-ons-wzxhzdk44wzxhzdk45">FOP add-ons <a id="products-fop-add-ons"></a></h3>
+<h2 id="products">Related/Useful Products</h2>
+<h3 id="products-fop-add-ons">FOP add-ons</h3>
 <ul>
 <li>
 <p>[software] TIFFRenderer is a renderer for outputting multi-page TIFF: <a href="http://www.tkachenko.com/fop/tiffrenderer.html">http://www.tkachenko.com/fop/tiffrenderer.html</a> (MPL)</p>
@@ -606,7 +606,7 @@ $(document).ready(function () {
 <p>[software &amp; tools] <a href="http://offo.sourceforge.net/">Objects For Formatting Objects</a> hosts hyphenation patterns and (eventually) files other accessory data files &amp; scripts.</p>
 </li>
 </ul>
-<h3 id="pdf-post-processors-wzxhzdk46wzxhzdk47">PDF post-processors <a id="products-pdf"></a></h3>
+<h3 id="products-pdf">PDF post-processors</h3>
 <ul>
 <li>
 <p>[software] <a href="http://pdfbox.apache.org">Apache PDFBox</a> (Apache License V2.0)</p>
@@ -621,7 +621,7 @@ $(document).ready(function () {
 <p>[software] <a href="http://www.accesspdf.com/pdftk/">pdftk</a> the pdf toolkit</p>
 </li>
 </ul>
-<h3 id="xsl-fo-editors-wzxhzdk48wzxhzdk49">XSL-FO editors <a id="products-editors"></a></h3>
+<h3 id="products-editors">XSL-FO editors</h3>
 <ul>
 <li>
 <p>[software] <a href="http://foa.sourceforge.net/">FOA (Formatting Objects Authoring)</a> (MPL)</p>
@@ -636,7 +636,7 @@ $(document).ready(function () {
 <p>[software] <a href="http://www.digiforms.com/">DIGIFORMS Document Designer</a> by Metafocus (commercial)</p>
 </li>
 </ul>
-<h3 id="other-products-wzxhzdk50wzxhzdk51">Other products <a id="products-other"></a></h3>
+<h3 id="products-other">Other products</h3>
 <ul>
 <li>
 <p>[software] <a href="http://foray.sourceforge.net/">FOray</a> a renderer for converting XML files to PDF via XSL Formatting Object elements (FOP fork)</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/status.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/status.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/status.html Thu Dec  6 14:12:18 2012
@@ -343,14 +343,14 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-status">Apache&trade; FOP Status</h1>
 <p><subtitle>Current Status of Apache&trade; FOP</subtitle></p>
-<h2 id="status-wzxhzdk4wzxhzdk5">Status <a id="Status"></a></h2>
+<h2 id="Status">Status</h2>
 <p>[last updated 5 July 2010]</p>
 <p>Apache&trade; FOP version 0.95 was released on 5 August 2008. Apache&trade; FOP version 1.0 was released on 21 July 2010.</p>
-<h2 id="development-status-wzxhzdk8wzxhzdk9">Development Status <a id="Development+Status"></a></h2>
+<h2 id="development-status-developmentstatus">Development Status {#Development+Status}</h2>
 <p>The FOP code base is gradually evolving, from version 0.90 released on 22 November 2005, to version 1.0 released on 21 July 2010. Further releases in the 1.x series may be expected.</p>
 <p>FOP releases before version 0.90 were based on a different code base. The last release in that series was version 0.20.5, released on 18 July 2003. This series is no longer maintained.</p>
 <p>If you're looking for a long-term road-map we have to disappoint you. This is Open Source and we're mostly volunteers working in their free time. What we have is an idea where we want to go. How fast we get there depends on the available time, on how well our ideas work out while developing and on you! There's a <a href="http://wiki.apache.org/xmlgraphics-fop/RoadMap">document in the Wiki</a> where ideas for new developments may be registered and documented.</p>
-<h3 id="status-of-the-individual-components-wzxhzdk10wzxhzdk11">Status of the individual components <a id="component-status"></a></h3>
+<h3 id="component-status">Status of the individual components</h3>
 <p>Not all the components of FOP currently have the same quality. The following table tries to give you an overview:</p>
 <table>
 <thead>

Modified: websites/staging/xmlgraphics/trunk/content/fop/team.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/team.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/team.html Thu Dec  6 14:12:18 2012
@@ -343,7 +343,7 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-development-team">Apache&trade; FOP: Development Team</h1>
 <p>All lists on this page are in alphabetical order. Some of them may be incomplete. If you know of an error or omission, please send a message to the <a href="mailto:fop-dev@xmlgraphics.apache.org">fop-dev</a> mailing list.</p>
-<h2 id="active-committers-wzxhzdk1wzxhzdk2">Active Committers <a id="commit-active"></a></h2>
+<h2 id="commit-active">Active Committers</h2>
 <p>Please don't write to any developer directly if you need help on using FOP. Only if you submit questions to the <a href="maillist.html#fop-user">FOP User Mailing List</a> will other FOP users be able to profit from answers given to your question. Another point is that a developer may have gone inactive or is on holidays in which case you may not get an answer in time.</p>
 <ul>
 <li>
@@ -386,7 +386,7 @@ $(document).ready(function () {
 <p><a href="mailto:tcho@club-internet.fr">Pascal Sancho</a> (PS) is an XML developper from Aix-en-Provence (France). He works on software solutions for rendering various kind of documents on various supports, more specifically taking care of PDF generation with FOP.</p>
 </li>
 </ul>
-<h2 id="active-contributors-wzxhzdk3wzxhzdk4">Active Contributors <a id="contribute-active"></a></h2>
+<h2 id="contribute-active">Active Contributors</h2>
 <ul>
 <li>
 <p>Georg Datterl is a software developer from Austria, currently working for Geneon media solutions gmbh in Nuremberg, Germany. He needs FOP to wrestle gigabytes of electronic data into thousands of printed pages.</p>
@@ -398,9 +398,9 @@ $(document).ready(function () {
 <p>Robert Meyer is a developer from England with experience in both Java and C#. Has an keen interest in software automation which first originated from writing a system to automate ground traffic in airports at university.</p>
 </li>
 </ul>
-<h2 id="founder-wzxhzdk5wzxhzdk6">Founder <a id="founder"></a></h2>
+<h2 id="founder">Founder</h2>
 <p>FOP was originally created and donated to the Apache Software Foundation by <a href="mailto:jtauber@jtauber.com">James Tauber</a>. Information about him can be found at<fork href="http://www.jtauber.com">his website</fork>.</p>
-<h2 id="inactive-committers-wzxhzdk9wzxhzdk10">Inactive Committers <a id="commit-inactive"></a></h2>
+<h2 id="commit-inactive">Inactive Committers</h2>
 <ul>
 <li>
 <p><a href="mailto:max AT berger DOT name">Max Berger</a> (MB)</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/accessibility.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/accessibility.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/accessibility.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="apachewzxhzdk4-fop-accessibility">Apache&trade; FOP: Accessibility</h1>
-<h2 id="overview-wzxhzdk5wzxhzdk6">Overview <a id="overview"></a></h2>
+<h2 id="overview">Overview</h2>
 <p>This page describes the <a href="http://en.wikipedia.org/wiki/Accessibility">accessibility</a> features of Apache&trade; FOP. <a href="http://www.section508.gov/">Section 508</a> defines accessibility in the context of electronic documents for the USA but other countries have similar requirements.</p>
 <p>Accessibility features are available only for the PDF output format and there are some implementation limitations. Also, certain actions must be undertaken by the content creator to ensure that FOP can create a truly accessible document.</p>
 <h2 id="enabling-accessibility">Enabling accessibility</h2>
@@ -354,7 +354,7 @@ $(document).ready(function () {
 </ol>
 <p>When accessibility is enabled, additional information relating to the logical structure of the document is added to the PDF. That information allows the PDF viewer (or a text-to-speech application) to retrieve the natural reading order of the document.
 The processing of the logical structure is memory-hungry. You may need to adjust the Java heap size in order to process larger files.</p>
-<h2 id="changes-to-your-xsl-fo-input-files-wzxhzdk8wzxhzdk9">Changes to your XSL-FO input files <a id="source"></a></h2>
+<h2 id="source">Changes to your XSL-FO input files</h2>
 <p>Apache FOP cannot automatically generate accessible PDFs. Some of the work can only be performed by the content provider. Following are some changes that may be necessary to your XSL-FO content in order to generate really accessible documents:</p>
 <ul>
 <li>
@@ -370,7 +370,7 @@ The processing of the logical structure 
 <p>Specify the natural language of the document using the language and country properties (or via the <code>xml:lang</code> shorthand property).</p>
 </li>
 </ul>
-<h2 id="customized-tagging-wzxhzdk10wzxhzdk11">Customized Tagging <a id="customTags"></a></h2>
+<h2 id="customTags">Customized Tagging</h2>
 <p>The <a href="#PDFReference">PDF Reference</a> defines a set of standard Structure Types to tag content. For example, ‘P’ is used for identifying paragraphs, ‘H1’ to ‘H6’ for headers, ‘L’ for lists, ‘Div’ for block-level groups of elements, etc. This standard set is aimed at improving interoperability between applications producing or consuming PDF.</p>
 <p>FOP provides a default mapping of Formatting Objects to elements from that standard set. For example, <code>fo:page-sequence</code> is mapped to ‘Part’, <code>fo:block</code> is mapped to ‘P’, <code>fo:list-block</code> to ‘L’, etc.</p>
 <p>You may want to customize that mapping to improve the accuracy of the tagging or deal with particular FO constructs. For example, you may want to make use of the ‘H1’ to ‘H6’ tags to make the hierarchical structure of the document appear in the PDF. This is achieved by using the <code>role</code> XSL-FO property:</p>
@@ -517,9 +517,9 @@ The processing of the logical structure 
 </tr>
 </tbody>
 </table>
-<h2 id="testing-wzxhzdk12wzxhzdk13">Testing <a id="testing"></a></h2>
+<h2 id="testing">Testing</h2>
 <p>Accessible PDFs can be tested, for example, using Adobe Acrobat Professional. Its Accessibility Check feature creates a report indicating any deficiencies with a PDF document. Alternatively, you can just let a screen reader read the document aloud.</p>
-<h2 id="limitations-wzxhzdk14wzxhzdk15">Limitations <a id="limitations"></a></h2>
+<h2 id="limitations">Limitations</h2>
 <p>Accessibility support in Apache FOP is relatively new, so there are certain limitations. Please help us identify and close any gaps.</p>
 <ul>
 <li>
@@ -535,7 +535,7 @@ The processing of the logical structure 
 <p>The side regions (region-before, region-after etc.) are currently not specially identified. Screen readers may read their content at page changes.</p>
 </li>
 </ul>
-<h2 id="related-links-wzxhzdk16wzxhzdk17">Related Links <a id="links"></a></h2>
+<h2 id="links">Related Links</h2>
 <p>Many resources providing guidance about creating accessible documents can be found on the web. Here are a few links, along with additional resources around the topic:</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html Thu Dec  6 14:12:18 2012
@@ -343,7 +343,7 @@ $(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="apachewzxhzdk5-fop-ant-task">Apache&trade; FOP: Ant task</h1>
 <p>Apache&trade; FOP provides an Ant task for automating the document build process.</p>
-<h2 id="description-wzxhzdk7wzxhzdk8">Description <a id="basics"></a></h2>
+<h2 id="basics">Description</h2>
 <p>The FOP Ant task will convert XSL-FO documents to PDF, PS, PCL etc. output (see <a href="output.html">Output formats</a> for available formats).</p>
 <p>To call FOP tasks within Ant, first add a FOP task definition to your Ant build file. One method of defining the task is as follows:</p>
 <div class="codehilite"><pre><span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;fop.home&quot;</span> <span class="na">value=</span><span class="s">&quot;....path to your FOP HOME directory...&quot;</span><span class="nt">/&gt;</span>
@@ -364,7 +364,7 @@ $(document).ready(function () {
 
 
 <p>Then create FOP tasks within your Ant build file, using the FOP task parameters listed below.</p>
-<h2 id="parameters-for-fop-ant-task-wzxhzdk9wzxhzdk10">Parameters for FOP Ant task <a id="parameters"></a></h2>
+<h2 id="parameters">Parameters for FOP Ant task</h2>
 <p><caption>Parameters specified as attributes</caption></p>
 <table>
 <thead>
@@ -463,7 +463,7 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h2 id="examples-wzxhzdk14wzxhzdk15">Examples <a id="examples"></a></h2>
+<h2 id="examples">Examples</h2>
 <p>The following example converts a single XSL-FO file to a PDF document:</p>
 <div class="codehilite"><pre><span class="nt">&lt;target</span> <span class="na">name=</span><span class="s">&quot;generate-pdf&quot;</span> <span class="na">description=</span><span class="s">&quot;Generates a single PDF file&quot;</span><span class="nt">&gt;</span>
    <span class="nt">&lt;fop</span> <span class="na">format=</span><span class="s">&quot;application/pdf&quot;</span>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/compiling.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/compiling.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/compiling.html Thu Dec  6 14:12:18 2012
@@ -342,18 +342,18 @@ $(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="apachewzxhzdk0-fop-building-from-source-code">Apache&trade; FOP: Building from Source Code</h1>
-<h2 id="do-you-need-to-build-wzxhzdk1wzxhzdk2">Do You Need To Build? <a id="build-needed"></a></h2>
+<h2 id="build-needed">Do You Need To Build?</h2>
 <p>Apache&trade; FOP snapshots are either pre-compiled binary or source. If you are using a binary snapshot, it is already built and there is no need to build it again. If you got the source code from a repository snapshot or via Subversion you will need to build FOP. See the <a href="../download.html">Download Instructions</a> for information about where to obtain binary or repository snapshots, and whether a binary or source snapshot is best for your needs.</p>
-<h2 id="set-up-your-environment-wzxhzdk4wzxhzdk5">Set Up Your Environment <a id="env"></a></h2>
-<h3 id="jdk-wzxhzdk6wzxhzdk7">JDK <a id="env-jdk"></a></h3>
+<h2 id="env">Set Up Your Environment</h2>
+<h3 id="env-jdk">JDK</h3>
 <p>Building FOP requires a minimum Java Development Kit (JDK/SDK) of 1.4 (A Java Runtime Environment is not sufficient).</p>
-<h3 id="classpath-wzxhzdk8wzxhzdk9">CLASSPATH <a id="env-classpath"></a></h3>
+<h3 id="env-classpath">CLASSPATH</h3>
 <p>There is generally no need to setup a classpath. All libraries needed to compile FOP are included in the source distribution and are referenced by the build script. You will only need to adjust the classpath if you build FOP in some other way. See the build script build.xml for details.</p>
-<h3 id="java_home-wzxhzdk10wzxhzdk11">JAVA_HOME <a id="env-java-home"></a></h3>
+<h3 id="env-java-home">JAVA_HOME</h3>
 <p>The build script uses <a href="http://ant.apache.org/">Apache Ant</a>, a popular Java-based build tool, which usually requires that the environment variable JAVA_HOME point to your local JDK root directory. This is true even if you use JDK 1.4 or above, which normally does not need this setting.</p>
-<h3 id="apache-ant-wzxhzdk12wzxhzdk13">Apache Ant <a id="env-ant"></a></h3>
+<h3 id="env-ant">Apache Ant</h3>
 <p><a href="http://ant.apache.org/">Apache Ant</a> (Version 1.7 or later) must be installed in order to build FOP. Following best practices we don't include Ant with FOP anymore. You can find the <a href="http://ant.apache.org/manual/">instructions to install Ant in the Ant manual</a> on the web.</p>
-<h2 id="run-the-build-script-wzxhzdk14wzxhzdk15">Run the Build Script <a id="build-script"></a></h2>
+<h2 id="build-script">Run the Build Script</h2>
 <p>Change to the FOP root directory and build FOP by executing the build script (build.xml) using the "ant" command.
 The "ant" command is only available on your system if you've properly <a href="http://ant.apache.org/manual/">installed Apache Ant</a> and added Ant's location to the PATH environment variable.
 The file build.xml in the FOP root directory is the blueprint that Ant uses for the build. It contains information for numerous build targets, many of which are building blocks to more useful target, and others which are primarily used by the FOP developers. You may benefit from looking through this file to learn more about the various build targets. To obtain a complete list of useful build targets:
@@ -378,7 +378,7 @@ OR
 ant all
 To clean the build directory first:
 ant clean allIf you want to shorten the build time you can just call the "package" target which doesn't perform any automated tests during the build.</p>
-<h2 id="troubleshooting-wzxhzdk16wzxhzdk17">Troubleshooting <a id="problems"></a></h2>
+<h2 id="problems">Troubleshooting</h2>
 <p>If you have problems building FOP, please try the following:</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.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="apachewzxhzdk0-fop-complex-scripts">Apache&trade; FOP: Complex Scripts</h1>
-<h2 id="overview-wzxhzdk1wzxhzdk2">Overview <a id="overview"></a></h2>
+<h2 id="overview">Overview</h2>
 <p>This page describes the <a href="http://en.wikipedia.org/wiki/Complex_scripts">complex scripts</a> features of Apache&trade; FOP, which include:</p>
 <ul>
 <li>
@@ -358,7 +358,7 @@ $(document).ready(function () {
 <p>Support for advanced number to string formatting.</p>
 </li>
 </ul>
-<h2 id="disabling-complex-scripts-wzxhzdk4wzxhzdk5">Disabling complex scripts <a id="Disabling+complex+scripts"></a></h2>
+<h2 id="disabling-complex-scripts-disablingcomplexscripts">Disabling complex scripts {#Disabling+complex+scripts}</h2>
 <p>Complex script features are enabled by default. If some application of FOP does not require this support, then it can be disabled in three ways:</p>
 <ol>
 <li><strong>Command line:</strong><br/>The command line option <code>-nocs</code> turns off complex script features:<br/><code>fop -nocs -fo mydocument.fo -pdf mydocument.pdf</code><br/></li>
@@ -367,7 +367,7 @@ $(document).ready(function () {
 </ol>
 <p>When complex scripts features are enabled, additional information related to bidirectional level resolution, the association between characters and glyphs, and glyph position adjustments are added to the internal, parsed representation of the XSL-FO tree and its corresponding formatted area tree. This additional information will somewhat increase the memory requirements for processing documents that use these features.
 A document author need not make explicit use of any complex scripts feature in order for this additional information to be created. For example, if the author makes use of a font that contains OpenType GSUB and/or GPOS tables, then those tables will be automatically used unless complex scripts features are disabled.</p>
-<h2 id="changes-to-your-xsl-fo-input-files-wzxhzdk6wzxhzdk7">Changes to your XSL-FO input files <a id="source"></a></h2>
+<h2 id="source">Changes to your XSL-FO input files</h2>
 <p>In most circumstances, XSL-FO content does not need to change in order to make use of complex scripts features; however, in certain contexts, fully automatic processing is not sufficient. In these cases, an author may make use of the following XSL-FO constructs:</p>
 <ul>
 <li>
@@ -392,9 +392,9 @@ A document author need not make explicit
 <p>Explicit join control characters: U+200C ZWNJ and U+200D ZWJ.</p>
 </li>
 </ul>
-<h2 id="authoring-details-wzxhzdk8wzxhzdk9">Authoring Details <a id="details"></a></h2>
+<h2 id="details">Authoring Details</h2>
 <p>The complex scripts related effects of the above enumerated XSL-FO constructs are more fully described in the following sub-sections.</p>
-<h3 id="script-property-wzxhzdk10wzxhzdk11">Script Property <a id="script_property"></a></h3>
+<h3 id="script_property">Script Property</h3>
 <p>In order to apply font specific complex script features, it is necessary to know the script that applies to the text undergoing layout processing. This script is determined using the following algorithm:</p>
 <ol>
 <li>
@@ -405,7 +405,7 @@ A document author need not make explicit
 </li>
 </ol>
 <p>In case the automatic algorithm does not produce the desired results, an author may explicitly specify a <code>script</code> property with the desired script. If specified, it must be one of the four-letter script code specified in <a href="http://unicode.org/iso15924/iso15924-codes.html">ISO 15924 Code List</a> or in the <a href="#extended_script_codes">Extended Script Codes</a> table. Comparison of script codes is performed in a case-insensitive manner, so it does not matter what case is used when specifying these codes in an XSL-FO document.</p>
-<h4 id="standard-script-codes-wzxhzdk12wzxhzdk13">Standard Script Codes <a id="standard_script_codes"></a></h4>
+<h4 id="standard_script_codes">Standard Script Codes</h4>
 <p>The following table enumerates the standard ISO 15924 4-letter codes recognized by FOP.</p>
 <table>
 <thead>
@@ -545,7 +545,7 @@ A document author need not make explicit
 </tr>
 </tbody>
 </table>
-<h4 id="extended-script-codes-wzxhzdk14wzxhzdk15">Extended Script Codes <a id="extended_script_codes"></a></h4>
+<h4 id="extended_script_codes">Extended Script Codes</h4>
 <p>The following table enumerates a number of non-standard extended script codes recognized by FOP.</p>
 <table>
 <thead>
@@ -604,10 +604,10 @@ A document author need not make explicit
 </tbody>
 </table>
 <p><warning>Explicit use of one of the above extended script codes is not portable, and should be limited to use with FOP only.</warning>When performing automatic script determination, FOP selects the OpenType Indic Version 2 script codes by default. If the author requires Version 1 behavior, then an explicit, non-extension script code should be specified in a governing <code>script</code> property.</p>
-<h3 id="language-property-wzxhzdk18wzxhzdk19">Language Property <a id="language_property"></a></h3>
+<h3 id="language_property">Language Property</h3>
 <p>Certain fonts that support complex script features can make use of language information in order for language specific processing rules to be applied. For example, a font designed for the Arabic script may support typographic variations according to whether the written language is Arabic, Farsi (Persian), Sindhi, Urdu, or another language written with the Arabic script. In order to apply these language specific features, the author may explicitly mark the text with a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#language">http://www.w3.org/TR/2006/REC-xsl11-20061205/#language</a> property.</p>
 <p>When specifying the <code>language</code> property, the value of the property must be either an <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes">ISO639-2 3-letter code</a> or an <a href="http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">ISO639-1 2-letter code</a>. Comparison of language codes is performed in a case-insensitive manner, so it does not matter what case is used when specifying these codes in an XSL-FO document.</p>
-<h3 id="writing-mode-property-wzxhzdk20wzxhzdk21">Writing Mode Property <a id="writing_mode_property"></a></h3>
+<h3 id="writing_mode_property">Writing Mode Property</h3>
 <p>The <code>writing-mode</code> property is used to determine the axes and direction of the inline progression direction, the block progression direction, the column progression direction (in tables and flows), the shift direction, region placement, the resolution of writing-mode relative property values (such as start, end, before, after), and the default block (paragraph) bidirectionality level.</p>
 <p>The <code>writing-mode</code> property is inherited, so it can appear on any XSL-FO element type; however, it applies (semantically) only to the following element types:</p>
 <ul>
@@ -647,10 +647,10 @@ A document author need not make explicit
 </li>
 </ul>
 <p>Writing modes that employ a vertical inline progression direction are not yet supported.</p>
-<h3 id="number-conversion-properties-wzxhzdk22wzxhzdk23">Number Conversion Properties <a id="number_conversion_properties"></a></h3>
-<h3 id="bidi-override-element-wzxhzdk24wzxhzdk25">Bidi Override Element <a id="bidi_override_element"></a></h3>
+<h3 id="number_conversion_properties">Number Conversion Properties</h3>
+<h3 id="bidi_override_element">Bidi Override Element</h3>
 <p>The <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">fo:bidi-override</a> element may be used to override default bidirectional processing behavior, including default embedding levels and default character directionality. In the absence of either this element or use of explicit <a href="#bidi_controls">Bidi Control Characters</a>, the default behavior prescribed by the <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#fo_bidi-override">Unicode Bidirectional Algorithm</a> applies.</p>
-<h3 id="bidi-control-characters-wzxhzdk26wzxhzdk27">Bidi Control Characters <a id="bidi_controls"></a></h3>
+<h3 id="bidi_controls">Bidi Control Characters</h3>
 <p>In addition to the use of the <a href="#bidi_override_element">Bidi Override Element</a>, an author may make use of the following explicit Unicode Bidi Control Characters:</p>
 <ul>
 <li>
@@ -676,11 +676,11 @@ A document author need not make explicit
 </li>
 </ul>
 <p>If an embedding or override is not terminated (using U+202C PDF) prior to the end of a <a href="http://www.w3.org/TR/2006/REC-xsl11-20061205/#d0e4879">delimited text range</a>, then it is automatically terminated by FOP.</p>
-<h3 id="join-control-characters-wzxhzdk28wzxhzdk29">Join Control Characters <a id="join_controls"></a></h3>
+<h3 id="join_controls">Join Control Characters</h3>
 <p>In order to prevent joining behavior in contexts where joining occurs by default, for example, between U+0628 ARABIC LETTER BEH and U+0646 ARABIC LETTER NOON, an author may used a U+200C ZERO WIDTH NON-JOINER (ZWNJ).</p>
 <p>Conversely, in order to force joining behavior in contexts where joining does not occur by default, for example, between U+0628 ARABIC LETTER BEH and U+0020 SPACE, an author may used a U+200D ZERO WIDTH JOINER (ZWJ).</p>
 <p>The behavior of ZWNJ and ZWJ is script specific. See <a href="http://www.unicode.org/versions/Unicode6.1.0/ch08.pdf">The Unicode Standard, Chapter 8, Middle Eastern Scripts</a> for information on the use of these control characters with the Arabic script. See <a href="http://www.unicode.org/versions/Unicode6.1.0/ch09.pdf">The Unicode Standard, Chapter 9, South Asian Scripts - I</a> for information on the use of these control characters with common Indic scripts.</p>
-<h2 id="supported-scripts-wzxhzdk30wzxhzdk31">Supported Scripts <a id="supported_scripts"></a></h2>
+<h2 id="supported_scripts">Supported Scripts</h2>
 <p>Support for specific complex scripts is enumerated in the following table. Support for those marked as not being supported is expected to be added in future revisions.</p>
 <table>
 <thead>
@@ -796,9 +796,9 @@ A document author need not make explicit
 </tr>
 </tbody>
 </table>
-<h2 id="supported-fonts-wzxhzdk32wzxhzdk33">Supported Fonts <a id="supported_fonts"></a></h2>
+<h2 id="supported_fonts">Supported Fonts</h2>
 <p>Support for specific fonts is enumerated in the following sub-sections. If a given font is not listed, then it has not been tested with these complex scripts features.</p>
-<h3 id="arabic-fonts-wzxhzdk34wzxhzdk35">Arabic Fonts <a id="fonts_arabic"></a></h3>
+<h3 id="fonts_arabic">Arabic Fonts</h3>
 <table>
 <thead>
 <tr>
@@ -865,7 +865,7 @@ A document author need not make explicit
 </tr>
 </tbody>
 </table>
-<h3 id="devanagari-fonts-wzxhzdk36wzxhzdk37">Devanagari Fonts <a id="devanagari_fonts"></a></h3>
+<h3 id="devanagari_fonts">Devanagari Fonts</h3>
 <table>
 <thead>
 <tr>
@@ -902,7 +902,7 @@ A document author need not make explicit
 </tr>
 </tbody>
 </table>
-<h2 id="other-limitations-wzxhzdk38wzxhzdk39">Other Limitations <a id="limitations"></a></h2>
+<h2 id="limitations">Other Limitations</h2>
 <p>Complex scripts support in Apache FOP is relatively new, so there are certain limitations. Please help us identify and close any gaps.</p>
 <ul>
 <li>
@@ -912,7 +912,7 @@ A document author need not make explicit
 <p>Shaping context does not extend across an element boundary. This limitation prevents the use of <code>fo:character</code>, <code>fo:inline</code> or <code>fo:wrapper</code> in order to colorize individual Arabic letters without affecting shaping behavior across the element boundary.</p>
 </li>
 </ul>
-<h2 id="related-links-wzxhzdk40wzxhzdk41">Related Links <a id="links"></a></h2>
+<h2 id="links">Related Links</h2>
 <p>In addition to the XSL-FO specification, a number of external resources provide guidance about authoring documents that employ complex scripts and the features described above:</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html Thu Dec  6 14:12:18 2012
@@ -342,10 +342,10 @@ $(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="apachewzxhzdk11-fop-configuration">Apache&trade; FOP: Configuration</h1>
-<h2 id="configuration-file-basics-wzxhzdk12wzxhzdk13">Configuration File Basics <a id="general"></a></h2>
+<h2 id="general">Configuration File Basics</h2>
 <p>The Apache&trade; FOP configuration file is an XML file containing a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use.</p>
 <p>The easiest way to get started using a FOP configuration file is to copy the sample found at <code>{fop-dir}/conf/fop.xconf</code> to a location of your choice, and then to edit it according to your needs. It contains templates for the various configuration options, most of which are commented out. Remove the comments and change the settings for entries that you wish to use. Be sure to follow any instructions, including comments which specify the value range. Also, since the configuration file is XML, be sure to keep it well-formed.</p>
-<h3 id="making-configuration-available-to-fop-wzxhzdk15wzxhzdk16">Making Configuration Available to FOP <a id="general-available"></a></h3>
+<h3 id="general-available">Making Configuration Available to FOP</h3>
 <p>After creating your configuration file, you must tell FOP how to find it:</p>
 <ul>
 <li>
@@ -356,7 +356,7 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>See <a href="embedding.html#config-internal">Setting the Configuration Programmatically</a> for instructions on how to do so in an embedded environment.</p>
-<h2 id="summary-of-the-general-configuration-options-wzxhzdk17wzxhzdk18">Summary of the General Configuration Options <a id="general-elements"></a></h2>
+<h2 id="general-elements">Summary of the General Configuration Options</h2>
 <table>
 <thead>
 <tr>
@@ -503,7 +503,7 @@ $(document).ready(function () {
 <p>The first penalty element increases the penalty for the raw CCITT loader. This practically forces the decoding of CCITT compressed TIFF images except if there are no TIFF codecs available.</p>
 <p>The second penalty element sets an "infinite" penalty for the TIFF loader using the internal TIFF codec. This practically disables that plug-in as it will never be chosen as a possible solution.</p>
 <p>Negative penalties are possible to promote a plug-in but a negative penalty sum will be treated as zero penalty in most cases. For more details on the image loading framework, please consult the documentation there.</p>
-<h2 id="renderer-configuration-wzxhzdk19wzxhzdk20">Renderer configuration <a id="renderers"></a></h2>
+<h2 id="renderers">Renderer configuration</h2>
 <p>Each Renderer has its own configuration section which is identified by the MIME type the Renderer is written for, ex. "application/pdf" for the PDF Renderer.</p>
 <p>The configuration for the PDF Renderer could look like this:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderers&gt;</span>
@@ -530,7 +530,7 @@ $(document).ready(function () {
 
 
 <p>The details on the font configuration can be found on the separate <a href="fonts.html">Fonts</a> page. Note especially the section entitled <a href="fonts.html#register">Register Fonts with FOP</a>.</p>
-<h3 id="special-settings-for-the-pdf-renderer-wzxhzdk21wzxhzdk22">Special Settings for the PDF Renderer <a id="pdf-renderer"></a></h3>
+<h3 id="pdf-renderer">Special Settings for the PDF Renderer</h3>
 <p>The configuration element for the PDF renderer contains two elements. One is for the font configuration (please follow the link above) and one is for the "filter list". The filter list controls how the individual objects in a PDF file are encoded. By default, all objects get "flate" encoded (i.e. simply compressed with the same algorithm that is also used in ZIP files). Most users don't need to change that setting. For debugging purposes, it may be desired not to compress the internal objects at all so the generated PDF commands can be read. In that case, you can simply use the following filter list. The second filter list (type="image") ensures that all images still get compressed but also ASCII-85 encoded so the produced PDF file is still easily readable in a text editor.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;filterList&gt;</span>
@@ -595,7 +595,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h3 id="special-settings-for-the-postscript-renderer-wzxhzdk23wzxhzdk24">Special Settings for the PostScript Renderer <a id="ps-renderer"></a></h3>
+<h3 id="ps-renderer">Special Settings for the PostScript Renderer</h3>
 <p>Besides the normal font configuration (the same "fonts" element as for the PDF renderer) the PostScript renderer has an additional setting to force landscape pages to be rotated to fit on a page inserted into the printer in portrait mode. Set the value to "true" to activate this feature. The default is "false". Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/postscript&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;auto-rotate-landscape&gt;</span>true<span class="nt">&lt;/auto-rotate-landscape&gt;</span>
@@ -614,7 +614,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h3 id="special-settings-for-the-pcl-renderer-wzxhzdk25wzxhzdk26">Special Settings for the PCL Renderer <a id="pcl-renderer"></a></h3>
+<h3 id="pcl-renderer">Special Settings for the PCL Renderer</h3>
 <p>Non-standard fonts for the PCL renderer are made available through the Java2D subsystem which means that you don't have to do any custom font configuration in this case but you have to use the font names offered by Java.</p>
 <p>Additionally, there are certain settings that control how the renderer handles various elements.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/vnd.hp-PCL&quot;</span><span class="nt">&gt;</span>
@@ -626,7 +626,7 @@ $(document).ready(function () {
 
 <p>The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.</p>
 <p>The default value for the "text-rendering" setting is "auto" which paints the base fonts using PCL fonts. Non-base fonts are painted as bitmaps through Java2D. If the mix of painting methods results in unwelcome output, you can set this to "bitmap" which causes all text to be rendered as bitmaps.</p>
-<h3 id="special-settings-for-the-afp-renderer-wzxhzdk27wzxhzdk28">Special Settings for the AFP Renderer <a id="afp-renderer"></a></h3>
+<h3 id="afp-renderer">Special Settings for the AFP Renderer</h3>
 <p>Additionally, there are certain settings that control how the renderer handles various elements.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/x-afp&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;images</span> <span class="na">mode=</span><span class="s">&quot;b+w&quot;</span> <span class="na">bits-per-pixel=</span><span class="s">&quot;8&quot;</span> <span class="na">native=</span><span class="s">&quot;true&quot;</span><span class="nt">/&gt;</span>
@@ -641,7 +641,7 @@ $(document).ready(function () {
 <p>The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.</p>
 <p>The default value for the "renderer-resolution" is 240 dpi.</p>
 <p>By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.</p>
-<h2 id="when-it-does-not-work-wzxhzdk29wzxhzdk30">When it does not work <a id="When+it+does+not+work"></a></h2>
+<h2 id="when-it-does-not-work-whenitdoesnotwork">When it does not work {#When+it+does+not+work}</h2>
 <p>FOP searches the configuration file for the information it expects, at the position it expects. When that information is not present, FOP will not complain, it will just continue. When there is other information in the file, FOP will not complain, it will just ignore it. That means that when your configuration information is in the file but in a different XML element, or in a different XML path, than FOP expects, it will be silently ignored.</p>
 <p>Check the following possibilities:</p>
 <ul>



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


Mime
View raw message