xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r841071 [1/2] - in /websites/staging/xmlgraphics/trunk/content: ./ batik/ batik/dev/ batik/using/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Fri, 07 Dec 2012 16:08:12 GMT
Author: buildbot
Date: Fri Dec  7 16:08:03 2012
New Revision: 841071

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/batik/dev/test.html
    websites/staging/xmlgraphics/trunk/content/batik/uses.html
    websites/staging/xmlgraphics/trunk/content/batik/using/extending.html
    websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/knownissues_overview.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/releaseNotes_1.0.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/accessibility.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/design/breakpos.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/design/pdf-library.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/design/renderers.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/design/svg.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/implement.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html
    websites/staging/xmlgraphics/trunk/content/fop/examples.html
    websites/staging/xmlgraphics/trunk/content/fop/knownissues.html
    websites/staging/xmlgraphics/trunk/content/fop/status.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/complexscripts.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/repo.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Dec  7 16:08:03 2012
@@ -1 +1 @@
-1418341
+1418371

Modified: websites/staging/xmlgraphics/trunk/content/batik/dev/test.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/dev/test.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/dev/test.html Fri Dec  7 16:08:03 2012
@@ -182,7 +182,7 @@ $(document).ready(function () {
 <p>The intent for the test infrastructure is that it grows along with Batik and keeps monitoring the health of the code base.</p>
 <p>While the test suites in the infrastructure will be run every day by build/test machines, they are also intended to help the commiters and developers get confident that their code modifications did not introduce regressions.</p>
 <h2 id="infrastructure">The test infrastructure</h2>
-<h3 id="high-level-interfaces-high-levelinterfaces">High-level interfaces {#High-level+interfaces}</h3>
+<h3 id="High-level-interfaces">High-level interfaces</h3>
 <p>The following are the high level interfaces in the infrastructure.</p>
 <p><a href="../javadoc/org/apache/batik/test/Test.html">Test</a>
 :
@@ -196,7 +196,7 @@ A <code>TestSuite</code> is a test aggre
 <p><a href="../javadoc/org/apache/batik/test/TestReportProcessor.html">TestReportProcessor</a>
 :
 A <code>TestReportProcessor</code> is used to analyze a <code>TestReport</code>. A specific implementation can choose to create graphs, send an email or write an HTML file.</p>
-<h3 id="default-implementations-defaultimplementations">Default implementations {#Default+implementations}</h3>
+<h3 id="Default-implementations">Default implementations</h3>
 <p>The test infrastructure comes with a number of default implementations for the interfaces described above. Specifically:</p>
 <p><a href="../javadoc/org/apache/batik/test/AbstractTest.html">AbstractTest</a>
 :
@@ -213,12 +213,12 @@ This class is a sample <code>TestReportP
 <p><a href="../javadoc/org/apache/batik/test/TestReportMailer.html">TestReportMailer</a>
 :
 This is another implementation of the <code>TestReportProcessor</code> interface that emails a test report to a list of destination e-mail addresses.</p>
-<h3 id="xml-implementations-xmlimplementations">XML implementations {#XML+implementations}</h3>
+<h3 id="XML-implementations">XML implementations</h3>
 <p>The test infrastructure is using XML-out (and XML-in too, see the <a href="#runningATestSuite">Running a test suite</a> section) as a favorite way to generate test reports. The <a href="../javadoc/org/apache/batik/test/XMLTestReportProcessor.html">XMLTestReportProcessor</a> implementation of the <code>TestReportProcessor</code> interface. It outputs reports in XML in a configurable directory.</p>
 <p>The <code>XMLTestReportProcessor</code> can notify an <a href="../javadoc/org/apache/batik/test/XMLReportConsumer.html">XMLReportConsumer</a> when it has created a new report. There is one implementation of that interface that can run an XSL stylesheet on the XML report (e.g., to generate an HTML report), called <a href="../javadoc/org/apache/batik/test/XSLXMLReportConsumer.html">XSLXMLReportConsumer</a>. This is used by the <code>regard</code> rule in the Batik build to produce an HTML report for the default regression test suite.</p>
 <h2 id="managingATestSuite">Managing test suites</h2>
 <p>The infrastructure is designed to make it easy to create, update and modify test suites. This section describes how to describe a set of tests to be run and how to actually run that test suite.</p>
-<h3 id="describing-a-test-suite-describingatestsuite">Describing a test suite {#Describing+a+test+suite}</h3>
+<h3 id="Describing-a-test-suite">Describing a test suite</h3>
 <p>Test suites can be described in XML (XML-in refered to earlier in this document). The general format for describing a test suite is:</p>
 <div class="codehilite"><pre><span class="nt">&lt;testSuite</span> <span class="na">id=</span><span class="s">&quot;testSuiteA&quot;</span> <span class="na">name=</span><span class="s">&quot;MyFavoriteTestSuite&quot;</span><span class="nt">&gt;</span>
   <span class="c">&lt;!-- Set of tests to be run --&gt;</span>
@@ -318,7 +318,7 @@ This is another implementation of the <c
 <h2 id="regard">regard: the Batik regression test suite</h2>
 <p>The regard test suite contains all the regression tests for the Batik project. The <code>regard</code> tool is a specific test suite description, <code>regard.xml</code> (which you can find in the <code>test-resources/org/apache/batik/test</code> directory). That file contains a set of test suite files which sould be run.</p>
 <p>The following describes how to use the regard tool and some of the most important tests in the regard test suite.</p>
-<h3 id="running-regard-runningregard">Running regard {#Running+regard}</h3>
+<h3 id="Running-regard">Running regard</h3>
 <p>The regard tool lets you run either all the tests or any specific test you want in the test suite. To run all the tests in the regard test suite, type the following at the command line, for Windows:</p>
 <p>build regard</p>
 <p>and for Unix:</p>
@@ -328,7 +328,7 @@ This is another implementation of the <c
 <p>For example:</p>
 <p>build.sh regard unitTesting.ts batikFX.svg</p>
 <p>will run all the tests with an ID containing <code>unitTesting.ts</code> (i.e., all the test selection unit testing, see <code>test-resources/org/apache/batik/gvt/unitTesting.xml</code>) and the accuracy rendering test on <code>batikFX.svg</code> (because it is the only test with <code>batikFX.svg</code> in its ID).</p>
-<h3 id="rendering-accuracy-tests-renderingaccuracytests">Rendering accuracy tests {#Rendering+accuracy+tests}</h3>
+<h3 id="Rendering-accuracy-tests">Rendering accuracy tests</h3>
 <p>There is a <code>Test</code> implementation, <a href="../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html">SVGRenderingAccuracyTest</a>, which checks that Batik’s rendering of an SVG document stays accurate. It compares reference images with the rendering Batik produces and reports any discrepency.</p>
 <p>An <code>SVGRenderingAccuracyTest</code> ’s constructor configuration is made of:</p>
 <ul>
@@ -350,8 +350,8 @@ This is another implementation of the <c
 </li>
 </ul>
 <p>Finally, to ease the process of creating “accepted” variation images, <code>SVGRenderingAccuracyTest</code> can take an optional file name (called <code>saveVariation</code>) describing where the variation between the rasterized SVG and the reference image will be stored in case the rasterized SVG is different from the reference image and the difference is not equal to the variation image, if any was defined. That way, it becomes possible to run a test, and if that test fails, the developer can review the <code>saveVariation</code> image and decide whether it is an acceptable variation or not and use it in subsequent test run as the “accepted” variation image, which will allow the test to pass if that exact same variation remains constant.</p>
-<h3 id="day-to-day-use-of-regard-daytodayuseofregard">Day to day use of regard {#Day+to+day+use+of+regard}</h3>
-<h4 id="initial-set-up-initialsetup">Initial set up ## {#Initial+set+up}</h4>
+<h3 id="Day-to-day-use-of-regard">Day to day use of regard</h3>
+<h4 id="Initial-set-up">Initial set up</h4>
 <p>To set up the test environment the first time, you need to:</p>
 <ul>
 <li>
@@ -371,13 +371,13 @@ This is another implementation of the <c
 <p>You can now run the test again:</p>
 <p>build regard</p>
 <p>Check the newly generated HTML report in the <code>test-reports/html</code> directory: there should no longer be any test failure.</p>
-<h4 id="daily-usage-dailyusage">Daily usage ## {#Daily+usage}</h4>
+<h4 id="Daily-usage">Daily usage</h4>
 <p>Once the intial set up has been done, you can use regard by simply updating your SVN copy, including the test-references. If no change occurs, your test will keep passing with your reference images. If a test fails (e.g., if someone checks in a new reference image from a platform different than the one you are using, you will have to check if it is because of system specific reasons or if there is a bigger problem.</p>
-<h3 id="svg-generator-tests-svggeneratortests">SVG generator tests {#SVG+generator+tests}</h3>
+<h3 id="SVG-generator-tests">SVG generator tests</h3>
 <p>Regard contains over 100 tests for checking regressions on the SVG generator. If you use <code>svggen</code> as an argument to regard, all the SVG generator tests will be run (because <code>regard.xml</code> points to <code>test-resources/org/apache/batik/svggen/regsvggen.xml</code>, which is a test suite description for the SVG generator and that file’s root <code>testSuite</code> element has the “svggen” ID).</p>
 <h2 id="writingNewTests">Writing new tests</h2>
 <p>Writing a new test involves either configuring a new test or writing a new <code>Test</code> class. In both cases, you will need to add an entry to a test suite’s XML description. This section uses two test suites as an example: the “regard” test suite to show how to configure a new test and the “unitTests” test suite to show how to add a new <code>Test</code> implementation.</p>
-<h3 id="adding-a-new-test-configuration-addinganewtestconfiguration">Adding a new test configuration {#Adding+a+new+test+configuration}</h3>
+<h3 id="Adding-a-new-test-configuration">Adding a new test configuration</h3>
 <p>Imagine that you add a cool new test case to the <code>samples</code> directory, such as <code>linking-viewBox.svg</code>. In order to check for regressions on that file you can add the following entry:</p>
 <div class="codehilite"><pre><span class="nt">&lt;test</span> <span class="na">id=</span><span class="s">&quot;anne.svg&quot;</span> <span class="na">class=</span><span class="s">&quot;org.apache.batik.test.svg.SVGRenderingAccuracyTest&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;arg</span> <span class="na">class=</span><span class="s">&quot;java.net.URL&quot;</span>
@@ -395,7 +395,7 @@ This is another implementation of the <c
 
 
 <p>to the <code>test-resources/org/apache/batik/test/samplesRendering.xml</code> test suite description, the description of the regard test suite. If you have access to the build machine where the reference images are typically generated, you can check 0n the reference image in <code>test-references/samples/tests</code>. Otherwise (and this is OK), you can let the test fail the first time it is run on the build/test machine and that will be a reminder for whoever is responsible for that machine that a valid reference image should be checked in.</p>
-<h3 id="writing-a-new-test-writinganewtest">Writing a new test {#Writing+a+new+test}</h3>
+<h3 id="Writing-a-new-test">Writing a new test</h3>
 <p>Imagine you want to validate some aspect of your code, and let's take the bridge error handling as an example. You could create a new class in the <code>test-sources</code> directory, in <code>test-sources/org/apache/batik/bridge</code> in our example, and let's call it <code>ErrorHandlingTest</code>. To simplify the implementation of the <code>Test</code> interface, you can choose to derive from the <code>AbstractTest</code> class and generate a <code>DefaultTestReport</code>.</p>
 <p>While writing the <code>Test</code> you may want to use your own XML file with just your test, for example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;testReportProcessor</span> <span class="na">class=</span><span class="s">&quot;org.apache.batik.test.SimpleTestReportProcessor&quot;</span><span class="nt">/&gt;</span>

Modified: websites/staging/xmlgraphics/trunk/content/batik/uses.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/uses.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/uses.html Fri Dec  7 16:08:03 2012
@@ -170,12 +170,12 @@ $(document).ready(function () {
 <div class="toc">
 <ul>
 <li><a href="#projects-using-batik">Projects using Batik</a><ul>
-<li><a href="#examples-of-projects-and-products-using-batik-examplesofprojectsandproductsusingbatik">Examples of projects and products using Batik {#Examples+of+projects+and+products+using+Batik}</a></li>
+<li><a href="#Examples-of-projects-and-products-using-Batik">Examples of projects and products using Batik</a></li>
 </ul>
 </li>
 </ul>
 </div>
-<h2 id="examples-of-projects-and-products-using-batik-examplesofprojectsandproductsusingbatik">Examples of projects and products using Batik {#Examples+of+projects+and+products+using+Batik}</h2>
+<h2 id="Examples-of-projects-and-products-using-Batik">Examples of projects and products using Batik</h2>
 <p>While it is hard to track projects and products which are using Batik, here are a few that are known of:</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/batik/using/extending.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/extending.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/extending.html Fri Dec  7 16:08:03 2012
@@ -283,7 +283,7 @@ A <a href="../javadoc/org/apache/batik/e
 <p>StreamRegistryEntry
 :
 A <a href="../javadoc/org/apache/batik/ext/awt/image/spi/StreamRegistryEntry.html">StreamRegistryEntry</a> works with a markable <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html">InputStream</a>. This is the preferred form of registry entry as it generally avoids opening a potentially expensive connection multiple times, instead it opens the stream once and relies on mark and reset to allow entries to check the stream.</p>
-<h3 id="helper-classes-helperclasses">Helper classes {#Helper+classes}</h3>
+<h3 id="Helper-classes">Helper classes</h3>
 <p>There exists quite a number of classes to assist in implementing a <code>RegistryEntry</code>. It is strongly recommended that you review these classes and make use of them where appropriate. They will likely save you time and improve the integration with Batik.</p>
 <p>MagicNumberRegistryEntry
 :

Modified: websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html Fri Dec  7 16:08:03 2012
@@ -275,7 +275,7 @@ Stream out the SVG content. The SVG gene
 <h2 id="custom">SVG Generator customization</h2>
 <p>In the previous section, we have just seen that the SVG generation process can be customized to output SVG styling properties as presentation attributes or CSS inline stylesheets. In this section we will talk about some examples of more advanced customizations.</p>
 <p>Instead of creating the <code>SVGGraphics2D</code> just by using the <code>Document</code> that will be used as a factory for creating the SVG elements, we can use the constructor that uses an <a href="../javadoc/org/apache/batik/svggen/SVGGeneratorContext.html">SVGGeneratorContext</a> instance. By providing your own <code>SVGGeneratorContext</code> instance, you will be able to do advanced customization. You will find below several examples of possible customizations.</p>
-<h3 id="have-your-own-comment-in-the-generated-svg-file-haveyourowncommentinthegeneratedsvgfile">Have your own comment in the generated SVG file {#Have+your+own+comment+in+the+generated+SVG+file}</h3>
+<h3 id="Have-your-own-comment-in-the-generated-SVG-file">Have your own comment in the generated SVG file</h3>
 <p>We begin with the simplest possible example. If you integrate the Batik SVG generator in your own Java application, you may want to specialize the comment generated in the XML code.</p>
 <div class="codehilite"><pre><span class="n">DOMImplementation</span> <span class="n">impl</span> <span class="o">=</span>
     <span class="n">GenericDOMImplementation</span><span class="o">.</span><span class="na">getDOMImplementation</span><span class="o">();</span>
@@ -288,7 +288,7 @@ Stream out the SVG content. The SVG gene
 </pre></div>
 
 
-<h2 id="use-embedded-svg-fonts-in-the-generated-svg-file-useembeddedsvgfontsinthegeneratedsvgfile">Use embedded SVG Fonts in the generated SVG file {#Use+embedded+SVG+Fonts+in+the+generated+SVG+file}</h2>
+<h2 id="Use-embedded-SVG-Fonts-in-the-generated-SVG-file">Use embedded SVG Fonts in the generated SVG file</h2>
 <p>In order to have a self-contained SVG file that doesn't have to use system fonts to be displayed, you can embed the fonts you used for drawing strings in the SVG file through the SVG fonts facility.</p>
 <div class="codehilite"><pre><span class="n">DOMImplementation</span> <span class="n">impl</span> <span class="o">=</span>
     <span class="n">GenericDOMImplementation</span><span class="o">.</span><span class="na">getDOMImplementation</span><span class="o">();</span>
@@ -301,7 +301,7 @@ Stream out the SVG content. The SVG gene
 </pre></div>
 
 
-<h2 id="customizing-the-way-images-are-stored-customizingthewayimagesarestored">Customizing the way images are stored {#Customizing+the+way+images+are+stored}</h2>
+<h2 id="Customizing-the-way-images-are-stored">Customizing the way images are stored</h2>
 <p>Every time you call one of the <code>drawImage</code> methods provided by the <code>Graphics2D</code> interface, a default representation of your image is created in a location and put in a default file. For instance, a base64 encoding is created and embedded in the SVG file by default. Alternatively, you can choose to have your images written to separate files in a predefined directory, in one of the two raster formats required by the SVG specification: JPEG or PNG.</p>
 <p>You can change the default behavior by explicitly providing the image handler to be used by the SVG generator. Once again, you use the <code>SVGGeneratorContext</code> for this. In the example below, all images are converted to PNG format and written to directory <code>res/images</code>.</p>
 <div class="codehilite"><pre><span class="n">DOMImplementation</span> <span class="n">impl</span> <span class="o">=</span>
@@ -359,7 +359,7 @@ Stream out the SVG content. The SVG gene
 </pre></div>
 
 
-<h2 id="customizing-the-generated-svg-style-customizingthegeneratedsvgstyle">Customizing the generated SVG style {#Customizing+the+generated+SVG+style}</h2>
+<h2 id="Customizing-the-generated-SVG-style">Customizing the generated SVG style</h2>
 <p>Your needs in matter of styling may be different from the two provided options (XML presentation attributes or CSS inline stylesheets). For example, you may want to put the CSS properties in a SVG <code>style</code> element section and reference them through the class attribute. In this case you will need to define a new <a href="../javadoc/org/apache/batik/svggen/StyleHandler.html">StyleHandler</a> as below.</p>
 <div class="codehilite"><pre><span class="kd">public</span> <span class="kd">class</span> <span class="nc">StyleSheetStyleHandler</span> <span class="kd">implements</span> <span class="n">StyleHandler</span> <span class="o">{</span>
 
@@ -418,7 +418,7 @@ Stream out the SVG content. The SVG gene
 </pre></div>
 
 
-<h2 id="extending-paint-object-to-svg-element-translation-extendingpaintobjecttosvgelementtranslation">Extending Paint object to SVG element translation {#Extending+Paint+object+to+SVG+element+translation}</h2>
+<h2 id="Extending-Paint-object-to-SVG-element-translation">Extending Paint object to SVG element translation</h2>
 <p>The <code>SVGGraphics2D</code> is able to generate SVG elements for generic Java 2D objects, but you sometimes have your own classes such as implementations of the Java 2D <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/awt/Paint.html">Paint</a> interface. In this case, you will need to write an <a href="../javadoc/org/apache/batik/svggen/ExtensionHandler.html">ExtensionHandler</a> that you will set on your <code>SVGGeneratorContext</code>.</p>
 <p>In the following example we define the first draft of an <code>ExtensionHandler</code> allowing to translate a Batik implementation of the <code>Paint</code> interface named <a href="../javadoc/org/apache/batik/ext/awt/LinearGradientPaint.html">LinearGradientPaint</a>.</p>
 <div class="codehilite"><pre><span class="kd">class</span> <span class="nc">MyExtensionHandler</span> <span class="kd">extends</span> <span class="n">DefaultExtensionHandler</span> <span class="o">{</span>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/configuration.html Fri Dec  7 16:08:03 2012
@@ -566,7 +566,7 @@ $(document).ready(function () {
 
 <p>The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.</p>
 <p>The default value for the "text-rendering" setting is "auto" which paints the base fonts using PCL fonts. Non-base fonts are painted as bitmaps through Java2D. If the mix of painting methods results in unwelcome output, you can set this to "bitmap" which causes all text to be rendered as bitmaps.</p>
-<h2 id="when-it-does-not-work-whenitdoesnotwork">When it does not work {#When+it+does+not+work}</h2>
+<h2 id="When-it-does-not-work">When it does not work</h2>
 <p>FOP searches the configuration file for the information it expects, at the position it expects. When that information is not present, FOP will not complain, it will just continue. When there is other information in the file, FOP will not complain, it will just ignore it. That means that when your configuration information is in the file but in a different XML element, or in a different XML path, than FOP expects, it will be silently ignored.</p>
 <p>Check the following possibilities:</p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/fonts.html Fri Dec  7 16:08:03 2012
@@ -421,10 +421,10 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h2 id="base-14-fonts-base-14fonts">Base-14 Fonts {#Base-14+Fonts}</h2>
+<h2 id="Base-14-Fonts">Base-14 Fonts</h2>
 <p>The Adobe PostScript and PDF Specification specify a set of 14 fonts that must be available to every PostScript interpreter and PDF reader: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats.</p>
 <p>Please note that recent versions of Adobe Acrobat Reader replace "Helvetica" with "Arial" and "Times" with "Times New Roman" internally. GhostScript replaces "Helvetica" with "Nimbus Sans L" and "Times" with "Nimbus Roman No9 L". Other document viewers may do similar font substitutions. If you need to make sure that there are no such substitutions, you need to specify an explicit font and embed it in the target document.</p>
-<h2 id="missing-fonts-missingfonts">Missing Fonts {#Missing+Fonts}</h2>
+<h2 id="Missing-Fonts">Missing Fonts</h2>
 <p>When FOP does not have a specific font at its disposal (because it's not installed in the operating system or set up in FOP's configuration), the font is replaced with "any". "any" is internally mapped to the Base-14 font "Times" (see above).</p>
 <h2 id="awt">Java2D/AWT/Operating System Fonts</h2>
 <p>The Java2D family of renderers (Java2D, AWT, Print, TIFF, PNG), use the Java AWT subsystem for font metric information. Through operating system registration, the AWT subsystem knows what fonts are available on the system, and the font metrics for each one.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html Fri Dec  7 16:08:03 2012
@@ -342,22 +342,22 @@ $(document).ready(function () {
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-known-issues">Apache&trade; FOP: Known Issues</h1>
-<h2 id="known-issues-knownissues">Known issues {#Known+issues}</h2>
+<h2 id="Known-issues">Known issues</h2>
 <p>This page lists currently known issues in the current release.</p>
 <p>For additional information on known issues in Apache&trade; FOP, please have a look at the following pages, too:</p>
 <ul>
 <li>
-<p><a href="../bugs.html">the bug list in Bugzilla</a> </p>
+<p><a href="../bugs.html">the bug list in Bugzilla</a></p>
 </li>
 <li>
-<p><a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks">the task list in the Wiki</a> </p>
+<p><a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks">the task list in the Wiki</a></p>
 </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>
-<h3 id="fo-tree-fotree">FO Tree {#FO+Tree}</h3>
+<h3 id="FO-Tree">FO Tree</h3>
 <p>This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.</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>
-<h3 id="layout-engine-layoutengine">Layout Engine {#Layout+Engine}</h3>
+<h3 id="Layout-Engine">Layout Engine</h3>
 <p>This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.</p>
 <p><strong>basic-link_external-destination_2.xml</strong> (External link around an SVG not properly sized):<br></br>The bpd trait of the inlineparent area for the basic-link is not sized correctly if it wraps an image that is higher than the nominal line.</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>
@@ -372,16 +372,16 @@ $(document).ready(function () {
 <p><strong>external-graphic_oversized.xml</strong> (external-graphic don't shrink):<br></br>Images currently don't shrink so they fit on a page when they are too big and shrinking is allowed to happen (min/opt/max).</p>
 <p><strong>external-graphic_src_uri.xml</strong> (Test case with HTTP URL):<br></br>Doesn't work behind a proxy which requires authorization.</p>
 <p><strong>footnote_space-resolution.xml</strong> (Space Resolution in foot note area):<br></br>Space resolution does not work between footnote regions.</p>
-<p><strong>footnote_in_list.xml</strong> (Footnotes swallowed in lists):<br></br>Element lists for lists are created by combining the element lists from list-item-label and list-item-body. The footnotes contained in the KnuthBlockBoxes are not propagated to the combined element list.<br></br>See also: <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37579">http://issues.apache.org/bugzilla/show_bug.cgi?id=37579</a> </p>
-<p><strong>footnote_in_table.xml</strong> (Footnotes swallowed in tables):<br></br>Element lists for tables are created by combining the element lists from the individual table-cells. The footnotes contained in the KnuthBlockBoxes are not propagated to the combined element list.<br></br>See also: <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37579">http://issues.apache.org/bugzilla/show_bug.cgi?id=37579</a> </p>
+<p><strong>footnote_in_list.xml</strong> (Footnotes swallowed in lists):<br></br>Element lists for lists are created by combining the element lists from list-item-label and list-item-body. The footnotes contained in the KnuthBlockBoxes are not propagated to the combined element list.<br></br>See also: <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37579">http://issues.apache.org/bugzilla/show_bug.cgi?id=37579</a></p>
+<p><strong>footnote_in_table.xml</strong> (Footnotes swallowed in tables):<br></br>Element lists for tables are created by combining the element lists from the individual table-cells. The footnotes contained in the KnuthBlockBoxes are not propagated to the combined element list.<br></br>See also: <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37579">http://issues.apache.org/bugzilla/show_bug.cgi?id=37579</a></p>
 <p><strong>inline_block_nested_3.xml</strong> (NPE for table inside an inline):<br></br>Placing a table as a child of an fo:inline produces a NullPointerException.</p>
 <p><strong>inline-container_block_nested.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed. The test case contains no checks.</p>
 <p><strong>inline-container_border_padding.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed.</p>
 <p><strong>inline_letter-spacing.xml</strong> (inline letter-spacing):<br></br>Letter-spacing may not work as expected within fo:inline.</p>
 <p><strong>inline_word-spacing.xml</strong> (inline word-spacing):<br></br>Word-spacing may not work as expected within fo:inline.</p>
-<p><strong>inline_word-spacing_text-align_justify.xml</strong> (inline word-spacing text-align justify):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </p>
+<p><strong>inline_word-spacing_text-align_justify.xml</strong> (inline word-spacing text-align justify):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em></p>
 <p><strong>leader-alignment.xml</strong> (leader-alignment NYI):<br></br>Leader-alignment is not yet implemented.</p>
-<p><strong>leader_leader-pattern_use-content_bug.xml</strong> (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: <a href="http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html">http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html</a> </p>
+<p><strong>leader_leader-pattern_use-content_bug.xml</strong> (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: <a href="http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html">http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html</a></p>
 <p><strong>list-block_keep-with-previous.xml</strong> (keep-with-previous doesn't work in lists):<br></br>Keep-with-previous doesn't work inside tables and lists, yet.</p>
 <p><strong>list-item_block_keep-with-previous.xml</strong> (keep-with-previous doesn't work in lists):<br></br>Keep-with-previous doesn't work inside tables and lists, yet.</p>
 <p><strong>page-breaking_4.xml</strong> (Page breaking doesn't deal with IPD changes):<br></br>Page breaking currently doesn't support changing available IPD between pages of a single page-sequence. Element list generation has to be reset to redetermine line breaks in this case.</p>
@@ -398,7 +398,7 @@ $(document).ready(function () {
 <p><strong>table_border-width_conditionality.xml</strong> (Border conditionality on table):<br></br>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the indended outcome according to the spec. The test case should be revisited.</p>
 <p><strong>wrapper_block_id.xml</strong> (fo:wrapper around block-level content (with id)):<br></br>"id" attributes on fo:wrapper around block-level content don't get added to the area tree.</p>
 <p><strong>block_shy_linebreaking_hyph.xml</strong> (Soft hyphen with normal hyphenation enabled):<br></br>A soft hyphen should be a preferred as break compared to a normal hyphenation point but is not.</p>
-<h3 id="other-known-issues-otherknownissues">Other known issues {#Other+known+issues}</h3>
+<h3 id="Other-known-issues">Other known issues</h3>
 <p>This section lists other known issues.</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html Fri Dec  7 16:08:03 2012
@@ -346,13 +346,13 @@ $(document).ready(function () {
 <h2 id="Overview">Overview</h2>
 <p>Apache&trade; FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited.</p>
 <p>For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.</p>
-<h2 id="usage-command-line-usage28commandline29">Usage (command line) {#Usage+%28command+line%29}</h2>
+<h2 id="usage-command-line-usage-28command-line29">Usage (command line) {#Usage-%28command-line%29}</h2>
 <p>Encryption is enabled by supplying any of the encryption related options.</p>
 <p>An owner password is set with the <code>-o</code> option. This password is actually used as encryption key. Many tools for PDF processing ask for this password to disregard any restriction imposed on the PDF document.</p>
 <p>If no owner password has been supplied but FOP was asked to apply some restrictions, a random password is used. In this case it is obviously impossiible to disregard restrictions in PDF processing tools.</p>
 <p>A user password, supplied with the <code>-u</code> option, will cause the PDF display software to ask the reader for this password in order to view the contents of the document. If no user password was supplied, viewing the content is not restricted.</p>
 <p>Further restrictions can be imposed by using the <code>-noprint</code>, <code>-nocopy</code>, <code>-noedit</code> and <code>-noannotations</code> options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.</p>
-<h2 id="usage-embedded-usage28embedded29">Usage (embedded) {#Usage+%28embedded%29}</h2>
+<h2 id="usage-embedded-usage-28embedded29">Usage (embedded) {#Usage-%28embedded%29}</h2>
 <p>When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:</p>
 <table>
 <thead>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html Fri Dec  7 16:08:03 2012
@@ -367,15 +367,15 @@ If an fo:table element contains explicit
 This final 0.95 release also includes all of the <a href="changes_0.95beta.html">changes made for Apache FOP 0.95beta</a>.</section></notes></p>
 <h1 id="version_0.95">Major Changes in Version 0.95</h1>
 <p>This is not a complete list of changes, just some of the more important ones. A full list of changes in this release <a href="changes_0.95.html">is available</a>.</p>
-<h2 id="changes-to-the-code-base-changestothecodebase">Changes to the Code Base {#Changes+to+the+Code+Base}</h2>
+<h2 id="Changes-to-the-Code-Base">Changes to the Code Base</h2>
 <ul>
 <li><img alt="fix" src="/images/fix.jpg" />Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44887">44887</a>.</li>
 </ul>
-<h3 id="changes-to-the-layout-engine-changestothelayoutengine">Changes to the Layout Engine {#Changes+to+the+Layout+Engine}</h3>
+<h3 id="Changes-to-the-Layout-Engine">Changes to the Layout Engine</h3>
 <ul>
 <li><img alt="fix" src="/images/fix.jpg" />Various bugfixes for table layout. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44621">44621</a>.</li>
 </ul>
-<h3 id="changes-to-renderers-output-formats-changestorenderers28outputformats29">Changes to Renderers (Output Formats) {#Changes+to+Renderers+%28Output+Formats%29}</h3>
+<h3 id="changes-to-renderers-output-formats-changes-to-renderers-28output-formats29">Changes to Renderers (Output Formats) {#Changes-to-Renderers-%28Output-Formats%29}</h3>
 <ul>
 <li>
 <p><img alt="fix" src="/images/fix.jpg" />Fixed positioning of absolutely positioned block-containers in multi-column documents. Committed by JM.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html Fri Dec  7 16:08:03 2012
@@ -345,7 +345,7 @@ $(document).ready(function () {
 <h2 id="overview">Overview</h2>
 <p>This page describes the <a href="http://en.wikipedia.org/wiki/Accessibility">accessibility</a> features of Apache&trade; FOP. <a href="http://www.section508.gov/">Section 508</a> defines accessibility in the context of electronic documents for the USA but other countries have similar requirements.</p>
 <p>Accessibility features are available only for the PDF output format and there are some implementation limitations. Also, certain actions must be undertaken by the content creator to ensure that FOP can create a truly accessible document.</p>
-<h2 id="enabling-accessibility-enablingaccessibility">Enabling accessibility {#Enabling+accessibility}</h2>
+<h2 id="Enabling-accessibility">Enabling accessibility</h2>
 <p>There are 3 ways to enable accessibility:</p>
 <ol>
 <li><strong>Command line:</strong> The command line option -a turns on accessibility:<br/><code>fop -a -fo mydocument.fo -pdf mydocument.pdf</code><br/></li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/configuration.html Fri Dec  7 16:08:03 2012
@@ -619,7 +619,7 @@ $(document).ready(function () {
 <p>The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.</p>
 <p>The default value for the "renderer-resolution" is 240 dpi.</p>
 <p>By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.</p>
-<h2 id="when-it-does-not-work-whenitdoesnotwork">When it does not work {#When+it+does+not+work}</h2>
+<h2 id="When-it-does-not-work">When it does not work</h2>
 <p>FOP searches the configuration file for the information it expects, at the position it expects. When that information is not present, FOP will not complain, it will just continue. When there is other information in the file, FOP will not complain, it will just ignore it. That means that when your configuration information is in the file but in a different XML element, or in a different XML path, than FOP expects, it will be silently ignored.</p>
 <p>Check the following possibilities:</p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html Fri Dec  7 16:08:03 2012
@@ -421,7 +421,7 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h2 id="base-14-fonts-base-14fonts">Base-14 Fonts {#Base-14+Fonts}</h2>
+<h2 id="Base-14-Fonts">Base-14 Fonts</h2>
 <p>The Adobe PostScript and PDF Specification specify a set of 14 fonts that must be available to every PostScript interpreter and PDF reader: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats.</p>
 <p>The following font family names are hard-coded into FOP for the Base-14 font set:</p>
 <table>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/knownissues_overview.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/knownissues_overview.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/knownissues_overview.html Fri Dec  7 16:08:03 2012
@@ -342,23 +342,23 @@ $(document).ready(function () {
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.0/">1.0</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-known-issues">Apache&trade; FOP: Known Issues</h1>
-<h2 id="known-issues-knownissues">Known issues {#Known+issues}</h2>
+<h2 id="Known-issues">Known issues</h2>
 <p>This page lists currently known issues in the current release.</p>
 <p>For additional information on known issues in Apache&trade; FOP, please have a look at the following pages, too:</p>
 <ul>
 <li>
-<p><a href="../bugs.html">the bug list in Bugzilla</a> </p>
+<p><a href="../bugs.html">the bug list in Bugzilla</a></p>
 </li>
 <li>
-<p><a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks">the task list in the Wiki</a> </p>
+<p><a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks">the task list in the Wiki</a></p>
 </li>
 </ul>
 <p>Apache&trade; FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.</p>
-<h3 id="fo-tree-fotree">FO Tree {#FO+Tree}</h3>
+<h3 id="FO-Tree">FO Tree</h3>
 <p>This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.</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>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>
-<h3 id="layout-engine-layoutengine">Layout Engine {#Layout+Engine}</h3>
+<h3 id="Layout-Engine">Layout Engine</h3>
 <p>This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.</p>
 <p><strong>basic-link_external-destination_2.xml</strong> (External link around an SVG not properly sized):<br></br>The bpd trait of the inlineparent area for the basic-link is not sized correctly if it wraps an image that is higher than the nominal line.</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>
@@ -378,9 +378,9 @@ $(document).ready(function () {
 <p><strong>inline-container_border_padding.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed.</p>
 <p><strong>inline_letter-spacing.xml</strong> (inline letter-spacing):<br></br>Letter-spacing may not work as expected within fo:inline.</p>
 <p><strong>inline_word-spacing.xml</strong> (inline word-spacing):<br></br>Word-spacing may not work as expected within fo:inline.</p>
-<p><strong>inline_word-spacing_text-align_justify.xml</strong> (inline word-spacing text-align justify):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </p>
+<p><strong>inline_word-spacing_text-align_justify.xml</strong> (inline word-spacing text-align justify):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em></p>
 <p><strong>leader-alignment.xml</strong> (leader-alignment NYI):<br></br>Leader-alignment is not yet implemented.</p>
-<p><strong>leader_leader-pattern_use-content_bug.xml</strong> (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: <a href="http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html">http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html</a> </p>
+<p><strong>leader_leader-pattern_use-content_bug.xml</strong> (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: <a href="http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html">http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html</a></p>
 <p><strong>page-breaking_4.xml</strong> (Page breaking doesn't deal with IPD changes):<br></br>Page breaking currently doesn't support changing available IPD between pages of a single page-sequence. Element list generation has to be reset to redetermine line breaks in this case.</p>
 <p><strong>page-breaking_6.xml</strong> (Overflow handing is incomplete):<br></br>Line breaking is not 100% correct when there's too little space. Overflows are not detected and warned.</p>
 <p><strong>page-height_indefinite_simple.xml</strong> (Indefinite page height handling is imcomplete):<br></br>A RuntimeException is thrown for a page of indefinite height. Lots of warnings.</p>
@@ -394,7 +394,7 @@ $(document).ready(function () {
 <p><strong>table_border-width_conditionality.xml</strong> (Border conditionality on table):<br></br>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the indended outcome according to the spec. The test case should be revisited.</p>
 <p><strong>block_shy_linebreaking_hyph.xml</strong> (Soft hyphen with normal hyphenation enabled):<br></br>A soft hyphen should be a preferred as break compared to a normal hyphenation point but is not.</p>
 <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>
-<h3 id="other-known-issues-otherknownissues">Other known issues {#Other+known+issues}</h3>
+<h3 id="Other-known-issues">Other known issues</h3>
 <p>This section lists other known issues.</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html Fri Dec  7 16:08:03 2012
@@ -346,13 +346,13 @@ $(document).ready(function () {
 <h2 id="Overview">Overview</h2>
 <p>Apache&trade; FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited.</p>
 <p>For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.</p>
-<h2 id="usage-command-line-usage28commandline29">Usage (command line) {#Usage+%28command+line%29}</h2>
+<h2 id="usage-command-line-usage-28command-line29">Usage (command line) {#Usage-%28command-line%29}</h2>
 <p>Encryption is enabled by supplying any of the encryption related options.</p>
 <p>An owner password is set with the <code>-o</code> option. This password is actually used as encryption key. Many tools for PDF processing ask for this password to disregard any restriction imposed on the PDF document.</p>
 <p>If no owner password has been supplied but FOP was asked to apply some restrictions, a random password is used. In this case it is obviously impossiible to disregard restrictions in PDF processing tools.</p>
 <p>A user password, supplied with the <code>-u</code> option, will cause the PDF display software to ask the reader for this password in order to view the contents of the document. If no user password was supplied, viewing the content is not restricted.</p>
 <p>Further restrictions can be imposed by using the <code>-noprint</code>, <code>-nocopy</code>, <code>-noedit</code> and <code>-noannotations</code> options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.</p>
-<h2 id="usage-embedded-usage28embedded29">Usage (embedded) {#Usage+%28embedded%29}</h2>
+<h2 id="usage-embedded-usage-28embedded29">Usage (embedded) {#Usage-%28embedded%29}</h2>
 <p>When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:</p>
 <table>
 <thead>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/releaseNotes_1.0.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/releaseNotes_1.0.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/releaseNotes_1.0.html Fri Dec  7 16:08:03 2012
@@ -344,7 +344,7 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="release-notes-for-apache-fop-10">Release Notes for Apache FOP 1.0</h1>
 <h2 id="version_1.0">Major Changes in Version 1.0</h2>
 <p>This is not a complete list of changes, just some of the more important ones. A full list of changes in this release <a href="changes_1.0.html">is available</a>.</p>
-<h2 id="changes-to-the-code-base-changestothecodebase">Changes to the Code Base {#Changes+to+the+Code+Base}</h2>
+<h2 id="Changes-to-the-Code-Base">Changes to the Code Base</h2>
 <ul>
 <li>
 <p><img alt="fix" src="/images/fix.jpg" /> Fixed memory leak in property cache (not cleaning stale PropertyCache$CacheEntry instances). Committed by JM.</p>
@@ -356,7 +356,7 @@ $(document).ready(function () {
 <p><img alt="add" src="/images/add.jpg" /> Added an event handling framework which allows to get better feedback from within FOP with the ability to customize problem management. Committed by JM.</p>
 </li>
 </ul>
-<h3 id="changes-to-the-font-subsystem-changestothefontsubsystem">Changes to the Font Subsystem {#Changes+to+the+Font+Subsystem}</h3>
+<h3 id="Changes-to-the-Font-Subsystem">Changes to the Font Subsystem</h3>
 <ul>
 <li>
 <p><img alt="add" src="/images/add.jpg" /> Add support for font substitution. Committed by AC.</p>
@@ -365,7 +365,7 @@ $(document).ready(function () {
 <p><img alt="add" src="/images/add.jpg" /> Added support for addressing all glyphs available in a Type 1 font, not just the ones in the font's primary encoding. Committed by JM.</p>
 </li>
 </ul>
-<h3 id="changes-to-the-layout-engine-changestothelayoutengine">Changes to the Layout Engine {#Changes+to+the+Layout+Engine}</h3>
+<h3 id="Changes-to-the-Layout-Engine">Changes to the Layout Engine</h3>
 <ul>
 <li>
 <p><img alt="add" src="/images/add.jpg" /> Added limited support for pages of different inline-progression-dimensions within a page-sequence. Committed by VH.</p>
@@ -374,7 +374,7 @@ $(document).ready(function () {
 <p><img alt="add" src="/images/add.jpg" /> Added minimal support for integer keep values on the various keep properties on block-level FOs. For now, all integer values are treated the same (i.e. without strength distinction). Using integers allows to avoid overflows that can happen when "always" is used extensively. Committed by JM.</p>
 </li>
 </ul>
-<h3 id="changes-to-renderers-output-formats-changestorenderers28outputformats29">Changes to Renderers (Output Formats) {#Changes+to+Renderers+%28Output+Formats%29}</h3>
+<h3 id="changes-to-renderers-output-formats-changes-to-renderers-28output-formats29">Changes to Renderers (Output Formats) {#Changes-to-Renderers-%28Output-Formats%29}</h3>
 <ul>
 <li>
 <p><img alt="add" src="/images/add.jpg" /> AFP Output: An AFPGraphics2D implementation which provides the ability to use Batik to drive the production of AFP Graphics (GOCA) output from SVG. Committed by AC.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/accessibility.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/accessibility.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/accessibility.html Fri Dec  7 16:08:03 2012
@@ -345,7 +345,7 @@ $(document).ready(function () {
 <h2 id="overview">Overview</h2>
 <p>This page describes the <a href="http://en.wikipedia.org/wiki/Accessibility">accessibility</a> features of Apache&trade; FOP. <a href="http://www.section508.gov/">Section 508</a> defines accessibility in the context of electronic documents for the USA but other countries have similar requirements.</p>
 <p>Accessibility features are available only for the PDF output format and there are some implementation limitations. Also, certain actions must be undertaken by the content creator to ensure that FOP can create a truly accessible document.</p>
-<h2 id="enabling-accessibility-enablingaccessibility">Enabling accessibility {#Enabling+accessibility}</h2>
+<h2 id="Enabling-accessibility">Enabling accessibility</h2>
 <p>There are 3 ways to enable accessibility:</p>
 <ol>
 <li><strong>Command line:</strong> The command line option -a turns on accessibility:<br/><code>fop -a -fo mydocument.fo -pdf mydocument.pdf</code><br/></li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/complexscripts.html Fri Dec  7 16:08:03 2012
@@ -358,7 +358,7 @@ $(document).ready(function () {
 <p>Support for advanced number to string formatting.</p>
 </li>
 </ul>
-<h2 id="disabling-complex-scripts-disablingcomplexscripts">Disabling complex scripts {#Disabling+complex+scripts}</h2>
+<h2 id="Disabling-complex-scripts">Disabling complex scripts</h2>
 <p>Complex script features are enabled by default. If some application of FOP does not require this support, then it can be disabled in three ways:</p>
 <ol>
 <li><strong>Command line:</strong><br/>The command line option <code>-nocs</code> turns off complex script features:<br/><code>fop -nocs -fo mydocument.fo -pdf mydocument.pdf</code><br/></li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/configuration.html Fri Dec  7 16:08:03 2012
@@ -643,7 +643,7 @@ $(document).ready(function () {
 <p>The default value for the "renderer-resolution" is 240 dpi.</p>
 <p>The default line width is device dependent and may need to be fine tuned so that the output matches the expected result. The default correction value is 2.5.</p>
 <p>By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.</p>
-<h2 id="when-it-does-not-work-whenitdoesnotwork">When it does not work {#When+it+does+not+work}</h2>
+<h2 id="When-it-does-not-work">When it does not work</h2>
 <p>FOP searches the configuration file for the information it expects, at the position it expects. When that information is not present, FOP will not complain, it will just continue. When there is other information in the file, FOP will not complain, it will just ignore it. That means that when your configuration information is in the file but in a different XML element, or in a different XML path, than FOP expects, it will be silently ignored.</p>
 <p>Check the following possibilities:</p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html Fri Dec  7 16:08:03 2012
@@ -421,7 +421,7 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h2 id="base-14-fonts-base-14fonts">Base-14 Fonts {#Base-14+Fonts}</h2>
+<h2 id="Base-14-Fonts">Base-14 Fonts</h2>
 <p>The Adobe PostScript and PDF Specification specify a set of 14 fonts that must be available to every PostScript interpreter and PDF reader: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats.</p>
 <p>The following font family names are hard-coded into FOP for the Base-14 font set:</p>
 <table>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html Fri Dec  7 16:08:03 2012
@@ -342,7 +342,7 @@ $(document).ready(function () {
         </div>
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.1/">1.1</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-known-issues">Apache&trade; FOP: Known Issues</h1>
-<h2 id="known-issues-knownissues">Known issues {#Known+issues}</h2>
+<h2 id="Known-issues">Known issues</h2>
 <p>This page lists currently known issues in the current release.</p>
 <p>For additional information on known issues in Apache&trade; FOP, please have a look at the following pages, too:</p>
 <ul>
@@ -354,11 +354,11 @@ $(document).ready(function () {
 </li>
 </ul>
 <p>Apache&trade; FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.</p>
-<h3 id="fo-tree-fotree">FO Tree {#FO+Tree}</h3>
+<h3 id="FO-Tree">FO Tree</h3>
 <p>This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.</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>
-<h3 id="layout-engine-layoutengine">Layout Engine {#Layout+Engine}</h3>
+<h3 id="Layout-Engine">Layout Engine</h3>
 <p>This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.</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>
@@ -394,7 +394,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>
-<h3 id="other-known-issues-otherknownissues">Other known issues {#Other+known+issues}</h3>
+<h3 id="Other-known-issues">Other known issues</h3>
 <p>This section lists some other issues that post-date the release of FOP 1.0. For known issues that pre-date FOP 1.0, see <a href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=2010-07-20&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2001-01-01&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">older bugs that remain open</a>. For all open issues that post-date FOP 1.0, see <a href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=Now&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2010-07-20&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">newer bugs that remain open</a>.</p>
 <ul>
 <li>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html Fri Dec  7 16:08:03 2012
@@ -346,7 +346,7 @@ $(document).ready(function () {
 <h2 id="Overview">Overview</h2>
 <p>Apache&trade; FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited.</p>
 <p>For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.</p>
-<h2 id="usage-command-line-usage28commandline29">Usage (command line) {#Usage+%28command+line%29}</h2>
+<h2 id="usage-command-line-usage-28command-line29">Usage (command line) {#Usage-%28command-line%29}</h2>
 <p>Encryption is enabled by supplying any of the encryption related options.</p>
 <p>An owner password is set with the <code>-o</code> option. This password is actually used as encryption key. Many tools for PDF processing ask for this password to disregard any restriction imposed on the PDF document.</p>
 <p>If no owner password has been supplied but FOP was asked to apply some restrictions, a random password is used. In this case it is obviously impossiible to disregard restrictions in PDF processing tools.</p>
@@ -394,7 +394,7 @@ $(document).ready(function () {
 </tr>
 </tbody>
 </table>
-<h2 id="usage-embedded-usage28embedded29">Usage (embedded) {#Usage+%28embedded%29}</h2>
+<h2 id="usage-embedded-usage-28embedded29">Usage (embedded) {#Usage-%28embedded%29}</h2>
 <p>When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:</p>
 <table>
 <thead>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html Fri Dec  7 16:08:03 2012
@@ -344,7 +344,7 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="release-notes-for-apache-fop-11">Release Notes for Apache FOP 1.1</h1>
 <h2 id="version_1.1">Major Changes in Version 1.1</h2>
 <p>This is not a complete list of changes, just some of the more important ones. A full list of changes in this release <a href="changes_1.1.html">is available</a>.</p>
-<h2 id="changes-to-the-code-base-changestothecodebase">Changes to the Code Base {#Changes+to+the+Code+Base}</h2>
+<h2 id="Changes-to-the-Code-Base">Changes to the Code Base</h2>
 <ul>
 <li>
 <p><img alt="fix" src="/images/fix.jpg" /> Update to use of checkstyle-5.5 as default configuration. Remove checkstyle-4.0 configuration. Also, import environment build properties before local properties, so that latter can refer to former. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53083">53083</a>.</p>
@@ -386,11 +386,11 @@ $(document).ready(function () {
 <p><img alt="add" src="/images/add.jpg" /> Added support for resolution of relative URIs against a specified xml:base during property refinement. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=48334">48334</a>.</p>
 </li>
 </ul>
-<h3 id="changes-to-the-user-configuration-changestotheuserconfiguration">Changes to the User Configuration {#Changes+to+the+User+Configuration}</h3>
+<h3 id="Changes-to-the-User-Configuration">Changes to the User Configuration</h3>
 <ul>
 <li><img alt="add" src="/images/add.jpg" /> Added configuration option to set the version of the output PDF document. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51385">51385</a>.</li>
 </ul>
-<h3 id="changes-to-the-font-subsystem-changestothefontsubsystem">Changes to the Font Subsystem {#Changes+to+the+Font+Subsystem}</h3>
+<h3 id="Changes-to-the-Font-Subsystem">Changes to the Font Subsystem</h3>
 <ul>
 <li>
 <p><img alt="add" src="/images/add.jpg" /> Add support for OpenType advanced typographic tables (GDEF, GSUB, GPOS). Committed by GA.</p>
@@ -408,11 +408,11 @@ $(document).ready(function () {
 <p><img alt="add" src="/images/add.jpg" /> Added convenience support for the flushing of the Fop font cache file from the command line. Committed by AC.</p>
 </li>
 </ul>
-<h3 id="changes-to-the-image-support-changestotheimagesupport">Changes to the Image Support {#Changes+to+the+Image+Support}</h3>
+<h3 id="Changes-to-the-Image-Support">Changes to the Image Support</h3>
 <ul>
 <li><img alt="fix" src="/images/fix.jpg" /> Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecssary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40676">40676</a>.</li>
 </ul>
-<h3 id="changes-to-the-layout-engine-changestothelayoutengine">Changes to the Layout Engine {#Changes+to+the+Layout+Engine}</h3>
+<h3 id="Changes-to-the-Layout-Engine">Changes to the Layout Engine</h3>
 <ul>
 <li>
 <p><img alt="fix" src="/images/fix.jpg" /> Fix for break before (break-before) not respected on blocks nested in inlines. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45715">45715</a>.</p>
@@ -439,7 +439,7 @@ $(document).ready(function () {
 <p><img alt="fix" src="/images/fix.jpg" /> Fix for correct behavior of keep-together.within-line in case there are nested inlines Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49848">49848</a>.</p>
 </li>
 </ul>
-<h3 id="changes-to-renderers-output-formats-changestorenderers28outputformats29">Changes to Renderers (Output Formats) {#Changes+to+Renderers+%28Output+Formats%29}</h3>
+<h3 id="changes-to-renderers-output-formats-changes-to-renderers-28output-formats29">Changes to Renderers (Output Formats) {#Changes-to-Renderers-%28Output-Formats%29}</h3>
 <ul>
 <li>
 <p><img alt="add" src="/images/add.jpg" /> Added possibility to embed TrueType fonts in PostScript. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52338">52338</a>.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/breakpos.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/breakpos.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/breakpos.html Fri Dec  7 16:08:03 2012
@@ -345,12 +345,12 @@ $(document).ready(function () {
 <p><subtitle>Break Possibility Proposal</subtitle><authors><person email="klease@club-internet.fr" name="Karen Lease"></person></authors></p>
 <h2 id="intro">Introduction</h2>
 <p>As explained in <a href="layout.html">Layout</a>, the hierarchy of Layout Managers is responsible for building and placing areas. Each Layout Manager is responsible for creating and filling areas of a particular type, either inline or block. This document explains one potential algorithm for this process. It is based on the the generation of <em>break possibilities</em> (BP for short). The Layout Managers (LM for short), will generate one or more BP and choose the best one. The BP is then used to generate the corresponding areas.</p>
-<h2 id="anatomy-of-a-break-possibility-anatomyofabreakpossibility">Anatomy of a Break Possibility {#Anatomy+of+a+Break+Possibility}</h2>
+<h2 id="Anatomy-of-a-Break-Possibility">Anatomy of a Break Possibility</h2>
 <p>A break possibility is represented by the BreakPoss class. A BreakPoss contains size information in the stacking direction and in the non-stacking direction (at least for inline areas, it must have both). Flags indicating various conditions (ISFIRST, ISLAST, CAN_BREAK_AFTER, FORCE_BREAK_AFTER, ANCHORS etc). A BreakPoss contains a reference to the top-level LayoutManager which generated it.</p>
 <p>A BreakPoss contains an object implementing the BreakPoss.Position interface. This object is specific to the layout manager which created the BreakPoss. It should indicate where the break occurs and allow the LM to create an area corresponding to the BP. A higher level LM Position must somehow reference or wrap the Position returned by its child LM in its BreakPoss object. The layout manager modifies the flags and dimension information in the BP to reflect its own requirements. For example an inline FO layout manager might add space-start, space-end, border and padding values to the stacking or non-stacking dimensions. It might also modify the flags based its on keep properties.</p>
-<h2 id="turning-break-possibilities-into-areas-turningbreakpossibilitiesintoareas">Turning Break Possibilities into Areas {#Turning+Break+Possibilities+into+Areas}</h2>
+<h2 id="Turning-Break-Possibilities-into-Areas">Turning Break Possibilities into Areas</h2>
 <p>Once break possibilities have been generated, the galley-level layout manager selects the best one and passes it back to the LayoutManager which generated it to create the area. A LayoutManager is responsible for storing enough information in its Position objects to be able to create the corresponding areas.</p>
-<h2 id="a-walk-through-awalk-through">A walk-through {#A+walk-through}</h2>
+<h2 id="A-walk-through">A walk-through</h2>
 <p>Layout Managers are created from the top down. First the page sequence creates a PageLM and a FlowLM. The PageLM will manage finding the right page model (with help from the PageSequenceMaster) and managing the balancing act between before-floats, footnotes and the normal text flow. The FlowLM will manage the normal content in the main flow. We can think of it as a <em>galley</em> manager.</p>
 <p>In general, each LM asks its child LMs to return sucessive break possibilities. It passes some information to the child in a flags object and it gets back a break possibility which contains the size in the stacking direction as well as information about such things as anchors, break conditions and span conditions which can change the reference area environment. This process continues down to the lowest level of the layout manager hierarchy which corresponds to atomic inline-level FOs such as characters or graphics.</p>
 <p>Each layout manager will repeatedly call getNextBreakPoss on its current child LM until the child returns a BP with the ISLAST flag set. Then the layout manager moves on to its next child LM (ie, it asks the next child FO to generate a layout manager.) Galley level layout managers which are Line and Flow will return to their parent layout managers either when they have finished their content or when they encounter a a BP which will fill one of their areas.</p>
@@ -367,9 +367,9 @@ So the Line LM will ask its child LM(s) 
 <p>Obviously there is more complicated logic involved when dealing with lists and tables. These cases need to be walked through in detail.</p>
 <p>The FlowLM sees if the returned stacking dimension will still fit in its available block-progression-dimension (BPD). It repeatedly calls getNextBreakPoss on its child LMs until it reaches the maximum BPD for the flow reference area or until there is no more content to lay out. If one child LM is finished, it moves on to the next until the last child LM has returned a BP with the ISLAST flag set. If any child LM returns a BP with a FORCE_BREAK_BEFORE or SPAN flag set, the FlowLM will force layout of any pending break possibilities and return to its parent (the PageLM) in order to handle the break or span condition.</p>
 <p>If the returned BP has any new before-float or footnote anchors in it (ANCHOR flag in the BP), the FlowLM will also return to the PageLM. The PageLM must then try to find space to place the floats, possibly asking the FlowLM for help if the body contains multiple columns.</p>
-<h2 id="some-issues-someissues">Some issues {#Some+issues}</h2>
+<h2 id="Some-issues">Some issues</h2>
 <p>Following are a few remarks on specific issues.</p>
-<h3 id="where-line-layout-managers-are-created-wherelinelayoutmanagersarecreated">Where Line Layout Managers are created {#Where+Line+Layout+Managers+are+created}</h3>
+<h3 id="Where-Line-Layout-Managers-are-created">Where Line Layout Managers are created</h3>
 <p>If the first child FO in a block FO is an inline-level FO such as text, the block LM creates an intermediate level LineLM to layout the sequence of inline content into Lines. Note that the whole sequence of inline FOs is managed by a single instance of LineLM. The LineLM becomes the parent to the various inline-level LM created by each individual inline FO. Since an fo:block can have both block and inline content, its LM may create a sequence of intermixed BlockLM and LineLM.</p>
 <h3 id="getRefIPD">Getting the reference IPD</h3>
 <p>When the layout process starts, with the FlowLM asking its first child LM for a break possibility, the IPD isn't known, since we don't know whether the first FO might be spanning, or on which page it might start. (Of course, if all page masters in the sequence have the same region-body IPD and all have only a single column, the IPD will never change and could already be calculated before starting layout.) The FlowLM gets its first child LM and calls its getNextBreakPoss method. That is a child LM for some block-level FO. For now, suppose it's an fo:block. The BlockLM will create its first child LM, which may be another block-level LM in the case of nested blocks or a LineLM as explained above. (Question: do we need a START flag for layout status?)</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html Fri Dec  7 16:08:03 2012
@@ -347,7 +347,7 @@ $(document).ready(function () {
 <p>This is the design for the external interface when Apache&trade; FOP is to be embedded inside another java application.</p>
 <p>Common places where FOP is embedded is in a report production application of a server side application such as <a href="http://xml.apache.org/cocoon/index.html">Cocoon</a>.</p>
 <h2 id="Settings">Settings</h2>
-<h3 id="user-agent-useragent">User Agent {#User+Agent}</h3>
+<h3 id="User-Agent">User Agent</h3>
 <p>Possible meanings for a user agent:</p>
 <ul>
 <li>
@@ -376,7 +376,7 @@ $(document).ready(function () {
 <p>Logging setup (LogKit, Log4J, JDK14Logging)</p>
 </li>
 </ul>
-<h3 id="xml-input-xmlinput">XML input {#XML+input}</h3>
+<h3 id="XML-input">XML input</h3>
 <ul>
 <li>
 <p>various ways to supply FOP with the xsl:fo file, fo, xml+xsl</p>
@@ -385,7 +385,7 @@ $(document).ready(function () {
 <p>sax handler</p>
 </li>
 </ul>
-<h3 id="general-options-generaloptions">general options {#general+options}</h3>
+<h3 id="general-options">general options</h3>
 <ul>
 <li>
 <p>base url</p>
@@ -397,7 +397,7 @@ $(document).ready(function () {
 <p>which implementation of a particular LayoutManager to use</p>
 </li>
 </ul>
-<h3 id="rendering-options-renderingoptions">Rendering Options {#Rendering+Options}</h3>
+<h3 id="Rendering-Options">Rendering Options</h3>
 <ul>
 <li>
 <p>embedding fonts</p>
@@ -421,7 +421,7 @@ $(document).ready(function () {
 <p>binary/ascii switch</p>
 </li>
 </ul>
-<h3 id="render-results-renderresults">Render Results {#Render+Results}</h3>
+<h3 id="Render-Results">Render Results</h3>
 <p>Generate Output statistics from FOP:</p>
 <ul>
 <li>
@@ -437,7 +437,7 @@ $(document).ready(function () {
 <p>recoverable errors such as overflow</p>
 </li>
 </ul>
-<h3 id="setting-up-settingup">Setting Up {#Setting+Up}</h3>
+<h3 id="Setting-Up">Setting Up</h3>
 <p>The Driver handles the XML input. The user agent information is through the FOUserAgent. Handle logging through the user agent. Options could also be handled through the user agent, using mime type selection for renderer options.</p>
 <h3 id="Others">Others</h3>
 <p>Render to more than one renderer at once (maybe not from the command line). For example you could generate a PDF for the archive and the PS for the printer in one run. It would probably be faster than converting the PDF to PostScript afterwards. Make the fo tree reuseable. If the fonts are the same then use the same area tree to output to different renderers.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html Fri Dec  7 16:08:03 2012
@@ -356,7 +356,7 @@ $(document).ready(function () {
 <p>Images are cached according to the context, using the FOUserAgent as a key. Once the context is finished the images are added to a common weak hashmap so that other contexts can load these images or the data will be garbage collected if required.</p>
 <p>If images are to be used commonly then we cannot dispose of data in the FopImage when cached by the renderer. Also if different contexts have different base directories for resolving relative url's then the loading and caching must be separate. We can have a cache that shares images among all contexts or only loads an image for a context.</p>
 <p>The cache uses an image loader so that it can synchronize the image loading on an image by image basis. Finding and adding an image loader to the cache is also synchronized to prevent thread problems.</p>
-<h2 id="invalid-images-invalidimages">Invalid Images {#Invalid+Images}</h2>
+<h2 id="Invalid-Images">Invalid Images</h2>
 <p>If an image cannot be loaded for some reason, for example the url is invalid or the image data is corrupt or an unknown type. Then it should only attempt to load the image once. All other attempts to get the image should return null so that it can be easily handled.<br></br>This will prevent any extra processing or waiting.</p>
 <h2 id="Reading">Reading</h2>
 <p>Once a stream is opened for the image url then a set of image readers is used to determine what type of image it is. The reader can peek at the image header or if necessary load the image. The reader can also get the image size at this stage. The reader then can provide the mime type to create the image object to load the rest of the information.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/pdf-library.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/pdf-library.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/pdf-library.html Fri Dec  7 16:08:03 2012
@@ -344,10 +344,10 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-design-pdf-library">Apache&trade; FOP Design: PDF Library</h1>
 <h2 id="intro">Introduction</h2>
 <p>The PDF Library is an independant package of classes in Apache&trade; FOP. These class provide a simple way to construct documents and add the contents. The classes are found in <code>org.apache.fop.pdf.*</code>.</p>
-<h2 id="pdf-document-pdfdocument">PDF Document {#PDF+Document}</h2>
+<h2 id="PDF-Document">PDF Document</h2>
 <p>This is where most of the document is created and put together.</p>
 <p>It sets up the header, trailer and resources. Each page is made and added to the document. There are a number of methods that can be used to create/add certain PDF objects to the document.</p>
-<h2 id="building-pdf-buildingpdf">Building PDF {#Building+PDF}</h2>
+<h2 id="Building-PDF">Building PDF</h2>
 <p>The PDF Document is built by creating a page for each page in the Area Tree.</p>
 <p>This page then has all the contents added. The page is then added to the document and available objects can be written to the output stream.</p>
 <p>The contents of the page are things such as text, lines, images etc. The PDFRenderer inserts the text directly into a pdf stream. The text consists of markup to set fonts, set text position and add text.</p>
@@ -359,7 +359,7 @@ $(document).ready(function () {
 <p>Support for embedding fonts and using the default Acrobat fonts.</p>
 <h3 id="Images">Images</h3>
 <p>Images can be inserted into a page. The image can either be inserted as a pixel map or directly insert a jpeg image.</p>
-<h3 id="stream-filters-streamfilters">Stream Filters {#Stream+Filters}</h3>
+<h3 id="Stream-Filters">Stream Filters</h3>
 <p>A number of filters are available to encode the pdf streams. These filters can compress the data or change it such as converting to hex.</p>
 <h3 id="Links">Links</h3>
 <p>A pdf link can be added for an area on the page. This link can then point to an external destination or a position on any page in the document.</p>



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


Mime
View raw message