xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From psan...@apache.org
Subject svn commit: r1417468 [2/3] - in /xmlgraphics/site/trunk/content: batik/ batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Wed, 05 Dec 2012 15:11:05 GMT
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=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext Wed Dec  5 15:10:55 2012
@@ -27,7 +27,7 @@ Apache FOP cannot automatically generate
 
 - Table cells must have a table row as their parent.
 
-- Images must have an alternate text: use the `fox:alt-text` extension attribute (in the [fox namespace](extensions.html#fox-namespace) ) on `fo:external-graphic` and `fo:instream-foreign-object` to specify a short text describing the image.
+- Images must have an alternate text: use the `fox:alt-text` extension attribute (in the [fox namespace](extensions.html#fox-namespace)) on `fo:external-graphic` and `fo:instream-foreign-object` to specify a short text describing the image.
 
 - Ensure that the order of `fo:block-container` elements in a page corresponds to the reading order.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext Wed Dec  5 15:10:55 2012
@@ -46,7 +46,7 @@ Then create FOP tasks within your Ant bu
 | relativebase | For fileset usage only. A value of `true` specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of `false` specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified. | No, default is `false`. |
 | userconfig | User configuration file (same as the FOP "-c" command line option). | No |
 | messagelevel | Logging level<br></br>Possible values: `error`, `warn`, `info`, `verbose`, `debug`. **Currently doesn't work in FOP Trunk!!!**  | No, defaults to `verbose`  |
-| logFiles | Controls whether the names of the files that are processed are logged ( `true` ) or not ( `false` ). **Currently doesn't work in FOP Trunk!!!**  | No, default is `true`  |
+| logFiles | Controls whether the names of the files that are processed are logged (`true`) or not (`false`). **Currently doesn't work in FOP Trunk!!!**  | No, default is `true`  |
 | throwexceptions | Controls whether or not an exception is thrown if an error occurs during rendering. | Default is `true`  |
 
 <br/>

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=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext Wed Dec  5 15:10:55 2012
@@ -248,4 +248,4 @@ Check the following possibilities:
 
 and run the configuration file through a validating schema parser. Note that the schema cannot detect all errors, and that it is stricter about the order of some elements than FOP itself is.
 
-- Run FOP in debug mode (command line option `-d` ). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.
+- Run FOP in debug mode (command line option `-d`). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.

Modified: xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext Wed Dec  5 15:10:55 2012
@@ -316,7 +316,7 @@ This [example](http://svn.apache.org/vie
 
 ### ExampleXML2FO.java <a id="ExampleXML2FO"></a>
 
-This [example](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup) has nothing to do with FOP. It is there to show you how an XML file can be converted to XSL-FO using XSLT. The JAXP API is used to do the transformation. Make sure you've got a JAXP-compliant XSLT processor in your classpath (ex. [Xalan](http://xml.apache.org/xalan-j) ).
+This [example](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup) has nothing to do with FOP. It is there to show you how an XML file can be converted to XSL-FO using XSLT. The JAXP API is used to do the transformation. Make sure you've got a JAXP-compliant XSLT processor in your classpath (ex. [Xalan](http://xml.apache.org/xalan-j)).
 
 ![Example XML to XSL-FO](images/EmbeddingExampleXML2FO.png)
 
@@ -338,7 +338,7 @@ For this example we've created two class
 
 The XMLReader implementation (regard it as a special kind of XML parser) is responsible for creating SAX events from the Java object. The InputSource class is only used to hold the ProjectTeam object to be used.
 
-Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. [An older JAXP tutorial](http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html) ).
+Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. [An older JAXP tutorial](http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html)).
 
 ### ExampleObj2PDF.java <a id="ExampleObj2PDF"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/events.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/events.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/events.mdtext Wed Dec  5 15:10:55 2012
@@ -67,7 +67,7 @@ It is possible to gather all events for 
 
 ### Adding an EventListener <a id="add-listener"></a>
 
-To register the event listener with FOP, get the `EventBroadcaster` which is associated with the user agent ( `FOUserAgent` ) and add it there:
+To register the event listener with FOP, get the `EventBroadcaster` which is associated with the user agent (`FOUserAgent`) and add it there:
 
     :::java
     FOUserAgent foUserAgent = fopFactory.newFOUserAgent();
@@ -136,7 +136,7 @@ The basics are very simple. Just instant
     EventBroadcaster broadcaster = [get it from somewhere];
     broadcaster.broadcastEvent(ev);
 
-The `Event.paramsBuilder()` is a [fluent interface](http://en.wikipedia.org/wiki/Fluent_interface) to help with the build-up of the parameters. You could just as well instantiate a `Map` ( `Map<String, Object>` ) and fill it with values.
+The `Event.paramsBuilder()` is a [fluent interface](http://en.wikipedia.org/wiki/Fluent_interface) to help with the build-up of the parameters. You could just as well instantiate a `Map` (`Map<String, Object>`) and fill it with values.
 
 ### The EventProducer interface <a id="event-producer"></a>
 
@@ -177,7 +177,7 @@ To produce the same event as in the firs
 
 ### The event model <a id="event-model"></a>
 
-Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time ( `ant resourcegen` ). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java` ) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/) to parse these interfaces.
+Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/) to parse these interfaces.
 
 The event model XML files are generated during build by the Ant task mentioned above when running the "resourcegen" task. So just run `"ant resourcegen"` if you receive a `MissingResourceException` at runtime indicating that `"event-model.xml"` is missing.
 
@@ -233,11 +233,11 @@ The XML format used by the `EventFormatt
       </message>
     </catalogue>
 
-The example (extracted from the RTF handler's event producer) has message templates for two event methods. The class used to do variable replacement in the templates is `org.apache.fop.util.text.AdvancedMessageFormat` which is more powerful than the `MessageFormat` classes provided by the Java class library ( `java.util.text` package).
+The example (extracted from the RTF handler's event producer) has message templates for two event methods. The class used to do variable replacement in the templates is `org.apache.fop.util.text.AdvancedMessageFormat` which is more powerful than the `MessageFormat` classes provided by the Java class library (`java.util.text` package).
 
 "locator" is a template that is reused by the other message templates by referencing it through "{{locator}}". This is some kind of include command.
 
-Normal event parameters are accessed by name inside single curly braces, for example: "{node}". For objects, this format just uses the `toString()` method to turn the object into a string, unless there is an `ObjectFormatter` registered for that type (there's an example for `org.xml.sax.Locator` ).
+Normal event parameters are accessed by name inside single curly braces, for example: "{node}". For objects, this format just uses the `toString()` method to turn the object into a string, unless there is an `ObjectFormatter` registered for that type (there's an example for `org.xml.sax.Locator`).
 
 The single curly braces pattern supports additional features. For example, it is possible to do this: "{start,if,start,end}". "if" here is a special field modifier that evaluates "start" as a boolean and if that is true returns the text right after the second comma ("start"). Otherwise it returns the text after the third comma ("end"). The "equals" modifier is similar to "if" but it takes as an additional (comma-separated) parameter right after the "equals" modifier, a string that is compared to the value of the variable. An example: {severity,equals,EventSeverity:FATAL,,some text} (this adds "some text" if the severity is not FATAL).
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/extensions.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/extensions.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/extensions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/extensions.mdtext Wed Dec  5 15:10:55 2012
@@ -154,7 +154,7 @@ Initial: 0pt
 
 Applies to: fo:simple-page-master
 
-If there is only one value, it applies to all sides. If there are two values, the top and bottom bleed widths are set to the first value and the right and left bleed widths are set to the second. If there are three values, the top is set to the first value, the left and right are set to the second, and the bottom is set to the third. If there are four values, they apply to the top, right, bottom, and left, respectively. (Corresponds to [the definition of padding](http://www.w3.org/TR/xsl11/#padding) ).
+If there is only one value, it applies to all sides. If there are two values, the top and bottom bleed widths are set to the first value and the right and left bleed widths are set to the second. If there are three values, the top is set to the first value, the left and right are set to the second, and the bottom is set to the third. If there are four values, they apply to the top, right, bottom, and left, respectively. (Corresponds to [the definition of padding](http://www.w3.org/TR/xsl11/#padding)).
 
 This extension indirectly defines the BleedBox and is calculated by expanding the TrimBox by the bleed widths. The lengths must be non-negative.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext Wed Dec  5 15:10:55 2012
@@ -186,7 +186,7 @@ Bitmap images are generally embedded int
 
 ## Page selection for multi-page formats <a id="page-selection"></a>
 
-Some image formats such as TIFF support multiple pages/sub-images per file. You can select a particular page using a special URI fragment in the form: <uri>#page=<nr> (for example: `http://localhost/images/myimage.tiff#page=3` )
+Some image formats such as TIFF support multiple pages/sub-images per file. You can select a particular page using a special URI fragment in the form: <uri>#page=<nr> (for example: `http://localhost/images/myimage.tiff#page=3`)
 
 ## Image caching <a id="caching"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext Wed Dec  5 15:10:55 2012
@@ -38,13 +38,13 @@ The language and country codes must matc
 
 1. There are basically three ways to make the FOP-compatible hyphenation pattern file(s) accessible to FOP:
 
-- Download the precompiled JAR from [OFFO](http://offo.sourceforge.net/hyphenation/index.html) and place it either in the `{fop-dir}/lib` directory, or in a directory of your choice (and append the full path to the JAR to the environment variable `FOP_HYPHENATION_PATH` ).
+- Download the precompiled JAR from [OFFO](http://offo.sourceforge.net/hyphenation/index.html) and place it either in the `{fop-dir}/lib` directory, or in a directory of your choice (and append the full path to the JAR to the environment variable `FOP_HYPHENATION_PATH`).
 
 - Download the desired FOP-compatible hyphenation pattern file(s) from [OFFO](http://offo.sourceforge.net/hyphenation/index.html), and/or take your self created hyphenation pattern file(s),
 
     - place them in the directory `{fop-dir}/hyph`,
 
-    - or place them in a directory of your choice and set the Ant variable `user.hyph.dir` to point to that directory (in `build-local.properties` ),
+    - or place them in a directory of your choice and set the Ant variable `user.hyph.dir` to point to that directory (in `build-local.properties`),
 and run Ant with build target `jar-hyphenation`. This will create a JAR containing the compiled patterns in `{fop-dir}/build` that will be added to the classpath on the next run. (When FOP is built from scratch, and there are pattern source file(s) present in the directory pointed to by the `user.hyph.dir` variable, this JAR will automatically be created from the supplied pattern(s)).
 
 - Put the pattern source file(s) into a directory of your choice and configure FOP to look for custom patterns in this directory, by setting the [<hyphenation-base>](configuration.html) configuration option.
@@ -79,7 +79,7 @@ This element is unused and not even read
     - numeric characters represent a scoring system for indicating the acceptability of a hyphen in this location. Odd numbers represent an acceptable location for a hyphen, with higher values overriding lower inhibiting values. Even numbers indicate an unacceptable location, with higher values overriding lower values indicating an acceptable position. A value of zero (inhibiting) is implied when there is no number present. Generally patterns are constructed so that valuse greater than 4 are rare. Due to a bug currently patterns with values of 8 and greater don't have an effect, so don't wonder.
 Here are some examples from the English patterns file:
 
-    - Knuth ( *The TeXBook*, Appendix H) uses the example **hach4**, which indicates that it is extremely undesirable to place a hyphen after the substring "hach", for example in the word "toothach-es".
+    - Knuth (*The TeXBook*, Appendix H) uses the example **hach4**, which indicates that it is extremely undesirable to place a hyphen after the substring "hach", for example in the word "toothach-es".
 
     -  **.leg5e** indicates that "leg-e", when it occurs at the beginning of a word, is a very good place to place a hyphen, if one is needed. Words like "leg-end" and "leg-er-de-main" fit this pattern.
 Note that the algorithm that uses this data searches for each of the word's substrings in the patterns, and chooses the *highest* value found for letter combination.

Modified: xmlgraphics/site/trunk/content/fop/1.0/intermediate.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/intermediate.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/intermediate.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/intermediate.mdtext Wed Dec  5 15:10:55 2012
@@ -45,7 +45,7 @@ More technical information about the two
 
 ## Usage of the Area Tree XML format (AT XML) <a id="usage"></a>
 
-As already mentioned, the area tree XML format is generated by using the **XMLRenderer** (MIME type: **application/X-fop-areatree** ). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
+As already mentioned, the area tree XML format is generated by using the **XMLRenderer** (MIME type: **application/X-fop-areatree**). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
 
 However, there is an important detail to consider: The various Renderers don't all use the same font sources. To be able to create the right area tree for the ultimate output format, you need to create the area tree XML file using the right font setup. This is achieved by telling the XMLRenderer to mimic another renderer. This is done by calling the XMLRenderer's mimicRenderer() method with an instance of the ultimate target renderer as the single parameter. This has a consequence: An area tree XML file rendered with the Java2DRenderer may not look as expected when it was actually generated for the PDF renderer. For renderers that use the same font setup, this restriction does not apply (PDF and PS, for example). Generating the area tree XML format file is the first step.
 
@@ -93,11 +93,11 @@ One of the most important use cases for 
 The area tree XML format is sensitive to changes in whitespace. If you're not careful, the modified file may not render correctly.
 ### Advanced Use <a id="advanced"></a>
 
-The generation of the area tree format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call `setTransformerHandler()` on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see `getContentHandler()` ).
+The generation of the area tree format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call `setTransformerHandler()` on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see `getContentHandler()`).
 
 ## Usage of the Intermediate Format (IF) <a id="usage-if"></a>
 
-The Intermediate Format (IF) is generated by the **IFSerializer** (MIME type: **application/X-fop-intermediate-format** ). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
+The Intermediate Format (IF) is generated by the **IFSerializer** (MIME type: **application/X-fop-intermediate-format**). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
 
 The IFSerializer is an implementation of the **IFDocumentHandler** and **IFPainter** interfaces. The **IFRenderer** class is responsible for converting FOP's area tree into calls against these two interfaces.
 
@@ -153,10 +153,10 @@ This initial example is obviously not ve
 
 One of the most important use cases for this format is obviously modifying the intermediate format before finally rendering it to the target format. You can easily use XSLT to process the IF file according to your needs.
 
-There is an XML Schema (located under [src/documentation/intermediate-format-ng](http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/intermediate-format-ng/) ) that helps you verify that your modified content is correct.
+There is an XML Schema (located under [src/documentation/intermediate-format-ng](http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/intermediate-format-ng/)) that helps you verify that your modified content is correct.
 
 For certain output formats there's a caveat: Formats like AFP and PCL do not support arbitrary transformations on the IF's "viewport" and "g" elements. Possible are only rotations in 90 degree steps and translations.
 
 ### Advanced Use <a id="advanced-if"></a>
 
-The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. So rather than just passing in a StreamResult to IFSerializer's setResult() method, you can also use a SAXResult or a DOMResult. And as you've already seen, the IFParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to start the parsing process (see `getContentHandler()` ).
+The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. So rather than just passing in a StreamResult to IFSerializer's setResult() method, you can also use a SAXResult or a DOMResult. And as you've already seen, the IFParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to start the parsing process (see `getContentHandler()`).

Modified: xmlgraphics/site/trunk/content/fop/1.0/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/output.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/output.mdtext Wed Dec  5 15:10:55 2012
@@ -96,7 +96,7 @@ Here is some sample code that uses iText
           System.out.println("Processed page " + i);
         }
         document.close();
-      } catch( Exception e) {
+      } catch (Exception e) {
         e.printStackTrace();
       }
     }
@@ -715,7 +715,7 @@ The default value for the `"color-mode"`
 
 -  `gray`: gray (8bit)
 
--  `bi-level` (or `binary` ): bi-level (1bit)
+-  `bi-level` (or `binary`): bi-level (1bit)
 
 Please note that there is currently no dithering or error diffusion available for bi-level bitmap output.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/running.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/running.mdtext Wed Dec  5 15:10:55 2012
@@ -184,7 +184,7 @@ If you are running out of memory when us
 
 - Increase memory available to the JVM. See [the -Xmx option](http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
 
-- Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document ( ["page N of TOTAL"](../faq.html#pagenum) ). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
+- Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (["page N of TOTAL"](../faq.html#pagenum)). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
 
 - Avoid large images, especially if they are scaled down. If they need to be scaled, scale them in another application upstream from FOP. For many image formats, memory consumption is driven mainly by the size of the image file itself, not its dimensions (width*height), so increasing the compression rate may help.
 

Modified: xmlgraphics/site/trunk/content/fop/1.0/upgrading.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/upgrading.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/upgrading.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/upgrading.mdtext Wed Dec  5 15:10:55 2012
@@ -20,7 +20,7 @@ If you're planning to upgrade to the lat
 
 -
 The new code is much more strict about the interpretation of the XSL-FO 1.1 specification. Things that worked fine in version 0.20.5 might start to produce warnings or even errors now. FOP 0.20.5 contains many bugs which have been corrected in the new code.
-While FOP 0.20.5 allowed you to have empty `fo:table-cell` elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element ( `(%block;)+`, see [XSL-FO 1.1, 6.7.10](http://www.w3.org/TR/xsl/#fo_table-cell) ) inside an `fo:table-cell` element.
+While FOP 0.20.5 allowed you to have empty `fo:table-cell` elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element (`(%block;)+`, see [XSL-FO 1.1, 6.7.10](http://www.w3.org/TR/xsl/#fo_table-cell)) inside an `fo:table-cell` element.
 
 - Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP extension for [Barcode4J](http://barcode4j.sourceforge.net) is available since January 2007.
 
@@ -37,6 +37,6 @@ When you use your existing FO files or X
 
 - As stated above empty table cells `<fo:table-cell></fo:table-cell>` are not allowed by the specification. The same applies to empty `static-content` and `block-container` elements, for example.
 
-- 0.20.5 is not XSL-FO compliant with respect to sizing images ( `external-graphic` ) or `instream-foreign-object` objects. If images or SVGs are sized differently in your outputs with the new FOP version check [Bug 37136](http://issues.apache.org/bugzilla/show_bug.cgi?id=37136) as it contains some hints on what to do. The file [http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup) has a number of good examples that show the new, more correct behaviour.
+- 0.20.5 is not XSL-FO compliant with respect to sizing images (`external-graphic` or `instream-foreign-object` objects). If images or SVGs are sized differently in your outputs with the new FOP version check [Bug 37136](http://issues.apache.org/bugzilla/show_bug.cgi?id=37136) as it contains some hints on what to do. The file [http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup) has a number of good examples that show the new, more correct behaviour.
 
 - The `fox:outline` extension is not implemented in this version anymore. It has been superseded by the new bookmark elements from XSL-FO 1.1.

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=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/accessibility.mdtext Wed Dec  5 15:10:55 2012
@@ -26,7 +26,7 @@ Apache FOP cannot automatically generate
 
 - Table cells must have a table row as their parent.
 
-- Images must have an alternate text: use the `fox:alt-text` extension attribute (in the [fox namespace](extensions.html#fox-namespace) ) on `fo:external-graphic` and `fo:instream-foreign-object` to specify a short text describing the image.
+- Images must have an alternate text: use the `fox:alt-text` extension attribute (in the [fox namespace](extensions.html#fox-namespace)) on `fo:external-graphic` and `fo:instream-foreign-object` to specify a short text describing the image.
 
 - Ensure that the order of `fo:block-container` elements in a page corresponds to the reading order.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext Wed Dec  5 15:10:55 2012
@@ -46,7 +46,7 @@ Then create FOP tasks within your Ant bu
 | relativebase | For fileset usage only. A value of `true` specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of `false` specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified. | No, default is `false`. |
 | userconfig | User configuration file (same as the FOP "-c" command line option). | No |
 | messagelevel | Logging level<br></br>Possible values: `error`, `warn`, `info`, `verbose`, `debug`. **Currently doesn't work in FOP Trunk!!!**  | No, defaults to `verbose`  |
-| logFiles | Controls whether the names of the files that are processed are logged ( `true` ) or not ( `false` ). **Currently doesn't work in FOP Trunk!!!**  | No, default is `true`  |
+| logFiles | Controls whether the names of the files that are processed are logged (`true`) or not (`false`). **Currently doesn't work in FOP Trunk!!!**  | No, default is `true`  |
 | throwexceptions | Controls whether or not an exception is thrown if an error occurs during rendering. | Default is `true`  |
 
 <br/>

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=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext Wed Dec  5 15:10:55 2012
@@ -271,4 +271,4 @@ Check the following possibilities:
 
 and run the configuration file through a validating schema parser. Note that the schema cannot detect all errors, and that it is stricter about the order of some elements than FOP itself is.
 
-- Run FOP in debug mode (command line option `-d` ). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.
+- Run FOP in debug mode (command line option `-d`). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.

Modified: xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/embedding.mdtext Wed Dec  5 15:10:55 2012
@@ -246,7 +246,7 @@ Set the **target resolution** for the do
     `userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)`
 
 -
-Set **your own Document Handler**. This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see [Document Handlers](#documenthandlers) ). This also allows advanced users to create their own implementation of the document handler.
+Set **your own Document Handler**. This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see [Document Handlers](#documenthandlers)). This also allows advanced users to create their own implementation of the document handler.
 
     `userAgent.setDocumentHandlerOverride(documentHandler) // documentHandler is an instance of org.apache.fop.render.intermediate.IFDocumentHandler`
 
@@ -349,7 +349,7 @@ This [example](http://svn.apache.org/vie
 
 ### ExampleXML2FO.java <a id="ExampleXML2FO"></a>
 
-This [example](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup) has nothing to do with FOP. It is there to show you how an XML file can be converted to XSL-FO using XSLT. The JAXP API is used to do the transformation. Make sure you've got a JAXP-compliant XSLT processor in your classpath (ex. [Xalan](http://xml.apache.org/xalan-j) ).
+This [example](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup) has nothing to do with FOP. It is there to show you how an XML file can be converted to XSL-FO using XSLT. The JAXP API is used to do the transformation. Make sure you've got a JAXP-compliant XSLT processor in your classpath (ex. [Xalan](http://xml.apache.org/xalan-j)).
 
 ![Example XML to XSL-FO](images/EmbeddingExampleXML2FO.png)
 
@@ -371,7 +371,7 @@ For this example we've created two class
 
 The XMLReader implementation (regard it as a special kind of XML parser) is responsible for creating SAX events from the Java object. The InputSource class is only used to hold the ProjectTeam object to be used.
 
-Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. [An older JAXP tutorial](http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html) ).
+Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. [An older JAXP tutorial](http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html)).
 
 ### ExampleObj2PDF.java <a id="ExampleObj2PDF"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/events.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/events.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/events.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/events.mdtext Wed Dec  5 15:10:55 2012
@@ -67,7 +67,7 @@ It is possible to gather all events for 
 
 ### Adding an EventListener <a id="add-listener"></a>
 
-To register the event listener with FOP, get the `EventBroadcaster` which is associated with the user agent ( `FOUserAgent` ) and add it there:
+To register the event listener with FOP, get the `EventBroadcaster` which is associated with the user agent (`FOUserAgent`) and add it there:
 
     :::java
     FOUserAgent foUserAgent = fopFactory.newFOUserAgent();
@@ -136,7 +136,7 @@ The basics are very simple. Just instant
     EventBroadcaster broadcaster = [get it from somewhere];
     broadcaster.broadcastEvent(ev);
 
-The `Event.paramsBuilder()` is a [fluent interface](http://en.wikipedia.org/wiki/Fluent_interface) to help with the build-up of the parameters. You could just as well instantiate a `Map` ( `Map<String, Object>` ) and fill it with values.
+The `Event.paramsBuilder()` is a [fluent interface](http://en.wikipedia.org/wiki/Fluent_interface) to help with the build-up of the parameters. You could just as well instantiate a `Map` (`Map<String, Object>`) and fill it with values.
 
 ### The EventProducer interface <a id="event-producer"></a>
 
@@ -178,7 +178,7 @@ To produce the same event as in the firs
 
 ### The event model <a id="event-model"></a>
 
-Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time ( `ant resourcegen` ). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java` ) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/) to parse these interfaces.
+Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the `Event` 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the `org.apache.fop.events.model` package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time (`ant resourcegen`). The Ant task (found in `src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java`) scans FOP's sources for descendants of the `EventProducer` interface and uses [QDox](http://qdox.codehaus.org/) to parse these interfaces.
 
 The event model XML files are generated during build by the Ant task mentioned above when running the "resourcegen" task. So just run `"ant resourcegen"` if you receive a `MissingResourceException` at runtime indicating that `"event-model.xml"` is missing.
 
@@ -234,11 +234,11 @@ The XML format used by the `EventFormatt
       </message>
     </catalogue>
 
-The example (extracted from the RTF handler's event producer) has message templates for two event methods. The class used to do variable replacement in the templates is `org.apache.fop.util.text.AdvancedMessageFormat` which is more powerful than the `MessageFormat` classes provided by the Java class library ( `java.util.text` package).
+The example (extracted from the RTF handler's event producer) has message templates for two event methods. The class used to do variable replacement in the templates is `org.apache.fop.util.text.AdvancedMessageFormat` which is more powerful than the `MessageFormat` classes provided by the Java class library (`java.util.text` package).
 
 "locator" is a template that is reused by the other message templates by referencing it through "{{locator}}". This is some kind of include command.
 
-Normal event parameters are accessed by name inside single curly braces, for example: "{node}". For objects, this format just uses the `toString()` method to turn the object into a string, unless there is an `ObjectFormatter` registered for that type (there's an example for `org.xml.sax.Locator` ).
+Normal event parameters are accessed by name inside single curly braces, for example: "{node}". For objects, this format just uses the `toString()` method to turn the object into a string, unless there is an `ObjectFormatter` registered for that type (there's an example for `org.xml.sax.Locator`).
 
 The single curly braces pattern supports additional features. For example, it is possible to do this: "{start,if,start,end}". "if" here is a special field modifier that evaluates "start" as a boolean and if that is true returns the text right after the second comma ("start"). Otherwise it returns the text after the third comma ("end"). The "equals" modifier is similar to "if" but it takes as an additional (comma-separated) parameter right after the "equals" modifier, a string that is compared to the value of the variable. An example: {severity,equals,EventSeverity:FATAL,,some text} (this adds "some text" if the severity is not FATAL).
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext Wed Dec  5 15:10:55 2012
@@ -150,7 +150,7 @@ Initial: 0pt
 
 Applies to: fo:simple-page-master
 
-If there is only one value, it applies to all sides. If there are two values, the top and bottom bleed widths are set to the first value and the right and left bleed widths are set to the second. If there are three values, the top is set to the first value, the left and right are set to the second, and the bottom is set to the third. If there are four values, they apply to the top, right, bottom, and left, respectively. (Corresponds to [the definition of padding](http://www.w3.org/TR/xsl11/#padding) ).
+If there is only one value, it applies to all sides. If there are two values, the top and bottom bleed widths are set to the first value and the right and left bleed widths are set to the second. If there are three values, the top is set to the first value, the left and right are set to the second, and the bottom is set to the third. If there are four values, they apply to the top, right, bottom, and left, respectively. (Corresponds to [the definition of padding](http://www.w3.org/TR/xsl11/#padding)).
 
 This extension indirectly defines the BleedBox and is calculated by expanding the TrimBox by the bleed widths. The lengths must be non-negative.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext Wed Dec  5 15:10:55 2012
@@ -186,7 +186,7 @@ Bitmap images are generally embedded int
 
 ## Page selection for multi-page formats <a id="page-selection"></a>
 
-Some image formats such as TIFF support multiple pages/sub-images per file. You can select a particular page using a special URI fragment in the form: <uri>#page=<nr> (for example: `http://localhost/images/myimage.tiff#page=3` )
+Some image formats such as TIFF support multiple pages/sub-images per file. You can select a particular page using a special URI fragment in the form: <uri>#page=<nr> (for example: `http://localhost/images/myimage.tiff#page=3`)
 
 ## Image caching <a id="caching"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext Wed Dec  5 15:10:55 2012
@@ -39,13 +39,13 @@ The language and country codes must matc
 
 1. There are basically three ways to make the FOP-compatible hyphenation pattern file(s) accessible to FOP:
 
-- Download the precompiled JAR from [OFFO](http://offo.sourceforge.net/hyphenation/index.html) and place it either in the `{fop-dir}/lib` directory, or in a directory of your choice (and append the full path to the JAR to the environment variable `FOP_HYPHENATION_PATH` ).
+- Download the precompiled JAR from [OFFO](http://offo.sourceforge.net/hyphenation/index.html) and place it either in the `{fop-dir}/lib` directory, or in a directory of your choice (and append the full path to the JAR to the environment variable `FOP_HYPHENATION_PATH`).
 
 - Download the desired FOP-compatible hyphenation pattern file(s) from [OFFO](http://offo.sourceforge.net/hyphenation/index.html), and/or take your self created hyphenation pattern file(s),
 
     - place them in the directory `{fop-dir}/hyph`,
 
-    - or place them in a directory of your choice and set the Ant variable `user.hyph.dir` to point to that directory (in `build-local.properties` ),
+    - or place them in a directory of your choice and set the Ant variable `user.hyph.dir` to point to that directory (in `build-local.properties`),
 and run Ant with build target `jar-hyphenation`. This will create a JAR containing the compiled patterns in `{fop-dir}/build` that will be added to the classpath on the next run. (When FOP is built from scratch, and there are pattern source file(s) present in the directory pointed to by the `user.hyph.dir` variable, this JAR will automatically be created from the supplied pattern(s)).
 
 - Put the pattern source file(s) into a directory of your choice and configure FOP to look for custom patterns in this directory, by setting the [<hyphenation-base>](configuration.html) configuration option.
@@ -80,7 +80,7 @@ This element is unused and not even read
     - numeric characters represent a scoring system for indicating the acceptability of a hyphen in this location. Odd numbers represent an acceptable location for a hyphen, with higher values overriding lower inhibiting values. Even numbers indicate an unacceptable location, with higher values overriding lower values indicating an acceptable position. A value of zero (inhibiting) is implied when there is no number present. Generally patterns are constructed so that valuse greater than 4 are rare. Due to a bug currently patterns with values of 8 and greater don't have an effect, so don't wonder.
 Here are some examples from the English patterns file:
 
-    - Knuth ( *The TeXBook*, Appendix H) uses the example **hach4**, which indicates that it is extremely undesirable to place a hyphen after the substring "hach", for example in the word "toothach-es".
+    - Knuth (*The TeXBook*, Appendix H) uses the example **hach4**, which indicates that it is extremely undesirable to place a hyphen after the substring "hach", for example in the word "toothach-es".
 
     -  **.leg5e** indicates that "leg-e", when it occurs at the beginning of a word, is a very good place to place a hyphen, if one is needed. Words like "leg-end" and "leg-er-de-main" fit this pattern.
 Note that the algorithm that uses this data searches for each of the word's substrings in the patterns, and chooses the *highest* value found for letter combination.

Modified: xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext Wed Dec  5 15:10:55 2012
@@ -45,7 +45,7 @@ More technical information about the two
 
 ## Usage of the Area Tree XML format (AT XML) <a id="usage"></a>
 
-As already mentioned, the area tree XML format is generated by using the **XMLRenderer** (MIME type: **application/X-fop-areatree** ). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
+As already mentioned, the area tree XML format is generated by using the **XMLRenderer** (MIME type: **application/X-fop-areatree**). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
 
 However, there is an important detail to consider: The various Renderers don't all use the same font sources. To be able to create the right area tree for the ultimate output format, you need to create the area tree XML file using the right font setup. This is achieved by telling the XMLRenderer to mimic another renderer. This is done by calling the XMLRenderer's mimicRenderer() method with an instance of the ultimate target renderer as the single parameter. This has a consequence: An area tree XML file rendered with the Java2DRenderer may not look as expected when it was actually generated for the PDF renderer. For renderers that use the same font setup, this restriction does not apply (PDF and PS, for example). Generating the area tree XML format file is the first step.
 
@@ -93,11 +93,11 @@ One of the most important use cases for 
 The area tree XML format is sensitive to changes in whitespace. If you're not careful, the modified file may not render correctly.
 ### Advanced Use <a id="advanced"></a>
 
-The generation of the area tree format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call `setTransformerHandler()` on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see `getContentHandler()` ).
+The generation of the area tree format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call `setTransformerHandler()` on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see `getContentHandler()`).
 
 ## Usage of the Intermediate Format (IF) <a id="usage-if"></a>
 
-The Intermediate Format (IF) is generated by the **IFSerializer** (MIME type: **application/X-fop-intermediate-format** ). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
+The Intermediate Format (IF) is generated by the **IFSerializer** (MIME type: **application/X-fop-intermediate-format**). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file.
 
 The IFSerializer is an implementation of the **IFDocumentHandler** and **IFPainter** interfaces. The **IFRenderer** class is responsible for converting FOP's area tree into calls against these two interfaces.
 
@@ -153,10 +153,10 @@ This initial example is obviously not ve
 
 One of the most important use cases for this format is obviously modifying the intermediate format before finally rendering it to the target format. You can easily use XSLT to process the IF file according to your needs.
 
-There is an XML Schema (located under [src/documentation/intermediate-format-ng](http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/intermediate-format-ng/) ) that helps you verify that your modified content is correct.
+There is an XML Schema (located under [src/documentation/intermediate-format-ng](http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/intermediate-format-ng/)) that helps you verify that your modified content is correct.
 
 For certain output formats there's a caveat: Formats like AFP and PCL do not support arbitrary transformations on the IF's "viewport" and "g" elements. Possible are only rotations in 90 degree steps and translations.
 
 ### Advanced Use <a id="advanced-if"></a>
 
-The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. So rather than just passing in a StreamResult to IFSerializer's setResult() method, you can also use a SAXResult or a DOMResult. And as you've already seen, the IFParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to start the parsing process (see `getContentHandler()` ).
+The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. So rather than just passing in a StreamResult to IFSerializer's setResult() method, you can also use a SAXResult or a DOMResult. And as you've already seen, the IFParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to start the parsing process (see `getContentHandler()`).

Modified: xmlgraphics/site/trunk/content/fop/1.1/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/output.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/output.mdtext Wed Dec  5 15:10:55 2012
@@ -96,7 +96,7 @@ Here is some sample code that uses iText
                 System.out.println("Processed page " + i);
             }
             document.close();
-        } catch( Exception e) {
+        } catch (Exception e) {
             e.printStackTrace();
         }
     }
@@ -791,7 +791,7 @@ The default value for the `"color-mode"`
 
 -  `gray`: gray (8bit)
 
--  `bi-level` (or `binary` ): bi-level (1bit)
+-  `bi-level` (or `binary`): bi-level (1bit)
 
 Please note that there is currently no dithering or error diffusion available for bi-level bitmap output.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/running.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/running.mdtext Wed Dec  5 15:10:55 2012
@@ -193,7 +193,7 @@ If you are running out of memory when us
 
 - Increase memory available to the JVM. See [the -Xmx option](http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html) for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning>
 
-- Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document ( ["page N of TOTAL"](../faq.html#pagenum) ). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
+- Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (["page N of TOTAL"](../faq.html#pagenum)). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).
 
 - Avoid large images, especially if they are scaled down. If they need to be scaled, scale them in another application upstream from FOP. For many image formats, memory consumption is driven mainly by the size of the image file itself, not its dimensions (width*height), so increasing the compression rate may help.
 

Modified: xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/upgrading.mdtext Wed Dec  5 15:10:55 2012
@@ -17,7 +17,7 @@ You should encounter very few issues in 
     - On the `border-rect` element, the attributes { `before`, `after`, `start`, `end` } have been renamed to { `top`, `bottom`, `left`, `right` }, respectively. For further information, see [complex script patch - intermediate format changes](http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/201202.mbox/%3cCACQ=j+evStXx=7hW=CHVNKCrZHUso9FHZCSk_5EoENOHcGpGOg@mail.gmail.com%3e).
 
 
-- The `IFPainter` interface (of package `org.apache.fop.render.intermediate` ), specifically the `drawText` and `drawBorderRect` method signatures, have been modified to express the semantics of the above changes to the IF output format.
+- The `IFPainter` interface (of package `org.apache.fop.render.intermediate`), specifically the `drawText` and `drawBorderRect` method signatures, have been modified to express the semantics of the above changes to the IF output format.
 
 - The area tree (AT) output format has underwent minor modification as follows:
 
@@ -45,7 +45,7 @@ If you're planning to upgrade to the lat
 
 -
 The new code is much more strict about the interpretation of the XSL-FO specification. Things that worked fine in version 0.20.5 might start to produce warnings or even errors now. FOP 0.20.5 contains many bugs which have been corrected in the new code.
-While FOP 0.20.5 allowed you to have empty `fo:table-cell` elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element ( `(%block;)+`, see [XSL-FO 1.1, 6.7.10](http://www.w3.org/TR/xsl/#fo_table-cell) ) inside an `fo:table-cell` element.
+While FOP 0.20.5 allowed you to have empty `fo:table-cell` elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element (`(%block;)+`, see [XSL-FO 1.1, 6.7.10](http://www.w3.org/TR/xsl/#fo_table-cell)) inside an `fo:table-cell` element.
 
 - Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP extension for [Barcode4J](http://barcode4j.sourceforge.net) is available since January 2007.
 
@@ -60,6 +60,6 @@ When you use your existing FO files or X
 
 - As stated above, empty table cells `<fo:table-cell></fo:table-cell>` are not allowed by the specification. The same applies to empty `fo:static-content` and `fo:block-container` elements, for example.
 
-- Version 0.20.5 is not XSL-FO compliant with respect to sizing images ( `external-graphic` ) or `instream-foreign-object` objects. If images or SVGs are sized differently in your outputs with the new FOP version check [Bug 37136](http://issues.apache.org/bugzilla/show_bug.cgi?id=37136) as it contains some hints on what to do. The file [http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup) has a number of good examples that show the correct behaviour.
+- Version 0.20.5 is not XSL-FO compliant with respect to sizing images (`external-graphic`) or `instream-foreign-object` objects. If images or SVGs are sized differently in your outputs with the new FOP version check [Bug 37136](http://issues.apache.org/bugzilla/show_bug.cgi?id=37136) as it contains some hints on what to do. The file [http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/fo/basic/images.fo?view=markup) has a number of good examples that show the correct behaviour.
 
 - The `fox:outline` extension is not implemented in the current version: it has been superseded by the new bookmark elements from XSL-FO 1.1.

Modified: xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext Wed Dec  5 15:10:55 2012
@@ -39,7 +39,7 @@ For developers that dislike these conven
 
 ### Checkstyle <a id="java-checkstyle"></a>
 
-The java syntax checker " <a href="http://checkstyle.sourceforge.net">Checkstyle</a> " is used to enforce many of the FOP coding standards. The standards enforced through Checkstyle are documented in its configuration file (xml-fop/checkstyle.cfg). The conventions defined in the configuration file are an integral part of FOP's coding conventions, and should not be changed without common consent. In other words, the configuration file contains additional conventions that are not documented on this page, but are generally accepted as good style within the java community (i.e. they are the default behavior of checkstyle, which the FOP developers have decided to adopt *de facto* ). Any apparent contradiction between the configuration file and this document should be raised on the fop-dev mailing list so that it can be clarified.
+The java syntax checker " <a href="http://checkstyle.sourceforge.net">Checkstyle</a> " is used to enforce many of the FOP coding standards. The standards enforced through Checkstyle are documented in its configuration file (xml-fop/checkstyle.cfg). The conventions defined in the configuration file are an integral part of FOP's coding conventions, and should not be changed without common consent. In other words, the configuration file contains additional conventions that are not documented on this page, but are generally accepted as good style within the java community (i.e. they are the default behavior of checkstyle, which the FOP developers have decided to adopt *de facto*). Any apparent contradiction between the configuration file and this document should be raised on the fop-dev mailing list so that it can be clarified.
 
 To use the "checkstyle" target in FOP's build process, download the source from the <a href="http://checkstyle.sourceforge.net">Checkstyle web site</a>, place checkstyle-all-*.jar in the lib directory and call "build checkstyle". Output (in the build directory) includes checkstyle_report.txt and checkstyle_report.xml. If you copy the file contrib/checkstyle-noframes.xsl from Checkstyle into FOP's root directory, you will also get an HTML report.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/design/fotree.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/design/fotree.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/design/fotree.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/design/fotree.mdtext Wed Dec  5 15:10:55 2012
@@ -24,7 +24,7 @@ Elements from [foreign namespaces](parsi
 
 For unrecognized namespaces, a dummy object or a generic DOM is created.
 
-While the tree building is mainly about creating the FO Tree, some FO Tree events trigger processes in other parts of FOP. The end of a page-sequence element triggers the layout process for that page-sequence (see discussion of [Recycling](#recycle) ). Also, the end of the XML document tells the renderer that it can finalize the output document.
+While the tree building is mainly about creating the FO Tree, some FO Tree events trigger processes in other parts of FOP. The end of a page-sequence element triggers the layout process for that page-sequence (see discussion of [Recycling](#recycle)). Also, the end of the XML document tells the renderer that it can finalize the output document.
 
 ## Recycling FO Tree Memory <a id="recycle"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/dev/release.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/release.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/release.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/release.mdtext Wed Dec  5 15:10:55 2012
@@ -22,17 +22,17 @@ The checklist below is based on a combin
 
 - Create a branch called `branches/fop-v_vv`
 
-- Edit release notes ( `README` and `status.xml` in the root).
+- Edit release notes (`README` and `status.xml` in the root).
 
 - Add the release to `news-data.xml` ; remove links to release notes of older versions from this file.
 
-- Update the FAQ ( `faq.xml` ) to the new release, e.g., update the answer for "When is the next release planned?".
+- Update the FAQ (`faq.xml`) to the new release, e.g., update the answer for "When is the next release planned?".
 
 - Check and update the copyright year in NOTICE and build.xml.
 
 - Update the file `doap.rdf`, and the files `index.xml`, `site.xml`, `download.xml`, `fo.xml`, `maillist.xml`, and `quickstartguide.xml` in directory `xdocs` for the new version.
 
-- Update the version numbers in the release column on the compliance page ( `compliance.xml` ); update the compliance in the release column to the current state (development column).
+- Update the version numbers in the release column on the compliance page (`compliance.xml`); update the compliance in the release column to the current state (development column).
 
 - Update version number in `build.xml` (not to be merged back into trunk).
 
@@ -48,7 +48,7 @@ The checklist below is based on a combin
 
 - Update `compiling.xml` in the new version directory: change the introduction for trunk to that for a release.
 
-- Build the dist files ( `build[.sh] dist` ) and upload them to your web directory on `people.apache.org`
+- Build the dist files (`build[.sh] dist`) and upload them to your web directory on `people.apache.org`
 
 - Ask on `fop-dev` ML to check the branch and the generated dist files for errors.
 
@@ -72,7 +72,7 @@ The checklist below is based on a combin
 
 - Make a test download.
 
-- Start a vote for the release on `general@xmlgraphics.apache.org`. The message should point to the release files and list the MD5 sums ( `cat *.md5` ). The vote should remain open for 72hrs.
+- Start a vote for the release on `general@xmlgraphics.apache.org`. The message should point to the release files and list the MD5 sums (`cat *.md5`). The vote should remain open for 72hrs.
 
 - When the release is accepted, copy the release files, their md5 sum files and the signature files to `/www/www.apache.org/dist/xmlgraphics/fop/` in the subdirectories `source` and `binaries`. Create links to all files in the `fop` directory. Remove the links to the files of the previous version.
 

Modified: xmlgraphics/site/trunk/content/fop/dev/tools.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/tools.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/tools.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/tools.mdtext Wed Dec  5 15:10:55 2012
@@ -10,15 +10,15 @@ This page documents items that may be he
 Here is a (probably not comprehensive) list of tools you will need to be a successful FOP developer:
 
 
-- A java IDE (see [IDE](#ide) ).
+- A java IDE (see [IDE](#ide)).
 
-- A Subversion client (see [Subversion](#svn) ).
+- A Subversion client (see [Subversion](#svn)).
 
-- Ant (see [Building FOP](../trunk/compiling.html) ).
+- Ant (see [Building FOP](../trunk/compiling.html)).
 
 - checkstyle (see [Checkstyle](conventions.html#java-checkstyle) on the conventions page).
 
-- JUnit (see [Basic Testing](testing.html#basic) ).
+- JUnit (see [Basic Testing](testing.html#basic)).
 
 ## General Developer Information <a id="general"></a>
 

Modified: xmlgraphics/site/trunk/content/fop/faq.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/faq.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/faq.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/faq.mdtext Wed Dec  5 15:10:55 2012
@@ -86,7 +86,7 @@ There are numerous ways that you can hel
 
 ### 2.1. I get the error: [ERROR]: 'master-reference' for 'fo:page-sequence' matches no 'simple-page-master' or 'page-sequence-master'<a id="no-page-master"></a>
 
-FOP was changed to be in accordance with the latest standard (see [XSL standard](resources.html#specs-xslfo) ).The page master for a fo:page-sequence is now referenced by the master-reference attribute. Replace the master-name attributes of your fo:page-sequence elements by master-reference attributes. You have to do this also for fo:single-page-master-reference, fo:repeatable-page-master-reference and fo:conditional-page-master-reference elements in you page master definitions.
+FOP was changed to be in accordance with the latest standard (see [XSL standard](resources.html#specs-xslfo)).The page master for a fo:page-sequence is now referenced by the master-reference attribute. Replace the master-name attributes of your fo:page-sequence elements by master-reference attributes. You have to do this also for fo:single-page-master-reference, fo:repeatable-page-master-reference and fo:conditional-page-master-reference elements in you page master definitions.
 
 Update your FO documents and style sheets.
 

Modified: xmlgraphics/site/trunk/content/fop/fo.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/fo.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/fo.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/fo.mdtext Wed Dec  5 15:10:55 2012
@@ -355,7 +355,7 @@ The FOP library provides a method to get
                 } finally {
                     out.close();
                 }
-            } catch( Exception e) {
+            } catch (Exception e) {
                 e.printStackTrace();
             }
         }

Modified: xmlgraphics/site/trunk/content/fop/index.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/index.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/index.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/index.mdtext Wed Dec  5 15:10:55 2012
@@ -10,7 +10,7 @@ The Apache&trade; FOP project is part of
 
 ![Render Diagram](images/document.jpg)
 
-A stable release of the latest version of FOP ( [1.0](1.0/) ) is available. It's the third stable release after the large redesign effort and implements a large subset of the [XSL-FO Version 1.1 W3C Recommendation](http://www.w3.org/TR/xsl11/).
+A stable release of the latest version of FOP ([1.0](1.0/)) is available. It's the third stable release after the large redesign effort and implements a large subset of the [XSL-FO Version 1.1 W3C Recommendation](http://www.w3.org/TR/xsl11/).
 
 Support for each of the standard's objects and properties is detailed in [FOP Compliance](compliance.html). [Download](download.html) options include a precompiled version, source code, and many example files to get you started. [Resources](resources.html) include links to XSL-FO introductions and many other useful references. A checklist for [Getting Help](gethelp.html) will guide you toward maximizing the usefulness of FOP.
 

Modified: xmlgraphics/site/trunk/content/fop/quickstartguide.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/quickstartguide.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/quickstartguide.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/quickstartguide.mdtext Wed Dec  5 15:10:55 2012
@@ -51,7 +51,7 @@ This section walks you through a "Hello 
     :::xml
     <name>Frank</name>
 
-1. To produce a PDF file from this XML file, we need an XSLT stylesheet that converts the XML to XSL-FO. This is the first step in the processing chain. The second step will be done by FOP when it reads the generated XSL-FO document and formats it to a PDF document. You can copy the following minimal XSLT stylesheet, which takes your first name and produces a "Hello World!"-style document (save it as `name2fo.xsl` ):<br></br>
+1. To produce a PDF file from this XML file, we need an XSLT stylesheet that converts the XML to XSL-FO. This is the first step in the processing chain. The second step will be done by FOP when it reads the generated XSL-FO document and formats it to a PDF document. You can copy the following minimal XSLT stylesheet, which takes your first name and produces a "Hello World!"-style document (save it as `name2fo.xsl`):<br></br>
 
     :::xml
     <?xml version="1.0" encoding="utf-8"?>

Modified: xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/accessibility.mdtext Wed Dec  5 15:10:55 2012
@@ -26,7 +26,7 @@ Apache FOP cannot automatically generate
 
 - Table cells must have a table row as their parent.
 
-- Images must have an alternate text: use the `fox:alt-text` extension attribute (in the [fox namespace](extensions.html#fox-namespace) ) on `fo:external-graphic` and `fo:instream-foreign-object` to specify a short text describing the image.
+- Images must have an alternate text: use the `fox:alt-text` extension attribute (in the [fox namespace](extensions.html#fox-namespace)) on `fo:external-graphic` and `fo:instream-foreign-object` to specify a short text describing the image.
 
 - Ensure that the order of `fo:block-container` elements in a page corresponds to the reading order.
 

Modified: xmlgraphics/site/trunk/content/fop/trunk/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/anttask.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/anttask.mdtext Wed Dec  5 15:10:55 2012
@@ -46,7 +46,7 @@ Then create FOP tasks within your Ant bu
 | relativebase | For fileset usage only. A value of `true` specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of `false` specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified. | No, default is `false`. |
 | userconfig | User configuration file (same as the FOP "-c" command line option). | No |
 | messagelevel | Logging level<br></br>Possible values: `error`, `warn`, `info`, `verbose`, `debug`. **Currently doesn't work in FOP Trunk!!!**  | No, defaults to `verbose`  |
-| logFiles | Controls whether the names of the files that are processed are logged ( `true` ) or not ( `false` ). **Currently doesn't work in FOP Trunk!!!**  | No, default is `true`  |
+| logFiles | Controls whether the names of the files that are processed are logged (`true`) or not (`false`). **Currently doesn't work in FOP Trunk!!!**  | No, default is `true`  |
 | throwexceptions | Controls whether or not an exception is thrown if an error occurs during rendering. | Default is `true`  |
 
 <br/>

Modified: xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext Wed Dec  5 15:10:55 2012
@@ -268,4 +268,4 @@ Check the following possibilities:
 
 and run the configuration file through a validating schema parser. Note that the schema cannot detect all errors, and that it is stricter about the order of some elements than FOP itself is.
 
-- Run FOP in debug mode (command line option `-d` ). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.
+- Run FOP in debug mode (command line option `-d`). This makes FOP report which configuration information it finds. Check if FOP finds what you expect.

Modified: xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext?rev=1417468&r1=1417467&r2=1417468&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext Wed Dec  5 15:10:55 2012
@@ -249,7 +249,7 @@ Set the **target resolution** for the do
     `userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)`
 
 -
-Set **your own Document Handler**. This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see [Document Handlers](#documenthandlers) ). This also allows advanced users to create their own implementation of the document handler.
+Set **your own Document Handler**. This feature can be used for several purposes, the most likey usage of which would probably be binding a MIME type when the output is Intermediate Format (see [Document Handlers](#documenthandlers)). This also allows advanced users to create their own implementation of the document handler.
 
     `userAgent.setDocumentHandlerOverride(documentHandler) // documentHandler is an instance of org.apache.fop.render.intermediate.IFDocumentHandler`
 
@@ -352,7 +352,7 @@ This [example](http://svn.apache.org/vie
 
 ### ExampleXML2FO.java <a id="ExampleXML2FO"></a>
 
-This [example](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup) has nothing to do with FOP. It is there to show you how an XML file can be converted to XSL-FO using XSLT. The JAXP API is used to do the transformation. Make sure you've got a JAXP-compliant XSLT processor in your classpath (ex. [Xalan](http://xml.apache.org/xalan-j) ).
+This [example](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup) has nothing to do with FOP. It is there to show you how an XML file can be converted to XSL-FO using XSLT. The JAXP API is used to do the transformation. Make sure you've got a JAXP-compliant XSLT processor in your classpath (ex. [Xalan](http://xml.apache.org/xalan-j)).
 
 ![Example XML to XSL-FO](images/EmbeddingExampleXML2FO.png)
 
@@ -374,7 +374,7 @@ For this example we've created two class
 
 The XMLReader implementation (regard it as a special kind of XML parser) is responsible for creating SAX events from the Java object. The InputSource class is only used to hold the ProjectTeam object to be used.
 
-Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. [An older JAXP tutorial](http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html) ).
+Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. [An older JAXP tutorial](http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html)).
 
 ### ExampleObj2PDF.java <a id="ExampleObj2PDF"></a>
 



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


Mime
View raw message