xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r813018 [17/24] - in /websites/staging/xmlgraphics/trunk/content: ./ fop/ fop/0.95/ fop/0.95/images/ fop/1.0/ fop/1.0/images/ fop/dev/ fop/dev/design/ fop/dev/fo/ fop/dev/svg/ fop/fo/ fop/trunk/ fop/trunk/images/
Date Sun, 15 Apr 2012 05:39:54 GMT
Added: websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,114 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: Testing</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP Development: Testing</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="build">"Build" Testing</h1>
+<p>Apache™ projects use an automated build tool called "gump" to create nightly builds from the SVN repository. Gump sends "nag" messages if the build fails. This can be considered a sort of basic test of the build process. To view the most recent logs of the gump builds:</p>
+<ul>
+<li>
+<p><a href="http://gump.cocoondev.org/xml-fop.html">Gump build for the Trunk</a> </p>
+</li>
+<li>
+<p><a href="http://gump.cocoondev.org/xml-fop-maintenance.html">Gump build for the Maintenance Branch</a> </p>
+</li>
+</ul>
+<h1 id="basic">Basic/API Testing</h1>
+<p>There is a group of basic API tests that are included in the build process. For these tests to occur, JUnit must be available to Ant (simply copy junit.jar into Ant's lib directory). The build will then report error(s) if the high-level APIs for Driver and the Transcoders fail. The tests do not check the output, but only ensure that something is generated and without exceptions.</p>
+<h1 id="layoutengine">Layout Engine Testing</h1>
+<p>The <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/test/layoutengine/"></a> directory in the repository contains a test suite for checking the functionality of Apache� FOP's layout engine. For information on how to create test cases for the layout engine, please visit the <a href="http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests">Wiki page</a> .</p>
+<h1 id="functional">Functional Testing</h1>
+<p><warning>The "functional" testing section on this page is currently inoperative.</warning></p>
+<h2 id="running-and-using-tests-runningandusingtests">Running and Using Tests ## {#Running+and+Using+Tests}</h2>
+<p>Testing is an important part of getting FOP to operate correctly and conform to the necessary standards.</p>
+<p>A testing system has been set up that works with as a build target when developing with FOP. A developer can run the tests after making changes to the code, the aim is to have the tests run to verfiy that nothing working has been broken.</p>
+<p>To setup the testing the developer must place a reference fop.jar in the "<cvs_repository>/test/reference/" directory. This jar will be dynamically loaded to create the reference output.</p>
+<h2 id="w3c-testsuite-w3ctestsuite">W3C TestSuite ## {#W3C+TestSuite}</h2>
+<p>The testing is set up so that you can download the testsuite from<jump href="http://www.w3.org/Style/XSL/TestSuite/">http://www.w3.org/Style/XSL/TestSuite/</jump>, unzip the file into the base directory of FOP. Then you can uncomment the lines in the build.xml file in the test target and itwill run through all the tests in the testsuite distribution.</p>
+<h2 id="writing-a-test-writingatest">Writing a Test ## {#Writing+a+Test}</h2>
+<p>A test belongs to one of a few catagories. A basic test should excercise one element in a number of situations such as changing a property. This should have at least one normal value, one border value and one invalid value. If the property can be of different types then this should also be included.</p>
+<p>A bug test is a test that is specifically aimed at a problem with FOP. That is, the test is not excercising the specification but rather a problem with FOP in handling a particular situation that is not exposed with the other testing.</p>
+<p>A system test is one that tests the abitlity of FOP to handle a number of different elements together.</p>
+<p>A test can consist of a complete fo document or a part of the document such as some elements that will be placed into the flow of a standard document.</p>
+<h2 id="submitting-a-test-submittingatest">Submitting a Test ## {#Submitting+a+Test}</h2>
+<p>If you have a test which you think would be useful you should supply the test and a diff to the appropriate test suite xml file. Make sure that the test works as would be expected against the current build.</p>
+<h2 id="how-testing-works-howtestingworks">How Testing Works ## {#How+Testing+Works}</h2>
+<p>The tests are stored in the "<svn_repository>/test" directory.</p>
+<p>You can run the tests by specifying the build target "test" ie:<br></br> <code>ant.sh test</code> (Unix)<br></br> <code>ant test</code> (Windows)<br></br></p>
+<p>This will then compare the current code in the local src directory to a specified release of FOP. Any differences between the current code and the output from the reference version will be reported. If the test previously passed then the test run will have failed.</p>
+<p>The testing is done by reading a test suite xml file, which corresponds to the standard testsuite.dtd supplied from w3c. This xml file contains a test xml file and an xsl file (which may simply copy the file). It also contains information such as if the test has passed and any comments.</p>
+<p>For FOP the testing is done by rendering all the testing documents using the XML renderer. The XML files are then compared to see if there are any differences.</p>
+<h2 id="svg-testing-svgtesting">SVG Testing ## {#SVG+Testing}</h2>
+<p>The testing of SVG is not part of this testing system. SVG is tested for its rendering accuracy by using the transcoding mechanism via <a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> . So that the only part that needs testing is how the SVG image is embedded inside the flow of the fo document.</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,154 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: Developer Tools</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP Development: Developer Tools</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<p>This page documents items that may be helpful to other developers, especially to those who are new to Apache™ FOP. Exhaustive treatment of these topics is better suited to other fora, but the information presented here is intended to deal with FOP-specific issues related to these tools, especially "gotchas", and to help developers get jump-started.</p>
+<h1 id="checklist">Developer Checklist</h1>
+<p>Here is a (probably not comprehensive) list of tools you will need to be a successful FOP developer:</p>
+<ul>
+<li>
+<p>A java IDE (see <a href="#ide">IDE</a> ).</p>
+</li>
+<li>
+<p>A Subversion client (see <a href="#svn">Subversion</a> ).</p>
+</li>
+<li>
+<p>Ant (see <a href="../trunk/compiling.html">Building FOP</a> ).</p>
+</li>
+<li>
+<p>checkstyle (see <a href="conventions.html#java-checkstyle">Checkstyle</a> on the conventions page).</p>
+</li>
+<li>
+<p>JUnit (see <a href="testing.html#basic">Basic Testing</a> ).</p>
+</li>
+</ul>
+<h1 id="general">General Developer Information</h1>
+<p>See <a href="http://www.apache.org/dev/contributors.html">the Apache Contributors Tech Guide</a> for useful information and links for Apache developers, including help with tools and procedures.</p>
+<h1 id="svn">Subversion (SVN)</h1>
+<h2 id="svn_general">General</h2>
+<p>Visit <a href="http://xmlgraphics.apache.org/repo.html">Apache XML Graphics Code Repositories</a> for useful information.</p>
+<p>You will need a SVN client to be able to gain access to the FOP repository. For general SVN information, visit <a href="http://subversion.tigris.org">Subversion Home</a> . A comprehensive list of clients for all operating systems and many IDEs can be found at <a href="http://subversion.tigris.org/project_links.html">the Subversion Links page</a> . For Microsoft Windows we recommend <a href="http://tortoisesvn.tigris.org">TortoiseSVN</a> . The command-line client that comes with Subversion is also very easy to use.</p>
+<h2 id="svn_download">Step-by-step instruction for downloading FOP using the SVN command-line client</h2>
+<p>On the command-line (Windows or Unix), simply run:</p>
+<p>svn co http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ fop-trunk</p>
+<p>This will download the FOP trunk into the directory "fop-trunk".</p>
+<h2 id="tortoisesvn_download">Step-by-step instructions for downloading FOP using TortoiseSVN (on Windows)</h2>
+<ul>
+<li>
+<p>Create a new, empty directory in a place of your choice.</p>
+</li>
+<li>
+<p>Right-click the new directory and select "SVN Checkout..." from the context menu.</p>
+</li>
+<li>
+<p>Enter <code>http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/</code> as the URL of the repository.</p>
+</li>
+<li>
+<p>Click "OK" and the download should begin.</p>
+</li>
+</ul>
+<h2 id="patches">Creating Patches</h2>
+<ul>
+<li>
+<p><code>cd</code> to a directory that contains all of the changes that you wish to include in the patch. To comprehend the entire distribution, <code>cd</code> to the top directory where you checked out the sources.</p>
+</li>
+<li>
+<p>Run: <code>svn up</code> to make sure the diff is created against the latest sources.</p>
+</li>
+<li>
+<p>Run: <code>svn diff &gt;mypatch.diff</code> <br></br>This will write the patch to the file "mypatch.diff".</p>
+</li>
+<li>
+<p>If you are running TortoiseSVN, you can select "Create Patch..." in the TortoiseSVN context menu.</p>
+</li>
+</ul>
+<h2 id="svn-doc">Documentation</h2>
+<ul>
+<li>
+<p>[online resource]<jump href="http://subversion.tigris.org">The Subversion Home Page</jump>.</p>
+</li>
+<li>
+<p>[electronic manual]<jump href="http://svnbook.red-bean.com">Version Control with Subversion</jump>(official Subversion manual). Note that this manual applies to the command-line version of SVN.</p>
+</li>
+<li>
+<p>[online resource]<jump href="http://subversion.tigris.org/project_links.html">Comprehensive list of links to documentation and Subversion clients and plugins.</jump></p>
+</li>
+</ul>
+<h1 id="ide">Integrated Development Environments (IDEs)</h1>
+<p>An IDE is not required, but will generally be found to be helpful, especially for serious debugging and refactoring.</p>
+<p>Borland's JBuilder 7/8 does not support Ant builds unless you have the Enterprise Edition (which is quite expensive). This causes problems with any code that is generated by the Ant build. First, you must run the Ant build before you can use the IDE. Second, when you are editing in the IDE, you must be editing the generated files, which means that you must make any changes to the source files in another editor. This is less serious for development on the trunk, but in the maintenance branch, all source files were "generated".</p>
+<p>Sun ONE Studio Four does support Ant, but seems to use a built-in version, and as of this writing chokes on the FOP build file, saying that it is not valid. There is awkward because there is no official DTD for Ant, and it may be merely an Ant version issue.</p>
+<p>Additional notes on setting up FOP within an IDE (ex. Eclipse) in the<fork href="http://wiki.apache.org/xmlgraphics-fop/FOPIDESetupGuide">Wiki</fork>.</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/download.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/download.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/download.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,147 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP: Downloading A Distribution</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP: Downloading A Distribution</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="dist-type">Binary or Source?</h1>
+<p>Most Apache™ FOP users will want to download the latest binary distribution, which is ready to run "out of the box." However, a source distribution will be preferable if you fall into one of the following categories:</p>
+<ul>
+<li>
+<p>You wish to modify FOP.</p>
+</li>
+<li>
+<p>You wish to use a version more recent than the latest release. For example, if you have read on the user mailing list that a bug has been fixed or a feature added that you are eager to try, you might download a source distribution from the SVN repository so that you don't have to wait for the next release.</p>
+</li>
+<li>
+<p>You wish to build a local copy of the API documentation (javadocs).</p>
+</li>
+</ul>
+<h1 id="binary">Binary Download</h1>
+<p>Binary distributions include "-bin" in their names, and can be downloaded from a <a href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop">FOP Distribution mirror</a> . Nightly builds of trunk code can be downloaded here: <a href="http://ci.apache.org/projects/xmlgraphics/fop/snapshots/">Nightly Snapshots</a> .</p>
+<h1 id="source">Source Download</h1>
+<p>There are several ways to obtain a source distribution. Please note that they are listed from least current to most current:</p>
+<ul>
+<li>
+<p>Download a released version from a <a href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop">FOP Distribution mirror</a> . Source distributions include "-src" in their names.</p>
+</li>
+<li>
+<p>Download a Subversion snapshot <a href="http://vc.apache.org/snapshots/fop/">here</a> . These snapshots are checked out from Subversion approximately every six hours, and have the GMT of their creation time embedded in their names.</p>
+</li>
+<li>
+<p>Download directly from the SVN repository. Anyone can do this using the <a href="http://xmlgraphics.apache.org/repo.html">Anonymous SVN Server</a> . By default, the code in SVN is up-to-the-minute, the same code that the developers are modifying. See the <a href="dev/tools.html#svn">SVN section of Developer Tools</a> for more information on using SVN.</p>
+</li>
+</ul>
+<table>
+<thead>
+<tr>
+<th>Latest Stable Release</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Repository URL</td>
+</tr>
+<tr>
+<td>Web view</td>
+</tr>
+<tr>
+<td>Previous Stable Release</td>
+</tr>
+<tr>
+<td>-------------------------</td>
+</tr>
+<tr>
+<td>Repository URL</td>
+</tr>
+<tr>
+<td>Web view</td>
+</tr>
+<tr>
+<td>Trunk</td>
+</tr>
+<tr>
+<td>-------</td>
+</tr>
+<tr>
+<td>Repository URL</td>
+</tr>
+<tr>
+<td>Web view</td>
+</tr>
+</tbody>
+</table>
+<p>With any source distribution, you will need to build FOP from the source files. For details please see the "Build" page on the documentation tab for the version you've downloaded.</p>
+<h1 id="archives">Archive Download</h1>
+<p>FOP Archive distributions are linked from the upper portion of the Apache FOP Download Mirror Page and can be downloaded from the FOP Archives <a href="http://archive.apache.org/dist/xmlgraphics/fop/binaries/">binaries</a> &amp; <a href="http://archive.apache.org/dist/xmlgraphics/fop/source/">source</a> links.</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/examples.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/examples.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/examples.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,203 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Examples</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP Examples</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="example-documents-using-apachetm-fop-exampledocumentsusingapachee284a2fop">Example Documents Using Apache™ FOP # {#Example+Documents+Using+Apache%E2%84%A2+FOP}</h1>
+<p>These examples have been rendered using Apache™ FOP:</p>
+<table>
+<thead>
+<tr>
+<th><caption>Generated examples</caption></th>
+<th>Description</th>
+<th>XSL-FO file</th>
+<th>PDF result</th>
+<th></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td></td>
+<td>default font characters</td>
+<td><a href="fo/fonts.fo">fonts.fo</a></td>
+<td><a href="fo/fonts.fo.pdf">fonts.fo.pdf</a></td>
+<td></td>
+</tr>
+</tbody>
+</table>
+<p>Other basic examples on the use of XSL-FO can be found in the FOP distribution in the subdirectory examples/fo. You can start transformation of all fo files into pdf files by running ant in this directory (only source distribution). The resulting test files can be found in examples/fo/tests</p>
+<p>At the moment the following files are part of the distribution:</p>
+<ul>
+<li>
+<p>simple.fo - a very simple file which gives use a first impression of the structure of an XSL-FO file</p>
+</li>
+<li>
+<p>normal.fo - a simple file showing the use of a 2 level of headings, normal text and a header.</p>
+</li>
+<li>
+<p>table.fo - some table examples</p>
+</li>
+<li>
+<p>list.fo - a short tutorial how to use list fo's and properties</p>
+</li>
+<li>
+<p>images.fo - shows how to embed GIF and JPEG images into the XSL-FO file using external-graphic.</p>
+</li>
+<li>
+<p>border.fo - a not so simple example how to use borders in tables</p>
+</li>
+<li>
+<p>extensive.fo - a longer test file containing a lot of different flow objects and properties. A good candidate to test your bugfix or new FOP code.</p>
+</li>
+<li>
+<p>leader.fo - shows different uses of fo:leader, p.e. as rule or in a table of content</p>
+</li>
+<li>
+<p>normalex.fo - shows the use of computed property values</p>
+</li>
+<li>
+<p>inhprop.fo - shows the use of inherited property values</p>
+</li>
+<li>
+<p>instream.fo - shows the use of fo:instream-foreign-object together with SVG</p>
+</li>
+<li>
+<p>textdeko.fo - shows the use of the property text-decoration</p>
+</li>
+<li>
+<p>readme.fo - uses an old version of FOP documentation for a longer example</p>
+</li>
+</ul>
+<p>Also, in the directory examples/fo/pagination you will find a suite of examples showing the use of XSL-FO pagination.</p>
+<p>Developers will find the first steps to a test suite for all implemented formatting objects and properties in test/xml in the source distribution.</p>
+<h1 id="images-examples-imagesexamples">Images Examples # {#Images+Examples}</h1>
+<p>Embedding images in FO:</p>
+<table>
+<thead>
+<tr>
+<th><caption>Images in FO</caption></th>
+<th>description</th>
+<th>fo file</th>
+<th>pdf result</th>
+<th></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td></td>
+<td>align in larger viewport</td>
+<td><a href="fo/align.fo">align.fo</a></td>
+<td><a href="fo/align.fo.pdf">align.fo.pdf</a></td>
+<td></td>
+</tr>
+<tr>
+<td></td>
+<td>align in smaller viewport</td>
+<td><a href="fo/align2.fo">align2.fo</a></td>
+<td><a href="fo/align2.fo.pdf">align2.fo.pdf</a></td>
+<td></td>
+</tr>
+<tr>
+<td></td>
+<td>scaling image</td>
+<td><a href="fo/size.fo">size.fo</a></td>
+<td><a href="fo/size.fo.pdf">size.fo.pdf</a></td>
+<td></td>
+</tr>
+</tbody>
+</table>
+<p>Look also into the directory examples/fo/svg. There you find some very extensive SVG examples.</p>
+<h1 id="instream-foreign-object-examples-instreamforeignobjectexamples">Instream Foreign Object Examples # {#Instream+Foreign+Object+Examples}</h1>
+<p>Instream Foreign Object images in FO, there are more on the <a href="dev/svg.html">SVG Page</a> :</p>
+<table>
+<thead>
+<tr>
+<th><caption>Embedding instream-foreign-object</caption></th>
+<th>description</th>
+<th>fo file</th>
+<th>pdf result</th>
+<th></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td></td>
+<td>embedding svg in viewport</td>
+<td><a href="fo/embed.fo">embed.fo</a></td>
+<td><a href="fo/embed.fo.pdf">embed.fo.pdf</a></td>
+<td></td>
+</tr>
+</tbody>
+</table></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/faq.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/faq.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/faq.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,472 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>FOP FAQ</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>FOP FAQ</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><h1 id="Questions">Questions</h1>
+<h2 id="part-general">1. Apache™ FOP: General questions</h2>
+<h3 id="fop-general">1.1. What is Apache™ FOP?</h3>
+<p>FOP is a print formatter for <a href="#XSLFO">XSL formatting objects</a> .</p>
+<p>It can be used to render an XML file containing XSL formatting objects into a page layout. The main target is PDF but other rendering targets are supported, such as AWT, PCL, text and direct printing.</p>
+<h3 id="fop-functions">1.2. What can I do with FOP?</h3>
+<p>FOP provides both an application and a library that converts an XSL FO document into paginated output.</p>
+<p>The FOP command line application can be directly used to transform XML into PDF, PostScript, PCL and other formats, there is also an AWT based viewer integrated.</p>
+<p>The library can be used in servlets and other Java applications.</p>
+<h3 id="fop-acronym">1.3. What does "FOP" stand for?</h3>
+<p>FOP is an acronym for <strong>F</strong> ormatting <strong>O</strong> bject <strong>P</strong> rocessor</p>
+<h3 id="fop-other-apache">1.4. How does FOP interact with other Apache Projects?</h3>
+<p>FOP is distributed with <a href="http://xml.apache.org/cocoon">Cocoon</a> as a PDF serializer for XSL (FO) documents.</p>
+<p><a href="http://xmlgraphics.apache.org/batik">Batik</a> can be used with FOP to <a href="http://xmlgraphics.apache.org/batik/svgrasterizer.html">transcode an SVG image</a> into a PDF document.</p>
+<h3 id="xsl-def">1.5. What is XSL?</h3>
+<p>XSL is a W3C standard concerned with publishing XML documents. It consists of two parts: <a href="#XSLT">XSLT</a> and <a href="#XSLFO">XSL-FO</a> . The acronym expands to e <strong>X</strong> tensible <strong>S</strong> tylesheet <strong>L</strong> anguage.</p>
+<h3 id="xslfo">1.6. What is XSL-FO?</h3>
+<p>XSLFO (aka XSL-FO) is an XML vocabulary that is used to specify a pagination and other styling for page layout output. The acronym “FO” stands for <strong>F</strong> ormatting <strong>O</strong> bjects. XSLFO can be used in conjunction with <a href="#XSLT">XSLT</a> to convert from any XML format into a paginated layout ready for printing or displaying.</p>
+<p>XSLFO defines a set of elements in XML that describes the way pages are set up. The contents of the pages are filled from flows. There can be static flows that appear on every page (for headers and footers) and the main flow which fills the body of the page.</p>
+<p>Synonyms: XSL FO, XSL (FO), XSL:FO, XSL-FO, Formatting Objects</p>
+<h3 id="XSLT">1.7. What is XSLT?</h3>
+<p>XSLT describes the transformation of arbitrary XML input into other XML (like XSLFO), HTML or plain text. The “T” comes from <strong>T</strong> ransformation. For historical reasons, a transformation is often also called a “style sheet”.</p>
+<p>Synonyms: XSL transformation, XSL:T, XSL style sheet.</p>
+<h3 id="when">1.8. When will feature X be implemented?</h3>
+<p>The short answer is "Don't ask." For more details, see <a href="gethelp.html#limitations">Understand FOP's Limitations</a> .</p>
+<h3 id="next-release">1.9. When is the next released planned?</h3>
+<p>When it's ready and the committers have enough time to go through the time-consuming process of creating a release. We released version 1.0 on 21 July 2010, and will release version 1.1 when we accumulated enough additions and bug fixes. If you want to speed up the process, consider <a href="dev/index.html#involved">contributing</a> to FOP.</p>
+<h3 id="redesign">1.10. Why did you redesign FOP?</h3>
+<p>The code redesign of FOP was necessary in order to be able to adress following issues:</p>
+<ul>
+<li>
+<p>Keeps and Breaks</p>
+</li>
+<li>
+<p>XSL-FO Compliance in general</p>
+</li>
+<li>
+<p>Process Files of Arbitrary Size</p>
+</li>
+<li>
+<p>Minimize Memory Use</p>
+</li>
+<li>
+<p>Table Layout</p>
+</li>
+</ul>
+<h3 id="contribute">1.11. How can I contribute?</h3>
+<p>There are numerous ways that you can help. They are outlined in the <a href="dev/index.html">Developer's Introduction</a> page.</p>
+<h2 id="part-running">2. Problems running FOP</h2>
+<h3 id="no-page-master">2.1. I get the error: [ERROR]: 'master-reference' for 'fo:page-sequence' matches no 'simple-page-master' or 'page-sequence-master'</h3>
+<p>FOP was changed to be in accordance with the latest standard (see <a href="resources.html#specs-xslfo">XSL standard</a> ).The page master for a fo:page-sequence is now referenced by the master-reference attribute. Replace the master-name attributes of your fo:page-sequence elements by master-reference attributes. You have to do this also for fo:single-page-master-reference, fo:repeatable-page-master-reference and fo:conditional-page-master-reference elements in you page master definitions.</p>
+<p>Update your FO documents and style sheets.</p>
+<h3 id="NoClassDefFound">2.2. I get a NoClassDefFound exception.</h3>
+<p>This is typically a problem with your classpath.</p>
+<p>If you are running FOP from the command line:</p>
+<ul>
+<li>
+<p>Use the command file <code>fop.bat</code> , <code>fop.cmd</code> or <code>fop.js</code> on MS Windows, or <code>fop</code> on Unix/Linux from the FOP distribution.</p>
+</li>
+<li>
+<p>If this doesn't help, check whether still all the jar files mentioned in the classpath in the <code>fop.bat</code> file are in their respective places.</p>
+</li>
+</ul>
+<p>If you run FOP embedded in your servlet, web application or other Java application, check the classpath of the application. Check the also the information pertaining to <a href="1.0/servlets.html#servlet-engine">servlet engines</a> for further hints.</p>
+<p>If you downloaded the source distribution, or a snapshop from the repository, remember you have to build the FOP jars first.</p>
+<h3 id="NoSuchMethodException">2.3. I get a NoSuchMethodException or a NoSuchFieldException exception.</h3>
+<p>This is usually caused by an older version of one of the FOP jars or old XML tools in the classpath. Check in particular for parser.jar, jaxp.jar, xml4j.jar or lotusxsl.jar.</p>
+<p>Incompatible versions of Batik may also cause this problem. Use the version of Batik that comes with FOP. It is not always possible to use a more recent version of Batik.</p>
+<h3 id="OutOfMemoryException">2.4. I get an OutOfMemoryException.</h3>
+<p>See <a href="1.0/running.html#memory">FOP Memory</a> .</p>
+<h3 id="MalformedURLException">2.5. I get a MalformedURLException.</h3>
+<p><anchor id="MalformedURL"></anchor>
+What you probably think of as "file names" are usually URLs, in particular the <code>src</code> attribute of fo:external-graphic.</p>
+<p>Because usage of URLs is growing, you should make yourself familiar with it. The relevant specification is <a href="http://www.rfc-editor.org/rfc/rfc2396.txt">RFC 2396</a> .</p>
+<p>In a nutshell, the correct syntax for an absolute file URL is <code>file:///some/path/file.ext</code> on Unix and <code>file:///z:/some/path/file.ext</code> on Windows systems. Note the triple slash, and also that only forward slashes are used, even on windows.</p>
+<p>A relative file URL starts with anything but a slash, and doesn't have the <code>file:</code> prefix, for example <code>file.ext</code> , <code>path/file.ext</code> or <code>../file.ext</code> . The string <code>file:path/file.ext</code> is <em>not</em> a relative URL, in fact, it isn't a valid URL at all. A relative URL is subject to a resolving process, which transforms it into an absolute URL.</p>
+<h3 id="NullPointerException">2.6. I get an "[ERROR]: null", or a NullPointerException.</h3>
+<p>This is often caused by an invalid FO document. Currently only very common errors are intercepted and produce a comprehensible error message. If you forgot container elements like <code>fo:page-sequence</code> or <code>fo:flow</code> and put blocks and inline elements directly as children of <code>fo:root</code> or <code>fo:page-sequence</code> , you'll only get a NullPointerException. Check whether your FO file has a proper structure. In some cases there are mandatory properties, like the master-reference in <code>fo:conditional-page-master-reference</code> , check also whether you got them right.</p>
+<p>You may find it helpful to use the <a href="#fo-validate">validation tools</a> to validate your FO document. This will catch most problems, but should not be relied upon to catch all.</p>
+<p>If you use XSLT, problems in your style sheet and in your source XML also can produce a NullPointerException. <a href="1.0/running.html#check-input">Run the transformation separately</a> to check for this, usually you'll get a detailed error message from the XSLT processor.</p>
+<p>If you turn on debugging with the " <code>-d</code> " option you may be able to see more detailed information.</p>
+<h3 id="not-implemented">2.7. FOP returns the message "[ERROR] object|property - 'x' is not implemented yet." When will it be implemented?</h3>
+<p>See FOP's Standards <a href="compliance.html">Compliance</a> page.</p>
+<h3 id="fop-hangs">2.8. FOP hangs. FOP does not exit.</h3>
+<p>The most likely reason is a known problem with the Java run time environment which is triggered by rendering SVGs. Suns JDK 1.4 does not have this problem. See also <a href="#svghangs">FOP does not exit if a SVG is included</a> .</p>
+<p>Another possibility is that FOP went into a non terminating loop. Usually this is indicated by lots of log messages of the form "[INFO]: [NNNN]" which indicate a new page has been started or <a href="#boxoverflow">box overflows</a> . After some time, FOP will crash with an OutOfMemoryException.</p>
+<p>If you called the FOP command line application from some other program, for example from Java using Runtime.exec(), it may hang while trying to write log entries to the output pipe. You have to read the FOP output regularly to empty the pipe buffer. It is best to avoid exec'ing FOP, use the library interface instead.</p>
+<h3 id="boxoverflow">2.9. FOP runs forever, writing lots of "&gt;" to the log.</h3>
+<p>There is something too large to fit into the intended place, usually a large image, a table whose rows are kept together or a block with a space-before or space-after larger than the page size. Catch the first page showing this phenomenon and check it. If it is not obvious which element causes the trouble, remove stuff until the problem goes away. Decrease the dimensions of the offending element or property, or increase the dimension of the enclosing element or container, or remove keep-with-* properties.</p>
+<h3 id="cannot-find-external-graphics">2.10. FOP cannot find a file for fo:external-graphics.</h3>
+<p>The src attribute of the <code>fo:external-graphics</code> element requires a URI, not a file name. See <a href="fo.html#external-resources">External Resources</a> for more information about specifying URIs.</p>
+<h3 id="fonts-not-found">2.11. FOP does not find my fonts.</h3>
+<p>Did you get: “Failed to read font metrics file C:\foo\arial.xml : File "C:\foo\arial.xml" not found”? The value for the metrics-file attribute in the user config file is actually an URL, not a file name. Use "file:///C:/foo/arial.xml" instead.</p>
+<p>If you used a relative URL, make sure your application has the working directory you expect. Currently FOP does not use the baseDir for resolving relative URLs pointing to font metric files.</p>
+<p>Try also setting the <a href="1.0/configuration.html#general-elements">font-base configuration</a> .</p>
+<h3 id="saxexception-mismatch">2.12. I get a SAXException: Mismatch: page-sequence vs. root (or similar).</h3>
+<p>The full exception usually looks similar to this:
+Mismatch: page-sequence (http://www.w3.org/1999/XSL/Format) vs. root
+        (http://www.w3.org/1999/XSL/Format)
+This exception is usually a follow-up error after another exception. Sometimes the original exception gets swallowed by Xalan's default <code>ErrorListener</code> (should be fixed in the latest Xalan release).</p>
+<p>The work-around is to set an explicit <code>ErrorListener</code> on the <code>Transformer</code> . The <code>ErrorListener</code> can be as simple as this:</p>
+<p>import javax.xml.transform.ErrorListener;
+import javax.xml.transform.TransformerException;</p>
+<p>public class DefaultErrorListener implements ErrorListener {</p>
+<div class="codehilite"><pre><span class="n">public</span> <span class="n">void</span> <span class="n">warning</span><span class="p">(</span><span class="n">TransformerException</span> <span class="n">exc</span><span class="p">)</span> <span class="p">{</span>
+    <span class="n">System</span><span class="o">.</span><span class="n">err</span><span class="o">.</span><span class="n">println</span><span class="p">(</span><span class="n">exc</span><span class="o">.</span><span class="n">toString</span><span class="p">());</span>
+<span class="p">}</span>
+
+<span class="n">public</span> <span class="n">void</span> <span class="n">error</span><span class="p">(</span><span class="n">TransformerException</span> <span class="n">exc</span><span class="p">)</span>
+        <span class="n">throws</span> <span class="n">TransformerException</span> <span class="p">{</span>
+    <span class="n">throw</span> <span class="n">exc</span><span class="p">;</span>
+<span class="p">}</span>
+
+<span class="n">public</span> <span class="n">void</span> <span class="n">fatalError</span><span class="p">(</span><span class="n">TransformerException</span> <span class="n">exc</span><span class="p">)</span>
+        <span class="n">throws</span> <span class="n">TransformerException</span> <span class="p">{</span>
+    <span class="n">throw</span> <span class="n">exc</span><span class="p">;</span>
+<span class="p">}</span>
+</pre></div>
+
+
+<p>}</p>
+<h3 id="faq-N1026C">2.13. The following message appears after recently upgrading FOP: "I/O exception while reading font cache (org.apache.fop.fonts.EmbedFontInfo; local class incompatible: stream classdesc serialVersionUID = -9075848379822693399, local class serialVersionUID = 8755432068669997367). Discarding font cache file."</h3>
+<p>This message is a warning that FOP failed to read from the Font cache. Which means any Font auto detection or Font directories will be re-scanned. So this failure doesn't break anything.</p>
+<p>To avoid the warning you can simply delete the old Font Cache file, which lives in ${base}\conf\font.cache (see <a href="1.0/configuration.html#general-elements">font-base configuration</a> ). Or you can disable Font Caching altogether using the option "use-cache."</p>
+<h2 id="part-output">3. Problems with FOP output</h2>
+<h3 id="leader-expansion">3.1. Leaders don't work in current FOP. Instead of filling the line, only three dots or a short ruler is output.</h3>
+<p>Leaders still work, in fact they work better than ever before. You'll just have to add <code>text-align="justify"</code> and/or <code>text-align-last="justify"</code> to the block with the leader. Be sure you haven't accidentally overridden the <code>leader-length.maximum="100%"</code> default value.</p>
+<p>Earlier versions of FOP used to expand a leader to fill the rest of the line unconditionally, anything following it, like page numbers in a TOC, was actually shifted beyond the right margin.</p>
+<p>The new implementation uses leader-length.optimum to determine where to break the line, and expands the leader only further if the line should be filled, as indicated by the text-align and text-align-last properties.</p>
+<p>Actually due to the fuzzyness of the specification both the old and the new method are conformant (although adding text after the expanded leader in the old variant never was).</p>
+<p>If you want to have a longer ruler or space in a non-justified line, you have to increase the leader-length.optimum property.</p>
+<h3 id="blank-page-between-page-sequences">3.2. Why does FOP insert a blank page between my page sequences?</h3>
+<p>This is because spec conformance has been improved.</p>
+<p>The <a href="http://www.w3.org/TR/xsl11/#force-page-count">force-page-count property</a> controls how a FO processor pads page sequences in order to get certain page counts or last page numbers. The default is " <code>auto</code> ". With this setting, if the next page sequence begins with an odd page number because you set the initial-page-number, and the current page sequence also ends with an odd page number, the processor inserts a blank page to keep odd and even page numbers alternating (similar for the case the current page sequence ends with an even page number and the next page sequence starts with an even page number).</p>
+<p>If you don't want to have this blank page, use <code>force-page-count="no-force"</code> .</p>
+<h3 id="graphic-not-displayed">3.3. Why is my graphic not rendered?</h3>
+<p>Most commonly, the external file is not being found by FOP. Check the following:</p>
+<ul>
+<li>
+<p>Empty or wrong baseDir setting.</p>
+</li>
+<li>
+<p>Spelling errors in the file name (including using the wrong case).</p>
+</li>
+<li>
+<p>Security Problems (i.e. the image could not be accessed because FOP is not allowed to read the file). This is especially a problem if the external file is retrieved over HTTP. Possible issues include security settings on the server, server configuration, and missing cookies or other authorization information. Any easy way to check this is to cut&amp;paste the source URL from the fo:external-graphic into the Location field of a browser <strong>on the machine where the FOP process will be running</strong> .</p>
+</li>
+</ul>
+<p>Other possibilities:</p>
+<ul>
+<li>
+<p>The image format is not supported or not supported completely. See <a href="1.0/graphics.html">FOP Graphics Formats</a> for a list of supported formats and related issues.</p>
+</li>
+<li>
+<p>The graphic may be too large to fit into the intended space.</p>
+</li>
+<li>
+<p>There may be something (static content) that is obscuring the graphic. (This is very rare).</p>
+</li>
+</ul>
+<h3 id="png-fails">3.4. My graphical images do not work properly.</h3>
+<p>See <a href="1.0/graphics.html">FOP Graphics Formats</a> for a list of supported graphics formats and related issues.</p>
+<h3 id="graphic-resolution">3.5. Why is my graphic rendered at a different resolution than it was created?</h3>
+<p>See <a href="1.0/graphics.html#resolution">Graphics Resolution</a> .</p>
+<h3 id="keep-with">3.6. Keep-with-next, keep-with-previous, keep-together don't work.</h3>
+<p>Current FOP releases have extensive support for these properties. The current release, FOP 1.0, still supports the values "always" and "never" only, no numerical values. There may be a few places where keep-* still don't work, this should be very rare.</p>
+<p>The concept is called “blind table”. The table is used for pure layout reasons and is not obvious in the output.</p>
+<p>An example of an image and the image caption to be kept together:
+<fo:table table-layout="fixed" width="100%">
+  <fo:table-column column-width="proportional-column-width(1)"/>
+  <fo:table-body>
+    <fo:table-row keep-with-next="always">
+      <fo:table-cell>
+        <fo:block>
+          <fo:external-graphic src="foo.jpg"/>
+        </fo:block>
+      </fo:table-cell>
+    </fo:table-row>
+    <fo:table-row>
+      <fo:table-cell>
+        <fo:block>Image Caption</fo:block>
+      </fo:table-cell>
+    </fo:table-row>
+  </fo:table-body>
+</fo:table>
+Consider upgrading to the latest version which supports keeps.</p>
+<h3 id="table-missing">3.7. My tables are missing, or missing their content.</h3>
+<p>Check for <code>fo:table-body</code> around the rows. Usually FOP will catch this problem.</p>
+<p>Also, the <code>fo:table-with-caption</code> element is not implemented, tables within such an element are dropped too. FOP generates an error message for this problem. Older DocBook style sheets generate <code>fo:table-with-caption</code> elements, so watch out.</p>
+<h3 id="cells-overflow">3.8. Text overflowing table cells and the like is not clipped. Long text flows into adjacent cells/block, obscuring stuff there.</h3>
+<p>Since the <code>overflow</code> property doesn't apply to table-cell, you can wrap the cell content in a block-container and specify <code>overflow="hidden"</code> there. Alternatively, if you have long words overflowing table cells, try to get them hyphenated. Artificial names like product identifications or long numbers usually aren't hyphenated. You can try special processing at XSLT level, like</p>
+<ul>
+<li>
+<p>clip long text,</p>
+</li>
+<li>
+<p>explicit wrapping+clipping,</p>
+</li>
+<li>
+<p>insert zero width spaces (U+200B or &#x200B;) to allow FOP to wrap.</p>
+</li>
+</ul>
+<p>Check the <a href="http://dpawson.co.uk/xsl">XSL FAQ</a> and the <a href="http://www.mulberrytech.com/xsl/xsl-list/">XSL list archive</a> for how to perform these tasks.</p>
+<h3 id="table-cell-wrap">3.9. The contents of table cells don’t wrap</h3>
+<p>You probably have <code>keep-together="always"</code> set on the table cell. See <a href="#keep-together">next question</a> .</p>
+<h3 id="keep-together">3.10. FOP behaves differently from earlier versions when keep-together="always" is set on table cells</h3>
+<p>Support for inline-level keeps has been added in FOP 0.95, and setting <code>keep-together="always"</code> also implicitly sets <code>keep-together.within-line="always"</code> , which forbids FOP to break the text into multiple lines. Set <code>keep-together.within-column="always"</code> on table-cell instead. It’s a good idea not to use the shorthand <code>keep-together="always"</code> at all!</p>
+<h3 id="row-height-constraint">3.11. FOP tells me: "The contents of row 1 are taller than they should be". What does that mean?</h3>
+<p>This is usually caused by setting a "height" on a table-row or table-cell and when the content is higher than the specified height. By setting "height" (a so-called corresponding property) you <a href="http://www.w3.org/TR/xsl11/#d0e4413">implicitely set</a> block-progression-dimension.minimum, block-progression-dimension.optimum and block-progression-dimension.maximum to the same value. You'll get some information about that in the warning message. Look for something like: "MinOptMax[min=opt=max=14000]".</p>
+<p>Assuming you set the height on the table-row to 14pt and your content is 75pt high, a constraint (maximum=14pt) is violated. Normally, you just want to make sure with the "height" property that the row has a minimum height. If that is so, the right solution is to specify block-progression-dimension.minimum="14pt" instead of height="14pt".</p>
+<h3 id="page-number-align">3.12. Page numbers are not properly right aligned.</h3>
+<p>This happens for <code>fo:page-number-citation</code> elements if the citation occurs before FOP formatted the requested page, usually in TOC or index pages. It is caused by the problem that FOP has to guess how much space the yet unknown page number will occupy, and usually the guesses are somewhat off.</p>
+<p>The most recent FOP releases should have this problem fixed. Check whether you can upgrade.</p>
+<h3 id="hyphenation-fails">3.13. Hyphenation does not work.</h3>
+<p>Make sure you have set the language and optionally the country attributes for an appropriate XSL-FO element (fo:page-sequence, fo:block or fo:character):
+<fo:page-sequence language="fi">
+See <a href="1.0/hyphenation.html#support">Hyphenation Support</a> for details and instructions on using hyphenation with FOP.</p>
+<p>Explicitly enable hyphenation for an appropriate XSL-FO element (fo:block, fo:character):
+<fo:block hyphenate="true"></p>
+<h3 id="indent-inheritance">3.14. When I use margins, my content in a nested table or block-containers gets indented twice. Is this a bug?</h3>
+<p>No, although you might easily think so. The problem has to do with property inheritance of the start-indent and end-indent properties to which the margin properties are mapped. Apache FOP strictly adheres to the XSL-FO specification here which many other commercial FO implementations don't do to better meet end-user expectations. You can make FOP behave like these if you set <code>setBreakIndentInheritanceOnReferenceAreaBoundary(true)</code> on the FOUserAgent. The better way is to reset <code>start-indent</code> and <code>end-indent</code> to "0pt" on table-body or block-container. For further details, please consult the <a href="http://wiki.apache.org/xmlgraphics-fop/IndentInheritance">Wiki page on Indent Inheritance</a> .</p>
+<h3 id="pdf-ps-java2d-differences">3.15. Why is the output of Java2D/AWT-based renderers different than, for example, PDF or PS?</h3>
+<p>If you render the same document once to a PNG or TIFF and once into a PDF, the output may not be the same, i.e. line breaks are different or lines may have different heights. The reason for this: The Java2D-based renderers use the font subsystem of Java2D/AWT. The PDF and PS renderers use FOP's own font subsystem which provides much better font metrics than Java2D. These can lead to different layout decisions when the same document is rendered with different renderers. An alternative approach to fix this problem might be available but it hasn't been tested, yet. See also the <a href="1.0/output.html#general-fonts">notes on fonts in the various output formats</a> .</p>
+<h2 id="part-embedding">4. Embedding FOP. Using FOP in a servlet.</h2>
+<h3 id="servlet">4.1. How do I use FOP in a servlet?</h3>
+<p>See <a href="1.0/servlets.html">Using FOP in a Servlet</a> .</p>
+<h3 id="servlet-with-xslt">4.2. How do I use FOP in a servlet with an XSLT transformation?</h3>
+<p>See <a href="1.0/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</a> .</p>
+<h3 id="servlet-xslt-params">4.3. How do I pass parameters to the XSLT transformation?</h3>
+<p>See <a href="1.0/servlets.html#xslt">Using FOP in a Servlet with XSLT Transformation</a> .</p>
+<h3 id="servlet-nonstd-fonts">4.4. How do I use my own fonts when running FOP from a servlet?</h3>
+<p>Declare the fonts in the <code>userconfig.xml</code> file as usual. See <a href="#usercfg">loading the user configuration file</a> for further details.</p>
+<h3 id="servlet-baseDir">4.5. How do I set the baseDir property in a servlet environment?</h3>
+<p>See <a href="1.0/embedding.html#config-internal">Setting the Configuration Programmatically</a> .</p>
+<h3 id="usercfg">4.6. How do I use a user configuration file from a servlet?</h3>
+<p>See <a href="1.0/embedding.html#config-external">Using a Configuration File in an Embedded App</a> .</p>
+<h3 id="servlet-NoClassDefFound">4.7. I keep getting NoClassDefFound and other exceptions. How do I get FOP working for various servlet engines?</h3>
+<p>See <a href="1.0/servlets.html#servlet-engine">Servlet Engines</a> .</p>
+<h3 id="multithreaded">4.8. Can FOP be used in multithreaded environments?</h3>
+<p>See <a href="1.0/embedding.html#multithreading">Multithreading FOP</a> .</p>
+<h2 id="part-svg">5. SVG specific questions</h2>
+<h3 id="svg-text">5.1. The rendering of SVG text in my PDF is of poor quality. Can I control this?</h3>
+<p>See <a href="1.0/graphics.html#svg-pdf-text">Placing SVG Text into PDF</a> .</p>
+<h3 id="svg-headless">5.2. How do I use FOP with SVG on headless servers?</h3>
+<p>See <a href="1.0/graphics.html#batik">FOP: Graphics (Batik)</a> .</p>
+<h3 id="svghangs">5.3. FOP does not exit if a SVG is included.</h3>
+<p>Applies to older FOP versions and JDK 1.3 and older. That's because there is an AWT thread hanging around. The solution is to put a System.exit(0) somewhere.</p>
+<h3 id="svg-url">5.4. I have problems with SVG referring to gradients etc. using "uri(#stuff)". I get a MalformedURLException.</h3>
+<p>This is really a "resolving relative URI" problem with some twists. The problem is that the <code>#stuff</code> URL fragment identifier is resolved within the current SVG document. So the reference must be valid within the XML subset and it cannot reference other SVG documents in the same XML file. Some options to try:</p>
+<ul>
+<li>
+<p>Put the SVG into a separate file and use it with fo:external-graphics.</p>
+</li>
+<li>
+<p>Use a separate SVG file which contains only the gradient (and perhaps other SVG stuff you want to reference) and point an absolute URL to it: <code>fill="url(file:///c:/refstuff/grad.svg#PurpleToWhite)"</code> .</p>
+</li>
+<li>
+<p>Same as above but use a relative URL: <code>fill="url(grad.svg#PurpleToWhite)"</code> . This may be easier to deploy.</p>
+</li>
+<li>
+<p>Make sure that the reference is valid in the current SVG document.</p>
+</li>
+</ul>
+<p>In any case, the referenced stuff has to be pointed to by an URL. It doesn't necessarily have to be a file URL, HTTP should also work. Also, expect a performance hit in all cases, because another XML file has to be retrieved and parsed.</p>
+<p>Ultimately, both FOP and especially Batik should be fixed to make your code work as expected, but this will not only take some time but also some effort by a standard committee in order to make the semantics of this kind of references in embedded SVG clearer.</p>
+<p>See also <a href="#MalformedURL">MalformedURLException</a> </p>
+<h3 id="svg-scaling">5.5. Why is my SVG rendered at a size different from that specified in my fo:external-graphic element?</h3>
+<p>See <a href="1.0/graphics.html#svg-scaling">SVG Scaling</a> .</p>
+<h3 id="svg-attribute-required">5.6. FOP fails with something like "The attribute "width" of the element <rect> is required". What's wrong?</h3>
+<p>This phenomenon is not a bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be fixed in the next release. In the latest release of Apache Xalan-J, the bug is already fixed. It only occurs in the Xalan version bundled with Sun's JVM, because Sun uses a rather old version.</p>
+<p>Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with <code>"null"</code> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty string as the namespace URI parameter for <code>org.w3c.dom.Element.setAttributeNS()</code> .</p>
+<p>Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</a> , i.e. you must place Xalan-J in the <code>"lib/endorsed"</code> directory of your JRE.</p>
+<h2 id="part-pdf">6. PDF specific (includes Acrobat peculiarities)</h2>
+<h3 id="pdf-embed-font">6.1. How do I embed fonts in PDF?</h3>
+<p>See the <a href="1.0/fonts.html">Fonts</a> page for information about embedding fonts.</p>
+<h3 id="pdf-characters">6.2. Some characters are not displayed, or displayed incorrectly, or displayed as “#”.</h3>
+<p>This usually means the selected font doesn't have a glyph for the character.</p>
+<p>The standard text fonts supplied with Acrobat Reader have mostly glyphs for characters from the ISO Latin 1 character set. For a variety of reasons, even those are not completely guaranteed to work, for example you can't use the fi ligature from the standard serif font. Check the <a href="1.0/output.html#pdf-fonts">overview</a> for the default PDF fonts.</p>
+<p>If you use your own fonts, the font must have a glyph for the desired character. Furthermore the font must be available on the machine where the PDF is viewed or it must have been embedded in the PDF file. See <a href="1.0/fonts.html">embedding fonts</a> .</p>
+<p>For most symbols, it is better to select the symbol font explicitely, for example in order to get the symbol for the mathematical empty set, write:
+<fo:inline font-family="Symbol">&#x2205;</fo:inline>
+The "#" shows up if the selected font does not define a glyph for the required character, for example if you try:
+<fo:inline font-family="Helvetica">&#x2205;</fo:inline></p>
+<h3 id="pdf-postprocess">6.3. What tools are available for post-processing my PDF document?</h3>
+<p>See <a href="1.0/output.html#pdf-postprocess">PDF Post-processing</a> .</p>
+<h3 id="pdf-security">6.4. How do I add security features (encryption, disable printing) to my PDF document?</h3>
+<p>See <a href="1.0/pdfencryption.html">PDF Encryption</a> . See also <a href="1.0/output.html#pdf-postprocess">PDF Post-processing</a> .</p>
+<h3 id="pdf-doc-properties">6.5. How do I add document properties (title, author, etc.) to my PDF document?</h3>
+<p>See <a href="1.0/metadata.html">Metadata</a> .</p>
+<h3 id="pdf-watermark">6.6. How do I add watermarks to my PDF document?</h3>
+<p>See <a href="1.0/output.html#pdf-watermark">PDF Watermarks</a> .</p>
+<h3 id="pdf-print-contortion">6.7. The PDF is printed contorted!</h3>
+<p>Check the paper size in Acrobat settings and the "fit to page" print setting. Contorted printing is often caused by a mismatched paper format, for example if the setting is "US Letter" but the PDF was made for A4. Sometimes also the printer driver interferes, check its settings too.</p>
+<h3 id="pdf-bookmark-display">6.8. How do I control the Acrobat bookmark display?</h3>
+<p>FOP supports the starting-state property of the XSL 1.1 <a href="http://www.w3.org/TR/xsl11/#fo_bookmark">fo:bookmark</a> element which can be used for this. The color, font-style and font-weight properties on <a href="http://www.w3.org/TR/xsl11/#fo_bookmark-title">fo:bookmark-title</a> are not yet supported, though.</p>
+<h3 id="acrobat-anti-aliasing">6.9. How can I get rid of strange single-pixel lines inside table borders or between table cells in Adobe Acrobat?</h3>
+<p>Since Apache FOP supports the collapsed border model, every border segment consists of two separate shapes. This is due to the fact that each side of the border segment can have a different color. Now, Adobe Acrobat may display thin (1 pixel wide) lines inside the border segment or sometimes even between to adjacent colored rectangles making up the background of a block or table cell. This effect is due to the way Adobe Acrobat does anti-aliasing. Adobe's algorithm seems to cause these artifacts. Other PDF viewers don't have that problem. Or at least we haven't had any reports in that direction.</p>
+<p>First of all, these artifacts do not appear in print since no anti-aliasing is done by Adobe Acrobat in this case (except maybe if you tell Acrobat to print the page as a bitmap in which case Adobe fully composes the page itself). So, if the artifacts appear on screen, it doesn't mean they have to appear in print, too.</p>
+<p>To get rid of the artifacts, you can call up the "Preferences" dialog of Adobe Acrobat and select the tab "Page display". Enabling "Enhance thin lines" may help in some situations. Otherwise, you can disable "Smooth line art". You may have to disable "Use 2D graphics acceleration", too, so you can disable "Smooth line art" in the first place.</p>
+<p>Here an example of how the effect can look like (left: anti-aliasing on, right: anti-aliasing off):
+<figure alt="Left: anti-aliasing on, Right: off" src="images/acrobat-anti-aliasing-artifacts.png"></figure>
+Unfortunately, it is not possible to control the above settings from within the PDF file. The user has to change these settings himself. Improving FOP to avoid this kind of problem would be possible although rather hard to achieve because we'd need to add a considerable amount of code to combine the various line segments. Something like that has been tried already years ago showing that this is a tricky task. Also, the improvement may not justify the amount of effort required.</p>
+<h2 id="part-iex">7. IEx specific stuff</h2>
+<h3 id="iex-servlet-multiple">7.1. The FOP servlet is called multiple times!</h3>
+<p>This is a problem of Internet Explorer requesting the content several times. Please see the <a href="1.0/servlets.html#ie">notes on Internet Explorer</a> for more information.</p>
+<h3 id="iex-pdf-print-from-browser">7.2. How do I print PDF directly from the browser?</h3>
+<p>It depends whether you mean "printing to a printer under control of the server" or "printing on the client's printer".</p>
+<p>For the first problem, look at the print servlet in the FOP examples. You'll have to gather any printer settings in a HTML form and send it to the server.</p>
+<p>For the second task, you can use some client side script to start Acrobat Reader in print mode, or use a Java applet based on the FOP print servlet. This depends heavily on the client installation and should not be relied on except in tightly controlled environments.</p>
+<p>See also <a href="http://marc.theaimsgroup.com/?l=fop-dev&amp;m=101065988325115&amp;w=2">http://marc.theaimsgroup.com/?l=fop-dev&amp;m=101065988325115&amp;w=2</a> </p>
+<h2 id="part-input">8. General questions regarding XSLT, XSLFO, and basic XML</h2>
+<h3 id="fo-center">8.1. (FO) How do I vertically center an image or a table (or whatever)?</h3>
+<p>See <a href="fo.html#fo-center-vertical">XSL-FO Vertical Centering</a> .</p>
+<h3 id="fo-center-table-horizon">8.2. (FO) How do I center a table horizontally?</h3>
+<p>See <a href="fo.html#fo-center-table-horizon">XSL-FO Horizontal Centering (Tables)</a> .</p>
+<h3 id="fo-page-outer">8.3. (FO) How to get page numbers printed on the "outer side" of the page (for books, for example)?</h3>
+<p>See <a href="fo.html#fo-oddeven">Recto/Verso Static Content Differences</a> .</p>
+<h3 id="oddeven">8.4. (FO) How do I use different static content for odd and even pages?</h3>
+<p>See <a href="fo.html#fo-oddeven">Recto/Verso Static Content Differences</a> .</p>
+<h3 id="fo-first-page-header">8.5. (FO) How do I get a special header on the first page?</h3>
+<p>See <a href="fo.html#fo-first-page">Making the First Page Special</a> .</p>
+<h3 id="fo-omit-headers">8.6. (FO) How do I omit my headers on a blank page? How do I write "This page is left blank" on an intentionally blank page?</h3>
+<p>See <a href="fo.html#fo-blank-pages">Blank Pages</a> .</p>
+<h3 id="fo-special-symbols">8.7. (FO) How do I print an Euro sign, a checkbox or other some other special symbols?</h3>
+<p>See <a href="fo.html#xml-special-chars">Special Characters</a> .</p>
+<h3 id="fo-preformat">8.8. (FO) How do I keep linebreaks and hard spaces? How do I get preformatted text displayed as expected?</h3>
+<p>See <a href="fo.html#fo-preformat">Preformatting Content</a> .</p>
+<h3 id="fo-total-pages">8.9. (FO) How do I print the total number of pages, for example "page 1 of 12"</h3>
+<p>See <a href="fo.html#fo-total-pages">Total Document Pages</a> .</p>
+<h3 id="fo-region-overlap">8.10. (FO) The header overlaps body content. The body extends into the footer.</h3>
+<p>See <a href="fo.html#fo-region-align">Aligning Regions</a> .</p>
+<h3 id="fo-lines">8.11. (FO) How do I get lines in the document, as separators, side bars or folding marks?</h3>
+<p>See <a href="fo.html#fo-lines">Drawing Lines</a> .</p>
+<h3 id="fo-validate">8.12. (FO) How do I validate my FO document?</h3>
+<p>See <a href="fo.html#fo-validate">Validating XSL-FO</a> .</p>
+<h3 id="xml-non-breaking-space">8.13. (XML) How do I get a non-breaking space in FO? There are complaints about &nbsp;.</h3>
+<p>See <a href="fo.html#xml-special-chars">XML Special Characters</a> .</p>
+<h3 id="xml-undefined-entities">8.14. (XML) How do I enter special characters in XML? There are complaints about undefined entities, such as &uuml;, which work in HTML.</h3>
+<p>See <a href="fo.html#xml-special-chars">XML Special Characters</a> .</p>
+<h3 id="xml-illegal-entities">8.15. (XML) There are complaints about illegal characters and entities in the input.</h3>
+<p>See <a href="fo.html#xml-entity-chars">Using HTML Character Names</a> .</p>
+<h3 id="xml-illegal-chars">8.16. (XML) There are complaints about illegal bytes or characters in the input. There are odd characters in the result.</h3>
+<p>See <a href="fo.html#xml-encoding">XML Encoding Issues</a> .</p>
+<h3 id="xslt-current-date">8.17. (XSLT) How can I use the current date and time in my document?</h3>
+<p>See <a href="fo.html#xslt-date">Current Date and Time</a> .</p>
+<h3 id="xhtml-to-pdf">8.18. Can I use FOP to convert XHTML or HTML files to PDF?</h3>
+<p>You will get better results if you transform your source XML directly into XSLFO. It is tempting to use the XML-&gt;XHTML-&gt;XSLFO approach, because this apparently means there's only one transformation to maintain, but XHTML and publishing grade PDF are dissimilar enough that an "generic" XHTML-&gt;XSLFO(PDF) usually wont cut it, because the XHTML already lacks information from the original XML. It may be worthwhile to go from the source XML to an intermediate custom XML which on one hand is close enough to representation to allow simple transformation to either XHTML or XSLFO for most of the structure, but on the other hand retains enough semantic from the original XML that elements which must be handled differently in the two representations can be handled differently. Setting this up requires experience and most likely extensive prototyping.</p>
+<h3 id="xhtml-to-pdf2">8.19. I know it may be a bad idea to use FOP to convert XHTML or HTML files to PDF, but I want to do it anyway. Are there any tools available to help me?</h3>
+<p>The <a href="resources.html">FOP Resources page</a> has links to a tool called <a href="http://html2fo.sourceforge.net/">html2fo</a> which can be used to make such a transformation. In addition, there are tools on the Antenna House <a href="http://www.antennahouse.com/XSLsample/XSLsample.htm">XSL-FO Tutorial and Sample</a> page.</p>
+<h2 id="dev-help">9. Development-related Questions.</h2>
+<h3 id="doc-mgt">9.1. Where can I learn how the FOP docs and web site are built?</h3>
+<p>See FOP <a href="dev/doc.html">Doc Management</a> . ;-)</p>
+<h2 id="part-help">10. General suggestions. How to solve problems.</h2>
+<h3 id="bugs">10.1. I think I have found a bug in FOP. What should I do?</h3>
+<p>See <a href="bugs.html">the Bugs page</a> for information about bugs already reported and how to report new ones.</p>
+<h3 id="postquestions">10.2. I have questions that are not addressed in this FAQ. Where should I post them?</h3>
+<ul>
+<li>
+<p>If your question is a development-related question, please see the <a href="dev/faq.html">Developer FAQs</a> .</p>
+</li>
+<li>
+<p>If you have a runtime exception or other runtime problem:</p>
+<ul>
+<li>
+<p>double-check the <a href="#part-running">Runtime FAQs</a> .</p>
+</li>
+<li>
+<p>ClassNotFoundException, NoSuchMethodException and NoSuchFieldException problems are almost always a problem with the local environment. Try to get local help first.</p>
+</li>
+<li>
+<p>Check <a href="bugs.html#issues_existing">Reported Issues</a> to see if this is a known problem.</p>
+</li>
+<li>
+<p>If none of the above apply, post a question to the fop-dev mailing list.</p>
+</li>
+</ul>
+</li>
+<li>
+<p>In the case where something works properly with another formatter, (AntennaHouse, PassiveTex, etc.) but doesn't work with FOP, please check theRelease Notes, the <a href="compliance.html">FOP Standards Compliance</a> document, and the remaining FAQ in this document. If not found there, look at the list of <a href="bugs.html#issues_existing">Bugs Already Reported</a> . If not found there, please post a question on the fop-user mailing list or <a href="bugs.html#issues_new">Open a New Bug</a> .</p>
+</li>
+<li>
+<p>Question about how to use FOP, how to perform certain tasks with FOP or how to integrate FOP into another application should be posted to fop-user.</p>
+</li>
+<li>
+<p>XSLT specific stuff sould go to the <a href="http://www.mulberrytech.com/xsl/xsl-list/">XSL list</a> . This includes problems with the language and XSLT HOW-TOs.</p>
+</li>
+<li>
+<p>Problems specific to a certain XSLT processor, like Xalan, Saxon or MSXML, should be handled by processor specific lists. This includes problems with deployment, processor specific extensions, suspected bugs and processor specific APIs. Note that JDK 1.4 comes with an XML parser and an XSLT processor which are older versions of Xerces and Xalan, respectively, and both have a number of annoying bugs. See http://java.sun.com/developer/EJTechTips/2003/tt0311.html and http://java.sun.com/j2se/1.4.2/docs/guide/standards/ (or similar pages for later Java releases) for some hints on how to use more recent versions or other packages instead.</p>
+</li>
+<li>
+<p>Problems with servlet containers should be asked on the vendor specific lists for these software packages.</p>
+</li>
+<li>
+<p>More general questions regarding Java, including deployment, Java APIs, classpath issues and property definitions should be redirected to an appropriate Java specific list.</p>
+</li>
+</ul></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>



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


Mime
View raw message