You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2012/10/24 06:04:05 UTC
svn commit: r835960 [15/18] - in
/websites/staging/xmlgraphics/trunk/content: ./ batik/ batik/dev/
batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/
fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Modified: websites/staging/xmlgraphics/trunk/content/fop/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/index.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/index.html Wed Oct 24 04:04:00 2012
@@ -330,19 +330,20 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="introduction-wzxhzdk2wzxhzdk3">Introduction <a id="intro"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop">Apache(tm) FOP</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="introduction-wzxhzdk2wzxhzdk3">Introduction <a id="intro"></a></h2>
<p>Apache™ 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™ FOP project is part of the <a href="http://www.apache.org">Apache™</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="demonstration-wzxhzdk9wzxhzdk10">Demonstration <a id="demo"></a></h1>
+<h2 id="demonstration-wzxhzdk9wzxhzdk10">Demonstration <a id="demo"></a></h2>
<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="fop-objectives-wzxhzdk13wzxhzdk14">FOP Objectives <a id="objectives"></a></h1>
+<h2 id="fop-objectives-wzxhzdk13wzxhzdk14">FOP Objectives <a id="objectives"></a></h2>
<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 Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="known-issues-wzxhzdk2wzxhzdk3">Known issues <a id="Known+issues"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-known-issues">Apache(tm) FOP: Known Issues</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="known-issues-wzxhzdk2wzxhzdk3">Known issues <a id="Known+issues"></a></h2>
<p>This page lists currently known issues in the Apache™ 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 +344,11 @@ $(document).ready(function () {
</li>
</ul>
<p>Apache™ 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-wzxhzdk6wzxhzdk7">FO Tree # <a id="FO+Tree"></a></h2>
+<h3 id="fo-tree-wzxhzdk6wzxhzdk7">FO Tree # <a id="FO+Tree"></a></h3>
<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-wzxhzdk12wzxhzdk13">Layout Engine # <a id="Layout+Engine"></a></h2>
+<h3 id="layout-engine-wzxhzdk12wzxhzdk13">Layout Engine # <a id="Layout+Engine"></a></h3>
<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 +384,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-wzxhzdk84wzxhzdk85">Other known issues # <a id="Other+known+issues"></a></h2>
+<h3 id="other-known-issues-wzxhzdk84wzxhzdk85">Other known issues # <a id="Other+known+issues"></a></h3>
<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 Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="license-wzxhzdk2wzxhzdk3">License <a id="License"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-license">Apache(tm) FOP License</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="license-wzxhzdk2wzxhzdk3">License <a id="License"></a></h2>
<p>All new Apache™ FOP releases will be licensed under the <strong>Apache™ License, version 2.0</strong> . Releases until version 0.20.5 are released unter the Apache™ 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 Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="general-information-wzxhzdk2wzxhzdk3">General Information <a id="general"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-mailing-list-resources">Apache(tm) FOP: Mailing List Resources</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="general-information-wzxhzdk2wzxhzdk3">General Information <a id="general"></a></h2>
<p>Before posting questions to any list:</p>
<ul>
<li>
@@ -348,9 +349,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="apachewzxhzdk10-fop-users-mailing-list-wzxhzdk8wzxhzdk9">Apache™ FOP Users Mailing List <a id="fop-user"></a></h1>
+<h2 id="apachewzxhzdk10-fop-users-mailing-list-wzxhzdk8wzxhzdk9">Apache™ FOP Users Mailing List <a id="fop-user"></a></h2>
<p>Use this forum to discuss topics of interest to FOP users.</p>
-<h2 id="archives-wzxhzdk11wzxhzdk12">Archives # <a id="fop-user-archive"></a></h2>
+<h3 id="archives-wzxhzdk11wzxhzdk12">Archives # <a id="fop-user-archive"></a></h3>
<p>To review the archives, you have several options:</p>
<ul>
<li>
@@ -445,7 +446,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&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="xsl-fo-mailing-list-at-w3c-wzxhzdk17wzxhzdk18">XSL-FO Mailing List (at W3C) <a id="w3c-xslfo"></a></h1>
+<h2 id="xsl-fo-mailing-list-at-w3c-wzxhzdk17wzxhzdk18">XSL-FO Mailing List (at W3C) <a id="w3c-xslfo"></a></h2>
<p>Use this forum to ask general XSL-FO questions.</p>
<ul>
<li>
@@ -458,7 +459,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="xsl-fo-mailing-list-at-yahoogroups-wzxhzdk19wzxhzdk20">XSL-FO Mailing List (at YahooGroups) <a id="yahoogroups-xslfo"></a></h1>
+<h2 id="xsl-fo-mailing-list-at-yahoogroups-wzxhzdk19wzxhzdk20">XSL-FO Mailing List (at YahooGroups) <a id="yahoogroups-xslfo"></a></h2>
<p>Use this forum to ask general XSL-FO questions.</p>
<ul>
<li>
@@ -468,7 +469,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-list-mulberry-tech-wzxhzdk21wzxhzdk22">XSLT List (Mulberry Tech) <a id="xslt-mulberry"></a></h1>
+<h2 id="xslt-list-mulberry-tech-wzxhzdk21wzxhzdk22">XSLT List (Mulberry Tech) <a id="xslt-mulberry"></a></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 Wed Oct 24 04:04:00 2012
@@ -330,9 +330,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+ <div class="section-content"><h1 id="apachetm-fop-news">Apache(tm) FOP News</h1>
+<p><version>$Revision: 1298724 $</version></p>
<p>RSS Feed: <a href="subproject-news-feed.rss"></a> </p>
-<h1 id="24-feb-2012-new-committer-wzxhzdk2wzxhzdk3">24 Feb 2012: New committer <a id="news-2012-02-24"></a></h1>
+<h2 id="24-feb-2012-new-committer-wzxhzdk2wzxhzdk3">24 Feb 2012: New committer <a id="news-2012-02-24"></a></h2>
<p><item date="2012-02-24" title="New committer">
Welcome Glenn Adams!
</item></p>
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 Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><subtitle>Everything you need to start using and appreciating Apache™ FOP quickly.</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="apachewzxhzdk7-fop-essentials-wzxhzdk5wzxhzdk6">Apache™ FOP Essentials <a id="essentials"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-quick-start-guide">Apache(tm) FOP: Quick Start Guide</h1>
+<p><subtitle>Everything you need to start using and appreciating Apache™ FOP quickly.</subtitle><version>$Revision: 1298724 $</version></p>
+<h2 id="apachewzxhzdk7-fop-essentials-wzxhzdk5wzxhzdk6">Apache™ FOP Essentials <a id="essentials"></a></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>
@@ -372,7 +373,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-with-fop-wzxhzdk8wzxhzdk9">Hello World with FOP <a id="hello-world"></a></h1>
+<h2 id="hello-world-with-fop-wzxhzdk8wzxhzdk9">Hello World with FOP <a id="hello-world"></a></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 Wed Oct 24 04:04:00 2012
@@ -330,9 +330,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><subtitle>Resources useful for developing and using Apache™ FOP</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="specifications-wzxhzdk5wzxhzdk6">Specifications <a id="specs"></a></h1>
-<h2 id="xsl-fo-wzxhzdk7wzxhzdk8">XSL-FO # <a id="specs-xslfo"></a></h2>
+ <div class="section-content"><h1 id="apachetm-fop-other-resources">Apache(tm) FOP: Other Resources</h1>
+<p><subtitle>Resources useful for developing and using Apache™ FOP</subtitle><version>$Revision: 1298724 $</version></p>
+<h2 id="specifications-wzxhzdk5wzxhzdk6">Specifications <a id="specs"></a></h2>
+<h3 id="xsl-fo-wzxhzdk7wzxhzdk8">XSL-FO # <a id="specs-xslfo"></a></h3>
<ul>
<li>
<p><jump href="http://www.w3.org/TR/xsl11/">XSL-FO Recommendation (05 December 2006)</jump></p>
@@ -341,7 +342,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="xslt-wzxhzdk9wzxhzdk10">XSLT # <a id="specs-xslt"></a></h2>
+<h3 id="xslt-wzxhzdk9wzxhzdk10">XSLT # <a id="specs-xslt"></a></h3>
<ul>
<li>
<p><jump href="http://www.w3.org/TR/xslt">XSLT 1.0 Recommendation</jump></p>
@@ -350,7 +351,7 @@ $(document).ready(function () {
<p><jump href="http://www.w3.org/TR/xslt20">XSLT 2.0 Recommendation</jump></p>
</li>
</ul>
-<h2 id="xml-wzxhzdk11wzxhzdk12">XML # <a id="specs-xml"></a></h2>
+<h3 id="xml-wzxhzdk11wzxhzdk12">XML # <a id="specs-xml"></a></h3>
<ul>
<li>
<p><jump href="http://www.w3.org/TR/xml">XML 1.0</jump></p>
@@ -377,7 +378,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="java-wzxhzdk13wzxhzdk14">Java # <a id="specs-java"></a></h2>
+<h3 id="java-wzxhzdk13wzxhzdk14">Java # <a id="specs-java"></a></h3>
<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 +390,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="pdf-wzxhzdk15wzxhzdk16">PDF # <a id="specs-pdf"></a></h2>
+<h3 id="pdf-wzxhzdk15wzxhzdk16">PDF # <a id="specs-pdf"></a></h3>
<ul>
<li><jump href="http://partners.adobe.com/asn/tech/pdf/specifications.jsp">Portable Document Format (PDF) Reference Manual</jump></li>
</ul>
-<h2 id="unicode-wzxhzdk17wzxhzdk18">Unicode # <a id="specs-unicode"></a></h2>
+<h3 id="unicode-wzxhzdk17wzxhzdk18">Unicode # <a id="specs-unicode"></a></h3>
<ul>
<li><jump href="http://www.unicode.org/reports/tr14">UTR-14 (Unicode Standard Annex #14: Line Breaking Properties)</jump></li>
</ul>
-<h2 id="other-wzxhzdk19wzxhzdk20">Other # <a id="specs-other"></a></h2>
+<h3 id="other-wzxhzdk19wzxhzdk20">Other # <a id="specs-other"></a></h3>
<ul>
<li><jump href="http://www.w3.org/TR/SVG/">Supported SVG Recommendation (04 September 2001)</jump></li>
</ul>
-<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>
+<h2 id="books-tutorials-articles-wzxhzdk21wzxhzdk22">Books, Tutorials, Articles <a id="documents"></a></h2>
+<h3 id="xsl-fo-wzxhzdk23wzxhzdk24">XSL-FO # <a id="documents-xslfo"></a></h3>
<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 +430,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="xslt-wzxhzdk25wzxhzdk26">XSLT # <a id="documents-xslt"></a></h2>
+<h3 id="xslt-wzxhzdk25wzxhzdk26">XSLT # <a id="documents-xslt"></a></h3>
<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 +460,7 @@ $(document).ready(function () {
<p>[book]<jump href="http://www.oreilly.com/catalog/javaxslt">Java and XSLT</jump>, by Eric M. Burke, O'Reilly & Associates, 2001, ISBN 0-596-00143-6.</p>
</li>
</ul>
-<h2 id="xml-wzxhzdk27wzxhzdk28">XML # <a id="documents-xml"></a></h2>
+<h3 id="xml-wzxhzdk27wzxhzdk28">XML # <a id="documents-xml"></a></h3>
<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 +472,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="java-wzxhzdk29wzxhzdk30">Java # <a id="documents-java"></a></h2>
+<h3 id="java-wzxhzdk29wzxhzdk30">Java # <a id="documents-java"></a></h3>
<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="pdf-wzxhzdk31wzxhzdk32">PDF # <a id="documents-pdf"></a></h2>
+<h3 id="pdf-wzxhzdk31wzxhzdk32">PDF # <a id="documents-pdf"></a></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,<jump href="http://partners.adobe.com/asn/acrobat/docs.jsp#filefmtspecs">Acrobat 5.0 SDK Documentation</jump>.</p>
@@ -487,7 +488,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="postscript-wzxhzdk33wzxhzdk34">PostScript # <a id="documents-ps"></a></h2>
+<h3 id="postscript-wzxhzdk33wzxhzdk34">PostScript # <a id="documents-ps"></a></h3>
<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 +497,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-wzxhzdk35wzxhzdk36">Mailing Lists <a id="mailing-lists"></a></h1>
+<h2 id="mailing-lists-wzxhzdk35wzxhzdk36">Mailing Lists <a id="mailing-lists"></a></h2>
<p>Before posting questions to any list:</p>
<ul>
<li>
@@ -513,7 +514,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-mailing-list-wzxhzdk37wzxhzdk38">Apache FOP Mailing List # <a id="Apache-FOP"></a></h2>
+<h3 id="apache-fop-mailing-list-wzxhzdk37wzxhzdk38">Apache FOP Mailing List # <a id="Apache-FOP"></a></h3>
<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 +556,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-mailing-list-at-w3c-wzxhzdk39wzxhzdk40">XSL-FO Mailing List (at W3C) # <a id="XSL-FO-at-W3C"></a></h2>
+<h3 id="xsl-fo-mailing-list-at-w3c-wzxhzdk39wzxhzdk40">XSL-FO Mailing List (at W3C) # <a id="XSL-FO-at-W3C"></a></h3>
<ul>
<li>
<p>[mailing list info]<jump href="http://www.w3.org/Mail/Request">http://www.w3.org/Mail/Request</jump></p>
@@ -564,16 +565,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-mailing-list-at-yahoogroups-wzxhzdk41wzxhzdk42">XSL-FO Mailing List (at YahooGroups) # <a id="XSL-FO-at-YahooGroups"></a></h2>
+<h3 id="xsl-fo-mailing-list-at-yahoogroups-wzxhzdk41wzxhzdk42">XSL-FO Mailing List (at YahooGroups) # <a id="XSL-FO-at-YahooGroups"></a></h3>
<ul>
<li>[mailing list info & archives]<jump href="http://groups.yahoo.com/group/XSL-FO">http://groups.yahoo.com/group/XSL-FO</jump></li>
</ul>
-<h2 id="xslt-list-mulberry-tech-wzxhzdk43wzxhzdk44">XSLT List (Mulberry Tech) # <a id="XSLT-at-Mulberry-Tech"></a></h2>
+<h3 id="xslt-list-mulberry-tech-wzxhzdk43wzxhzdk44">XSLT List (Mulberry Tech) # <a id="XSLT-at-Mulberry-Tech"></a></h3>
<ul>
<li>[mailing list info & archives]<jump href="http://www.mulberrytech.com/xsl/xsl-list">http://www.mulberrytech.com/xsl/xsl-list</jump></li>
</ul>
-<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>
+<h2 id="relateduseful-products-wzxhzdk45wzxhzdk46">Related/Useful Products <a id="products"></a></h2>
+<h3 id="fop-add-ons-wzxhzdk47wzxhzdk48">FOP add-ons # <a id="products-fop-add-ons"></a></h3>
<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 +595,7 @@ $(document).ready(function () {
<p>[software & tools]<jump href="http://offo.sourceforge.net/">Objects For Formatting Objects</jump>hosts hyphenation patterns and (eventually) files other accessory data files & scripts.</p>
</li>
</ul>
-<h2 id="pdf-post-processors-wzxhzdk49wzxhzdk50">PDF post-processors # <a id="products-pdf"></a></h2>
+<h3 id="pdf-post-processors-wzxhzdk49wzxhzdk50">PDF post-processors # <a id="products-pdf"></a></h3>
<ul>
<li>
<p>[software]<jump href="http://pdfbox.apache.org">Apache PDFBox</jump>(Apache License V2.0)</p>
@@ -609,7 +610,7 @@ $(document).ready(function () {
<p>[software]<jump href="http://www.accesspdf.com/pdftk/">pdftk</jump>the pdf toolkit</p>
</li>
</ul>
-<h2 id="xsl-fo-editors-wzxhzdk51wzxhzdk52">XSL-FO editors # <a id="products-editors"></a></h2>
+<h3 id="xsl-fo-editors-wzxhzdk51wzxhzdk52">XSL-FO editors # <a id="products-editors"></a></h3>
<ul>
<li>
<p>[software]<jump href="http://foa.sourceforge.net/">FOA (Formatting Objects Authoring)</jump>(MPL)</p>
@@ -624,7 +625,7 @@ $(document).ready(function () {
<p>[software]<jump href="http://www.digiforms.com/">DIGIFORMS Document Designer</jump>by Metafocus (commercial)</p>
</li>
</ul>
-<h2 id="other-products-wzxhzdk53wzxhzdk54">Other products # <a id="products-other"></a></h2>
+<h3 id="other-products-wzxhzdk53wzxhzdk54">Other products # <a id="products-other"></a></h3>
<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 Wed Oct 24 04:04:00 2012
@@ -330,15 +330,16 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><subtitle>Current Status of Apache™ FOP</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="status-wzxhzdk5wzxhzdk6">Status <a id="Status"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-status">Apache(tm) FOP Status</h1>
+<p><subtitle>Current Status of Apache™ FOP</subtitle><version>$Revision: 1298724 $</version></p>
+<h2 id="status-wzxhzdk5wzxhzdk6">Status <a id="Status"></a></h2>
<p>[last updated 5 July 2010]</p>
<p>Apache™ FOP version 0.95 was released on 5 August 2008. Apache™ FOP version 1.0 was released on 21 July 2010.</p>
-<h1 id="development-status-wzxhzdk9wzxhzdk10">Development Status <a id="Development+Status"></a></h1>
+<h2 id="development-status-wzxhzdk9wzxhzdk10">Development Status <a id="Development+Status"></a></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>
-<h2 id="status-of-the-individual-components-wzxhzdk11wzxhzdk12">Status of the individual components # <a id="component-status"></a></h2>
+<h3 id="status-of-the-individual-components-wzxhzdk11wzxhzdk12">Status of the individual components # <a id="component-status"></a></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 Wed Oct 24 04:04:00 2012
@@ -330,9 +330,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+ <div class="section-content"><h1 id="apachetm-fop-development-team">Apache(tm) FOP: Development Team</h1>
+<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="active-committers-wzxhzdk2wzxhzdk3">Active Committers <a id="commit-active"></a></h1>
+<h2 id="active-committers-wzxhzdk2wzxhzdk3">Active Committers <a id="commit-active"></a></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>
@@ -372,7 +373,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="active-contributors-wzxhzdk4wzxhzdk5">Active Contributors <a id="contribute-active"></a></h1>
+<h2 id="active-contributors-wzxhzdk4wzxhzdk5">Active Contributors <a id="contribute-active"></a></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>
@@ -384,9 +385,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-wzxhzdk6wzxhzdk7">Founder <a id="founder"></a></h1>
+<h2 id="founder-wzxhzdk6wzxhzdk7">Founder <a id="founder"></a></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>
-<h1 id="inactive-committers-wzxhzdk10wzxhzdk11">Inactive Committers <a id="commit-inactive"></a></h1>
+<h2 id="inactive-committers-wzxhzdk10wzxhzdk11">Inactive Committers <a id="commit-inactive"></a></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 Wed Oct 24 04:04:00 2012
@@ -330,10 +330,11 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/trunk/">Trunk</a></div> -->
- <div class="section-content"><h1 id="overview-wzxhzdk4wzxhzdk5">Overview <a id="overview"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-accessibility">Apache(tm) FOP: Accessibility</h1>
+<h2 id="overview-wzxhzdk4wzxhzdk5">Overview <a id="overview"></a></h2>
<p>This page describes the <a href="http://en.wikipedia.org/wiki/Accessibility">accessibility</a> features of Apache™ 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>
+<h2 id="enabling-accessibility">Enabling accessibility</h2>
<p>There are 3 ways to enable accessibility:</p>
<ol>
<li>
@@ -367,7 +368,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="customized-tagging-wzxhzdk9wzxhzdk10">Customized Tagging <a id="customTags"></a></h1>
+<h2 id="customized-tagging-wzxhzdk9wzxhzdk10">Customized Tagging <a id="customTags"></a></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>
@@ -379,7 +380,7 @@ The processing of the logical structure
<p>If a non-standard structure type is specified, FOP will issue a warning and fall back to the default tag associated to the Formatting Object.</p>
-<h1 id="treating-content-as-artifact">Treating Content as Artifact</h1>
+<h2 id="treating-content-as-artifact">Treating Content as Artifact</h2>
<p>If your document has content that is not meant to appear in the structure tree, you can wrap it in an <code>fo:wrapper</code> element whose <code>role</code> property has been set to âartifactâ. For example:</p>
<div class="codehilite"><pre><span class="nt"><fo:block></span>blah... blah...
<span class="nt"><fo:wrapper</span> <span class="na">role=</span><span class="s">"artifact"</span><span class="nt">></span>Funny graphical thing without logical meaning<span class="nt"></fo:wrapper></span>
@@ -394,7 +395,7 @@ The processing of the logical structure
</pre></div>
-<h1 id="fox:header">Scope of Header Table Cells</h1>
+<h2 id="fox:header">Scope of Header Table Cells</h2>
<p>In XSL-FO, tables are inherently defined row by row. The <code>fo:table-header</code> element can be used to define âheader rowsâ, in which each cell is a header of the corresponding column (like <code>TH</code> cells in HTML). The cell is said to have a column <em>scope</em>.</p>
<p>There is no way, however, to define ârow headersâ: cells that have a row scope. Of course it is possible to style a cell to make it look like a header (for example, by using a bolder font), but that wonât be reflected in the structure of the document.</p>
<p>When creating accessible documents, it is desirable to have that information, as it can be used by a screen reader to help the user build a mental representation of the table.</p>
@@ -514,9 +515,9 @@ The processing of the logical structure
</tr>
</tbody>
</table>
-<h1 id="testing-wzxhzdk11wzxhzdk12">Testing <a id="testing"></a></h1>
+<h2 id="testing-wzxhzdk11wzxhzdk12">Testing <a id="testing"></a></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>
-<h1 id="limitations-wzxhzdk13wzxhzdk14">Limitations <a id="limitations"></a></h1>
+<h2 id="limitations-wzxhzdk13wzxhzdk14">Limitations <a id="limitations"></a></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>
@@ -532,7 +533,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="related-links-wzxhzdk15wzxhzdk16">Related Links <a id="links"></a></h1>
+<h2 id="related-links-wzxhzdk15wzxhzdk16">Related Links <a id="links"></a></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 Wed Oct 24 04:04:00 2012
@@ -330,9 +330,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/trunk/">Trunk</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+ <div class="section-content"><h1 id="apachetm-fop-ant-task">Apache(tm) FOP: Ant task</h1>
+<p><version>$Revision: 1298724 $</version></p>
<p>Apache™ FOP provides an Ant task for automating the document build process.</p>
-<h1 id="description-wzxhzdk4wzxhzdk5">Description <a id="basics"></a></h1>
+<h2 id="description-wzxhzdk4wzxhzdk5">Description <a id="basics"></a></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>
<property name="fop.home" value="....path to your FOP HOME directory..."/>
@@ -352,7 +353,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 <a id="parameters"></a>
+## Parameters for FOP Ant task <a id="parameters"></a>
<caption>Parameters specified as attributes</caption>| Attribute | Description | Required |
|-----------|-------------|----------|
@@ -374,7 +375,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 <a id="examples"></a>
+## 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 Wed Oct 24 04:04:00 2012
@@ -330,19 +330,20 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/trunk/">Trunk</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="do-you-need-to-build-wzxhzdk2wzxhzdk3">Do You Need To Build? <a id="build-needed"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-building-from-source-code">Apache(tm) FOP: Building from Source Code</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="do-you-need-to-build-wzxhzdk2wzxhzdk3">Do You Need To Build? <a id="build-needed"></a></h2>
<p>Apache™ 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="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>
+<h2 id="set-up-your-environment-wzxhzdk5wzxhzdk6">Set Up Your Environment <a id="env"></a></h2>
+<h3 id="jdk-wzxhzdk7wzxhzdk8">JDK # <a id="env-jdk"></a></h3>
<p>Building FOP requires a minimum Java Development Kit (JDK/SDK) of 1.4 (A Java Runtime Environment is not sufficient).</p>
-<h2 id="classpath-wzxhzdk9wzxhzdk10">CLASSPATH # <a id="env-classpath"></a></h2>
+<h3 id="classpath-wzxhzdk9wzxhzdk10">CLASSPATH # <a id="env-classpath"></a></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>
-<h2 id="java_home-wzxhzdk11wzxhzdk12">JAVA_HOME # <a id="env-java-home"></a></h2>
+<h3 id="java_home-wzxhzdk11wzxhzdk12">JAVA_HOME # <a id="env-java-home"></a></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>
-<h2 id="apache-ant-wzxhzdk13wzxhzdk14">Apache Ant # <a id="env-ant"></a></h2>
+<h3 id="apache-ant-wzxhzdk13wzxhzdk14">Apache Ant # <a id="env-ant"></a></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>
-<h1 id="run-the-build-script-wzxhzdk15wzxhzdk16">Run the Build Script <a id="build-script"></a></h1>
+<h2 id="run-the-build-script-wzxhzdk15wzxhzdk16">Run the Build Script <a id="build-script"></a></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:
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 Wed Oct 24 04:04:00 2012
@@ -330,7 +330,8 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/trunk/">Trunk</a></div> -->
- <div class="section-content"><h1 id="overview-wzxhzdk0wzxhzdk1">Overview <a id="overview"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-complex-scripts">Apache(tm) FOP: Complex Scripts</h1>
+<h2 id="overview-wzxhzdk0wzxhzdk1">Overview <a id="overview"></a></h2>
<p>This page describes the <a href="http://en.wikipedia.org/wiki/Complex_scripts">complex scripts</a> features of Apache™ FOP, which include:</p>
<ul>
<li>
@@ -346,7 +347,7 @@ $(document).ready(function () {
<p>Support for advanced number to string formatting.</p>
</li>
</ul>
-<h1 id="disabling-complex-scripts-wzxhzdk3wzxhzdk4">Disabling complex scripts <a id="Disabling+complex+scripts"></a></h1>
+<h2 id="disabling-complex-scripts-wzxhzdk3wzxhzdk4">Disabling complex scripts <a id="Disabling+complex+scripts"></a></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>
@@ -389,9 +390,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="authoring-details-wzxhzdk7wzxhzdk8">Authoring Details <a id="details"></a></h1>
+<h2 id="authoring-details-wzxhzdk7wzxhzdk8">Authoring Details <a id="details"></a></h2>
<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-wzxhzdk9wzxhzdk10">Script Property # <a id="script_property"></a></h2>
+<h3 id="script-property-wzxhzdk9wzxhzdk10">Script Property # <a id="script_property"></a></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>
@@ -402,7 +403,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-wzxhzdk11wzxhzdk12">Standard Script Codes ## <a id="standard_script_codes"></a></h3>
+<h4 id="standard-script-codes-wzxhzdk11wzxhzdk12">Standard Script Codes ## <a id="standard_script_codes"></a></h4>
<p>The following table enumerates the standard ISO 15924 4-letter codes recognized by FOP.</p>
<table>
<thead>
@@ -542,7 +543,7 @@ A document author need not make explicit
</tr>
</tbody>
</table>
-<h3 id="extended-script-codes-wzxhzdk13wzxhzdk14">Extended Script Codes ## <a id="extended_script_codes"></a></h3>
+<h4 id="extended-script-codes-wzxhzdk13wzxhzdk14">Extended Script Codes ## <a id="extended_script_codes"></a></h4>
<p>The following table enumerates a number of non-standard extended script codes recognized by FOP.</p>
<table>
<thead>
@@ -636,12 +637,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-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>
+<h3 id="writing-mode-property-wzxhzdk15wzxhzdk16">Writing Mode Property # <a id="writing_mode_property"></a></h3>
+<h3 id="number-conversion-properties-wzxhzdk17wzxhzdk18">Number Conversion Properties # <a id="number_conversion_properties"></a></h3>
+<h3 id="bidi-override-element-wzxhzdk19wzxhzdk20">Bidi Override Element # <a id="bidi_override_element"></a></h3>
+<h3 id="bidi-control-characters-wzxhzdk21wzxhzdk22">Bidi Control Characters # <a id="bidi_controls"></a></h3>
+<h3 id="join-control-characters-wzxhzdk23wzxhzdk24">Join Control Characters # <a id="join_controls"></a></h3>
+<h2 id="supported-scripts-wzxhzdk25wzxhzdk26">Supported Scripts <a id="supported_scripts"></a></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>
@@ -793,9 +794,9 @@ A document author need not make explicit
</tr>
</tbody>
</table>
-<h1 id="supported-fonts-wzxhzdk27wzxhzdk28">Supported Fonts <a id="supported_fonts"></a></h1>
+<h2 id="supported-fonts-wzxhzdk27wzxhzdk28">Supported Fonts <a id="supported_fonts"></a></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>
-<h2 id="arabic-fonts-wzxhzdk29wzxhzdk30">Arabic Fonts # <a id="fonts_arabic"></a></h2>
+<h3 id="arabic-fonts-wzxhzdk29wzxhzdk30">Arabic Fonts # <a id="fonts_arabic"></a></h3>
<table>
<thead>
<tr>
@@ -882,7 +883,7 @@ A document author need not make explicit
</tr>
</tbody>
</table>
-<h2 id="devanagari-fonts-wzxhzdk31wzxhzdk32">Devanagari Fonts # <a id="devanagari_fonts"></a></h2>
+<h3 id="devanagari-fonts-wzxhzdk31wzxhzdk32">Devanagari Fonts # <a id="devanagari_fonts"></a></h3>
<table>
<thead>
<tr>
@@ -929,7 +930,7 @@ A document author need not make explicit
</tr>
</tbody>
</table>
-<h1 id="other-limitations-wzxhzdk33wzxhzdk34">Other Limitations <a id="limitations"></a></h1>
+<h2 id="other-limitations-wzxhzdk33wzxhzdk34">Other Limitations <a id="limitations"></a></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>
@@ -939,7 +940,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="related-links-wzxhzdk35wzxhzdk36">Related Links <a id="links"></a></h1>
+<h2 id="related-links-wzxhzdk35wzxhzdk36">Related Links <a id="links"></a></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 Wed Oct 24 04:04:00 2012
@@ -330,11 +330,12 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/trunk/">Trunk</a></div> -->
- <div class="section-content"><p><version>$Revision: 1302518 $</version></p>
-<h1 id="configuration-file-basics-wzxhzdk8wzxhzdk9">Configuration File Basics <a id="general"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-configuration">Apache(tm) FOP: Configuration</h1>
+<p><version>$Revision: 1302518 $</version></p>
+<h2 id="configuration-file-basics-wzxhzdk8wzxhzdk9">Configuration File Basics <a id="general"></a></h2>
<p>The Apache™ 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>
-<h2 id="making-configuration-available-to-fop-wzxhzdk11wzxhzdk12">Making Configuration Available to FOP # <a id="general-available"></a></h2>
+<h3 id="making-configuration-available-to-fop-wzxhzdk11wzxhzdk12">Making Configuration Available to FOP # <a id="general-available"></a></h3>
<p>After creating your configuration file, you must tell FOP how to find it:</p>
<ul>
<li>
@@ -345,7 +346,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>
-<h1 id="summary-of-the-general-configuration-options-wzxhzdk13wzxhzdk14">Summary of the General Configuration Options <a id="general-elements"></a></h1>
+<h2 id="summary-of-the-general-configuration-options-wzxhzdk13wzxhzdk14">Summary of the General Configuration Options <a id="general-elements"></a></h2>
<table>
<thead>
<tr>
@@ -474,7 +475,7 @@ $(document).ready(function () {
<fop version="1.0"></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>
-<h1 id="renderer-configuration-wzxhzdk44wzxhzdk45">Renderer configuration <a id="renderers"></a></h1>
+<h2 id="renderer-configuration-wzxhzdk44wzxhzdk45">Renderer configuration <a id="renderers"></a></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>
<p><renderers>
@@ -500,7 +501,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>
-<h2 id="special-settings-for-the-pdf-renderer-wzxhzdk64wzxhzdk65">Special Settings for the PDF Renderer # <a id="pdf-renderer"></a></h2>
+<h3 id="special-settings-for-the-pdf-renderer-wzxhzdk64wzxhzdk65">Special Settings for the PDF Renderer # <a id="pdf-renderer"></a></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"><renderer</span> <span class="na">mime=</span><span class="s">"application/pdf"</span><span class="nt">></span>
<span class="nt"><filterList></span>
@@ -562,7 +563,7 @@ $(document).ready(function () {
<version>1.5</version>
<!-- Versions 1.4, 1.5, 1.6 and 1.7 are accepted, all other values are invalid -->
</renderer></p>
-<h2 id="special-settings-for-the-postscript-renderer-wzxhzdk71wzxhzdk72">Special Settings for the PostScript Renderer # <a id="ps-renderer"></a></h2>
+<h3 id="special-settings-for-the-postscript-renderer-wzxhzdk71wzxhzdk72">Special Settings for the PostScript Renderer # <a id="ps-renderer"></a></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"><renderer</span> <span class="na">mime=</span><span class="s">"application/postscript"</span><span class="nt">></span>
<span class="nt"><auto-rotate-landscape></span>true<span class="nt"></auto-rotate-landscape></span>
@@ -590,7 +591,7 @@ $(document).ready(function () {
</renderer>
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>
-<h2 id="special-settings-for-the-afp-renderer-wzxhzdk81wzxhzdk82">Special Settings for the AFP Renderer # <a id="afp-renderer"></a></h2>
+<h3 id="special-settings-for-the-afp-renderer-wzxhzdk81wzxhzdk82">Special Settings for the AFP Renderer # <a id="afp-renderer"></a></h3>
<p>Additionally, there are certain settings that control how the renderer handles various elements.
<renderer mime="application/x-afp">
<images mode="b+w" bits-per-pixel="8" native="true"/>
@@ -601,7 +602,7 @@ The default value for the "rendering" se
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>
-<h1 id="when-it-does-not-work-wzxhzdk91wzxhzdk92">When it does not work <a id="When+it+does+not+work"></a></h1>
+<h2 id="when-it-does-not-work-wzxhzdk91wzxhzdk92">When it does not work <a id="When+it+does+not+work"></a></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>
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html Wed Oct 24 04:04:00 2012
@@ -330,11 +330,12 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/trunk/">Trunk</a></div> -->
- <div class="section-content"><p><subtitle>How to Embed FOP in a Java application</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="overview-wzxhzdk4wzxhzdk5">Overview <a id="overview"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-embedding">Apache(tm) FOP: Embedding</h1>
+<p><subtitle>How to Embed FOP in a Java application</subtitle><version>$Revision: 1298724 $</version></p>
+<h2 id="overview-wzxhzdk4wzxhzdk5">Overview <a id="overview"></a></h2>
<p>Review <a href="running.html">Running Apache™ FOP</a> for important information that applies to embedded applications as well as command-line use, such as options and performance.</p>
<p>To embed Apache™ FOP in your application, first create a new org.apache.fop.apps.FopFactory instance. This object can be used to launch multiple rendering runs. For each run, create a new org.apache.fop.apps.Fop instance through one of the factory methods of FopFactory. In the method call you specify which output format (i.e. MIME type) to use and, if the selected output format requires an OutputStream, which OutputStream to use for the results of the rendering. You can customize FOP's behaviour in a rendering run by supplying your own FOUserAgent instance. The FOUserAgent can, for example, be used to set your own document handler instance (details below). Finally, you retrieve a SAX DefaultHandler instance from the Fop object and use that as the SAXResult of your transformation.</p>
-<h1 id="the-api-wzxhzdk8wzxhzdk9">The API <a id="API"></a></h1>
+<h2 id="the-api-wzxhzdk8wzxhzdk9">The API <a id="API"></a></h2>
<p>FOP has many classes which express the "public" access modifier, however, this is not indicative of their inclusion into the public API. Every attempt will be made to keep the public API static, to minimize regressions for existing users, however, since the API is not clearly defined, the list of classes below are the generally agreed public API:
org.apache.fop.apps.*
org.apache.fop.fo.FOEventHandler
@@ -352,7 +353,7 @@ org.apache.fop.render.intermediate.IFPar
org.apache.fop.render.intermediate.IFSerializer
org.apache.fop.render.intermediate.IFUtil
org.apache.fop.render.intermediate.util.IFConcatenator</p>
-<h1 id="basic-usage-pattern-wzxhzdk10wzxhzdk11">Basic Usage Pattern <a id="basics"></a></h1>
+<h2 id="basic-usage-pattern-wzxhzdk10wzxhzdk11">Basic Usage Pattern <a id="basics"></a></h2>
<p>Apache FOP relies heavily on JAXP. It uses SAX events exclusively to receive the XSL-FO input document. It is therefore a good idea that you know a few things about JAXP (which is a good skill anyway). Let's look at the basic usage pattern for FOP...</p>
<p>Here is the basic pattern to render an XSL-FO file to PDF:</p>
<p>import org.apache.fop.apps.FopFactory;
@@ -405,7 +406,7 @@ Let's discuss these 5 steps in detail:</
</ul>
<p>If you're not totally familiar with JAXP Transformers, please have a look at the <a href="#examples">Embedding examples</a> below. The section contains examples for all sorts of use cases. If you look at all of them in turn you should be able to see the patterns in use and the flexibility this approach offers without adding too much complexity.</p>
<p>This may look complicated at first, but it's really just the combination of an XSL transformation and a FOP run. It's also easy to comment out the FOP part for debugging purposes, for example when you're tracking down a bug in your stylesheet. You can easily write the XSL-FO output from the XSL transformation to a file to check if that part generates the expected output. An example for that can be found in the <a href="#examples">Embedding examples</a> (See "ExampleXML2FO").</p>
-<h2 id="logging-wzxhzdk12wzxhzdk13">Logging # <a id="basic-logging"></a></h2>
+<h3 id="logging-wzxhzdk12wzxhzdk13">Logging # <a id="basic-logging"></a></h3>
<p>Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a> . While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.</p>
<p>By default, <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a> uses JDK logging (available in JDKs 1.4 or higher) as its backend. You can configure Commons Logging to use an alternative backend, for example Log4J. Please consult the <a href="http://commons.apache.org/logging/">documentation for Jakarta Commons Logging</a> on how to configure alternative backends.</p>
<p>As a result of the above we differentiate between two kinds of "logging":</p>
@@ -418,9 +419,9 @@ Let's discuss these 5 steps in detail:</
</li>
</ul>
<p>The use of "feedback" instead of "logging" is intentional. Most people were using log output as a means to get feedback from events within FOP. Therefore, FOP now includes an <code>event</code> package which can be used to receive feedback from the layout engine and other components within FOP <strong>per rendering run</strong> . This feedback is not just some text but event objects with parameters so these events can be interpreted by code. Of course, there is a facility to turn these events into normal human-readable messages. For details, please read on on the <a href="events.html">Events page</a> . This leaves normal logging to be mostly a thing used by the FOP developers although anyone can surely activate certain logging categories but the feedback from the loggers won't be separated by processing runs. If this is required, the <a href="events.html">Events subsystem</a> is the right approach.</p>
-<h2 id="processing-xsl-fo-wzxhzdk14wzxhzdk15">Processing XSL-FO # <a id="render"></a></h2>
+<h3 id="processing-xsl-fo-wzxhzdk14wzxhzdk15">Processing XSL-FO # <a id="render"></a></h3>
<p>Once the Fop instance is set up, call <code>getDefaultHandler()</code> to obtain a SAX DefaultHandler instance to which you can send the SAX events making up the XSL-FO document you'd like to render. FOP processing starts as soon as the DefaultHandler's <code>startDocument()</code> method is called. Processing stops again when the DefaultHandler's <code>endDocument()</code> method is called. Please refer to the basic usage pattern shown above to render a simple XSL-FO document.</p>
-<h2 id="processing-xsl-fo-generated-from-xmlxslt-wzxhzdk16wzxhzdk17">Processing XSL-FO generated from XML+XSLT # <a id="render-with-xslt"></a></h2>
+<h3 id="processing-xsl-fo-generated-from-xmlxslt-wzxhzdk16wzxhzdk17">Processing XSL-FO generated from XML+XSLT # <a id="render-with-xslt"></a></h3>
<p>If you want to process XSL-FO generated from XML using XSLT we recommend again using standard JAXP to do the XSLT part and piping the generated SAX events directly through to FOP. The only thing you'd change to do that on the basic usage pattern above is to set up the Transformer differently:</p>
<p>//without XSLT:
//Transformer transformer = factory.newTransformer(); // identity transformer</p>
@@ -454,9 +455,9 @@ Let's discuss these 5 steps in detail:</
</li>
</ul>
<p>There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in <a href="http://xml.apache.org/xalan-j/usagepatterns.html">Xalan Basic Usage Patterns</a> .</p>
-<h1 id="configuring-apache-fop-programmatically-wzxhzdk20wzxhzdk21">Configuring Apache FOP Programmatically <a id="config-internal"></a></h1>
+<h2 id="configuring-apache-fop-programmatically-wzxhzdk20wzxhzdk21">Configuring Apache FOP Programmatically <a id="config-internal"></a></h2>
<p>Apache FOP provides two levels on which you can customize FOP's behaviour: the FopFactory and the user agent.</p>
-<h2 id="customizing-the-fopfactory-wzxhzdk22wzxhzdk23">Customizing the FopFactory # <a id="fop-factory"></a></h2>
+<h3 id="customizing-the-fopfactory-wzxhzdk22wzxhzdk23">Customizing the FopFactory # <a id="fop-factory"></a></h3>
<p>The FopFactory holds configuration data and references to objects which are reusable over multiple rendering runs. It's important to instantiate it only once (except in special environments) and reuse it every time to create new FOUserAgent and Fop instances.</p>
<p>You can set all sorts of things on the FopFactory:</p>
<ul>
@@ -489,7 +490,7 @@ fopFactory.addElementMapping(myElementMa
fopFactory.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolverBoth the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used if no other URIResolver (for example on the FOUserAgent) resolved the URI first.</p>
</li>
</ul>
-<h2 id="customizing-the-user-agent-wzxhzdk24wzxhzdk25">Customizing the User Agent # <a id="user-agent"></a></h2>
+<h3 id="customizing-the-user-agent-wzxhzdk24wzxhzdk25">Customizing the User Agent # <a id="user-agent"></a></h3>
<p>The user agent is the entity that allows you to interact with a single rendering run, i.e. the processing of a single document. If you wish to customize the user agent's behaviour, the first step is to create your own instance of FOUserAgent using the appropriate factory method on FopFactory and pass that to the factory method that will create a new Fop instance:</p>
<p>FopFactory fopFactory = FopFactory.newInstance(); // Reuse the FopFactory if possible!
// do the following for each new rendering run
@@ -555,7 +556,7 @@ fopFactory.setUserConfig(cfg);</p>
<p>/<em> ..or.. </em>/</p>
<p>fopFactory.setUserConfig(new File("C:/Temp/mycfg.xml"));
The layout of the configuration file is described on the <a href="configuration.html">Configuration page</a> .</p>
-<h1 id="document-handlers-wzxhzdk28wzxhzdk29">Document Handlers <a id="documenthandlers"></a></h1>
+<h2 id="document-handlers-wzxhzdk28wzxhzdk29">Document Handlers <a id="documenthandlers"></a></h2>
<p>The document handlers are classes that inherit from <code>org.apache.fop.render.intermediate.IFDocumentHandler</code> . This is an interface for which a MIME type specific implementation can be created. This same handler is used either when XSL-FO is used as the input or when Intermediate Format is used. Since IF is output format agnostic, if custom fonts or other configuration information that affect layout (specific to a particular MIME type) are given then FOP needs that contextual information. The document handler provides that context so that when the IF is rendered, it is more visually consistent with FO rendering. The code below shows an example of how a document handler can be used to provide PDF configuration data to the IFSerializer.
IFDocumentHandler targetHandler = userAgent.getRendererFactory().createDocumentHandler(userAgent, MimeConstants.MIME_PDF);</p>
<p>IFSerializer ifSerializer = new IFSerializer(); //Create the IFSerializer to write the intermediate format
@@ -563,16 +564,16 @@ ifSerializer.setContext(new IFContext(us
ifSerializer.mimicDocumentHandler(targetHandler); //Tell the IFSerializer to mimic the target format</p>
<p>userAgent.setDocumentHandlerOverride(ifSerializer); //Make sure the prepared document handler is used
The rest of the code is the same as in <a href="#basics">Basic Usage Patterns</a> .</p>
-<h1 id="hints-wzxhzdk30wzxhzdk31">Hints <a id="hints"></a></h1>
-<h2 id="object-reuse-wzxhzdk32wzxhzdk33">Object reuse # <a id="object-reuse"></a></h2>
+<h2 id="hints-wzxhzdk30wzxhzdk31">Hints <a id="hints"></a></h2>
+<h3 id="object-reuse-wzxhzdk32wzxhzdk33">Object reuse # <a id="object-reuse"></a></h3>
<p>Fop instances shouldn't (and can't) be reused. Please recreate Fop and FOUserAgent instances for each rendering run using the FopFactory. This is a cheap operation as all reusable information is held in the FopFactory. That's why it's so important to reuse the FopFactory instance.</p>
-<h2 id="awt-issues-wzxhzdk34wzxhzdk35">AWT issues # <a id="awt"></a></h2>
+<h3 id="awt-issues-wzxhzdk34wzxhzdk35">AWT issues # <a id="awt"></a></h3>
<p>If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is initialised it uses certain classes in <code>java.awt</code> that intialise the Java AWT classes. This means that a daemon thread is created by the JVM and on Unix it will need to connect to a DISPLAY.</p>
<p>The thread means that the Java application may not automatically quit when finished, you will need to call <code>System.exit()</code> . These issues should be fixed in the JDK 1.4.</p>
<p>If you run into trouble running FOP on a head-less server, please see the <a href="graphics.html#batik">notes on Batik</a> .</p>
-<h2 id="getting-information-on-the-rendering-process-wzxhzdk36wzxhzdk37">Getting information on the rendering process # <a id="render-info"></a></h2>
+<h3 id="getting-information-on-the-rendering-process-wzxhzdk36wzxhzdk37">Getting information on the rendering process # <a id="render-info"></a></h3>
<p>To get the number of pages that were rendered by FOP you can call <code>Fop.getResults()</code> . This returns a <code>FormattingResults</code> object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.</p>
-<h1 id="improving-performance-wzxhzdk38wzxhzdk39">Improving performance <a id="performance"></a></h1>
+<h2 id="improving-performance-wzxhzdk38wzxhzdk39">Improving performance <a id="performance"></a></h2>
<p>There are several options to consider:</p>
<ul>
<li>
@@ -594,12 +595,12 @@ ifSerializer.mimicDocumentHandler(target
<p>You may also wish to consider trying to reduce <a href="http://xmlgraphics.apache.org/fop/trunk/running.html#memory">memory usage</a> .</p>
</li>
</ul>
-<h1 id="multithreading-fop-wzxhzdk40wzxhzdk41">Multithreading FOP <a id="multithreading"></a></h1>
+<h2 id="multithreading-fop-wzxhzdk40wzxhzdk41">Multithreading FOP <a id="multithreading"></a></h2>
<p>Apache FOP may currently not be completely thread safe. The code has not been fully tested for multi-threading issues, yet. If you encounter any suspicious behaviour, please notify us.</p>
<p>There is also a known issue with fonts being jumbled between threads when using the Java2D/AWT renderer (which is used by the -awt and -print output options). In general, you cannot safely run multiple threads through the AWT renderer.</p>
-<h1 id="examples-wzxhzdk42wzxhzdk43">Examples <a id="examples"></a></h1>
+<h2 id="examples-wzxhzdk42wzxhzdk43">Examples <a id="examples"></a></h2>
<p>The directory "{fop-dir}/examples/embedding" contains several working examples.</p>
-<h2 id="examplefo2pdfjava-wzxhzdk44wzxhzdk45">ExampleFO2PDF.java # <a id="ExampleFO2PDF"></a></h2>
+<h3 id="examplefo2pdfjava-wzxhzdk44wzxhzdk45">ExampleFO2PDF.java # <a id="ExampleFO2PDF"></a></h3>
<p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleFO2PDF.java?view=markup">example</a> demonstrates the basic usage pattern to transform an XSL-FO file to PDF using FOP.
<figure alt="Example XSL-FO to PDF" src="images/EmbeddingExampleFO2PDF.png"></figure></p>
<h2 id="examplexml2fojava-wzxhzdk48wzxhzdk49">ExampleXML2FO.java # <a id="ExampleXML2FO"></a></h2>
@@ -609,22 +610,22 @@ ifSerializer.mimicDocumentHandler(target
<p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2PDF.java?view=markup">example</a> demonstrates how you can convert an arbitrary XML file to PDF using XSLT and XSL-FO/FOP. It is a combination of the first two examples above. The example uses JAXP to transform the XML file to XSL-FO and FOP to transform the XSL-FO to PDF.
<figure alt="Example XML to PDF (via XSL-FO)" src="images/EmbeddingExampleXML2PDF.png"></figure>
The output (XSL-FO) from the XSL transformation is piped through to FOP using SAX events. This is the most efficient way to do this because the intermediate result doesn't have to be saved somewhere. Often, novice users save the intermediate result in a file, a byte array or a DOM tree. We strongly discourage you to do this if it isn't absolutely necessary. The performance is significantly higher with SAX.</p>
-<h2 id="exampleobj2xmljava-wzxhzdk56wzxhzdk57">ExampleObj2XML.java # <a id="ExampleObj2XML"></a></h2>
+<h3 id="exampleobj2xmljava-wzxhzdk56wzxhzdk57">ExampleObj2XML.java # <a id="ExampleObj2XML"></a></h3>
<p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleObj2XML.java?view=markup">example</a> is a preparatory example for the next one. It's an example that shows how an arbitrary Java object can be converted to XML. It's an often needed task to do this. Often people create a DOM tree from a Java object and use that. This is pretty straightforward. The example here, however, shows how to do this using SAX, which will probably be faster and not even more complicated once you know how this works.
<figure alt="Example Java object to XML" src="images/EmbeddingExampleObj2XML.png"></figure>
For this example we've created two classes: ProjectTeam and ProjectMember (found in xml-fop/examples/embedding/java/embedding/model). They represent the same data structure found in xml-fop/examples/embedding/xml/xml/projectteam.xml. We want to serialize to XML a project team with several members which exist as Java objects. Therefore we created the two classes: ProjectTeamInputSource and ProjectTeamXMLReader (in the same place as ProjectTeam above).</p>
<p>The XMLReader implementation (regard it as a special kind of XML parser) is responsible for creating SAX events from the Java object. The InputSource class is only used to hold the ProjectTeam object to be used.</p>
<p>Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. <a href="http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html">An older JAXP tutorial</a> ).</p>
-<h2 id="exampleobj2pdfjava-wzxhzdk60wzxhzdk61">ExampleObj2PDF.java # <a id="ExampleObj2PDF"></a></h2>
+<h3 id="exampleobj2pdfjava-wzxhzdk60wzxhzdk61">ExampleObj2PDF.java # <a id="ExampleObj2PDF"></a></h3>
<p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleObj2PDF.java?view=markup">example</a> combines the previous and the third to demonstrate how you can transform a Java object to a PDF directly in one smooth run by generating SAX events from the Java object that get fed to an XSL transformation. The result of the transformation is then converted to PDF using FOP as before.
<figure alt="Example Java object to PDF (via XML and XSL-FO)" src="images/EmbeddingExampleObj2PDF.png"></figure></p>
<h2 id="exampledom2pdfjava-wzxhzdk64wzxhzdk65">ExampleDOM2PDF.java # <a id="ExampleDOM2PDF"></a></h2>
<p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleDOM2PDF.java?view=markup">example</a> has FOP use a DOMSource instead of a StreamSource in order to use a DOM tree as input for an XSL transformation.</p>
-<h2 id="examplesvg2pdfjava-pdf-transcoder-example-wzxhzdk66wzxhzdk67">ExampleSVG2PDF.java (PDF Transcoder example) # <a id="ExampleSVG2PDF"></a></h2>
+<h3 id="examplesvg2pdfjava-pdf-transcoder-example-wzxhzdk66wzxhzdk67">ExampleSVG2PDF.java (PDF Transcoder example) # <a id="ExampleSVG2PDF"></a></h3>
<p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleSVG2PDF.java?view=markup">example</a> shows the usage of the PDF Transcoder, a sub-application within FOP. It is used to generate a PDF document from an SVG file.</p>
-<h2 id="exampleconcatjava-if-concatenation-example-wzxhzdk68wzxhzdk69">ExampleConcat.java (IF Concatenation example) # <a id="ExampleConcat"></a></h2>
+<h3 id="exampleconcatjava-if-concatenation-example-wzxhzdk68wzxhzdk69">ExampleConcat.java (IF Concatenation example) # <a id="ExampleConcat"></a></h3>
<p>This can be found in the <code>embedding.intermediate</code> package within the examples and describes how IF can be concatenated to produce a document. Because IF has been through FOPs layout engine, it should be visually consistent with FO rendered documents while allowing the user to merge numerous documents together.</p>
-<h2 id="final-notes-wzxhzdk70wzxhzdk71">Final notes # <a id="example-notes"></a></h2>
+<h3 id="final-notes-wzxhzdk70wzxhzdk71">Final notes # <a id="example-notes"></a></h3>
<p>These examples should give you an idea of what's possible. It should be easy to adjust these examples to your needs. Also, if you have other examples that you think should be added here, please let us know via either the fop-users or fop-dev mailing lists. Finally, for more help please send your questions to the fop-users mailing list.</p></div>
</div>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org