xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r835892 [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 Tue, 23 Oct 2012 15:05:47 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/fo.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/fo.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/fo.html Tue Oct 23 15:05:41 2012
@@ -331,10 +331,10 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><subtitle>Basic Help for Using XML, XSLT, and XSL-FO</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="overview">Overview</h1>
+<h1 id="overview-wzxhzdk5wzxhzdk6">Overview  <a id="#overview"></a></h1>
 <p>Apache&trade; FOP uses XSL-FO as input. It is the responsibility of the user to make sure that the XSL-FO submitted to FOP is correct. The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another good FAQ is<fork href="http://www.dpawson.co.uk/xsl/">Dave Pawson's XSL FAQ</fork>.</p>
-<h1 id="xml">XML Issues</h1>
-<h2 id="xml-special-chars">Special Characters</h2>
+<h1 id="xml-issues-wzxhzdk10wzxhzdk11">XML Issues  <a id="#xml"></a></h1>
+<h2 id="special-characters-wzxhzdk12wzxhzdk13">Special Characters # <a id="#xml-special-chars"></a></h2>
 <p>When entering special (non-ASCII) characters in XML, the general rule is to use the applicable Unicode character instead of trying to use a character entity as you would with HTML. Remember that HTML is an SGML document type. SGML has a limited character set, which requires it to use character entities to represent special characters. One of the improvements of XML over SGML (and thus HTML) is native support for Unicode. Basic XML has only a handful of character entities, primarily because it doesn't really need more.</p>
 <p>Entities such as <code>&amp;uuml;</code> (u with an umlaut), which work in HTML, will be flagged as undefined entities unless you define them yourself in your DTD. Use the corresponding Unicode character instead. A list of predefined HTML entities and their Unicode codepoints can be found at <a href="http://www.w3.org/TR/html4/sgml/entities.html">Character entity references in HTML 4</a> .</p>
 <p>One common example is <code>&amp;nbsp;</code> , used to obtain a non-breaking space in HTML. In XML, use &#160; instead.</p>
@@ -343,14 +343,14 @@ $(document).ready(function () {
 &#x20AC;
 Getting your XML correctly encoded is only part of the job. If you want the character to display or print correctly (and you probably do), then the selected font must contain the necessary glyph. Because of differences between font encoding methods, and limitations in some font technologies, this can be a troublesome issue, especially for symbol characters. The FOP example file <a href="fo/fonts.fo.pdf">Base-14 Font Character Mapping</a> is a very useful resource in sorting these issues out for the Base-14 fonts. For other fonts, use font editing sofware or operating system utilities (such as the Character Map in most Windows platforms) to determine what characters the font supports.</p>
 <p>An alternative to encoding the character and making it available through a font is to use an embedded graphic to represent the character: GIF, PNG, SVG, etc.</p>
-<h2 id="xml-entity-chars">Entity Characters</h2>
+<h2 id="entity-characters-wzxhzdk16wzxhzdk17">Entity Characters # <a id="#xml-entity-chars"></a></h2>
 <p>The handful of basic XML character entities that do exist are the ampersand, apostrophe, less-than, greater-than, and single-quote characters. These are needed to distinguish markup tags from content, and to distinguish character entities from content. To avoid parser complaints about illegal characters and entities in your input, ensure that ampersands in text and attributes are written as &amp;, "&lt;" is written as &lt;, and "&gt;" as &gt;. It is not necessary everywhere, but it is wise to do so anyway, just to be sure.</p>
 <p>Most XML parsers will provide a line number and sometimes a column number for offending characters.</p>
 <p>Review the <a href="http://www.w3.org/XML/">XML Specification</a> or a good tutorial for details of the XML file format.</p>
-<h2 id="xml-encoding">Encoding Issues</h2>
+<h2 id="encoding-issues-wzxhzdk21wzxhzdk22">Encoding Issues # <a id="#xml-encoding"></a></h2>
 <p>If the parser complains about illegal bytes or characters in the input, or there are unexpected characters in the output, this is usually the result of a character encoding problem. See the <a href="http://www.dpawson.co.uk/xsl">XSL FAQ</a> for additional information. Many software packages that produce XML, including XSLT processors, use UTF-8 encoding as a default. If you view their output with something not aware of the encoding, like Notepad for Win95/98/ME/NT, funny characters are displayed. A � is a giveaway.</p>
-<h1 id="xslt">XSLT Issues</h1>
-<h2 id="xslt-date">Current Date and Time</h2>
+<h1 id="xslt-issues-wzxhzdk23wzxhzdk24">XSLT Issues  <a id="#xslt"></a></h1>
+<h2 id="current-date-and-time-wzxhzdk25wzxhzdk26">Current Date and Time # <a id="#xslt-date"></a></h2>
 <p>XSL-FO does not currently have a function for retrieving the current date and time. However, in some cases, XSLT can be used to place the current date and time into the XSL-FO document as it is generated.</p>
 <p>One possibility is to use the<jump href="http://exslt.org/date/index.html">exslt date and time extension</jump>.</p>
 <p>Another possibility is to use java or javascript (or perhaps some other language). Here is an example, using java, that works with Xalan. First, create the appropriate namespace:
@@ -363,8 +363,8 @@ Next, use the java language to retrieve 
     <xsl:value-of select="java:format(java:java.text.SimpleDateFormat.new
 ('MMMM d, yyyy, h:mm:ss a (zz)'), java:java.util.Date.new())"/>
   </xsl:template></p>
-<h1 id="xsl-fo">XSL-FO Issues</h1>
-<h2 id="fo-center-vertical">Vertical Centering</h2>
+<h1 id="xsl-fo-issues-wzxhzdk32wzxhzdk33">XSL-FO Issues  <a id="#xsl-fo"></a></h1>
+<h2 id="vertical-centering-wzxhzdk34wzxhzdk35">Vertical Centering # <a id="#fo-center-vertical"></a></h2>
 <p>To vertically center an image, table, or other item, use display-align="center". See <a href="compliance.html#fo-property-display-align">display-align Compliance</a> for implementation status. Here is a small, self-contained document centering an image on a page:
 &lt;?xml version="1.0"?&gt;
 <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
@@ -391,7 +391,7 @@ Next, use the java language to retrieve 
     </fo:flow>
   </fo:page-sequence>
 </fo:root></p>
-<h2 id="fo-center-table-horizon">Horizontal Centering (Tables)</h2>
+<h2 id="horizontal-centering-tables-wzxhzdk59wzxhzdk60">Horizontal Centering (Tables) # <a id="#fo-center-table-horizon"></a></h2>
 <p>To center a table horizontally, one possibility is to add one column on the left and one on the right which pad the table so that the visible part is centered:
 &lt;?xml version="1.0"?&gt;
 <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
@@ -419,9 +419,9 @@ Next, use the java language to retrieve 
   </fo:page-sequence>
 </fo:root>
 If your table is more complicated, or if defining borders on individual cells becomes too much work, use the code above and nest your table within the middle cell.</p>
-<h2 id="fo-right-align-table-horizon">Right-Aligning (Tables)</h2>
+<h2 id="right-aligning-tables-wzxhzdk85wzxhzdk86">Right-Aligning (Tables) # <a id="#fo-right-align-table-horizon"></a></h2>
 <p>To right-align a table, you can use the same approach as above for centering tables. Just remove the last table-column element which causes all the left-over space not used by the columns with a fixed column-width to be assigned to the first column which effectively right-aligns the table.</p>
-<h2 id="fo-oddeven">Recto/Verso Static Content Differences</h2>
+<h2 id="rectoverso-static-content-differences-wzxhzdk87wzxhzdk88">Recto/Verso Static Content Differences # <a id="#fo-oddeven"></a></h2>
 <p>One frequent request is that static content be different between recto pages (right-side or odd-numbered pages typically) and verso pages(left-side or even-numbered pages typically). For example, you may wish to place the page number on the "outer" side of each page. There are examples in the FO distribution and in the <a href="http://www.dpawson.co.uk/xsl/sect3/index.html">XSL FAQ FO section</a> .</p>
 <p>First, define a page master with alternating pages masters for odd and even pages. Then specify appropriate regions in these page masters, giving them different names. Use these names to put different static content in these regions. Here is a self-contained demonstration:
 &lt;?xml version="1.0"?&gt;
@@ -463,7 +463,7 @@ If your table is more complicated, or if
     </fo:flow>
   </fo:page-sequence>
 </fo:root></p>
-<h2 id="fo-first-page">Making the First Page Special</h2>
+<h2 id="making-the-first-page-special-wzxhzdk123wzxhzdk124">Making the First Page Special # <a id="#fo-first-page"></a></h2>
 <p>To get a special header on the first page, one possibility is to insert it into the flow instead of the static content. Alternatively, use a page master referring to different page masters for the first page and the rest. Here is a code sample:
 &lt;?xml version="1.0"?&gt;
 <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
@@ -505,7 +505,7 @@ If your table is more complicated, or if
     </fo:flow>
   </fo:page-sequence>
 </fo:root></p>
-<h2 id="fo-blank-pages">Blank Pages</h2>
+<h2 id="blank-pages-wzxhzdk158wzxhzdk159">Blank Pages # <a id="#fo-blank-pages"></a></h2>
 <p>Sometimes it is desirable to insert blank pages within your output, starting, for example, a new chapter on an odd page or an even page. A blank page can be forced by using <code>break-before="page-even"</code> or similar properties, or by a force-page-count="end-on-odd" on a page sequence.</p>
 <p>To write "This page is intentionally left blank" (or something similar) on an intentionally blank page, first define a conditional page master with a page master specific for blank pages. This allows you to specify static content for blank pages (by definition, a page is blank if no content from a flow is rendered on the page). Omit your normal headers and footers, and use (for example) an extended header to print the "..left blank" statement:
 &lt;?xml version="1.0"?&gt;
@@ -547,9 +547,9 @@ If your table is more complicated, or if
     </fo:flow>
   </fo:page-sequence>
 </fo:root></p>
-<h2 id="fo-preformat">Preformatting Content</h2>
+<h2 id="preformatting-content-wzxhzdk191wzxhzdk192">Preformatting Content # <a id="#fo-preformat"></a></h2>
 <p>Sometimes it is desirable to retain linebreaks and hard spaces, and to get preformatted text to pass through without being changed. The XSL-FO specification provides some properties for this: <a href="http://www.w3.org/TR/xsl11/#white-space-collapse">white-space-collapse</a> and <a href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice7.html#white-space-collapse">linefeed-treatment</a> . In FOP, use white-space-collapse="false" on an enclosing block.</p>
-<h2 id="fo-total-pages">Total Document Pages</h2>
+<h2 id="total-document-pages-wzxhzdk193wzxhzdk194">Total Document Pages # <a id="#fo-total-pages"></a></h2>
 <p>It is frequently desirable to know the total number of pages in a document and to use that number within the document. For example, you might wish to show the page number on the first page as being "page 1 of 12".</p>
 <p>To accomplish this in <strong>XSL 1.0</strong> , place an empty block with an id at the end of the flow:
 <fo:flow ...>
@@ -614,10 +614,10 @@ import javax.xml.transform.stream.</em>;
 }
 Declare and use the parameter "page-count" in your XSLT.
 <warning>It is possible to run into a convergence problem with this solution. Replacing the "#" placeholder in the first run with the actual page count in the second run, may change the total number of pages in the document.</warning></p>
-<h2 id="fo-region-align">Aligning Regions</h2>
+<h2 id="aligning-regions-wzxhzdk204wzxhzdk205">Aligning Regions # <a id="#fo-region-align"></a></h2>
 <p>Although it may seem counterintuitive, the regions on a page may overlap. Defining a certain body region does not automatically constrain other regions. Instead, this has to be done explicitly. Sometimes for creative reasons it may be desirable to have the regions overlap. Otherwise, you will want to set them up so that the header does not overlap body content or the body extend into the footer.</p>
 <p>Assuming you wish to keep the regions separate, if you have a header region with an extent of 20mm, you should define a margin for the body region of at least 20mm too. Otherwise the header content may overwrite some stuff in the body region. This applies similarly to the extent of the after region and the bottom margin of the body region.</p>
-<h2 id="fo-lines">Drawing Lines</h2>
+<h2 id="drawing-lines-wzxhzdk206wzxhzdk207">Drawing Lines # <a id="#fo-lines"></a></h2>
 <p>It is frequently desirable to draw lines in a document, as separators, side bars or folding marks. There are several possibilities:</p>
 <ul>
 <li>
@@ -630,10 +630,10 @@ Declare and use the parameter "page-coun
 <p>Insert a graphic. GIF, PNG SVG, whatever.</p>
 </li>
 </ul>
-<h2 id="fo-validate">Validating XSL-FO</h2>
+<h2 id="validating-xsl-fo-wzxhzdk208wzxhzdk209">Validating XSL-FO # <a id="#fo-validate"></a></h2>
 <p><a href="http://www.renderx.com">RenderX</a> has provided an <a href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for FO Documents</a> , which may be helpful in validating general FO issues.</p>
 <p>FOP also maintains an <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop.xsd?view=co">Unofficial FOP Schema</a> in the FOP Subversion Repository. This document can be used either to validate against the FO standard, or against the actual FOP implementation. See the notes near the beginning of the document for instructions on how to use it.</p>
-<h2 id="landscape">Producing landscape pages</h2>
+<h2 id="producing-landscape-pages-wzxhzdk210wzxhzdk211">Producing landscape pages # <a id="#landscape"></a></h2>
 <p>Pages in landscape format can easily be produced by exchanging the page-height and page-width values of a simple-page-master element.
 <fo:layout-master-set>
   <fo:simple-page-master master-name="A4-portrait" page-height="29.7cm" page-width="21cm" [..]>
@@ -643,7 +643,7 @@ Declare and use the parameter "page-coun
     <fo:region-body/>
   </fo:simple-page-master>
 </fo:layout-master-set></p>
-<h2 id="external-resources">External Resources</h2>
+<h2 id="external-resources-wzxhzdk220wzxhzdk221">External Resources # <a id="#external-resources"></a></h2>
 <p>Resources needed by an XSL-FO file that are external to it (graphics, for example), are defined in the XSL-FO standard as being of type "uri-specification". This is defined in the standard at<jump href="http://www.w3.org/TR/xsl11/#datatype">Section 5.11 Property Datatypes</jump>, which includes a link to the URI standard itself. Refer to the XSL-FO and URI standards themselves for more detailed instructions.</p>
 <p>URIs may be either absolute or relative to a base URI. (See <a href="1.0/configuration.html">FOP: Configuration</a> for information on setting the base URI for a FOP session). Here is an example referencing an external-graphic that is relative to the base URI:
 <fo:external-graphic src="url('images/logo.jpg')"/>

Modified: websites/staging/xmlgraphics/trunk/content/fop/gethelp.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/gethelp.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/gethelp.html Tue Oct 23 15:05:41 2012
@@ -332,27 +332,27 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><subtitle>Checklist for Finding Appropriate Resources</subtitle><version>$Revision: 1298724 $</version></p>
 <p>The Apache&trade; FOP developer community is eager to help you maximize the usefulness of FOP. However, to make wise use of its limited resources, support must be primarily self-service. Go through the following checklist sequentially to determine what kind of help you need, and where to get it:</p>
-<h1 id="underlying">Understand Underlying Technologies</h1>
+<h1 id="understand-underlying-technologies-wzxhzdk5wzxhzdk6">Understand Underlying Technologies  <a id="#underlying"></a></h1>
 <p>If you have a questions about XML, XSLT, or XSL-FO that are not directly related to FOP, please consult resources that are appropriate for those questions. FOP is an implementation of these technologies, and when you use FOP, there is a presumption that you have a working understanding of them. We have included several useful links on our <a href="resources.html">Resources</a> page that may help you get started.</p>
-<h1 id="limitations">Understand FOP's Limitations</h1>
+<h1 id="understand-fops-limitations-wzxhzdk7wzxhzdk8">Understand FOP's Limitations  <a id="#limitations"></a></h1>
 <p>FOP is a work in progress, and has some limitations.</p>
 <p>FOP does not yet fully comply with the W3C XSL-FO standard. The developers track which standard requirements have been implemented, and have documented these capabilities on the <a href="compliance.html">Compliance</a> page. FOP has other limitations regarding specific output formats, graphic formats, etc. These limitations are noted in appropriate places in the documentation. If these documents appear to be in error, continue down this checklist so that either the document or the software can be corrected. Otherwise, please do not submit mailing list questions or bug reports regarding features documented in the standard, or documented as limitations in other parts of the documentation.</p>
 <p>Please especially do not submit questions asking when a particular feature will be implemented. There are too many unknowns to make even a reasonable estimate. Every time a developer stops to answer such a question, the answer will inevitably be "I don't know", but the time taken to respond is time spent away from development. The only sure way to get a feature implemented is to <a href="#how-to-help">pitch in and help</a> .</p>
-<h1 id="doc">Read the Documentation</h1>
+<h1 id="read-the-documentation-wzxhzdk9wzxhzdk10">Read the Documentation  <a id="#doc"></a></h1>
 <p>Review the documentation pages on this site. There is information about how to run FOP, how to embed it, how to add custom fonts etc.</p>
-<h1 id="faq">Check the FAQs</h1>
+<h1 id="check-the-faqs-wzxhzdk11wzxhzdk12">Check the FAQs  <a id="#faq"></a></h1>
 <p>Consult the <a href="faq.html">Frequently Asked Questions (FAQ)</a> to see if your question has already been answered.</p>
-<h1 id="user-archive">Review FOP User Mailing List Archive</h1>
+<h1 id="review-fop-user-mailing-list-archive-wzxhzdk13wzxhzdk14">Review FOP User Mailing List Archive  <a id="#user-archive"></a></h1>
 <p>It is possible that your question has already been answered but has not yet found its way into the FAQ. Links to the FOP User mailing list archives are on the <a href="maillist.html#fop-user">Mailing List</a> page.</p>
-<h1 id="existing-issue">Look for an Existing Issue Report</h1>
+<h1 id="look-for-an-existing-issue-report-wzxhzdk15wzxhzdk16">Look for an Existing Issue Report  <a id="#existing-issue"></a></h1>
 <p>See <a href="bugs.html#issues_existing">Reported Issues</a> for instructions on how to use the list of open issues. Review these open issues to see if any match your concerns. If so, please do not post a mailing list question or report another issue, as these will only slow the development team down.</p>
-<h1 id="user-mailing-list">Submit Question to FOP User Mailing List</h1>
+<h1 id="submit-question-to-fop-user-mailing-list-wzxhzdk17wzxhzdk18">Submit Question to FOP User Mailing List  <a id="#user-mailing-list"></a></h1>
 <p>See <a href="maillist.html#fop-user">FOP User Mailing List</a> for details.
 Please don't write to any developer directly. 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>
-<h1 id="enter-issue">Enter an Issue Report</h1>
+<h1 id="enter-an-issue-report-wzxhzdk19wzxhzdk20">Enter an Issue Report  <a id="#enter-issue"></a></h1>
 <p>If, and only if, you have followed all of the above steps, and believe that there is a bug or needed feature that you would like to report, please enter an issue in Bugzilla. Never use Bugzilla to post questions, only to enter issues that have already been asked on the user mailing list.</p>
 <p>See <a href="bugs.html#issues_new">Reporting New Issues</a> for detailed instructions on how to enter an issue.</p>
-<h1 id="how-to-help">Find Out How You Can Help</h1>
+<h1 id="find-out-how-you-can-help-wzxhzdk21wzxhzdk22">Find Out How You Can Help  <a id="#how-to-help"></a></h1>
 <p>As stated above, the FOP development team is a limited resource. Most make their livings doing things other than writing and supporting FOP. Perhaps you need a feature from the XSL-FO standard to be implemented right away, or a bug fixed, or a new output format, or .... If so, there are several ways that you can help:</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/index.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/index.html Tue Oct 23 15:05:41 2012
@@ -331,18 +331,18 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="intro">Introduction</h1>
+<h1 id="introduction-wzxhzdk2wzxhzdk3">Introduction  <a id="#intro"></a></h1>
 <p>Apache&trade; FOP (Formatting Objects Processor) is a print formatter driven by XSL formatting objects (XSL-FO) and an output independent formatter. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. <a href="1.0/output.html">Output formats</a> currently supported include PDF, PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a lesser extent, RTF and TXT. The primary output target is PDF.</p>
 <p>The Apache&trade; FOP project is part of the <a href="http://www.apache.org">Apache&trade;</a> Software Foundation, which is a wider community of users and developers of open source projects.
 <figure alt="Render Diagram" height="260" src="images/document.jpg" width="480"></figure>
 A stable release of the latest version of FOP ( <a href="1.0/">1.0</a> ) is available. It's the third stable release after the large redesign effort and implements a large subset of the <a href="http://www.w3.org/TR/xsl11/">XSL-FO Version 1.1 W3C Recommendation</a> .</p>
 <p>Support for each of the standard's objects and properties is detailed in <a href="compliance.html">FOP Compliance</a> . <a href="download.html">Download</a> options include a precompiled version, source code, and many example files to get you started. <a href="resources.html">Resources</a> include links to XSL-FO introductions and many other useful references. A checklist for <a href="gethelp.html">Getting Help</a> will guide you toward maximizing the usefulness of FOP.</p>
 <p>FOP is proud to be part of <a href="http://xmlgraphics.apache.org">Apache's XML Graphics project</a> .</p>
-<h1 id="demo">Demonstration</h1>
+<h1 id="demonstration-wzxhzdk9wzxhzdk10">Demonstration  <a id="#demo"></a></h1>
 <p><figure alt="Formatting Diagram" height="260" src="images/layout.jpg" width="480"></figure>
 This image is a demonstration of a real two page document. The XML data on the left is formatted into the two pages on the right. The document contains static areas that appear on every page, an external graphic, a footnote on the first page, and a table that goes across both pages.</p>
 <p>FOP uses the standard XSL-FO file format as input, lays the content out into pages, then renders it to the requested output. One great advantage of using XSL-FO as input is that XSL-FO is itself an XML file, which means that it can be conveniently created from a variety of sources. The most common method is to convert semantic XML to XSL-FO, using an XSLT transformation.</p>
-<h1 id="objectives">FOP Objectives</h1>
+<h1 id="fop-objectives-wzxhzdk13wzxhzdk14">FOP Objectives  <a id="#objectives"></a></h1>
 <p>The goals of the Apache FOP project are to deliver an XSL-FO to PDF formatter that is compliant to at least the Basic conformance level described in the W3C Recommendation from 05 December 2006, and that complies with the November 2001 Portable Document Format Specification (Version 1.4) from Adobe Systems.</p>
 <p>Conformance to the XML 1.0 and 1.1 Recommendations, XSLT 1.0 and 2.0 Recommendations and the XML Namespaces Recommendation is understood. Other relevant documents, such as the XPath and XLink Working Drafts, are referenced as necessary. The FOP Project will attempt to use the latest version of evolving specifications.
 The PDF files on this site are created using Apache FOP.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/knownissues.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/knownissues.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/knownissues.html Tue Oct 23 15:05:41 2012
@@ -331,7 +331,7 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="known-issues-knownissues">Known issues # {#Known+issues}</h1>
+<h1 id="known-issues-wzxhzdk2wzxhzdk3">Known issues  <a id="#Known+issues"></a></h1>
 <p>This page lists currently known issues in the Apache&trade; FOP codebase. Please note that this list is generated from data in FOP's code repository (Trunk) and may not exactly represent the list of issues in the latest release.</p>
 <p>For additional information on known issues in Apache FOP, please have a look at the following pages, too:</p>
 <ul>
@@ -343,11 +343,11 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>Apache&trade; FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.</p>
-<h2 id="fo-tree-fotree">FO Tree ## {#FO+Tree}</h2>
+<h2 id="fo-tree-wzxhzdk6wzxhzdk7">FO Tree # <a id="#FO+Tree"></a></h2>
 <p>This section lists currently disabled test cases in the test suite for the FO tree tests. The data for this section comes from <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/fotree/disabled-testcases.xml">test/fotree/disabled-testcases.xml</a> .</p>
 <p><strong>demo-test-failure.fo</strong> (demo test failure):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </p>
 <p><strong>from-table-column_marker.fo</strong> (Markers and core function evaluation):<br></br>The code currently evaluates this function according to the column in which the marker appears in the source document, rather than the column it is retrieved in.</p>
-<h2 id="layout-engine-layoutengine">Layout Engine ## {#Layout+Engine}</h2>
+<h2 id="layout-engine-wzxhzdk12wzxhzdk13">Layout Engine # <a id="#Layout+Engine"></a></h2>
 <p>This section lists currently disabled test cases in the test suite for the layout engine tests. The data for this section comes from <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/layoutengine/disabled-testcases.xml">test/layoutengine/disabled-testcases.xml</a> .</p>
 <p><strong>block-container_space-before_space-after_3.xml</strong> (Auto-height block-containers produce fences):<br></br>Block-containers with no height currently don't create a fence for spaces as they should (they behave like a normal block).</p>
 <p><strong>block_font-stretch.xml</strong> (font-stretch NYI):<br></br>Font-stretch is not implemented, yet.</p>
@@ -383,7 +383,7 @@ $(document).ready(function () {
 <p><strong>keep_within-page_multi-column_overflow.xml</strong> (Page-keep not respected in multi-column layout):<br></br>The block should cause overflow in the last column on the page, rather than be broken.</p>
 <p><strong>block-container_reference-orientation_bug36391.xml</strong> (Block Container Reference Orientation Bug):<br></br>An assert is failing</p>
 <p><strong>simple-page-master_writing-mode_rl_region-body_writing-mode-lr.xml</strong> (Writing mode problems):<br></br>Test erroneously depends upon incorrect implementation of writing-mode trait derivation on fo:region-*.</p>
-<h2 id="other-known-issues-otherknownissues">Other known issues ## {#Other+known+issues}</h2>
+<h2 id="other-known-issues-wzxhzdk84wzxhzdk85">Other known issues # <a id="#Other+known+issues"></a></h2>
 <p>This section lists other known issues.</p>
 <ul>
 <li>

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 Tue Oct 23 15:05:41 2012
@@ -331,7 +331,7 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="License">License</h1>
+<h1 id="license-wzxhzdk2wzxhzdk3">License  <a id="#License"></a></h1>
 <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<jump href="http://www.apache.org/licenses/">Apache Licenses page</jump>.</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 Tue Oct 23 15:05:41 2012
@@ -331,7 +331,7 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="general">General Information</h1>
+<h1 id="general-information-wzxhzdk2wzxhzdk3">General Information  <a id="#general"></a></h1>
 <p>Before posting questions to any list:</p>
 <ul>
 <li>
@@ -348,9 +348,9 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>For help in understanding email acronyms, see the<jump href="http://www.lingo2word.com/lists/acronym_listA.html">Lingo2Word Acronym List</jump>, or the<jump href="http://www.keno.org/web_design/acronyms.htm">Keno Internet Services Internet Glossary</jump>.</p>
-<h1 id="fop-user">Apache&trade; FOP Users Mailing List</h1>
+<h1 id="apachewzxhzdk10-fop-users-mailing-list-wzxhzdk8wzxhzdk9">Apache&trade; FOP Users Mailing List  <a id="#fop-user"></a></h1>
 <p>Use this forum to discuss topics of interest to FOP users.</p>
-<h2 id="fop-user-archive">Archives</h2>
+<h2 id="archives-wzxhzdk11wzxhzdk12">Archives # <a id="#fop-user-archive"></a></h2>
 <p>To review the archives, you have several options:</p>
 <ul>
 <li>
@@ -376,7 +376,7 @@ $(document).ready(function () {
 If you don't like mailing lists and prefer a forum-like system, have a look at<jump href="http://dir.gmane.org/gmane.text.xml.fop.user">GMANE</jump>or<jump href="http://www.nabble.com/FOP---Users-f353.html">Nabble</jump>. They allow you to post to the mailing list without having to subscribe.</p>
 </li>
 </ul>
-<h2 id="fop-user-subscribe">Subscription Information</h2>
+<h2 id="subscription-information-wzxhzdk13wzxhzdk14">Subscription Information # <a id="#fop-user-subscribe"></a></h2>
 <ul>
 <li>
 <p>See <a href="http://xmlgraphics.apache.org/mail.html">Apache XML Graphics Mailing Lists</a> for detailed subscription information.</p>
@@ -395,7 +395,7 @@ If you don't like mailing lists and pref
 You can find the developer mailing list on the <a href="dev/index.html#mail-fop-dev">Development pages</a> .</p>
 </li>
 </ul>
-<h2 id="fop-user-policy">Submitting a Question</h2>
+<h2 id="submitting-a-question-wzxhzdk15wzxhzdk16">Submitting a Question # <a id="#fop-user-policy"></a></h2>
 <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>
@@ -445,7 +445,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>
-<h1 id="w3c-xslfo">XSL-FO Mailing List (at W3C)</h1>
+<h1 id="xsl-fo-mailing-list-at-w3c-wzxhzdk17wzxhzdk18">XSL-FO Mailing List (at W3C)  <a id="#w3c-xslfo"></a></h1>
 <p>Use this forum to ask general XSL-FO questions.</p>
 <ul>
 <li>
@@ -458,7 +458,7 @@ You can find the developer mailing list 
 <p>Subscription administration information can be found at<jump href="http://www.w3.org/Mail/Request">W3C Mailing List Administrativia</jump>. 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>
-<h1 id="yahoogroups-xslfo">XSL-FO Mailing List (at YahooGroups)</h1>
+<h1 id="xsl-fo-mailing-list-at-yahoogroups-wzxhzdk19wzxhzdk20">XSL-FO Mailing List (at YahooGroups)  <a id="#yahoogroups-xslfo"></a></h1>
 <p>Use this forum to ask general XSL-FO questions.</p>
 <ul>
 <li>
@@ -468,7 +468,7 @@ You can find the developer mailing list 
 <p>The home page for this groups is<jump href="http://groups.yahoo.com/group/XSL-FO">XSL-FO - discussion of XSL Formatting Objects</jump>.</p>
 </li>
 </ul>
-<h1 id="xslt-mulberry">XSLT List (Mulberry Tech)</h1>
+<h1 id="xslt-list-mulberry-tech-wzxhzdk21wzxhzdk22">XSLT List (Mulberry Tech)  <a id="#xslt-mulberry"></a></h1>
 <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 Tue Oct 23 15:05:41 2012
@@ -332,100 +332,100 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
 <p>RSS Feed: <a href="subproject-news-feed.rss"></a> </p>
-<h1 id="news-2012-02-24">24 Feb 2012: New committer</h1>
+<h1 id="24-feb-2012-new-committer-wzxhzdk2wzxhzdk3">24 Feb 2012: New committer  <a id="#news-2012-02-24"></a></h1>
 <p><item date="2012-02-24" title="New committer">
 Welcome Glenn Adams!
 </item></p>
-<h1 id="news-2011-11-17">17 Nov 2011: New committer</h1>
+<h1 id="17-nov-2011-new-committer-wzxhzdk6wzxhzdk7">17 Nov 2011: New committer  <a id="#news-2011-11-17"></a></h1>
 <p><item date="2011-11-17" title="New committer">
 Welcome Mehdi Houshmand!
 </item></p>
-<h1 id="news-2010-07-21">21 Jul 2010: Apache&trade; FOP 1.0 Released</h1>
+<h1 id="21-jul-2010-apachewzxhzdk12-fop-10-released-wzxhzdk10wzxhzdk11">21 Jul 2010: Apache&trade; FOP 1.0 Released  <a id="#news-2010-07-21"></a></h1>
 <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>
-<h1 id="news-2009-12-14">14 Dec 2009: New committer</h1>
+<h1 id="14-dec-2009-new-committer-wzxhzdk16wzxhzdk17">14 Dec 2009: New committer  <a id="#news-2009-12-14"></a></h1>
 <p><item date="2009-12-14" title="New committer">
 Welcome Pascal Sancho!
 </item></p>
-<h1 id="news-2008-08-05">5 Aug 2008: Apache&trade; FOP 0.95 Released</h1>
+<h1 id="5-aug-2008-apachewzxhzdk22-fop-095-released-wzxhzdk20wzxhzdk21">5 Aug 2008: Apache&trade; FOP 0.95 Released  <a id="#news-2008-08-05"></a></h1>
 <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>
-<h1 id="news-2008-03-16">16 Mar 2008: Apache&trade; FOP 0.95beta Released</h1>
+<h1 id="16-mar-2008-apachewzxhzdk28-fop-095beta-released-wzxhzdk26wzxhzdk27">16 Mar 2008: Apache&trade; FOP 0.95beta Released  <a id="#news-2008-03-16"></a></h1>
 <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>
-<h1 id="news-2007-10-30">30 Oct 2007: New committer</h1>
+<h1 id="30-oct-2007-new-committer-wzxhzdk32wzxhzdk33">30 Oct 2007: New committer  <a id="#news-2007-10-30"></a></h1>
 <p><item date="2007-10-30" title="New committer">
 Welcome Max Berger!
 </item></p>
-<h1 id="news-2007-10-15">15 Oct 2007: New Committer</h1>
+<h1 id="15-oct-2007-new-committer-wzxhzdk36wzxhzdk37">15 Oct 2007: New Committer  <a id="#news-2007-10-15"></a></h1>
 <p><item date="2007-10-15" title="New Committer">
 Welcome Adrian Cumiskey!
 </item></p>
-<h1 id="news-2007-08-24">24 Aug 2007: Apache&trade; FOP 0.94 Released</h1>
+<h1 id="24-aug-2007-apachewzxhzdk42-fop-094-released-wzxhzdk40wzxhzdk41">24 Aug 2007: Apache&trade; FOP 0.94 Released  <a id="#news-2007-08-24"></a></h1>
 <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>
-<h1 id="news-2007-01-26">26 Jan 2007: New Committer</h1>
+<h1 id="26-jan-2007-new-committer-wzxhzdk46wzxhzdk47">26 Jan 2007: New Committer  <a id="#news-2007-01-26"></a></h1>
 <p><item date="2007-01-26" title="New Committer">
 Welcome Jay Bryant!
 </item></p>
-<h1 id="news-2007-01-09">9 Jan 2007: Apache&trade; FOP 0.93 released</h1>
+<h1 id="9-jan-2007-apachewzxhzdk52-fop-093-released-wzxhzdk50wzxhzdk51">9 Jan 2007: Apache&trade; FOP 0.93 released  <a id="#news-2007-01-09"></a></h1>
 <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>
-<h1 id="news-2006-10-16">16 Oct 2006: New Committer</h1>
+<h1 id="16-oct-2006-new-committer-wzxhzdk56wzxhzdk57">16 Oct 2006: New Committer  <a id="#news-2006-10-16"></a></h1>
 <p><item date="2006-10-16" title="New Committer">
 Welcome Vincent Hennebert!
 </item></p>
-<h1 id="news-2006-04-18">18 Apr 2006: Apache&trade; FOP 0.92 beta released</h1>
+<h1 id="18-apr-2006-apachewzxhzdk62-fop-092-beta-released-wzxhzdk60wzxhzdk61">18 Apr 2006: Apache&trade; FOP 0.92 beta released  <a id="#news-2006-04-18"></a></h1>
 <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>
-<h1 id="news-2005-12-23">23 Dec 2005: Apache&trade; FOP 0.91 beta released</h1>
+<h1 id="23-dec-2005-apachewzxhzdk67-fop-091-beta-released-wzxhzdk65wzxhzdk66">23 Dec 2005: Apache&trade; FOP 0.91 beta released  <a id="#news-2005-12-23"></a></h1>
 <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>
-<h1 id="news-2005-11-22">22 Nov 2005: Apache&trade; FOP 0.90 alpha 1 released</h1>
+<h1 id="22-nov-2005-apachewzxhzdk72-fop-090-alpha-1-released-wzxhzdk70wzxhzdk71">22 Nov 2005: Apache&trade; FOP 0.90 alpha 1 released  <a id="#news-2005-11-22"></a></h1>
 <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>
-<h1 id="news-2005-09-08">8 Sep 2005: New Committer</h1>
+<h1 id="8-sep-2005-new-committer-wzxhzdk76wzxhzdk77">8 Sep 2005: New Committer  <a id="#news-2005-09-08"></a></h1>
 <p><item date="2005-09-08" title="New Committer">
 Welcome Manuel Mall!
 </item></p>
-<h1 id="news-2004-10-20">20 Oct 2004: Creation of the Apache&trade; XML Graphics project</h1>
+<h1 id="20-oct-2004-creation-of-the-apachewzxhzdk82-xml-graphics-project-wzxhzdk80wzxhzdk81">20 Oct 2004: Creation of the Apache&trade; XML Graphics project  <a id="#news-2004-10-20"></a></h1>
 <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>
-<h1 id="news-2004-10-08">8 Oct 2004: New Committer</h1>
+<h1 id="8-oct-2004-new-committer-wzxhzdk87wzxhzdk88">8 Oct 2004: New Committer  <a id="#news-2004-10-08"></a></h1>
 <p><item date="2004-10-08" title="New Committer">
 Welcome Luca Furini!
 </item></p>
-<h1 id="news-2004-04-24">24 Apr 2004: New Committer</h1>
+<h1 id="24-apr-2004-new-committer-wzxhzdk91wzxhzdk92">24 Apr 2004: New Committer  <a id="#news-2004-04-24"></a></h1>
 <p><item date="2004-04-24" title="New Committer">
 Welcome Simon Pepping!
 </item></p>
-<h1 id="news-2004-03-07">7 Mar 2004: New Committer</h1>
+<h1 id="7-mar-2004-new-committer-wzxhzdk95wzxhzdk96">7 Mar 2004: New Committer  <a id="#news-2004-03-07"></a></h1>
 <p><item date="2004-03-07" title="New Committer">
 Welcome Web Maestro Clay Leeds!
 </item></p>
-<h1 id="news-2004-01-10">10 Jan 2004: New Committers</h1>
+<h1 id="10-jan-2004-new-committers-wzxhzdk99wzxhzdk100">10 Jan 2004: New Committers  <a id="#news-2004-01-10"></a></h1>
 <p><item date="2004-01-10" title="New Committers">
 Welcome Chris Bowditch and Andreas Delmelle!
 </item></p>
-<h1 id="news-2004-01-04">4 Jan 2004: New Committer</h1>
+<h1 id="4-jan-2004-new-committer-wzxhzdk103wzxhzdk104">4 Jan 2004: New Committer  <a id="#news-2004-01-04"></a></h1>
 <p><item date="2004-01-04" title="New Committer">
 Welcome Finn Bock!
 </item></p>
-<h1 id="news-2003-11-29">29 Nov 2003: New Committer</h1>
+<h1 id="29-nov-2003-new-committer-wzxhzdk107wzxhzdk108">29 Nov 2003: New Committer  <a id="#news-2003-11-29"></a></h1>
 <p><item date="2003-11-29" title="New Committer">
 Welcome Peter Herweg!
 </item></p>
-<h1 id="news-2003-07-18">18 Jul 2003: Apache&trade; FOP 0.20.5 released</h1>
+<h1 id="18-jul-2003-apachewzxhzdk113-fop-0205-released-wzxhzdk111wzxhzdk112">18 Jul 2003: Apache&trade; FOP 0.20.5 released  <a id="#news-2003-07-18"></a></h1>
 <p><item date="2003-07-18" title="Apache&trade; FOP 0.20.5 released">
 Changes since 0.20.4 include:</p>
 <ul>
@@ -477,43 +477,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>
-<h1 id="news-2003-06-29">29 Jun 2003: New Committer</h1>
+<h1 id="29-jun-2003-new-committer-wzxhzdk116wzxhzdk117">29 Jun 2003: New Committer  <a id="#news-2003-06-29"></a></h1>
 <p><item date="2003-06-29" title="New Committer">
 Welcome Glen Mazza!
 </item></p>
-<h1 id="news-2003-05-23">23 May 2003: Apache&trade; FOP 0.20.5 Release Candidate 3 available</h1>
+<h1 id="23-may-2003-apachewzxhzdk122-fop-0205-release-candidate-3-available-wzxhzdk120wzxhzdk121">23 May 2003: Apache&trade; FOP 0.20.5 Release Candidate 3 available  <a id="#news-2003-05-23"></a></h1>
 <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>
-<h1 id="news-2003-02-18">18 Feb 2003: Apache&trade; FOP 0.20.5 Release Candidate 2 available</h1>
+<h1 id="18-feb-2003-apachewzxhzdk127-fop-0205-release-candidate-2-available-wzxhzdk125wzxhzdk126">18 Feb 2003: Apache&trade; FOP 0.20.5 Release Candidate 2 available  <a id="#news-2003-02-18"></a></h1>
 <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>
-<h1 id="news-2003-02-02">2 Feb 2003: New XML PMC</h1>
+<h1 id="2-feb-2003-new-xml-pmc-wzxhzdk130wzxhzdk131">2 Feb 2003: New XML PMC  <a id="#news-2003-02-02"></a></h1>
 <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>
-<h1 id="news-2003-01-28">28 Jan 2003: FOP logo contest</h1>
+<h1 id="28-jan-2003-fop-logo-contest-wzxhzdk134wzxhzdk135">28 Jan 2003: FOP logo contest  <a id="#news-2003-01-28"></a></h1>
 <p><item date="2003-01-28" title="FOP logo contest">
 We are looking for a new logo. FOP logo contest is started!
 </item></p>
-<h1 id="news-2002-12-23">23 Dec 2002: Official FOP Wiki</h1>
+<h1 id="23-dec-2002-official-fop-wiki-wzxhzdk138wzxhzdk139">23 Dec 2002: Official FOP Wiki  <a id="#news-2002-12-23"></a></h1>
 <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>
-<h1 id="news-2002-12-10">10 Dec 2002: FOP 0.20.5 Release Candidate available</h1>
+<h1 id="10-dec-2002-fop-0205-release-candidate-available-wzxhzdk142wzxhzdk143">10 Dec 2002: FOP 0.20.5 Release Candidate available  <a id="#news-2002-12-10"></a></h1>
 <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>
-<h1 id="news-2002-11-23">23 Nov 2002: EXLSFO project has been created</h1>
+<h1 id="23-nov-2002-exlsfo-project-has-been-created-wzxhzdk146wzxhzdk147">23 Nov 2002: EXLSFO project has been created  <a id="#news-2002-11-23"></a></h1>
 <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>
-<h1 id="news-2002-11-22">22 Nov 2002: New Committer</h1>
+<h1 id="22-nov-2002-new-committer-wzxhzdk150wzxhzdk151">22 Nov 2002: New Committer  <a id="#news-2002-11-22"></a></h1>
 <p><item date="2002-11-22" title="New Committer">
 Welcome Victor Mote!
 </item></p>
-<h1 id="news-2002-11-09">9 Nov 2002: New Committer</h1>
+<h1 id="9-nov-2002-new-committer-wzxhzdk154wzxhzdk155">9 Nov 2002: New Committer  <a id="#news-2002-11-09"></a></h1>
 <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 Tue Oct 23 15:05:41 2012
@@ -331,7 +331,7 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><subtitle>Everything you need to start using and appreciating Apache&trade; FOP quickly.</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="essentials">Apache&trade; FOP Essentials</h1>
+<h1 id="apachewzxhzdk7-fop-essentials-wzxhzdk5wzxhzdk6">Apache&trade; FOP Essentials  <a id="#essentials"></a></h1>
 <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>
@@ -372,7 +372,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>
-<h1 id="hello-world">Hello World with FOP</h1>
+<h1 id="hello-world-with-fop-wzxhzdk8wzxhzdk9">Hello World with FOP  <a id="#hello-world"></a></h1>
 <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 Tue Oct 23 15:05:41 2012
@@ -331,8 +331,8 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><subtitle>Resources useful for developing and using Apache&trade; FOP</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="specs">Specifications</h1>
-<h2 id="specs-xslfo">XSL-FO</h2>
+<h1 id="specifications-wzxhzdk5wzxhzdk6">Specifications  <a id="#specs"></a></h1>
+<h2 id="xsl-fo-wzxhzdk7wzxhzdk8">XSL-FO # <a id="#specs-xslfo"></a></h2>
 <ul>
 <li>
 <p><jump href="http://www.w3.org/TR/xsl11/">XSL-FO Recommendation (05 December 2006)</jump></p>
@@ -341,7 +341,7 @@ $(document).ready(function () {
 <p><jump href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for the XSL-FO Recommendation</jump>provided by N. Grigoriev from RenderX.</p>
 </li>
 </ul>
-<h2 id="specs-xslt">XSLT</h2>
+<h2 id="xslt-wzxhzdk9wzxhzdk10">XSLT # <a id="#specs-xslt"></a></h2>
 <ul>
 <li>
 <p><jump href="http://www.w3.org/TR/xslt">XSLT 1.0 Recommendation</jump></p>
@@ -350,7 +350,7 @@ $(document).ready(function () {
 <p><jump href="http://www.w3.org/TR/xslt20">XSLT 2.0 Recommendation</jump></p>
 </li>
 </ul>
-<h2 id="specs-xml">XML</h2>
+<h2 id="xml-wzxhzdk11wzxhzdk12">XML # <a id="#specs-xml"></a></h2>
 <ul>
 <li>
 <p><jump href="http://www.w3.org/TR/xml">XML 1.0</jump></p>
@@ -377,7 +377,7 @@ $(document).ready(function () {
 <p><jump href="http://www.w3.org/TR/xml-names11/">Namespaces in XML 1.1</jump></p>
 </li>
 </ul>
-<h2 id="specs-java">Java</h2>
+<h2 id="java-wzxhzdk13wzxhzdk14">Java # <a id="#specs-java"></a></h2>
 <ul>
 <li>
 <p><jump href="http://java.sun.com/j2se/1.4/docs/api/index.html">Java 2 Platform, Standard Edition, v 1.4.2 API Specification</jump></p>
@@ -389,20 +389,20 @@ $(document).ready(function () {
 <p><jump href="http://java.sun.com/javase/6/docs/api/index.html">Java Platform, Standard Edition 6 API Specification</jump></p>
 </li>
 </ul>
-<h2 id="specs-pdf">PDF</h2>
+<h2 id="pdf-wzxhzdk15wzxhzdk16">PDF # <a id="#specs-pdf"></a></h2>
 <ul>
 <li><jump href="http://partners.adobe.com/asn/tech/pdf/specifications.jsp">Portable Document Format (PDF) Reference Manual</jump></li>
 </ul>
-<h2 id="specs-unicode">Unicode</h2>
+<h2 id="unicode-wzxhzdk17wzxhzdk18">Unicode # <a id="#specs-unicode"></a></h2>
 <ul>
 <li><jump href="http://www.unicode.org/reports/tr14">UTR-14 (Unicode Standard Annex #14: Line Breaking Properties)</jump></li>
 </ul>
-<h2 id="specs-other">Other</h2>
+<h2 id="other-wzxhzdk19wzxhzdk20">Other # <a id="#specs-other"></a></h2>
 <ul>
 <li><jump href="http://www.w3.org/TR/SVG/">Supported SVG Recommendation (04 September 2001)</jump></li>
 </ul>
-<h1 id="documents">Books, Tutorials, Articles</h1>
-<h2 id="documents-xslfo">XSL-FO</h2>
+<h1 id="books-tutorials-articles-wzxhzdk21wzxhzdk22">Books, Tutorials, Articles  <a id="#documents"></a></h1>
+<h2 id="xsl-fo-wzxhzdk23wzxhzdk24">XSL-FO # <a id="#documents-xslfo"></a></h2>
 <ul>
 <li>
 <p>[online book]<jump href="http://www.ibiblio.org/xml/books/bible2/chapters/ch18.html">The XML Bible</jump>, by Elliotte Rusty Harold. Chapter 18 of XSL Formatting Objects</p>
@@ -429,7 +429,7 @@ $(document).ready(function () {
 <p>[book]<jump href="http://www.cranesoftwrights.com/training/index.htm#pfux">Practical Formatting Using XSLFO</jump>, Crane Softwrights Ltd., 2003, ISBN 1-894049-11-X.</p>
 </li>
 </ul>
-<h2 id="documents-xslt">XSLT</h2>
+<h2 id="xslt-wzxhzdk25wzxhzdk26">XSLT # <a id="#documents-xslt"></a></h2>
 <ul>
 <li>
 <p>[online resource]<jump href="http://www.w3.org/Style/XSL/">Extensible Stylesheet Language Family (XSL)</jump>, W3C XSL Family page.</p>
@@ -459,7 +459,7 @@ $(document).ready(function () {
 <p>[book]<jump href="http://www.oreilly.com/catalog/javaxslt">Java and XSLT</jump>, by Eric M. Burke, O'Reilly &amp; Associates, 2001, ISBN 0-596-00143-6.</p>
 </li>
 </ul>
-<h2 id="documents-xml">XML</h2>
+<h2 id="xml-wzxhzdk27wzxhzdk28">XML # <a id="#documents-xml"></a></h2>
 <ul>
 <li>
 <p>[online book]<jump href="http://www.ibiblio.org/xml/books/bible2">The XML Bible</jump>, by Elliotte Rusty Harold. See hardcopy version below.</p>
@@ -471,11 +471,11 @@ $(document).ready(function () {
 <p>[online resource] A great number of additional XML-related books and articles can be found at the<jump href="http://xml.oreilly.com">O'Reilly XML Site</jump>.</p>
 </li>
 </ul>
-<h2 id="documents-java">Java</h2>
+<h2 id="java-wzxhzdk29wzxhzdk30">Java # <a id="#documents-java"></a></h2>
 <ul>
 <li>[online resource] A great number of Java-related books and articles can be found at the<jump href="http://java.oreilly.com">O'Reilly Java Site</jump>.</li>
 </ul>
-<h2 id="documents-pdf">PDF</h2>
+<h2 id="pdf-wzxhzdk31wzxhzdk32">PDF # <a id="#documents-pdf"></a></h2>
 <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,<jump href="http://partners.adobe.com/asn/acrobat/docs.jsp#filefmtspecs">Acrobat 5.0 SDK Documentation</jump>.</p>
@@ -487,7 +487,7 @@ $(document).ready(function () {
 <p>[online resource] A list of Acrobat and PDF developer resources can be found at Adobe Solutions Network, Acrobat Resources,<jump href="http://partners.adobe.com/asn/acrobat">Resources for Developers</jump>.</p>
 </li>
 </ul>
-<h2 id="documents-ps">PostScript</h2>
+<h2 id="postscript-wzxhzdk33wzxhzdk34">PostScript # <a id="#documents-ps"></a></h2>
 <ul>
 <li>
 <p>[online resource] A list of PostScript-related technical resources can be found at Adobe Solutions Network,<jump href="http://partners.adobe.com/asn/tech/ps/technotes.jsp">PostScript Language Technical Notes</jump></p>
@@ -496,7 +496,7 @@ $(document).ready(function () {
 <p>[online resource] Additional PostScript-related developer resources can be found at Adobe Solutions Network,<jump href="http://partners.adobe.com/asn/tech/ps/index.jsp">PostScript SDK Archive</jump>.</p>
 </li>
 </ul>
-<h1 id="mailing-lists">Mailing Lists</h1>
+<h1 id="mailing-lists-wzxhzdk35wzxhzdk36">Mailing Lists  <a id="#mailing-lists"></a></h1>
 <p>Before posting questions to any list:</p>
 <ul>
 <li>
@@ -513,7 +513,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>
-<h2 id="Apache-FOP">Apache FOP Mailing List</h2>
+<h2 id="apache-fop-mailing-list-wzxhzdk37wzxhzdk38">Apache FOP Mailing List # <a id="#Apache-FOP"></a></h2>
 <ul>
 <li>
 <p>[mailing list info]<jump href="http://xml.apache.org/fop/maillist.html">http://xml.apache.org/fop/maillist.html</jump></p>
@@ -555,7 +555,7 @@ $(document).ready(function () {
 <p>[fop-dev-unsubscribe]<jump href="mailto:fop-dev-unsubscribe@xmlgraphics.apache.org">fop-dev-unsubscribe@xmlgraphics.apache.org</jump></p>
 </li>
 </ul>
-<h2 id="XSL-FO-at-W3C">XSL-FO Mailing List (at W3C)</h2>
+<h2 id="xsl-fo-mailing-list-at-w3c-wzxhzdk39wzxhzdk40">XSL-FO Mailing List (at W3C) # <a id="#XSL-FO-at-W3C"></a></h2>
 <ul>
 <li>
 <p>[mailing list info]<jump href="http://www.w3.org/Mail/Request">http://www.w3.org/Mail/Request</jump></p>
@@ -564,16 +564,16 @@ $(document).ready(function () {
 <p>[mailing list archives]<jump href="http://lists.w3.org/Archives/Public/www-xsl-fo/">http://lists.w3.org/Archives/Public/www-xsl-fo/</jump></p>
 </li>
 </ul>
-<h2 id="XSL-FO-at-YahooGroups">XSL-FO Mailing List (at YahooGroups)</h2>
+<h2 id="xsl-fo-mailing-list-at-yahoogroups-wzxhzdk41wzxhzdk42">XSL-FO Mailing List (at YahooGroups) # <a id="#XSL-FO-at-YahooGroups"></a></h2>
 <ul>
 <li>[mailing list info &amp; archives]<jump href="http://groups.yahoo.com/group/XSL-FO">http://groups.yahoo.com/group/XSL-FO</jump></li>
 </ul>
-<h2 id="XSLT-at-Mulberry-Tech">XSLT List (Mulberry Tech)</h2>
+<h2 id="xslt-list-mulberry-tech-wzxhzdk43wzxhzdk44">XSLT List (Mulberry Tech) # <a id="#XSLT-at-Mulberry-Tech"></a></h2>
 <ul>
 <li>[mailing list info &amp; archives]<jump href="http://www.mulberrytech.com/xsl/xsl-list">http://www.mulberrytech.com/xsl/xsl-list</jump></li>
 </ul>
-<h1 id="products">Related/Useful Products</h1>
-<h2 id="products-fop-add-ons">FOP add-ons</h2>
+<h1 id="relateduseful-products-wzxhzdk45wzxhzdk46">Related/Useful Products  <a id="#products"></a></h1>
+<h2 id="fop-add-ons-wzxhzdk47wzxhzdk48">FOP add-ons # <a id="#products-fop-add-ons"></a></h2>
 <ul>
 <li>
 <p>[software] TIFFRenderer is a renderer for outputting multi-page TIFF:<jump href="http://www.tkachenko.com/fop/tiffrenderer.html">http://www.tkachenko.com/fop/tiffrenderer.html</jump>(MPL)</p>
@@ -594,7 +594,7 @@ $(document).ready(function () {
 <p>[software &amp; tools]<jump href="http://offo.sourceforge.net/">Objects For Formatting Objects</jump>hosts hyphenation patterns and (eventually) files other accessory data files &amp; scripts.</p>
 </li>
 </ul>
-<h2 id="products-pdf">PDF post-processors</h2>
+<h2 id="pdf-post-processors-wzxhzdk49wzxhzdk50">PDF post-processors # <a id="#products-pdf"></a></h2>
 <ul>
 <li>
 <p>[software]<jump href="http://pdfbox.apache.org">Apache PDFBox</jump>(Apache License V2.0)</p>
@@ -609,7 +609,7 @@ $(document).ready(function () {
 <p>[software]<jump href="http://www.accesspdf.com/pdftk/">pdftk</jump>the pdf toolkit</p>
 </li>
 </ul>
-<h2 id="products-editors">XSL-FO editors</h2>
+<h2 id="xsl-fo-editors-wzxhzdk51wzxhzdk52">XSL-FO editors # <a id="#products-editors"></a></h2>
 <ul>
 <li>
 <p>[software]<jump href="http://foa.sourceforge.net/">FOA (Formatting Objects Authoring)</jump>(MPL)</p>
@@ -624,7 +624,7 @@ $(document).ready(function () {
 <p>[software]<jump href="http://www.digiforms.com/">DIGIFORMS Document Designer</jump>by Metafocus (commercial)</p>
 </li>
 </ul>
-<h2 id="products-other">Other products</h2>
+<h2 id="other-products-wzxhzdk53wzxhzdk54">Other products # <a id="#products-other"></a></h2>
 <ul>
 <li>
 <p>[software]<jump href="http://foray.sourceforge.net/">FOray</jump>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 Tue Oct 23 15:05:41 2012
@@ -331,14 +331,14 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><subtitle>Current Status of Apache&trade; FOP</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="Status">Status</h1>
+<h1 id="status-wzxhzdk5wzxhzdk6">Status  <a id="#Status"></a></h1>
 <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>
-<h1 id="development-status-developmentstatus">Development Status # {#Development+Status}</h1>
+<h1 id="development-status-wzxhzdk9wzxhzdk10">Development Status  <a id="#Development+Status"></a></h1>
 <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>
-<h2 id="component-status">Status of the individual components</h2>
+<h2 id="status-of-the-individual-components-wzxhzdk11wzxhzdk12">Status of the individual components # <a id="#component-status"></a></h2>
 <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 Tue Oct 23 15:05:41 2012
@@ -332,7 +332,7 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
 <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>
-<h1 id="commit-active">Active Committers</h1>
+<h1 id="active-committers-wzxhzdk2wzxhzdk3">Active Committers  <a id="#commit-active"></a></h1>
 <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>
@@ -372,7 +372,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>
-<h1 id="contribute-active">Active Contributors</h1>
+<h1 id="active-contributors-wzxhzdk4wzxhzdk5">Active Contributors  <a id="#contribute-active"></a></h1>
 <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>
@@ -384,9 +384,9 @@ $(document).ready(function () {
 <p>Vanukuri Venkat Reddy is a Senior Software Engineer in UK, using XML Graphics Project and FOP for his work, and is committed to contributing more to the Apache to be part a great team.</p>
 </li>
 </ul>
-<h1 id="founder">Founder</h1>
+<h1 id="founder-wzxhzdk6wzxhzdk7">Founder  <a id="#founder"></a></h1>
 <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>
-<h1 id="commit-inactive">Inactive Committers</h1>
+<h1 id="inactive-committers-wzxhzdk10wzxhzdk11">Inactive Committers  <a id="#commit-inactive"></a></h1>
 <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 Tue Oct 23 15:05:41 2012
@@ -330,7 +330,7 @@ $(document).ready(function () {
       
       <div id="content" class="grid_16">
       	<!-- <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="overview">Overview</h1>
+      	<div class="section-content"><h1 id="overview-wzxhzdk4wzxhzdk5">Overview  <a id="#overview"></a></h1>
 <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>
 <h1 id="enabling-accessibility">Enabling accessibility</h1>
@@ -351,7 +351,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>
-<h1 id="source">Changes to your XSL-FO input files</h1>
+<h1 id="changes-to-your-xsl-fo-input-files-wzxhzdk7wzxhzdk8">Changes to your XSL-FO input files  <a id="#source"></a></h1>
 <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>
@@ -367,7 +367,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>
-<h1 id="customTags">Customized Tagging</h1>
+<h1 id="customized-tagging-wzxhzdk9wzxhzdk10">Customized Tagging  <a id="#customTags"></a></h1>
 <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>
@@ -514,9 +514,9 @@ The processing of the logical structure 
 </tr>
 </tbody>
 </table>
-<h1 id="testing">Testing</h1>
+<h1 id="testing-wzxhzdk11wzxhzdk12">Testing  <a id="#testing"></a></h1>
 <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>
-<h1 id="limitations">Limitations</h1>
+<h1 id="limitations-wzxhzdk13wzxhzdk14">Limitations  <a id="#limitations"></a></h1>
 <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>
@@ -532,7 +532,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>
-<h1 id="links">Related Links</h1>
+<h1 id="related-links-wzxhzdk15wzxhzdk16">Related Links  <a id="#links"></a></h1>
 <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 Tue Oct 23 15:05:41 2012
@@ -332,7 +332,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"><p><version>$Revision: 1298724 $</version></p>
 <p>Apache&trade; FOP provides an Ant task for automating the document build process.</p>
-<h1 id="basics">Description</h1>
+<h1 id="description-wzxhzdk4wzxhzdk5">Description  <a id="#basics"></a></h1>
 <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>
 <property name="fop.home" value="....path to your FOP HOME directory..."/>
@@ -352,7 +352,7 @@ $(document).ready(function () {
 
 Then create FOP tasks within your Ant build file, using the FOP task parameters listed below.
 
-# Parameters for FOP Ant task # {#parameters}
+# Parameters for FOP Ant task  <a id="#parameters"></a>
 
 <caption>Parameters specified as attributes</caption>| Attribute | Description | Required |
 |-----------|-------------|----------|
@@ -374,7 +374,7 @@ Then create FOP tasks within your Ant bu
 |-----------|-------------|----------|
 | fileset |  [FileSets](http://ant.apache.org/manual/CoreTypes/fileset.html) are used to specify multiple XSL-FO files to be rendered. | Yes, if no fofile attribute is supplied |
 
-# Examples # {#examples}
+# Examples  <a id="#examples"></a>
 
 The following example converts a single XSL-FO file to a PDF document:
 

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 Tue Oct 23 15:05:41 2012
@@ -331,18 +331,18 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <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"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="build-needed">Do You Need To Build?</h1>
+<h1 id="do-you-need-to-build-wzxhzdk2wzxhzdk3">Do You Need To Build?  <a id="#build-needed"></a></h1>
 <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>
-<h1 id="env">Set Up Your Environment</h1>
-<h2 id="env-jdk">JDK</h2>
+<h1 id="set-up-your-environment-wzxhzdk5wzxhzdk6">Set Up Your Environment  <a id="#env"></a></h1>
+<h2 id="jdk-wzxhzdk7wzxhzdk8">JDK # <a id="#env-jdk"></a></h2>
 <p>Building FOP requires a minimum Java Development Kit (JDK/SDK) of 1.4 (A Java Runtime Environment is not sufficient).</p>
-<h2 id="env-classpath">CLASSPATH</h2>
+<h2 id="classpath-wzxhzdk9wzxhzdk10">CLASSPATH # <a id="#env-classpath"></a></h2>
 <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>
-<h2 id="env-java-home">JAVA_HOME</h2>
+<h2 id="java_home-wzxhzdk11wzxhzdk12">JAVA_HOME # <a id="#env-java-home"></a></h2>
 <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>
-<h2 id="env-ant">Apache Ant</h2>
+<h2 id="apache-ant-wzxhzdk13wzxhzdk14">Apache Ant # <a id="#env-ant"></a></h2>
 <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>
-<h1 id="build-script">Run the Build Script</h1>
+<h1 id="run-the-build-script-wzxhzdk15wzxhzdk16">Run the Build Script  <a id="#build-script"></a></h1>
 <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:
@@ -367,7 +367,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>
-<h1 id="problems">Troubleshooting</h1>
+<h1 id="troubleshooting-wzxhzdk17wzxhzdk18">Troubleshooting  <a id="#problems"></a></h1>
 <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 Tue Oct 23 15:05:41 2012
@@ -330,7 +330,7 @@ $(document).ready(function () {
       
       <div id="content" class="grid_16">
       	<!-- <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="overview">Overview</h1>
+      	<div class="section-content"><h1 id="overview-wzxhzdk0wzxhzdk1">Overview  <a id="#overview"></a></h1>
 <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>
@@ -346,7 +346,7 @@ $(document).ready(function () {
 <p>Support for advanced number to string formatting.</p>
 </li>
 </ul>
-<h1 id="disabling-complex-scripts-disablingcomplexscripts">Disabling complex scripts # {#Disabling+complex+scripts}</h1>
+<h1 id="disabling-complex-scripts-wzxhzdk3wzxhzdk4">Disabling complex scripts  <a id="#Disabling+complex+scripts"></a></h1>
 <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>
@@ -364,7 +364,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>
-<h1 id="source">Changes to your XSL-FO input files</h1>
+<h1 id="changes-to-your-xsl-fo-input-files-wzxhzdk5wzxhzdk6">Changes to your XSL-FO input files  <a id="#source"></a></h1>
 <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>
@@ -389,9 +389,9 @@ A document author need not make explicit
 <p>Explicit join control characters: U+200C ZWNJ and U+200D ZWJ.</p>
 </li>
 </ul>
-<h1 id="details">Authoring Details</h1>
+<h1 id="authoring-details-wzxhzdk7wzxhzdk8">Authoring Details  <a id="#details"></a></h1>
 <p>The complex scripts related effects of the above enumerated XSL-FO constructs are more fully described in the following sub-sections.</p>
-<h2 id="script_property">Script Property</h2>
+<h2 id="script-property-wzxhzdk9wzxhzdk10">Script Property # <a id="#script_property"></a></h2>
 <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>
@@ -402,7 +402,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>
-<h3 id="standard_script_codes">Standard Script Codes</h3>
+<h3 id="standard-script-codes-wzxhzdk11wzxhzdk12">Standard Script Codes ## <a id="#standard_script_codes"></a></h3>
 <p>The following table enumerates the standard ISO 15924 4-letter codes recognized by FOP.</p>
 <table>
 <thead>
@@ -542,7 +542,7 @@ A document author need not make explicit
 </tr>
 </tbody>
 </table>
-<h3 id="extended_script_codes">Extended Script Codes</h3>
+<h3 id="extended-script-codes-wzxhzdk13wzxhzdk14">Extended Script Codes ## <a id="#extended_script_codes"></a></h3>
 <p>The following table enumerates a number of non-standard extended script codes recognized by FOP.</p>
 <table>
 <thead>
@@ -626,7 +626,7 @@ A document author need not make explicit
 <td></td>
 </tr>
 <tr>
-<td id="language_property">## Language Property</td>
+<td>## Language Property # <a id="#language_property"></a></td>
 <td></td>
 <td></td>
 <td></td>
@@ -636,12 +636,12 @@ A document author need not make explicit
 </table>
 <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"></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>
-<h2 id="writing_mode_property">Writing Mode Property</h2>
-<h2 id="number_conversion_properties">Number Conversion Properties</h2>
-<h2 id="bidi_override_element">Bidi Override Element</h2>
-<h2 id="bidi_controls">Bidi Control Characters</h2>
-<h2 id="join_controls">Join Control Characters</h2>
-<h1 id="supported_scripts">Supported Scripts</h1>
+<h2 id="writing-mode-property-wzxhzdk15wzxhzdk16">Writing Mode Property # <a id="#writing_mode_property"></a></h2>
+<h2 id="number-conversion-properties-wzxhzdk17wzxhzdk18">Number Conversion Properties # <a id="#number_conversion_properties"></a></h2>
+<h2 id="bidi-override-element-wzxhzdk19wzxhzdk20">Bidi Override Element # <a id="#bidi_override_element"></a></h2>
+<h2 id="bidi-control-characters-wzxhzdk21wzxhzdk22">Bidi Control Characters # <a id="#bidi_controls"></a></h2>
+<h2 id="join-control-characters-wzxhzdk23wzxhzdk24">Join Control Characters # <a id="#join_controls"></a></h2>
+<h1 id="supported-scripts-wzxhzdk25wzxhzdk26">Supported Scripts  <a id="#supported_scripts"></a></h1>
 <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>
@@ -793,9 +793,9 @@ A document author need not make explicit
 </tr>
 </tbody>
 </table>
-<h1 id="supported_fonts">Supported Fonts</h1>
+<h1 id="supported-fonts-wzxhzdk27wzxhzdk28">Supported Fonts  <a id="#supported_fonts"></a></h1>
 <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>
-<h2 id="fonts_arabic">Arabic Fonts</h2>
+<h2 id="arabic-fonts-wzxhzdk29wzxhzdk30">Arabic Fonts # <a id="#fonts_arabic"></a></h2>
 <table>
 <thead>
 <tr>
@@ -882,7 +882,7 @@ A document author need not make explicit
 </tr>
 </tbody>
 </table>
-<h2 id="devanagari_fonts">Devanagari Fonts</h2>
+<h2 id="devanagari-fonts-wzxhzdk31wzxhzdk32">Devanagari Fonts # <a id="#devanagari_fonts"></a></h2>
 <table>
 <thead>
 <tr>
@@ -929,7 +929,7 @@ A document author need not make explicit
 </tr>
 </tbody>
 </table>
-<h1 id="limitations">Other Limitations</h1>
+<h1 id="other-limitations-wzxhzdk33wzxhzdk34">Other Limitations  <a id="#limitations"></a></h1>
 <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>
@@ -939,7 +939,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>
-<h1 id="links">Related Links</h1>
+<h1 id="related-links-wzxhzdk35wzxhzdk36">Related Links  <a id="#links"></a></h1>
 <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>



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


Mime
View raw message