xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From psan...@apache.org
Subject svn commit: r1418370 - in /xmlgraphics/site/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:07:02 GMT
Author: psancho
Date: Fri Dec  7 16:06:48 2012
New Revision: 1418370

URL: http://svn.apache.org/viewvc?rev=1418370&view=rev
Log:
markdown.headerid doesn't like '+'; replaced with '-'

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

Modified: xmlgraphics/site/trunk/content/batik/dev/test.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/dev/test.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/dev/test.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/dev/test.mdtext Fri Dec  7 16:06:48 2012
@@ -18,7 +18,7 @@ While the test suites in the infrastruct
 
 ## The test infrastructure {#infrastructure}
 
-### High-level interfaces {#High-level+interfaces}
+### High-level interfaces {#High-level-interfaces}
 
 The following are the high level interfaces in the infrastructure.
 
@@ -43,7 +43,7 @@ A `TestSuite` is a test aggregation whic
 :
 A `TestReportProcessor` is used to analyze a `TestReport`. A specific implementation can choose to create graphs, send an email or write an HTML file.
 
-### Default implementations {#Default+implementations}
+### Default implementations {#Default-implementations}
 
 The test infrastructure comes with a number of default implementations for the interfaces described above. Specifically:
 
@@ -73,7 +73,7 @@ This class is a sample `TestReportProces
 :
 This is another implementation of the `TestReportProcessor` interface that emails a test report to a list of destination e-mail addresses.
 
-### XML implementations {#XML+implementations}
+### XML implementations {#XML-implementations}
 
 The test infrastructure is using XML-out (and XML-in too, see the [Running a test suite](#runningATestSuite) section) as a favorite way to generate test reports. The [XMLTestReportProcessor](../javadoc/org/apache/batik/test/XMLTestReportProcessor.html) implementation of the `TestReportProcessor` interface. It outputs reports in XML in a configurable directory.
 
@@ -83,7 +83,7 @@ The `XMLTestReportProcessor` can notify 
 
 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.
 
-### Describing a test suite {#Describing+a+test+suite}
+### Describing a test suite {#Describing-a-test-suite}
 
 Test suites can be described in XML (XML-in refered to earlier in this document). The general format for describing a test suite is:
 
@@ -197,7 +197,7 @@ The regard test suite contains all the r
 
 The following describes how to use the regard tool and some of the most important tests in the regard test suite.
 
-### Running regard {#Running+regard}
+### Running regard {#Running-regard}
 
 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:
 
@@ -217,7 +217,7 @@ build.sh regard unitTesting.ts batikFX.s
 
 will run all the tests with an ID containing `unitTesting.ts` (i.e., all the test selection unit testing, see `test-resources/org/apache/batik/gvt/unitTesting.xml`) and the accuracy rendering test on `batikFX.svg` (because it is the only test with `batikFX.svg` in its ID).
 
-### Rendering accuracy tests {#Rendering+accuracy+tests}
+### Rendering accuracy tests {#Rendering-accuracy-tests}
 
 There is a `Test` implementation, [SVGRenderingAccuracyTest](../javadoc/org/apache/batik/test/SVGRenderingAccuracyTest.html), 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.
 
@@ -239,9 +239,9 @@ In addition to this default behavior, th
 
 Finally, to ease the process of creating “accepted” variation images, `SVGRenderingAccuracyTest` can take an optional file name (called `saveVariation`) 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 `saveVariation` 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.
 
-### Day to day use of regard {#Day+to+day+use+of+regard}
+### Day to day use of regard {#Day-to-day-use-of-regard}
 
-#### Initial set up ## {#Initial+set+up}
+#### Initial set up ## {#Initial-set-up}
 
 To set up the test environment the first time, you need to:
 
@@ -263,11 +263,11 @@ build regard
 
 Check the newly generated HTML report in the `test-reports/html` directory: there should no longer be any test failure.
 
-#### Daily usage ## {#Daily+usage}
+#### Daily usage ## {#Daily-usage}
 
 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.
 
-### SVG generator tests {#SVG+generator+tests}
+### SVG generator tests {#SVG-generator-tests}
 
 Regard contains over 100 tests for checking regressions on the SVG generator. If you use `svggen` as an argument to regard, all the SVG generator tests will be run (because `regard.xml` points to `test-resources/org/apache/batik/svggen/regsvggen.xml`, which is a test suite description for the SVG generator and that file’s root `testSuite` element has the “svggen” ID).
 
@@ -275,7 +275,7 @@ Regard contains over 100 tests for check
 
 Writing a new test involves either configuring a new test or writing a new `Test` 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 `Test` implementation.
 
-### Adding a new test configuration {#Adding+a+new+test+configuration}
+### Adding a new test configuration {#Adding-a-new-test-configuration}
 
 Imagine that you add a cool new test case to the `samples` directory, such as `linking-viewBox.svg`. In order to check for regressions on that file you can add the following entry:
 
@@ -295,7 +295,7 @@ Imagine that you add a cool new test cas
 
 to the `test-resources/org/apache/batik/test/samplesRendering.xml` 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 `test-references/samples/tests`. 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.
 
-### Writing a new test {#Writing+a+new+test}
+### Writing a new test {#Writing-a-new-test}
 
 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 `test-sources` directory, in `test-sources/org/apache/batik/bridge` in our example, and let's call it `ErrorHandlingTest`. To simplify the implementation of the `Test` interface, you can choose to derive from the `AbstractTest` class and generate a `DefaultTestReport`.
 

Modified: xmlgraphics/site/trunk/content/batik/uses.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/uses.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/uses.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/uses.mdtext Fri Dec  7 16:06:48 2012
@@ -5,7 +5,7 @@ Title: Projects using Batik
 [TOC]
 
 
-## Examples of projects and products using Batik {#Examples+of+projects+and+products+using+Batik}
+## Examples of projects and products using Batik {#Examples-of-projects-and-products-using-Batik}
 
 While it is hard to track projects and products which are using Batik, here are a few that are known of:
 

Modified: xmlgraphics/site/trunk/content/batik/using/extending.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/extending.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/extending.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/extending.mdtext Fri Dec  7 16:06:48 2012
@@ -200,7 +200,7 @@ StreamRegistryEntry
 :
 A [StreamRegistryEntry](../javadoc/org/apache/batik/ext/awt/image/spi/StreamRegistryEntry.html) works with a markable [InputStream](http://java.sun.com/j2se/1.5.0/docs/api/java/io/InputStream.html). 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.
 
-### Helper classes {#Helper+classes}
+### Helper classes {#Helper-classes}
 
 There exists quite a number of classes to assist in implementing a `RegistryEntry`. 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.
 

Modified: xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext (original)
+++ xmlgraphics/site/trunk/content/batik/using/svg-generator.mdtext Fri Dec  7 16:06:48 2012
@@ -119,7 +119,7 @@ In the previous section, we have just se
 
 Instead of creating the `SVGGraphics2D` just by using the `Document` that will be used as a factory for creating the SVG elements, we can use the constructor that uses an [SVGGeneratorContext](../javadoc/org/apache/batik/svggen/SVGGeneratorContext.html) instance. By providing your own `SVGGeneratorContext` instance, you will be able to do advanced customization. You will find below several examples of possible customizations.
 
-### Have your own comment in the generated SVG file {#Have+your+own+comment+in+the+generated+SVG+file}
+### Have your own comment in the generated SVG file {#Have-your-own-comment-in-the-generated-SVG-file}
 
 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.
 
@@ -133,7 +133,7 @@ We begin with the simplest possible exam
     ctx.setComment("Generated by FooApplication with Batik SVG Generator");
     SVGGraphics2D g2d = new SVGGraphics2D(ctx, false);
 
-## Use embedded SVG Fonts in the generated SVG file {#Use+embedded+SVG+Fonts+in+the+generated+SVG+file}
+## Use embedded SVG Fonts in the generated SVG file {#Use-embedded-SVG-Fonts-in-the-generated-SVG-file}
 
 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.
 
@@ -147,7 +147,7 @@ In order to have a self-contained SVG fi
     ctx.setEmbeddedFontsOn(true);
     SVGGraphics2D g2d = new SVGGraphics2D(ctx, true);
 
-## Customizing the way images are stored {#Customizing+the+way+images+are+stored}
+## Customizing the way images are stored {#Customizing-the-way-images-are-stored}
 
 Every time you call one of the `drawImage` methods provided by the `Graphics2D` 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.
 
@@ -207,7 +207,7 @@ With the caching image handlers, it is e
       }
     }
 
-## Customizing the generated SVG style {#Customizing+the+generated+SVG+style}
+## Customizing the generated SVG style {#Customizing-the-generated-SVG-style}
 
 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 `style` element section and reference them through the class attribute. In this case you will need to define a new [StyleHandler](../javadoc/org/apache/batik/svggen/StyleHandler.html) as below.
 
@@ -267,7 +267,7 @@ Then you can create and use an `SVGGraph
     // Dump the root content to a given Writer myWriter.
     g2d.stream(root, myWriter);
 
-## Extending Paint object to SVG element translation {#Extending+Paint+object+to+SVG+element+translation}
+## Extending Paint object to SVG element translation {#Extending-Paint-object-to-SVG-element-translation}
 
 The `SVGGraphics2D` 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 [Paint](http://java.sun.com/j2se/1.4.2/docs/api/java/awt/Paint.html) interface. In this case, you will need to write an [ExtensionHandler](../javadoc/org/apache/batik/svggen/ExtensionHandler.html) that you will set on your `SVGGeneratorContext`.
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext Fri Dec  7 16:06:48 2012
@@ -171,7 +171,7 @@ The default value for the "rendering" se
 
 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.
 
-## When it does not work {#When+it+does+not+work}
+## When it does not work {#When-it-does-not-work}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext Fri Dec  7 16:06:48 2012
@@ -19,13 +19,13 @@ The following table summarizes the font 
 | TXT | yes (used for layout but not for output) | no | yes (used for layout but not for output) | no |
 | XML | yes | no | yes | n/a |
 
-## Base-14 Fonts {#Base-14+Fonts}
+## Base-14 Fonts {#Base-14-Fonts}
 
 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.
 
 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.
 
-## Missing Fonts {#Missing+Fonts}
+## Missing Fonts {#Missing-Fonts}
 
 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).
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/knownissues_overview.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/knownissues_overview.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/knownissues_overview.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/knownissues_overview.mdtext Fri Dec  7 16:06:48 2012
@@ -3,20 +3,20 @@ Title: Apache(tm) FOP: Known Issues
 #Apache™ FOP: Known Issues
 
 
-## Known issues {#Known+issues}
+## Known issues {#Known-issues}
 
 This page lists currently known issues in the current release.
 
 For additional information on known issues in Apache™ FOP, please have a look at the following pages, too:
 
 
--  [the bug list in Bugzilla](../bugs.html) 
+-  [the bug list in Bugzilla](../bugs.html)
 
--  [the task list in the Wiki](http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks) 
+-  [the task list in the Wiki](http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks)
 
 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.
 
-### FO Tree {#FO+Tree}
+### FO Tree {#FO-Tree}
 
 This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.
 
@@ -24,7 +24,7 @@ This section lists disabled test cases i
 
 
 
-### Layout Engine {#Layout+Engine}
+### Layout Engine {#Layout-Engine}
 
 This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.
 
@@ -80,11 +80,11 @@ This section lists disabled test cases i
 
 
 
- **footnote_in_list.xml** (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: [http://issues.apache.org/bugzilla/show_bug.cgi?id=37579](http://issues.apache.org/bugzilla/show_bug.cgi?id=37579) 
+ **footnote_in_list.xml** (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: [http://issues.apache.org/bugzilla/show_bug.cgi?id=37579](http://issues.apache.org/bugzilla/show_bug.cgi?id=37579)
 
 
 
- **footnote_in_table.xml** (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: [http://issues.apache.org/bugzilla/show_bug.cgi?id=37579](http://issues.apache.org/bugzilla/show_bug.cgi?id=37579) 
+ **footnote_in_table.xml** (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: [http://issues.apache.org/bugzilla/show_bug.cgi?id=37579](http://issues.apache.org/bugzilla/show_bug.cgi?id=37579)
 
 
 
@@ -108,7 +108,7 @@ This section lists disabled test cases i
 
 
 
- **inline_word-spacing_text-align_justify.xml** (inline word-spacing text-align justify):<br></br> *TODO: Add missing description in disabled-testcases.xml!* 
+ **inline_word-spacing_text-align_justify.xml** (inline word-spacing text-align justify):<br></br> *TODO: Add missing description in disabled-testcases.xml!*
 
 
 
@@ -116,7 +116,7 @@ This section lists disabled test cases i
 
 
 
- **leader_leader-pattern_use-content_bug.xml** (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: [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) 
+ **leader_leader-pattern_use-content_bug.xml** (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: [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)
 
 
 
@@ -184,7 +184,7 @@ This section lists disabled test cases i
 
 
 
-### Other known issues {#Other+known+issues}
+### Other known issues {#Other-known-issues}
 
 This section lists other known issues.
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext Fri Dec  7 16:06:48 2012
@@ -9,7 +9,7 @@ Apache&trade; FOP supports encryption of
 
 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.
 
-## Usage (command line) {#Usage+%28command+line%29}
+## Usage (command line) {#Usage-%28command-line%29}
 
 Encryption is enabled by supplying any of the encryption related options.
 
@@ -21,7 +21,7 @@ A user password, supplied with the `-u` 
 
 Further restrictions can be imposed by using the `-noprint`, `-nocopy`, `-noedit` and `-noannotations` options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.
 
-## Usage (embedded) {#Usage+%28embedded%29}
+## Usage (embedded) {#Usage-%28embedded%29}
 
 When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/releaseNotes_0.95.mdtext Fri Dec  7 16:06:48 2012
@@ -29,17 +29,17 @@ The image libraries Jimi and JAI are no 
 This final 0.95 release also includes all of the [changes made for Apache FOP 0.95beta](changes_0.95beta.html).</section></notes>
 # Major Changes in Version 0.95 {#version_0.95}
 This is not a complete list of changes, just some of the more important ones. A full list of changes in this release [is available](changes_0.95.html).
-## Changes to the Code Base {#Changes+to+the+Code+Base}
+## Changes to the Code Base {#Changes-to-the-Code-Base}
 
 
 - ![fix](/images/fix.jpg)Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue [44887](http://issues.apache.org/bugzilla/show_bug.cgi?id=44887).
 
-### Changes to the Layout Engine {#Changes+to+the+Layout+Engine}
+### Changes to the Layout Engine {#Changes-to-the-Layout-Engine}
 
 
 - ![fix](/images/fix.jpg)Various bugfixes for table layout. Committed by VH. See Issue [44621](http://issues.apache.org/bugzilla/show_bug.cgi?id=44621).
 
-### Changes to Renderers (Output Formats) {#Changes+to+Renderers+%28Output+Formats%29}
+### Changes to Renderers (Output Formats) {#Changes-to-Renderers-%28Output-Formats%29}
 
 
 - ![fix](/images/fix.jpg)Fixed positioning of absolutely positioned block-containers in multi-column documents. Committed by JM.

Modified: xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext Fri Dec  7 16:06:48 2012
@@ -9,7 +9,7 @@ This page describes the [accessibility](
 
 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.
 
-## Enabling accessibility {#Enabling+accessibility}
+## Enabling accessibility {#Enabling-accessibility}
 
 There are 3 ways to enable accessibility:
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext Fri Dec  7 16:06:48 2012
@@ -229,7 +229,7 @@ The default value for the "renderer-reso
 
 By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.
 
-## When it does not work {#When+it+does+not+work}
+## When it does not work {#When-it-does-not-work}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext Fri Dec  7 16:06:48 2012
@@ -19,7 +19,7 @@ The following table summarizes the font 
 | TXT | yes (used for layout but not for output) | no | yes (used for layout but not for output) | no |
 | XML | yes | no | yes | n/a |
 
-## Base-14 Fonts {#Base-14+Fonts}
+## Base-14 Fonts {#Base-14-Fonts}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/knownissues_overview.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/knownissues_overview.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/knownissues_overview.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/knownissues_overview.mdtext Fri Dec  7 16:06:48 2012
@@ -3,24 +3,24 @@ Title: Apache(tm) FOP: Known Issues
 #Apache&trade; FOP: Known Issues
 
 
-## Known issues {#Known+issues}
+## Known issues {#Known-issues}
 
 This page lists currently known issues in the current release.
 
 For additional information on known issues in Apache&trade; FOP, please have a look at the following pages, too:
 
 
--  [the bug list in Bugzilla](../bugs.html) 
+-  [the bug list in Bugzilla](../bugs.html)
 
--  [the task list in the Wiki](http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks) 
+-  [the task list in the Wiki](http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks)
 
 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.
 
-### FO Tree {#FO+Tree}
+### FO Tree {#FO-Tree}
 
 This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.
 
- **demo-test-failure.fo** (demo test failure):<br></br> *TODO: Add missing description in disabled-testcases.xml!* 
+ **demo-test-failure.fo** (demo test failure):<br></br> *TODO: Add missing description in disabled-testcases.xml!*
 
 
 
@@ -28,7 +28,7 @@ This section lists disabled test cases i
 
 
 
-### Layout Engine {#Layout+Engine}
+### Layout Engine {#Layout-Engine}
 
 This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.
 
@@ -104,7 +104,7 @@ This section lists disabled test cases i
 
 
 
- **inline_word-spacing_text-align_justify.xml** (inline word-spacing text-align justify):<br></br> *TODO: Add missing description in disabled-testcases.xml!* 
+ **inline_word-spacing_text-align_justify.xml** (inline word-spacing text-align justify):<br></br> *TODO: Add missing description in disabled-testcases.xml!*
 
 
 
@@ -112,7 +112,7 @@ This section lists disabled test cases i
 
 
 
- **leader_leader-pattern_use-content_bug.xml** (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: [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) 
+ **leader_leader-pattern_use-content_bug.xml** (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: [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)
 
 
 
@@ -168,7 +168,7 @@ This section lists disabled test cases i
 
 
 
-### Other known issues {#Other+known+issues}
+### Other known issues {#Other-known-issues}
 
 This section lists other known issues.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext Fri Dec  7 16:06:48 2012
@@ -9,7 +9,7 @@ Apache&trade; FOP supports encryption of
 
 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.
 
-## Usage (command line) {#Usage+%28command+line%29}
+## Usage (command line) {#Usage-%28command-line%29}
 
 Encryption is enabled by supplying any of the encryption related options.
 
@@ -21,7 +21,7 @@ A user password, supplied with the `-u` 
 
 Further restrictions can be imposed by using the `-noprint`, `-nocopy`, `-noedit` and `-noannotations` options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.
 
-## Usage (embedded) {#Usage+%28embedded%29}
+## Usage (embedded) {#Usage-%28embedded%29}
 
 When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/releaseNotes_1.0.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/releaseNotes_1.0.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/releaseNotes_1.0.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/releaseNotes_1.0.mdtext Fri Dec  7 16:06:48 2012
@@ -5,7 +5,7 @@ Title: Release Notes for Apache FOP 1.0
 
 ## Major Changes in Version 1.0 {#version_1.0}
 This is not a complete list of changes, just some of the more important ones. A full list of changes in this release [is available](changes_1.0.html).
-## Changes to the Code Base {#Changes+to+the+Code+Base}
+## Changes to the Code Base {#Changes-to-the-Code-Base}
 
 
 - ![fix](/images/fix.jpg) Fixed memory leak in property cache (not cleaning stale PropertyCache$CacheEntry instances). Committed by JM.
@@ -14,21 +14,21 @@ This is not a complete list of changes, 
 
 - ![add](/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.
 
-### Changes to the Font Subsystem {#Changes+to+the+Font+Subsystem}
+### Changes to the Font Subsystem {#Changes-to-the-Font-Subsystem}
 
 
 - ![add](/images/add.jpg) Add support for font substitution. Committed by AC.
 
 - ![add](/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.
 
-### Changes to the Layout Engine {#Changes+to+the+Layout+Engine}
+### Changes to the Layout Engine {#Changes-to-the-Layout-Engine}
 
 
 - ![add](/images/add.jpg) Added limited support for pages of different inline-progression-dimensions within a page-sequence. Committed by VH.
 
 - ![add](/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.
 
-### Changes to Renderers (Output Formats) {#Changes+to+Renderers+%28Output+Formats%29}
+### Changes to Renderers (Output Formats) {#Changes-to-Renderers-%28Output-Formats%29}
 
 
 - ![add](/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.

Modified: xmlgraphics/site/trunk/content/fop/1.1/accessibility.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/accessibility.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/accessibility.mdtext Fri Dec  7 16:06:48 2012
@@ -8,7 +8,7 @@ This page describes the [accessibility](
 
 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.
 
-## Enabling accessibility {#Enabling+accessibility}
+## Enabling accessibility {#Enabling-accessibility}
 
 There are 3 ways to enable accessibility:
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext Fri Dec  7 16:06:48 2012
@@ -16,7 +16,7 @@ This page describes the [complex scripts
 
 - Support for advanced number to string formatting.
 
-## Disabling complex scripts {#Disabling+complex+scripts}
+## Disabling complex scripts {#Disabling-complex-scripts}
 
 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:
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext Fri Dec  7 16:06:48 2012
@@ -252,7 +252,7 @@ The default line width is device depende
 
 By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.
 
-## When it does not work {#When+it+does+not+work}
+## When it does not work {#When-it-does-not-work}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext Fri Dec  7 16:06:48 2012
@@ -19,7 +19,7 @@ The following table summarizes the font 
 | TXT | yes (used for layout but not for output) | no | yes (used for layout but not for output) | no |
 | XML | yes | no | yes | n/a |
 
-## Base-14 Fonts {#Base-14+Fonts}
+## Base-14 Fonts {#Base-14-Fonts}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/knownissues_overview.mdtext Fri Dec  7 16:06:48 2012
@@ -3,7 +3,7 @@ Title: Apache(tm) FOP: Known Issues
 #Apache&trade; FOP: Known Issues
 
 
-## Known issues {#Known+issues}
+## Known issues {#Known-issues}
 
 This page lists currently known issues in the current release.
 
@@ -16,7 +16,7 @@ For additional information on known issu
 
 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.
 
-### FO Tree {#FO+Tree}
+### FO Tree {#FO-Tree}
 
 This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.
 
@@ -28,7 +28,7 @@ This section lists disabled test cases i
 
 
 
-### Layout Engine {#Layout+Engine}
+### Layout Engine {#Layout-Engine}
 
 This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.
 
@@ -168,7 +168,7 @@ This section lists disabled test cases i
 
 
 
-### Other known issues {#Other+known+issues}
+### Other known issues {#Other-known-issues}
 
 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 [older bugs that remain open](http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=2010-07-20&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=2001-01-01&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&product=Fop). For all open issues that post-date FOP 1.0, see [newer bugs that remain open](http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=Now&chfield=%5BBug%20creation%5D&query_format=advanced&chfieldfrom=2010-07-20&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&product=Fop).
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext Fri Dec  7 16:06:48 2012
@@ -9,7 +9,7 @@ Apache&trade; FOP supports encryption of
 
 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.
 
-## Usage (command line) {#Usage+%28command+line%29}
+## Usage (command line) {#Usage-%28command-line%29}
 
 Encryption is enabled by supplying any of the encryption related options.
 
@@ -33,7 +33,7 @@ Further restrictions can be imposed by u
 |  `-noprinthq`  | disable high quality printing |
 
 
-## Usage (embedded) {#Usage+%28embedded%29}
+## Usage (embedded) {#Usage-%28embedded%29}
 
 When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/releaseNotes_1.1.mdtext Fri Dec  7 16:06:48 2012
@@ -5,7 +5,7 @@ Title: Release Notes for Apache FOP 1.1
 
 ## Major Changes in Version 1.1 {#version_1.1}
 This is not a complete list of changes, just some of the more important ones. A full list of changes in this release [is available](changes_1.1.html).
-## Changes to the Code Base {#Changes+to+the+Code+Base}
+## Changes to the Code Base {#Changes-to-the-Code-Base}
 
 
 - ![fix](/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 [53083](http://issues.apache.org/bugzilla/show_bug.cgi?id=53083).
@@ -34,12 +34,12 @@ This is not a complete list of changes, 
 
 - ![add](/images/add.jpg) Added support for resolution of relative URIs against a specified xml:base during property refinement. Committed by AD. See Issue [48334](http://issues.apache.org/bugzilla/show_bug.cgi?id=48334).
 
-### Changes to the User Configuration {#Changes+to+the+User+Configuration}
+### Changes to the User Configuration {#Changes-to-the-User-Configuration}
 
 
 - ![add](/images/add.jpg) Added configuration option to set the version of the output PDF document. Committed by VH. Thanks to Mehdi Houshmand. See Issue [51385](http://issues.apache.org/bugzilla/show_bug.cgi?id=51385).
 
-### Changes to the Font Subsystem {#Changes+to+the+Font+Subsystem}
+### Changes to the Font Subsystem {#Changes-to-the-Font-Subsystem}
 
 
 - ![add](/images/add.jpg) Add support for OpenType advanced typographic tables (GDEF, GSUB, GPOS). Committed by GA.
@@ -52,12 +52,12 @@ This is not a complete list of changes, 
 
 - ![add](/images/add.jpg) Added convenience support for the flushing of the Fop font cache file from the command line. Committed by AC.
 
-### Changes to the Image Support {#Changes+to+the+Image+Support}
+### Changes to the Image Support {#Changes-to-the-Image-Support}
 
 
 - ![fix](/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 [40676](http://issues.apache.org/bugzilla/show_bug.cgi?id=40676).
 
-### Changes to the Layout Engine {#Changes+to+the+Layout+Engine}
+### Changes to the Layout Engine {#Changes-to-the-Layout-Engine}
 
 
 - ![fix](/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 [45715](http://issues.apache.org/bugzilla/show_bug.cgi?id=45715).
@@ -76,7 +76,7 @@ This is not a complete list of changes, 
 
 - ![fix](/images/fix.jpg) Fix for correct behavior of keep-together.within-line in case there are nested inlines Committed by AD. See Issue [49848](http://issues.apache.org/bugzilla/show_bug.cgi?id=49848).
 
-### Changes to Renderers (Output Formats) {#Changes+to+Renderers+%28Output+Formats%29}
+### Changes to Renderers (Output Formats) {#Changes-to-Renderers-%28Output-Formats%29}
 
 
 - ![add](/images/add.jpg) Added possibility to embed TrueType fonts in PostScript. Committed by VH. See Issue [52338](http://issues.apache.org/bugzilla/show_bug.cgi?id=52338).

Modified: xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/breakpos.mdtext Fri Dec  7 16:06:48 2012
@@ -7,17 +7,17 @@ Title: Apache(tm) FOP Design: Layout Man
 
 As explained in [Layout](layout.html), 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 *break possibilities* (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.
 
-## Anatomy of a Break Possibility {#Anatomy+of+a+Break+Possibility}
+## Anatomy of a Break Possibility {#Anatomy-of-a-Break-Possibility}
 
 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.
 
 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.
 
-## Turning Break Possibilities into Areas {#Turning+Break+Possibilities+into+Areas}
+## Turning Break Possibilities into Areas {#Turning-Break-Possibilities-into-Areas}
 
 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.
 
-## A walk-through {#A+walk-through}
+## A walk-through {#A-walk-through}
 
 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 *galley* manager.
 
@@ -47,11 +47,11 @@ The FlowLM sees if the returned stacking
 
 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.
 
-## Some issues {#Some+issues}
+## Some issues {#Some-issues}
 
 Following are a few remarks on specific issues.
 
-### Where Line Layout Managers are created {#Where+Line+Layout+Managers+are+created}
+### Where Line Layout Managers are created {#Where-Line-Layout-Managers-are-created}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext Fri Dec  7 16:06:48 2012
@@ -12,7 +12,7 @@ Common places where FOP is embedded is i
 
 ## Settings {#Settings}
 
-### User Agent {#User+Agent}
+### User Agent {#User-Agent}
 
 Possible meanings for a user agent:
 
@@ -36,14 +36,14 @@ The user agent is responsible for supply
 
 - Logging setup (LogKit, Log4J, JDK14Logging)
 
-### XML input {#XML+input}
+### XML input {#XML-input}
 
 
 - various ways to supply FOP with the xsl:fo file, fo, xml+xsl
 
 - sax handler
 
-### general options {#general+options}
+### general options {#general-options}
 
 
 - base url
@@ -52,7 +52,7 @@ The user agent is responsible for supply
 
 - which implementation of a particular LayoutManager to use
 
-### Rendering Options {#Rendering+Options}
+### Rendering Options {#Rendering-Options}
 
 
 - embedding fonts
@@ -70,7 +70,7 @@ for the PS renderer (eventually):
 
 - binary/ascii switch
 
-### Render Results {#Render+Results}
+### Render Results {#Render-Results}
 
 Generate Output statistics from FOP:
 
@@ -83,7 +83,7 @@ Generate Output statistics from FOP:
 
 - recoverable errors such as overflow
 
-### Setting Up {#Setting+Up}
+### Setting Up {#Setting-Up}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/design/images.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/images.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/images.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/images.mdtext Fri Dec  7 16:06:48 2012
@@ -31,7 +31,7 @@ If images are to be used commonly then w
 
 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.
 
-## Invalid Images {#Invalid+Images}
+## Invalid Images {#Invalid-Images}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/design/pdf-library.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/pdf-library.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/pdf-library.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/pdf-library.mdtext Fri Dec  7 16:06:48 2012
@@ -7,13 +7,13 @@ Title: Apache(tm) FOP Design: PDF Librar
 
 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 `org.apache.fop.pdf.*`.
 
-## PDF Document {#PDF+Document}
+## PDF Document {#PDF-Document}
 
 This is where most of the document is created and put together.
 
 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.
 
-## Building PDF {#Building+PDF}
+## Building PDF {#Building-PDF}
 
 The PDF Document is built by creating a page for each page in the Area Tree.
 
@@ -37,7 +37,7 @@ Support for embedding fonts and using th
 
 Images can be inserted into a page. The image can either be inserted as a pixel map or directly insert a jpeg image.
 
-### Stream Filters {#Stream+Filters}
+### Stream Filters {#Stream-Filters}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/design/renderers.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/renderers.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/renderers.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/renderers.mdtext Fri Dec  7 16:06:48 2012
@@ -29,7 +29,7 @@ Because font metrics (and therefore layo
 
 The render context is used by handlers. It contains information about the current state of the renderer, such as the page, the position, and any other miscellanous objects that are required to draw into the page.
 
-## XML Handling {#XML+Handling}
+## XML Handling {#XML-Handling}
 
 A document may contain information in the form of XML for an image or instream foreign object. This XML is handled through the user agent. A standard extension for PDF is the SVG handler.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/design/svg.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/svg.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/svg.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/svg.mdtext Fri Dec  7 16:06:48 2012
@@ -17,7 +17,7 @@ This creates the necessary PDF informati
 
 Most of the work is done in the PDFGraphics2D class. There are also a few bridges that are plugged into batik to provide different behaviour for some SVG elements.
 
-## Text Drawing {#Text+Drawing}
+## Text Drawing {#Text-Drawing}
 
 Normally batik converts text into a set of curved shapes.
 
@@ -27,7 +27,7 @@ To handle this there is a PDFTextElement
 
 Text is considered simple if the font is available, the font size is useable and there are no tspans or other complications. This can make the resulting PDF significantly smaller.
 
-## PDF Links {#PDF+Links}
+## PDF Links {#PDF-Links}
 
 To support links in PDF another batik element bridge is used. The PDFAElementBridge creates a PDFANode which inserts a link into the PDF document via the PDFGraphics2D.
 
@@ -39,11 +39,11 @@ Images are normally drawn into the PDFGr
 
 As PDF can support jpeg images then another element bridge is used so that the jpeg can be directly inserted into the PDF.
 
-## PDF Transcoder {#PDF+Transcoder}
+## PDF Transcoder {#PDF-Transcoder}
 
 Batik provides a mechanism to convert SVG into various formats. Through FOP we can convert an SVG document into a single paged PDF document. The page contains the SVG drawn as best as possible on the page. There is a PDFDocumentGraphics2D that creates a standalone PDF document with a single page. This is then drawn into by batik in the same way as with the PDFGraphics2D.
 
-## Other Outputs {#Other+Outputs}
+## Other Outputs {#Other-Outputs}
 
 When rendering to AWT the SVG is simply drawn onto the awt canvas using batik.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/implement.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/implement.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/implement.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/implement.mdtext Fri Dec  7 16:06:48 2012
@@ -18,7 +18,7 @@ The input FO document is sent to the FO 
 
 - Control is passed to *apps.Driver.render()*. This class fires up a SAX parser, the events from which indirectly control the remaining processing, including building the FO Tree, building the Area Tree, rendering, output and logging.
 
-## Formatting Object Tree {#Formatting+Object+Tree}
+## Formatting Object Tree {#Formatting-Object-Tree}
 
 | Trunk | Maintenance |
 |-------|-------------|
@@ -32,7 +32,7 @@ The input FO document is sent to the FO 
 
 There are layout managers for each type of layout decision. They take an FO Tree as input and build a laid-out Area Tree from it. The layout process involves finding out where line breaks and page breaks should be made, then creating the areas on the page. Static areas can then be added for any static regions. As pages are completed, they are added to the Area Tree.
 
-## Area Tree {#Area+Tree}
+## Area Tree {#Area-Tree}
 
 The area tree is a data structure designed to hold the page areas. These pages are then filled with the page regions and various areas. The area tree is used primarily as a minimal structure that can be rendered by the renderers.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/svg.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/svg.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/svg.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/svg.mdtext Fri Dec  7 16:06:48 2012
@@ -24,7 +24,7 @@ You will need Acrobat 5.0 to see transpa
 |--|---------|------------|
 | embedding svg |  [embedding.fo](fo/embedding.fo)  |  [embedding.fo.pdf](fo/embedding.fo.pdf)  |
 
-## Developer Notes {#Developer+Notes}
+## Developer Notes {#Developer-Notes}
 
 For most output formats in FOP the SVG is simply drawn into an image with Batik. For PDF there are a set of classes to handle drawing the [GVT (Graphic Vector Toolkit)](http://xml.apache.org/batik/architecture.html) into PDF markup.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/testing.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/testing.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/testing.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/testing.mdtext Fri Dec  7 16:06:48 2012
@@ -22,7 +22,7 @@ The [http://svn.apache.org/viewcvs.cgi/x
 
 ## Functional Testing {#functional}
 <warning>The "functional" testing section on this page is currently inoperative.</warning>
-## Running and Using Tests {#Running+and+Using+Tests}
+## Running and Using Tests {#Running-and-Using-Tests}
 
 Testing is an important part of getting FOP to operate correctly and conform to the necessary standards.
 
@@ -30,11 +30,11 @@ A testing system has been set up that wo
 
 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.
 
-### W3C TestSuite {#W3C+TestSuite}
+### W3C TestSuite {#W3C-TestSuite}
 
 The testing is set up so that you can download the testsuite from [http://www.w3.org/Style/XSL/TestSuite/](http://www.w3.org/Style/XSL/TestSuite/), 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.
 
-### Writing a Test {#Writing+a+Test}
+### Writing a Test {#Writing-a-Test}
 
 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.
 
@@ -44,11 +44,11 @@ A system test is one that tests the abit
 
 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.
 
-### Submitting a Test {#Submitting+a+Test}
+### Submitting a Test {#Submitting-a-Test}
 
 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.
 
-### How Testing Works {#How+Testing+Works}
+### How Testing Works {#How-Testing-Works}
 
 The tests are stored in the "<svn_repository>/test" directory.
 
@@ -60,6 +60,6 @@ The testing is done by reading a test su
 
 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.
 
-### SVG Testing {#SVG+Testing}
+### SVG Testing {#SVG-Testing}
 
 The testing of SVG is not part of this testing system. SVG is tested for its rendering accuracy by using the transcoding mechanism via [Apache Batik](http://xmlgraphics.apache.org/batik/). So that the only part that needs testing is how the SVG image is embedded inside the flow of the fo document.

Modified: xmlgraphics/site/trunk/content/fop/examples.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/examples.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/examples.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/examples.mdtext Fri Dec  7 16:06:48 2012
@@ -3,7 +3,7 @@ Title: Apache(tm) FOP Examples
 #Apache&trade; FOP Examples
 
 
-## Example Documents Using Apache&trade; FOP {#Example+Documents+Using+Apache%E2%84%A2+FOP}
+## Example Documents Using Apache&trade; FOP {#Example-Documents-Using-Apache%E2%84%A2-FOP}
 
 These examples have been rendered using Apache&trade; FOP:
 
@@ -33,7 +33,7 @@ Also, in the directory examples/fo/pagin
 
 Developers will find the first steps to a test suite for all implemented formatting objects and properties in test/xml in the source distribution.
 
-## Images Examples {#Images+Examples}
+## Images Examples {#Images-Examples}
 
 Embedding images in FO:
 
@@ -45,7 +45,7 @@ Embedding images in FO:
 
 Look also into the directory examples/fo/svg. There you find some very extensive SVG examples.
 
-## Instream Foreign Object Examples {#Instream+Foreign+Object+Examples}
+## Instream Foreign Object Examples {#Instream-Foreign-Object-Examples}
 
 Instream Foreign Object images in FO, there are more on the [SVG Page](dev/svg.html):
 

Modified: xmlgraphics/site/trunk/content/fop/knownissues.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/knownissues.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/knownissues.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/knownissues.mdtext Fri Dec  7 16:06:48 2012
@@ -3,7 +3,7 @@ Title: Apache(tm) FOP: Known Issues
 #Apache&trade; FOP: Known Issues
 
 
-## Known issues {#Known+issues}
+## Known issues {#Known-issues}
 
 This page lists currently known issues in the Apache&trade; FOP codebase. Please note that this list is generated from data in FOP's code repository (Trunk) and may not exactly represent the list of issues in the latest release.
 
@@ -16,7 +16,7 @@ For additional information on known issu
 
 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.
 
-### FO Tree {#FO+Tree}
+### FO Tree {#FO-Tree}
 
 This section lists currently disabled test cases in the test suite for the FO tree tests. The data for this section comes from [test/fotree/disabled-testcases.xml](http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/fotree/disabled-testcases.xml).
 
@@ -28,7 +28,7 @@ This section lists currently disabled te
 
 
 
-### Layout Engine {#Layout+Engine}
+### Layout Engine {#Layout-Engine}
 
 This section lists currently disabled test cases in the test suite for the layout engine tests. The data for this section comes from [test/layoutengine/disabled-testcases.xml](http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/layoutengine/disabled-testcases.xml).
 
@@ -168,7 +168,7 @@ This section lists currently disabled te
 
 
 
-### Other known issues {#Other+known+issues}
+### Other known issues {#Other-known-issues}
 
 This section lists other known issues.
 

Modified: xmlgraphics/site/trunk/content/fop/status.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/status.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/status.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/status.mdtext Fri Dec  7 16:06:48 2012
@@ -9,7 +9,7 @@ Title: Apache(tm) FOP Status
 
 Apache&trade; FOP version 0.95 was released on 5 August 2008. Apache&trade; FOP version 1.0 was released on 21 July 2010.
 
-## Development Status {#Development+Status}
+## Development Status {#Development-Status}
 
 The FOP code base is gradually evolving, from version 0.90 released on 22 November 2005, to version 1.0 released on 21 July 2010. Further releases in the 1.x series may be expected.
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/complexscripts.mdtext Fri Dec  7 16:06:48 2012
@@ -16,7 +16,7 @@ This page describes the [complex scripts
 
 - Support for advanced number to string formatting.
 
-## Disabling complex scripts {#Disabling+complex+scripts}
+## Disabling complex scripts {#Disabling-complex-scripts}
 
 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:
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext Fri Dec  7 16:06:48 2012
@@ -249,7 +249,7 @@ The default value for the "renderer-reso
 
 By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.
 
-## When it does not work {#When+it+does+not+work}
+## When it does not work {#When-it-does-not-work}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/fonts.mdtext Fri Dec  7 16:06:48 2012
@@ -19,7 +19,7 @@ The following table summarizes the font 
 | TXT | yes (used for layout but not for output) | no | yes (used for layout but not for output) | no |
 | XML | yes | no | yes | n/a |
 
-## Base-14 Fonts {#Base-14+Fonts}
+## Base-14 Fonts {#Base-14-Fonts}
 
 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.
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/pdfencryption.mdtext Fri Dec  7 16:06:48 2012
@@ -9,7 +9,7 @@ Apache&trade; FOP supports encryption of
 
 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.
 
-## Usage (command line) {#Usage+%28command+line%29}
+## Usage (command line) {#Usage-%28command-line%29}
 
 Encryption is enabled by supplying any of the encryption related options.
 
@@ -33,7 +33,7 @@ Further restrictions can be imposed by u
 |  `-noprinthq`  | disable high quality printing |
 
 
-## Usage (embedded) {#Usage+%28embedded%29}
+## Usage (embedded) {#Usage-%28embedded%29}
 
 When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:
 

Modified: xmlgraphics/site/trunk/content/repo.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/repo.mdtext?rev=1418370&r1=1418369&r2=1418370&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/repo.mdtext (original)
+++ xmlgraphics/site/trunk/content/repo.mdtext Fri Dec  7 16:06:48 2012
@@ -17,11 +17,11 @@ You can browse the repositories belongin
 
 - Apache&trade; XML Graphics Site: [http://svn.apache.org/viewvc/xmlgraphics/site/](http://svn.apache.org/viewvc/xmlgraphics/site/) (SVN repository)
 
-## Access the Source Tree {#Access+the+Source+Tree}
+## Access the Source Tree {#Access-the-Source-Tree}
 
 So, you've decided that you need access to the source tree to see the latest and greatest code. There're two different forms of SVN access. The first is `anonymous` and anybody can use it. The second requires that you have a login to the development server. If you don't know what this means, join the mailing list and find out.
 
-### Anonymous (read-only) SVN access {#Anonymous+%28read-only%29+SVN+access}
+### Anonymous (read-only) SVN access {#Anonymous-%28read-only%29-SVN-access}
 
 Anyone can checkout source code from our anonymous SVN server. To do so, simply use the following commands (if you are using a GUI SVN client, configure it appropriately):
 



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


Mime
View raw message