xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From psan...@apache.org
Subject svn commit: r1416565 [1/5] - in /xmlgraphics/site/trunk/content/fop: 0.95/ 1.0/ 1.1/ trunk/
Date Mon, 03 Dec 2012 15:46:44 GMT
Author: psancho
Date: Mon Dec  3 15:46:33 2012
New Revision: 1416565

URL: http://svn.apache.org/viewvc?rev=1416565&view=rev
Log:
Synchronization between all fop versions tabs

Modified:
    xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/compiling.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/embedding.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/extensions.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/intermediate.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/metadata.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/output.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/running.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/compiling.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/embedding.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/events.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/extensions.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/graphics.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/hyphenation.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/intermediate.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/metadata.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/output.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/pdfa.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/pdfencryption.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/running.mdtext
    xmlgraphics/site/trunk/content/fop/1.0/servlets.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/accessibility.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/compiling.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/embedding.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/events.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/extensions.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/fonts.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/graphics.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/hyphenation.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/intermediate.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/output.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/pdfa.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/pdfencryption.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/running.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/servlets.mdtext
    xmlgraphics/site/trunk/content/fop/trunk/configuration.mdtext
    xmlgraphics/site/trunk/content/fop/trunk/embedding.mdtext
    xmlgraphics/site/trunk/content/fop/trunk/extensions.mdtext
    xmlgraphics/site/trunk/content/fop/trunk/output.mdtext
    xmlgraphics/site/trunk/content/fop/trunk/servlets.mdtext

Modified: xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext Mon Dec  3 15:46:33 2012
@@ -11,26 +11,28 @@ The FOP Ant task will convert XSL-FO doc
 
 To call FOP tasks within Ant, first add a FOP task definition to your Ant build file. One method of defining the task is as follows:
 
-<property name="fop.home" value="....path to your FOP HOME directory..."/>
-
-<taskdef name="fop" 
-         classname="org.apache.fop.tools.anttasks.Fop">
-  <classpath>
-    <fileset dir="${fop.home}/lib">
-      <include name="*.jar"/>
-    </fileset>
-    <fileset dir="${fop.home}/build">
-      <include name="fop.jar"/>
-      <include name="fop-hyph.jar" />
-    </fileset>
-  </classpath>
-</taskdef>
+    <property name="fop.home" value="....path to your FOP HOME directory..."/>
+    
+    <taskdef name="fop" 
+             classname="org.apache.fop.tools.anttasks.Fop">
+      <classpath>
+        <fileset dir="${fop.home}/lib">
+          <include name="*.jar"/>
+        </fileset>
+        <fileset dir="${fop.home}/build">
+          <include name="fop.jar"/>
+          <include name="fop-hyph.jar" />
+        </fileset>
+      </classpath>
+    </taskdef>
     
 Then create FOP tasks within your Ant build file, using the FOP task parameters listed below.
 
 ## Parameters for FOP Ant task <a id="parameters"></a>
 
-<caption>Parameters specified as attributes</caption>| Attribute | Description | Required |
+<caption>Parameters specified as attributes</caption>
+
+| Attribute | Description | Required |
 |-----------|-------------|----------|
 | fofile | XSL-FO file to be rendered | Yes, if no fileset nested element is used |
 | outfile | Output filename | Yes, when fofile is used. (This attribute is not valid for filesets.) |
@@ -43,7 +45,7 @@ Then create FOP tasks within your Ant bu
 | 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`  |
 
-
+<br/>
 
 <caption>Parameters specified as nested elements</caption>| Attribute | Description | Required |
 |-----------|-------------|----------|

Modified: xmlgraphics/site/trunk/content/fop/0.95/compiling.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/compiling.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/compiling.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/compiling.mdtext Mon Dec  3 15:46:33 2012
@@ -50,7 +50,7 @@ OR
 ant all
 To clean the build directory first:
 ant clean allIf you want to shorten the build time you can just call the "package" target which doesn't perform any automated tests during the build.
-# Troubleshooting <a id="problems"></a>
+## Troubleshooting <a id="problems"></a>
 
 If you have problems building FOP, please try the following:
 

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=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext Mon Dec  3 15:46:33 2012
@@ -65,7 +65,7 @@ This is an excerpt from the example conf
       <!-- etc. etc..... -->
     </fop>
 
-# Renderer configuration <a id="renderers"></a>
+## Renderer configuration <a id="renderers"></a>
 
 Each Renderer has its own configuration section which is identified by the MIME type the Renderer is written for, ex. "application/pdf" for the PDF Renderer.
 
@@ -130,7 +130,7 @@ Some people don't have high requirements
           <fonts....
           </renderer>
 
-## Special Settings for the PostScript Renderer <a id="ps-renderer"></a>
+### Special Settings for the PostScript Renderer <a id="ps-renderer"></a>
 
 Besides the normal font configuration (the same "fonts" element as for the PDF renderer) the PostScript renderer has an additional setting to force landscape pages to be rotated to fit on a page inserted into the printer in portrait mode. Set the value to "true" to activate this feature. The default is "false". Example:
 
@@ -149,7 +149,7 @@ Besides the normal font configuration (t
           </fonts>
         </renderer>
 
-## Special Settings for the PCL Renderer <a id="pcl-renderer"></a>
+### Special Settings for the PCL Renderer <a id="pcl-renderer"></a>
 
 Non-standard fonts for the PCL renderer are made available through the Java2D subsystem which means that you don't have to do any custom font configuration in this case but you have to use the font names offered by Java.
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/embedding.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/embedding.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/embedding.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/embedding.mdtext Mon Dec  3 15:46:33 2012
@@ -9,48 +9,48 @@ Review [Running Apache&trade; FOP](runni
 
 To embed Apache&trade; FOP in your application, first create a new org.apache.fop.apps.FopFactory instance. This object can be used to launch multiple rendering runs. For each run, create a new org.apache.fop.apps.Fop instance through one of the factory methods of FopFactory. In the method call you specify which output format (i.e. Renderer) to use and, if the selected renderer requires an OutputStream, which OutputStream to use for the results of the rendering. You can customize FOP's behaviour in a rendering run by supplying your own FOUserAgent instance. The FOUserAgent can, for example, be used to set your own Renderer instance (details below). Finally, you retrieve a SAX DefaultHandler instance from the Fop object and use that as the SAXResult of your transformation.
 We recently changed FOP's outer API to what we consider the final API. This might require some changes in your application. The main reasons for these changes were performance improvements due to better reuse of reusable objects and reduced use of static variables for added flexibility in complex environments.
-# Basic Usage Pattern <a id="basics"></a>
+## Basic Usage Pattern <a id="basics"></a>
 
 Apache FOP relies heavily on JAXP. It uses SAX events exclusively to receive the XSL-FO input document. It is therefore a good idea that you know a few things about JAXP (which is a good skill anyway). Let's look at the basic usage pattern for FOP...
 
 Here is the basic pattern to render an XSL-FO file to PDF:
 
-import org.apache.fop.apps.FopFactory;
-import org.apache.fop.apps.Fop;
-import org.apache.fop.apps.MimeConstants;
-
-/*..*/
-
-// Step 1: Construct a FopFactory
-// (reuse if you plan to render multiple documents!)
-FopFactory fopFactory = FopFactory.newInstance();
-
-// Step 2: Set up output stream.
-// Note: Using BufferedOutputStream for performance reasons (helpful with FileOutputStreams).
-OutputStream out = new BufferedOutputStream(new FileOutputStream(new File("C:/Temp/myfile.pdf")));
-
-try {
-  // Step 3: Construct fop with desired output format
-  Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, out);
-
-  // Step 4: Setup JAXP using identity transformer
-  TransformerFactory factory = TransformerFactory.newInstance();
-  Transformer transformer = factory.newTransformer(); // identity transformer
-           
-  // Step 5: Setup input and output for XSLT transformation 
-  // Setup input stream
-  Source src = new StreamSource(new File("C:/Temp/myfile.fo"));
-
-  // Resulting SAX events (the generated FO) must be piped through to FOP
-  Result res = new SAXResult(fop.getDefaultHandler());
-            
-  // Step 6: Start XSLT transformation and FOP processing
-  transformer.transform(src, res);
-
-} finally {
-  //Clean-up
-  out.close();
-}
+    import org.apache.fop.apps.FopFactory;
+    import org.apache.fop.apps.Fop;
+    import org.apache.fop.apps.MimeConstants;
+
+    /*..*/
+
+    // Step 1: Construct a FopFactory
+    // (reuse if you plan to render multiple documents!)
+    FopFactory fopFactory = FopFactory.newInstance();
+
+    // Step 2: Set up output stream.
+    // Note: Using BufferedOutputStream for performance reasons (helpful with FileOutputStreams).
+    OutputStream out = new BufferedOutputStream(new FileOutputStream(new File("C:/Temp/myfile.pdf")));
+
+    try {
+      // Step 3: Construct fop with desired output format
+      Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, out);
+
+      // Step 4: Setup JAXP using identity transformer
+      TransformerFactory factory = TransformerFactory.newInstance();
+      Transformer transformer = factory.newTransformer(); // identity transformer
+
+      // Step 5: Setup input and output for XSLT transformation
+      // Setup input stream
+      Source src = new StreamSource(new File("C:/Temp/myfile.fo"));
+
+      // Resulting SAX events (the generated FO) must be piped through to FOP
+      Result res = new SAXResult(fop.getDefaultHandler());
+
+      // Step 6: Start XSLT transformation and FOP processing
+      transformer.transform(src, res);
+
+    } finally {
+      //Clean-up
+      out.close();
+    }
 Let's discuss these 5 steps in detail:
 
 
@@ -86,28 +86,28 @@ If you want to process XSL-FO generated 
 
   //without XSLT:
   //Transformer transformer = factory.newTransformer(); // identity transformer
-  
+
   //with XSLT:
   Source xslt = new StreamSource(new File("mystylesheet.xsl"));
   Transformer transformer = factory.newTransformer(xslt);
-# Input Sources <a id="input"></a>
+## Input Sources <a id="input"></a>
 
 The input XSL-FO document is always received by FOP as a SAX stream (see the [Parsing Design Document](../dev/design/parsing.html) for the rationale).
 
 However, you may not always have your input document available as a SAX stream. But with JAXP it's easy to convert different input sources to a SAX stream so you can pipe it into FOP. That sounds more difficult than it is. You simply have to set up the right Source instance as input for the JAXP transformation. A few examples:
 
 
--  **URL:**  `Source src = new StreamSource("http://localhost:8080/testfile.xml");` 
+-  **URL:**  `Source src = new StreamSource("http://localhost:8080/testfile.xml");`
 
--  **File:**  `Source src = new StreamSource(new File("C:/Temp/myinputfile.xml"));` 
+-  **File:**  `Source src = new StreamSource(new File("C:/Temp/myinputfile.xml"));`
 
--  **String:**  `Source src = new StreamSource(new StringReader(myString)); // myString is a String` 
+-  **String:**  `Source src = new StreamSource(new StringReader(myString)); // myString is a String`
 
--  **InputStream:**  `Source src = new StreamSource(new MyInputStream(something));` 
+-  **InputStream:**  `Source src = new StreamSource(new MyInputStream(something));`
 
--  **Byte Array:**  `Source src = new StreamSource(new ByteArrayInputStream(myBuffer)); // myBuffer is a byte[] here` 
+-  **Byte Array:**  `Source src = new StreamSource(new ByteArrayInputStream(myBuffer)); // myBuffer is a byte[] here`
 
--  **DOM:**  `Source src = new DOMSource(myDocument); // myDocument is a Document or a Node` 
+-  **DOM:**  `Source src = new DOMSource(myDocument); // myDocument is a Document or a Node`
 
 -  **Java Objects:** Please have a look at the [Embedding examples](#examples) which contain an example for this.
 
@@ -124,106 +124,126 @@ The FopFactory holds configuration data 
 You can set all sorts of things on the FopFactory:
 
 
-- 
+-
 The **font base URL** to use when resolving relative URLs for fonts. Example:
-fopFactory.setFontBaseURL("file:///C:/Temp/fonts");
 
-- 
+    `fopFactory.setFontBaseURL("file:///C:/Temp/fonts");`
+
+-
 The **hyphenation base URL** to use when resolving relative URLs for hyphenation patterns. Example:
-fopFactory.setHyphenBaseURL("file:///C:/Temp/hyph");
 
-- 
+    `fopFactory.setHyphenBaseURL("file:///C:/Temp/hyph");`
+
+-
 Disable **strict validation** . When disabled FOP is less strict about the rules established by the XSL-FO specification. Example:
-fopFactory.setStrictValidation(false);
 
-- 
+    `fopFactory.setStrictValidation(false);`
+
+-
 Enable an **alternative set of rules for text indents** that tries to mimic the behaviour of many commercial FO implementations, that chose to break the specification in this respect. The default of this option is 'false', which causes Apache FOP to behave exactly as described in the specification. To enable the alternative behaviour, call:
-fopFactory.setBreakIndentInheritanceOnReferenceAreaBoundary(true);
 
-- 
+    `fopFactory.setBreakIndentInheritanceOnReferenceAreaBoundary(true);`
+
+-
 Set the **source resolution** for the document. This is used internally to determine the pixel size for SVG images and bitmap images without resolution information. Default: 72 dpi. Example:
-fopFactory.setSourceResolution(96); // =96dpi (dots/pixels per Inch)
 
-- 
+    `fopFactory.setSourceResolution(96); // =96dpi (dots/pixels per Inch)`
+
+-
 Manually add an **ElementMapping instance** . If you want to supply a special FOP extension you can give the instance to the FOUserAgent. Normally, the FOP extensions can be automatically detected (see the documentation on extension for more info). Example:
-fopFactory.addElementMapping(myElementMapping); // myElementMapping is a org.apache.fop.fo.ElementMapping
 
-- 
+    `fopFactory.addElementMapping(myElementMapping); // myElementMapping is a org.apache.fop.fo.ElementMapping`
+
+-
 Set a **URIResolver** for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example, you can use [Apache XML Commons Resolver](http://xml.apache.org/commons/components/resolver/) to make use of XCatalogs. Example:
-fopFactory.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolverBoth the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used if no other URIResolver (for example on the FOUserAgent) resolved the URI first.
+
+    `fopFactory.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolver`
+Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used if no other URIResolver (for example on the FOUserAgent) resolved the URI first.
 
 ### Customizing the User Agent <a id="user-agent"></a>
 
 The user agent is the entity that allows you to interact with a single rendering run, i.e. the processing of a single document. If you wish to customize the user agent's behaviour, the first step is to create your own instance of FOUserAgent using the appropriate factory method on FopFactory and pass that to the factory method that will create a new Fop instance:
 
-  FopFactory fopFactory = FopFactory.newInstance(); // Reuse the FopFactory if possible!
-  // do the following for each new rendering run
-  FOUserAgent userAgent = fopFactory.newFOUserAgent();
-  // customize userAgent
-  Fop fop = fopFactory.newFop(MimeConstants.MIME_POSTSCRIPT, userAgent, out);
+    FopFactory fopFactory = FopFactory.newInstance(); // Reuse the FopFactory if possible!
+    // do the following for each new rendering run
+    FOUserAgent userAgent = fopFactory.newFOUserAgent();
+    // customize userAgent
+    Fop fop = fopFactory.newFop(MimeConstants.MIME_POSTSCRIPT, userAgent, out);
 You can do all sorts of things on the user agent:
 
 
-- 
+-
 The **base URL** to use when resolving relative URLs. Example:
-userAgent.setBaseURL("file:///C:/Temp/");
 
-- 
+    `userAgent.setBaseURL("file:///C:/Temp/");`
+
+-
 Set the **producer** of the document. This is metadata information that can be used for certain output formats such as PDF. The default producer is "Apache FOP". Example:
-userAgent.setProducer("MyKillerApplication");
 
-- 
+    `userAgent.setProducer("MyKillerApplication");`
+
+-
 Set the **creating user** of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setCreator("John Doe");
 
-- 
+    `userAgent.setCreator("John Doe");`
+
+-
 Set the **author** of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setAuthor("John Doe");
 
-- 
+    `userAgent.setAuthor("John Doe");`
+
+-
 Override the **creation date and time** of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setCreationDate(new Date());
 
-- 
+    `userAgent.setCreationDate(new Date());`
+
+-
 Set the **title** of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setTitle("Invoice No 138716847");
 
-- 
+    `userAgent.setTitle("Invoice No 138716847");`
+
+-
 Set the **keywords** of the document. This is metadata information that can be used for certain output formats such as PDF. Example:
-userAgent.setKeywords("XML XSL-FO");
 
-- 
+    `userAgent.setKeywords("XML XSL-FO");`
+
+-
 Set the **target resolution** for the document. This is used to specify the output resolution for bitmap images generated by bitmap renderers (such as the TIFF renderer) and by bitmaps generated by Apache Batik for filter effects and such. Default: 72 dpi. Example:
-userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)
 
-- 
+    `userAgent.setTargetResolution(300); // =300dpi (dots/pixels per Inch)`
+
+-
 Set **your own Renderer instance** . If you want to supply your own renderer or configure a Renderer in a special way you can give the instance to the FOUserAgent. Normally, the Renderer instance is created by FOP. Example:
-userAgent.setRendererOverride(myRenderer); // myRenderer is an org.apache.fop.render.Renderer
 
-- 
-Set **your own FOEventHandler instance** . If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:
-userAgent.setFOEventHandlerOverride(myFOEventHandler); // myFOEventHandler is an org.apache.fop.fo.FOEventHandler
+    `userAgent.setRendererOverride(myRenderer); // myRenderer is an org.apache.fop.render.Renderer`
 
-- 
-Set a **URIResolver** for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example, you can use [Apache XML Commons Resolver](http://xml.apache.org/commons/components/resolver/) to make use of XCatalogs. Example:
-userAgent.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolverBoth the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FOUserAgent is used for resolving URIs which are document-related. If it's not set or cannot resolve a URI, the URIResolver from the FopFactory is used.
-You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially in multi-threaded environment, this is a bad idea.
-# Using a Configuration File <a id="config-external"></a>
+-
+Set **your own FOEventHandler instance** . If you want to supply your own FOEventHandler or configure an FOEventHandler subclass in a special way you can give the instance to the FOUserAgent. Normally, the FOEventHandler instance is created by FOP. Example:
 
-Instead of setting the parameters manually in code as shown above you can also set many values from an XML configuration file:
+    `userAgent.setFOEventHandlerOverride(myFOEventHandler); // myFOEventHandler is an org.apache.fop.fo.FOEventHandler`
 
-import org.apache.avalon.framework.configuration.Configuration;
-import org.apache.avalon.framework.configuration.DefaultConfigurationBuilder;
+-
+Set a **URIResolver** for custom URI resolution. By supplying a JAXP URIResolver you can add custom URI resolution functionality to FOP. For example, you can use [Apache XML Commons Resolver](http://xml.apache.org/commons/components/resolver/) to make use of XCatalogs. Example:
 
-/*..*/
+    `userAgent.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolver`
+Both the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FOUserAgent is used for resolving URIs which are document-related. If it's not set or cannot resolve a URI, the URIResolver from the FopFactory is used. You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially in multi-threaded environment, this is a bad idea.
 
-DefaultConfigurationBuilder cfgBuilder = new DefaultConfigurationBuilder();
-Configuration cfg = cfgBuilder.buildFromFile(new File("C:/Temp/mycfg.xml"));
-fopFactory.setUserConfig(cfg);
+## Using a Configuration File <a id="config-external"></a>
 
-/* ..or.. */
+Instead of setting the parameters manually in code as shown above you can also set many values from an XML configuration file:
 
-fopFactory.setUserConfig(new File("C:/Temp/mycfg.xml"));
+    import org.apache.avalon.framework.configuration.Configuration;
+    import org.apache.avalon.framework.configuration.DefaultConfigurationBuilder;
+    
+    /*..*/
+    
+    DefaultConfigurationBuilder cfgBuilder = new DefaultConfigurationBuilder();
+    Configuration cfg = cfgBuilder.buildFromFile(new File("C:/Temp/mycfg.xml"));
+    fopFactory.setUserConfig(cfg);
+    
+    /* ..or.. */
+    
+    fopFactory.setUserConfig(new File("C:/Temp/mycfg.xml"));
 The layout of the configuration file is described on the [Configuration page](configuration.html) .
 
 ## Hints <a id="hints"></a>
@@ -275,13 +295,13 @@ This [example](http://svn.apache.org/vie
 
 ![Example XSL-FO to PDF](images/EmbeddingExampleFO2PDF.png)
 
-## ExampleXML2FO.java <a id="ExampleXML2FO"></a>
+### 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) ).
 
 ![Example XML to XSL-FO](images/EmbeddingExampleXML2FO.png)
 
-## ExampleXML2PDF.java <a id="ExampleXML2PDF"></a>
+### ExampleXML2PDF.java <a id="ExampleXML2PDF"></a>
 
 This [example](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2PDF.java?view=markup) demonstrates how you can convert an arbitrary XML file to PDF using XSLT and XSL-FO/FOP. It is a combination of the first two examples above. The example uses JAXP to transform the XML file to XSL-FO and FOP to transform the XSL-FO to PDF.
 
@@ -307,7 +327,7 @@ This [example](http://svn.apache.org/vie
 
 ![Example Java object to PDF (via XML and XSL-FO)](images/EmbeddingExampleObj2PDF.png)
 
-## ExampleDOM2PDF.java <a id="ExampleDOM2PDF"></a>
+### ExampleDOM2PDF.java <a id="ExampleDOM2PDF"></a>
 
 This [example](http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleDOM2PDF.java?view=markup) has FOP use a DOMSource instead of a StreamSource in order to use a DOM tree as input for an XSL transformation.
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/extensions.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/extensions.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/extensions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/extensions.mdtext Mon Dec  3 15:46:33 2012
@@ -5,9 +5,9 @@ Title: Standard Apache&trade; FOP Extens
 
 By "extension", we mean any data that can be placed in the input XML document that is not addressed by the XSL-FO standard. By having a mechanism for supporting extensions, FOP is able to add features that are not covered in the specification.
 
-The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the [Developers' Extension Page](../dev/extensions.html) .
+The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the [Developers' Extension Page](../dev/extensions.html).
 All extensions require the correct use of an appropriate namespace in your input document.
-# SVG <a id="svg"></a>
+## SVG <a id="svg"></a>
 
 Please see the [SVG documentation](graphics.html#svg) for more details.
 
@@ -20,7 +20,7 @@ By convention, FO extensions in FOP use 
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:fox="http://xmlgraphics.apache.org/fop/extensions">
 
-## PDF Bookmarks <a id="bookmarks"></a>
+### PDF Bookmarks <a id="bookmarks"></a>
 
 In previous versions of Apache FOP there was a `fox:outline` element which was used to create outlines in PDF files. The redesigned code makes use of the new [bookmark feature defined in the latest XSL 1.1 working draft](http://www.w3.org/TR/xsl11/#fo_bookmark-tree) .
 
@@ -30,27 +30,27 @@ Use the fox:destination element to defin
 
     <fox:destination internal-destination="table-of-contents"/>
     ...
-    <fo:block id="table-of-contents">Table of Contents</fo:block><warning>It is possible that in some future release of FOP, *all* elements with "id" attributes will generate named-destinations, which will eliminate the need for fox:destination.</warning>
+    <fo:block id="table-of-contents">Table of Contents</fo:block>
+<warning>It is possible that in some future release of FOP, *all* elements with "id" attributes will generate named-destinations, which will eliminate the need for fox:destination.</warning>
 
-## Table Continuation Label <a id="table-continue-label"></a>
+### Table Continuation Label <a id="table-continue-label"></a>
 
 This extension element hasn't been reimplemented for the redesigned code, yet.
 
 ### fox:orphan-content-limit and fox:widow-content-limit <a id="widow-orphan-content-limit"></a>
 
-The two proprietary extension properties, fox:orphan-content-limit and fox:widow-content-limit, are used to improve the layout of list-blocks and tables. If you have a table with many entries, you don't want a single row to be left over on a page. You will want to make sure that at least two or three lines are kept together. The properties take an absolute length which specifies the area at the beginning (fox:widow-content-limit) or at the end (fox:orphan-content-limit) of a table or list-block. The properties are inherited and only have an effect on fo:table and fo:list-block. An example: fox:widow-content-limit="3 * 1.2em" would make sure the you'll have at least three lines (assuming line-height="1.2") together on a table or list-block.
+The two proprietary extension properties, `fox:orphan-content-limit` and `fox:widow-content-limit`, are used to improve the layout of list-blocks and tables. If you have a table with many entries, you don't want a single row to be left over on a page. You will want to make sure that at least two or three lines are kept together. The properties take an absolute length which specifies the area at the beginning (`fox:widow-content-limit`) or at the end (`fox:orphan-content-limit`) of a table or list-block. The properties are inherited and only have an effect on `fo:table` and `fo:list-block`. An example: `fox:widow-content-limit="3 * 1.2em"` would make sure the you'll have at least three lines (assuming `line-height="1.2"`) together on a table or list-block.
 
 ### fox:external-document <a id="external-document"></a>
 This feature is incomplete. Support for multi-page documents will be added shortly. At the moment, only single-page images will work. And this will not work with RTF output.
+
 This is a proprietary extension element which allows to add whole images as pages to an FO document. For example, if you have a scanned document or a fax as multi-page TIFF file, you can append or insert this document using the `fox:external-document` element. Each page of the external document will create one full page in the target format.
 
 The `fox:external-document` element is structurally a peer to `fo:page-sequence` , so wherever you can put an `fo:page-sequence` you could also place a `fox:external-document` . Therefore, the specified contents for `fo:root` change to:
 
- `
             (layout-master-set, declarations?, bookmark-tree?, (page-sequence|page-sequence-wrapper|fox:external-document|fox:destination)+)
-          ` 
 
-#### Specification ## <a id="Specification"></a>
+#### Specification<a id="Specification"></a>
 
 The `fox:external-document` extension formatting object is used to specify how to create a (sub-)sequence of pages within a document. The content of these pages comes from the individual subimages/pages of an image or paged document (for example: multi-page TIFF in the form of faxes or scanned documents, or PDF files). The formatting object creates the necessary areas to display one image per page.
 
@@ -99,17 +99,17 @@ The following properties apply to this f
 
 Datatype "page-set": Value: auto | <integer-range>, Default: "auto" which means all pages/subimages of the document. <integer-range> allows values such as "7" or "1-3"
  `fox:external-document` is not suitable for concatenating FO documents. For this, XInclude is recommended.
-## Free-form Transformation for fo:block-container <a id="transform"></a>
+### Free-form Transformation for fo:block-container <a id="transform"></a>
 
 For `fo:block-container` elements whose `absolute-position` set to "absolute" or "fixed" you can use the extension attribute `fox:transform` to apply a free-form transformation to the whole block-container. The content of the `fox:transform` attribute is the same as for [SVG's transform attribute](http://www.w3.org/TR/SVG/coords.html#TransformAttribute) . The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.
 
 Examples: `fox:transform="rotate(45)"` would rotate the block-container by 45 degrees clock-wise around its upper-left corner. `fox:transform="translate(10000,0)"` would move the block-container to the right by 10 points (=10000 millipoints, FOP uses millipoints internally!).
 This extension attribute doesn't work for all output formats! It's currently only supported for PDF, PS and Java2D-based renderers.
-## Color functions <a id="color-functions"></a>
+### Color functions <a id="color-functions"></a>
 
 XSL-FO supports specifying color using the rgb(), rgb-icc() and system-color() functions. Apache FOP provides additional color functions for special use cases. Please note that using these functions compromises the interoperability of an FO document.
 
-#### cmyk() ## <a id="color-function-cmyk"></a>
+#### cmyk()<a id="color-function-cmyk"></a>
 
  `color cmyk(numeric, numeric, numeric, numeric)` 
 

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=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext Mon Dec  3 15:46:33 2012
@@ -65,7 +65,7 @@ If you want FOP to use custom fonts, you
     </fonts>
 
 Review the documentation for [FOP Configuration](configuration.html) for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. It is currently not possible to easily configure fonts from Java code.
-# Advanced font configuration <a id="advanced"></a>
+## Advanced font configuration <a id="advanced"></a>
 
 The instructions found above should be sufficient for most users. Below are some additional instructions in case the basic font configuration doesn't lead to the desired results.
 
@@ -160,7 +160,7 @@ You must tell FOP how to find and use th
 
 - If relative URLs are specified, they are evaluated relative to the value of the "font-base" setting. If there is no "font-base" setting, the fonts are evaluated relative to the base directory.
 
-### Auto-Detect and auto-embedd feature <a id="autodetect"></a>
+### Auto-Detect and auto-embed feature <a id="autodetect"></a>
 
 When the "auto-detect" flag is set in the configuration, FOP will automatically search for fonts in the default paths for your operating system.
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/graphics.mdtext Mon Dec  3 15:46:33 2012
@@ -20,10 +20,8 @@ The actual [image loading framework](htt
 
 The table below summarizes the *theoretical* support for graphical formats within FOP. In other words, within the constraints of the limitations listed here, these formats *should* work. However, many of them have not been tested, and there may be limitations that have not yet been discovered or documented. The packages needed to support some formats are not included in the FOP distribution and must be installed separately. Follow the links in the "Support Through" columns for more details.
 
-| Format | Type | Support Through |
-|--------|------|-----------------|
-|  [Apache FOP (native)](#native)  |  [Apache Batik](#batik)  |  [Image I/O](#imageio)  |
-|---------------------|--------------|-----------|
+| Format | Type | Support Through [Apache FOP (native)](#native)  |   Support Through [Apache Batik](#batik)  |   Support Through [Image I/O](#imageio)  |
+|--------|------|:-----------:|:--------------:|:-----------:|
 |  [BMP](#bmp) (Microsoft Windows Bitmap) | bitmap |  |  | X [1] |
 |  [EMF](#emf) (Windows Enhanced Metafile) | vector (with embedded bitmaps) | (X) |  |  |
 |  [EPS](#eps) (Encapsulated PostScript) | metafile (both bitmap and vector), most frequently used for vector drawings | (X) |  |  |
@@ -41,12 +39,12 @@ Legend:
 
 - [1]: Requires the presence of [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.
  [JAI Image I/O Tools](http://jai-imageio.dev.java.net/) is not the same as the [JAI library](http://java.sun.com/javase/technologies/desktop/media/jai/) ! The former simply exposes JAI's codecs using the Image&nbsp;I/O API but does not include all the image manipulation functionality.
-## Map of supported image formats by output format <a id="format-map"></a>
+### Map of supported image formats by output format <a id="format-map"></a>
 
 Not all image formats are supported for all output formats! For example, while you can use EPS (Encapsulated PostScript) files when you generate PostScript output, this format will not be supported by any other output format. Here's an overview of which image formats are supported by which output format:
 
 | Image Format | PDF | PostScript | Java2D, PNG, TIFF, AWT | PCL | AFP | RTF |
-|--------------|-----|------------|------------------------|-----|-----|-----|
+|--------------|:---:|:----------:|:----------------------:|:---:|:---:|:---:|
 |  [BMP](#bmp) (Microsoft Windows Bitmap) | X | X | X | X | X | X |
 |  [EMF](#emf) (Windows Enhanced Metafile) |  |  |  |  |  | X [1] |
 |  [EPS](#eps) (Encapsulated PostScript) |  | X [1] |  |  |  |  |
@@ -125,11 +123,11 @@ PNG images are supported through an Imag
 
 ### SVG <a id="svg"></a>
 
-#### Introduction ## <a id="svg-intro"></a>
+#### Introduction<a id="svg-intro"></a>
 
 FOP uses [Apache Batik](#batik) for SVG support. This format can be handled as an `fo:instream-foreign-object` or in a separate file referenced with `fo:external-graphic` .
 Batik's SVG Rasterizer utility may also be used to convert standalone SVG documents into PDF. For more information please see the [SVG Rasterizer documentation](http://xmlgraphics.apache.org/batik/svgrasterizer.html) on the Batik site.
-### Placing SVG Graphics into PDF ## <a id="svg-pdf-graphics"></a>
+#### Placing SVG Graphics into PDF<a id="svg-pdf-graphics"></a>
 
 The SVG is rendered into PDF by using PDF commands to draw and fill lines and curves. This means that the graphical objects created with this remain as vector graphics. The same applies to PostScript output. For other output formats the SVG graphic may be converted to a bitmap image.
 
@@ -137,7 +135,7 @@ There are a number of SVG things that ca
 
 Currently transparency is limited in PDF so many SVG images that contain effects or graphics with transparent areas may not be displayed correctly.
 
-#### Placing SVG Text into PDF and PostScript ## <a id="svg-pdf-text"></a>
+#### Placing SVG Text into PDF and PostScript<a id="svg-pdf-text"></a>
 
 If possible, Batik will use normal PDF or PostScript text when inserting text. It does this by checking if the text can be drawn normally and the font is supported. This example svg [text.svg](../dev/svg/text.svg) /text.pdfshows how various types and effects with text are handled. Note that tspan and outlined text are not yet implemented.
 
@@ -145,13 +143,13 @@ Otherwise, text is converted and drawn a
 
 Note that because SVG text can be rendered as either text or a vector graphic, you may need to consider settings in your viewer for both. The Acrobat viewer has both "smooth line art" and "smooth text" settings that may need to be set for SVG images to be displayed nicely on your screen (see Edit / Preferences / Display). This setting will not affect the printing of your document, which should be OK in any case, but will only affect the quality of the screen display.
 
-#### Scaling ## <a id="svg-scaling"></a>
+#### Scaling<a id="svg-scaling"></a>
 
 Currently, SVG images are rendered with the dimensions specified *in the SVG file* , within the viewport specified in the fo:external-graphic element. For everything to work properly, the two should be equal. The SVG standard leaves this issue as an implementation detail. Additional scaling options are available through XSL-FO means.
 
 If you use pixels to specify the size of an SVG graphic the "source resolution" setting in the [configuration](configuration.html) will be used to determine the size of a pixel. The use of pixels to specify sizes is discouraged as they may be interpreted differently in different environments.
 
-#### Known Problems ## <a id="svg-problems"></a>
+#### Known Problems<a id="svg-problems"></a>
 
 
 - Soft mask transparency is combined with white so that it looks better on PDF 1.3 viewers but this causes the soft mask to be slightly lighter or darker on PDF 1.4 viewers.

Modified: xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/hyphenation.mdtext Mon Dec  3 15:46:33 2012
@@ -11,13 +11,13 @@ Apache&trade; FOP uses Liang's hyphenati
 
 Because of [licensing issues](#license-issues) (and for convenience), all hyphenation patterns for FOP are made available through the [Objects For Formatting Objects](http://offo.sourceforge.net/hyphenation/index.html) project.
 If you have made improvements to an existing FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the [FOP User mailing list](../maillist.html#fop-user) .
-## License Issues <a id="license-issues"></a>
+### License Issues <a id="license-issues"></a>
 
 Many of the hyphenation files distributed with TeX and its offspring are licenced under the [LaTeX Project Public License (LPPL)](http://www.latex-project.org/lppl.html) , which prevents them from being distributed with Apache software. The LPPL puts restrictions on file names in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files have other or additional restrictions, for example against use for commercial purposes.
 
 Although Apache FOP cannot redistribute hyphenation pattern files that do not conform with its license scheme, that does not necessarily prevent users from using such hyphenation patterns with FOP. However, it does place on the user the responsibility for determining whether the user can rightly use such hyphenation patterns under the hyphenation pattern license.
 <warning>The user is responsible to settle license issues for hyphenation pattern files that are obtained from non-Apache sources.</warning>
-## Sources of Custom Hyphenation Pattern Files <a id="sources"></a>
+### Sources of Custom Hyphenation Pattern Files <a id="sources"></a>
 
 The most important source of hyphenation pattern files is the [CTAN TeX Archive](http://www.ctan.org/tex-archive/language/hyphenation/) .
 
@@ -49,7 +49,7 @@ and run Ant with build target `jar-hyphe
 - 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.
 
 <warning>Either of these three options will ensure hyphenation is working when using FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the [<hyphenation-dir>](configuration.html#hyphenation-dir) configuration option programmatically (option 3).</warning>
-# Hyphenation Patterns <a id="patterns"></a>
+## Hyphenation Patterns <a id="patterns"></a>
 
 If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See [OFFO's Hyphenation page](http://offo.sourceforge.net/hyphenation/index.html) for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
 <warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the [FOP User mailing list](../maillist.html#fop-user) , either confirming their accuracy, or raising specific problems that we can address.</warning>

Modified: xmlgraphics/site/trunk/content/fop/0.95/intermediate.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/intermediate.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/intermediate.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/intermediate.mdtext Mon Dec  3 15:46:33 2012
@@ -3,7 +3,7 @@ Title: Apache(tm) FOP: Intermediate Form
 #Apache&trade; FOP: Intermediate Format
 
 Please note that the intermediate format is an **advanced feature** and can be ignored by most users of Apache&trade; FOP.
-# Introduction <a id="introduction"></a>
+## Introduction <a id="introduction"></a>
 
 The intermediate format (IF) is a proprietary XML format that represents the area tree generated by the layout engine. The area tree is conceptually defined in the [XSL-FO specification in chapter 1.1.2](http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting) . The IF can be generated through the area tree XML Renderer (the XMLRenderer).
 
@@ -17,30 +17,30 @@ The second step is to reparse the IF fil
 
 The basic pattern to parse the IF format looks like this:
 
-FopFactory fopFactory = FopFactory.newInstance();      
-      
-// Setup output
-OutputStream out = new java.io.FileOutputStream(pdffile);
-out = new java.io.BufferedOutputStream(out);
-try {
-    //Setup fonts and user agent
-    FontInfo fontInfo = new FontInfo();
-    FOUserAgent userAgent = fopFactory.newFOUserAgent();
-
-    //Construct the AreaTreeModel that will received the individual pages
-    AreaTreeModel treeModel = new RenderPagesModel(userAgent, 
-            MimeConstants.MIME_PDF, fontInfo, out);
-            
-    //Parse the IF file into the area tree
-    AreaTreeParser parser = new AreaTreeParser();
-    Source src = new StreamSource(myIFFile);
-    parser.parse(src, treeModel, userAgent);
-            
-    //Signal the end of the processing. The renderer can finalize the target document.
-    treeModel.endDocument();
-} finally {
-    out.close();
-}
+    FopFactory fopFactory = FopFactory.newInstance();      
+          
+    // Setup output
+    OutputStream out = new java.io.FileOutputStream(pdffile);
+    out = new java.io.BufferedOutputStream(out);
+    try {
+        //Setup fonts and user agent
+        FontInfo fontInfo = new FontInfo();
+        FOUserAgent userAgent = fopFactory.newFOUserAgent();
+    
+        //Construct the AreaTreeModel that will received the individual pages
+        AreaTreeModel treeModel = new RenderPagesModel(userAgent, 
+                MimeConstants.MIME_PDF, fontInfo, out);
+                
+        //Parse the IF file into the area tree
+        AreaTreeParser parser = new AreaTreeParser();
+        Source src = new StreamSource(myIFFile);
+        parser.parse(src, treeModel, userAgent);
+                
+        //Signal the end of the processing. The renderer can finalize the target document.
+        treeModel.endDocument();
+    } finally {
+        out.close();
+    }
 This example simply reads an IF file and renders it to a PDF file. Please note, that in normal FOP operation you're shielded from having to instantiate the FontInfo object yourself. This is normally a task of the AreaTreeHandler which is not present in this scenario. The same applies to the AreaTreeModel instance, in this case an instance of a subclass called RenderPagesModel. RenderPagesModel is ideal in this case as it has very little overhead processing the individual pages. An important line in the example is the call to `endDocument()` on the AreaTreeModel. This lets the Renderer know that the processing is now finished.
 
 The intermediate format can also be used from the [command-line](running.html#standalone-start) by using the "-atin" parameter for specifying the area tree XML as input file. You can also specify a "mimic renderer" by inserting a MIME type between "-at" and the output file.

Modified: xmlgraphics/site/trunk/content/fop/0.95/metadata.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/metadata.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/metadata.mdtext Mon Dec  3 15:46:33 2012
@@ -36,9 +36,10 @@ Document-level metadata can be specified
 	  </x:xmpmeta>
 	</fo:declarations>
 	<fo:page-sequence ...
-	[..] `fo:declarations`  **must** be declared after `fo:layout-master-set` and before the first `page-sequence` .
+	[..]
+`fo:declarations`  **must** be declared after `fo:layout-master-set` and before the first `page-sequence`.
 
-# Implementation in Apache FOP <a id="xmp-impl-in-fop"></a>
+## Implementation in Apache FOP <a id="xmp-impl-in-fop"></a>
 
 Currently, XMP support is only available for PDF output.
 
@@ -48,9 +49,7 @@ Apache FOP now synchronizes the Info and
 
 The mapping between the Info and the Metadata object used by Apache FOP comes from the [PDF/A-1 specification](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920) . For convenience, here's the mapping table:
 
-| Document information dictionary | XMP |
-|---------------------------------|-----|
-| Entry | PDF type | Property | XMP type | Category |
+| Document information dictionary<br/>Entry | PDF type | XMP Property | XMP type | XMP Category |
 |-------|----------|----------|----------|----------|
 | Title | text string | dc:title | Text | External |
 | Author | text string | dc:creator | seq Text | External |
@@ -61,7 +60,8 @@ The mapping between the Info and the Met
 | CreationDate | date | xmp:CreationDate | Date | Internal |
 | ModDate | date | xmp:ModifyDate | Date | Internal |
 "Internal" in the Category column means that the user should not set this value. It is set by the application.The "Subject" used to be mapped to `dc:subject` in the initial publication of PDF/A-1 (ISO 19005-1). In the [Technical Corrigendum 1](http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613) this was changed to map to `dc:description["x-default"]` .
-## Namespaces <a id="namespaces"></a>
+
+### Namespaces <a id="namespaces"></a>
 
 Metadata is made of property sets where each property set uses a different namespace URI.
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/output.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/output.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/output.mdtext Mon Dec  3 15:46:33 2012
@@ -57,47 +57,48 @@ FOP does not currently support several d
 Another popular post-processing tool is [iText](http://www.lowagie.com/iText) , which has tools for adding security features, document properties, watermarks, and many other features to PDF files.
 <warning>Caveat: iText may swallow PDF bookmarks. But [Jens Stavnstrup tells us](http://issues.apache.org/bugzilla/show_bug.cgi?id=37589) that this doesn't happen if you use iText's PDFStamper.</warning>
 Here is some sample code that uses iText to encrypt a FOP-generated PDF. (Note that FOP now supports [PDF encryption](pdfencryption.html) . However the principles for using iText for other PDF features are similar.)
-public static void main(String args[]) {
-  try {
-    ByteArrayOutputStream fopout = new ByteArrayOutputStream();
-    FileOutputStream outfile = new FileOutputStream(args[2]);
-    FopFactory fopFactory = FopFactory.newInstance();
-    Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, fopout);
-    
-    Transformer transformer = TransformerFactory.newInstance().newTransformer(
-        new StreamSource(new File(args[1])));
-    transformer.transform(new StreamSource(new File(args[0])),
-        new SAXResult(fop.getDefaultHandler()));
-    PdfReader reader = new PdfReader(fopout.toByteArray());
-    int n = reader.getNumberOfPages();
-    Document document = new Document(reader.getPageSizeWithRotation(1));
-    PdfWriter writer = PdfWriter.getInstance(document, outfile);
-    writer.setEncryption(PdfWriter.STRENGTH40BITS, "pdf", null,
-      PdfWriter.AllowCopy);
-    document.open();
-    PdfContentByte cb = writer.getDirectContent();
-    PdfImportedPage page;
-    int rotation;
-    int i = 0;
-    while (i < n) {
-      i++;
-      document.setPageSize(reader.getPageSizeWithRotation(i));
-      document.newPage();
-      page = writer.getImportedPage(reader, i);
-      rotation = reader.getPageRotation(i);
-      if (rotation == 90 || rotation == 270) {
-        cb.addTemplate(page, 0, -1f, 1f, 0, 0,
-        reader.getPageSizeWithRotation(i).height());
-      } else {
-        cb.addTemplate(page, 1f, 0, 0, 1f, 0, 0);
+
+    public static void main(String args[]) {
+      try {
+        ByteArrayOutputStream fopout = new ByteArrayOutputStream();
+        FileOutputStream outfile = new FileOutputStream(args[2]);
+        FopFactory fopFactory = FopFactory.newInstance();
+        Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, fopout);
+        
+        Transformer transformer = TransformerFactory.newInstance().newTransformer(
+            new StreamSource(new File(args[1])));
+        transformer.transform(new StreamSource(new File(args[0])),
+            new SAXResult(fop.getDefaultHandler()));
+        PdfReader reader = new PdfReader(fopout.toByteArray());
+        int n = reader.getNumberOfPages();
+        Document document = new Document(reader.getPageSizeWithRotation(1));
+        PdfWriter writer = PdfWriter.getInstance(document, outfile);
+        writer.setEncryption(PdfWriter.STRENGTH40BITS, "pdf", null,
+          PdfWriter.AllowCopy);
+        document.open();
+        PdfContentByte cb = writer.getDirectContent();
+        PdfImportedPage page;
+        int rotation;
+        int i = 0;
+        while (i < n) {
+          i++;
+          document.setPageSize(reader.getPageSizeWithRotation(i));
+          document.newPage();
+          page = writer.getImportedPage(reader, i);
+          rotation = reader.getPageRotation(i);
+          if (rotation == 90 || rotation == 270) {
+            cb.addTemplate(page, 0, -1f, 1f, 0, 0,
+            reader.getPageSizeWithRotation(i).height());
+          } else {
+            cb.addTemplate(page, 1f, 0, 0, 1f, 0, 0);
+          }
+          System.out.println("Processed page " + i);
+        }
+        document.close();
+      } catch( Exception e) {
+        e.printStackTrace();
       }
-      System.out.println("Processed page " + i);
     }
-    document.close();
-  } catch( Exception e) {
-    e.printStackTrace();
-  }
-}
 Check the iText tutorial and documentation for setting access flags, password, encryption strength and other parameters.
 
 ### Watermarks <a id="pdf-watermark"></a>
@@ -116,13 +117,14 @@ The PostScript renderer has been brought
 ### Configuration <a id="ps-configuration"></a>
 
 The PostScript renderer configuration currently allows the following settings:
-<renderer mime="application/postscript">
-  <auto-rotate-landscape>false</auto-rotate-landscape>
-  <language-level>3</language-level>
-  <optimize-resources>false</optimize-resources>
-  <safe-set-page-device>false</safe-set-page-device>
-  <dsc-compliant>true</dsc-compliant>
-</renderer>
+
+    <renderer mime="application/postscript">
+      <auto-rotate-landscape>false</auto-rotate-landscape>
+      <language-level>3</language-level>
+      <optimize-resources>false</optimize-resources>
+      <safe-set-page-device>false</safe-set-page-device>
+      <dsc-compliant>true</dsc-compliant>
+    </renderer>
 The default value for the "auto-rotate-landscape" setting is "false". Setting it to "true" will automatically rotate landscape pages and will mark them as landscape.
 
 The default value for the "language-level" setting is "3". This setting specifies the PostScript language level which should be used by FOP. Set this to "2" only if you don't have a Level 3 capable interpreter.
@@ -179,11 +181,12 @@ The output created by the PCLRenderer is
 ### Configuration <a id="pcl-configuration"></a>
 
 The PCL renderer configuration currently allows the following settings:
-<renderer mime="application/vnd.hp-PCL">
-  <rendering>quality</rendering>
-  <text-rendering>bitmap</text-rendering>
-  <disable-pjl>false</disable-pjl>
-</renderer>
+
+    <renderer mime="application/vnd.hp-PCL">
+      <rendering>quality</rendering>
+      <text-rendering>bitmap</text-rendering>
+      <disable-pjl>false</disable-pjl>
+    </renderer>
 The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.
 
 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.
@@ -199,7 +202,7 @@ The PCL Renderer supports some PCL speci
       <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:pcl="http://xmlgraphics.apache.org/fop/extensions/pcl">
 
-#### Page Source (Tray selection) ## <a id="pcl-page-source"></a>
+#### Page Source (Tray selection)<a id="pcl-page-source"></a>
 
 The page-source extension attribute on fo:simple-page-master allows to select the paper tray the sheet for a particular simple-page-master is to be taken from. Example:
 
@@ -233,13 +236,14 @@ This list is most likely badly incomplet
 
 ### Configuration <a id="afp-configuration"></a>
 
-#### Fonts ## <a id="afp-font-config"></a>
+#### Fonts<a id="afp-font-config"></a>
 
 The AFP Renderer requires special configuration particularly related to fonts. AFP Render configuration is done through the normal FOP configuration file. The MIME type for the AFP Renderer is application/x-afp which means the AFP Renderer section in the FOP configuration file looks like:
-<renderer mime="application/x-afp">
-  <!-- AFP Renderer -->
-  ...
-</renderer>
+
+    <renderer mime="application/x-afp">
+      <!-- AFP Renderer -->
+      ...
+    </renderer>
 There are 3 font configuration variants supported:
 
 
@@ -359,13 +363,13 @@ Experimentation has shown that the font 
         <font-triplet name="Courier" style="normal" weight="bold"/>
       </font>
 
-### Output Resolution ## <a id="afp-renderer-resolution-config"></a>
+#### Output Resolution<a id="afp-renderer-resolution-config"></a>
 
 By default the AFP Renderer creates output with a resolution of 240 dpi. This can be overridden by the <renderer-resolution/> configuration element. Example:
 
       <renderer-resolution>240</renderer-resolution>
 
-### Images ## <a id="afp-image-config"></a>
+#### Images<a id="afp-image-config"></a>
 
 By default the AFP Renderer converts all images to 8 bit grey level. This can be overridden by the <images> configuration element. Example:
 
@@ -384,7 +388,7 @@ The AFP Renderer supports some AFP speci
       <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
 
-#### Page Overlay Extension ## <a id="afp-page-overlay"></a>
+#### Page Overlay Extension<a id="afp-page-overlay"></a>
 
 The include-page-overlay extension element allows to define on a per simple-page-master basis a page overlay resource. Example:
 
@@ -397,7 +401,7 @@ The include-page-overlay extension eleme
 
 The mandatory name attribute must refer to an 8 character (space padded) resource name that must be known in the AFP processing environment.
 
-#### Page Segment Extension ## <a id="afp-page-segment"></a>
+#### Page Segment Extension<a id="afp-page-segment"></a>
 
 The include-page-segment extension element allows to define resource substitution for fo:external-graphics elements. Example:
 
@@ -412,7 +416,7 @@ The include-page-segment extension eleme
 
 The include-page-segment extension element can only occur within a simple-page-master. Multiple include-page-segment extension elements within a simple-page-master are allowed. The mandatory name attribute must refer to an 8 character (space padded) resource name that must be known in the AFP processing environment. The value of the mandatory src attribute is compared against the value of the src attribute in fo:external-graphic elements and if it is identical (string matching is used) in the generated AFP the external graphic is replaced by a reference to the given resource.
 
-#### Tag Logical Element Extension ## <a id="afp-tag-logical-element"></a>
+#### Tag Logical Element Extension<a id="afp-tag-logical-element"></a>
 
 The tag-logical-element extension element allows to injects TLEs into the AFP output stream. Example:
 
@@ -427,7 +431,7 @@ The tag-logical-element extension elemen
 
 The tag-logical-element extension element can only occur within a simple-page-master. Multiple tag-logical-element extension elements within a simple-page-master are allowed. The name and value attributes are mandatory.
 
-#### No Operation Extension ## <a id="afp-no-operation"></a>
+#### No Operation Extension<a id="afp-no-operation"></a>
 
 The no-operation extension provides the ability to carry up to 32K of comments or any other type of unarchitected data into the AFP output stream. Example:
 
@@ -519,23 +523,23 @@ In addition to the above values the TIFF
 The default value for the "compression" setting is "PackBits" which which is a widely supported RLE compression scheme for TIFF. The set of compression names to be used here matches the set that the Image I/O API uses. Note that not all compression schemes may be available during runtime. This depends on the actual codecs being available. Here is a list of possible values:
 
 
-- NONE (no compression)
+- `NONE` (no compression)
 
-- PackBits (RLE, run-length encoding)
+- `PackBits` (RLE, run-length encoding)
 
-- JPEG
+- `JPEG`
 
-- Deflate
+- `Deflate`
 
-- LZW
+- `LZW`
 
-- ZLib
+- `ZLib`
 
-- CCITT T.4 (Fax Group 3)
+- `CCITT T.4` (Fax Group 3)
 
-- CCITT T.6 (Fax Group 4)
+- `CCITT T.6` (Fax Group 4)
 If you want to use CCITT compression, please make sure you've got a J2SE 1.4 or later and [Java Advanced Imaging Image I/O Tools](http://java.sun.com/products/java-media/jai/current.html) in your classpath. The Sun JRE doesn't come with a TIFF codec built in, so it has to be added separately. The internal TIFF codec from XML Graphics Commons only supports PackBits, Deflate and JPEG compression for writing.
-# TXT <a id="txt"></a>
+## TXT <a id="txt"></a>
 
 The text renderer produces plain ASCII text output that attempts to match the output of the PDFRenderer as closely as possible. This was originally developed to accommodate an archive system that could only accept plain text files, and is primarily useful for getting a quick-and-dirty view of the document text. The renderer is very limited, so do not be surprised if it gives unsatisfactory results.
 

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=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/pdfencryption.mdtext Mon Dec  3 15:46:33 2012
@@ -36,15 +36,15 @@ When FOP is embedded in another Java app
 Encryption is enabled as soon as one of these options is set.
 An example to enable PDF encryption in Java code:
 
-import org.apache.fop.pdf.PDFEncryptionParams;
-
-[..]
-
-FOUserAgent userAgent = fopFactory.newFOUserAgent();
-useragent.getRendererOptions().put("encryption-params", new PDFEncryptionParams(
-    null, "password", false, false, true, true));
-Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent);
-[..]
+    import org.apache.fop.pdf.PDFEncryptionParams;
+    
+    [..]
+    
+    FOUserAgent userAgent = fopFactory.newFOUserAgent();
+    useragent.getRendererOptions().put("encryption-params", new PDFEncryptionParams(
+        null, "password", false, false, true, true));
+    Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent);
+    [..]
 The parameters for the constructor of PDFEncryptionParams are:
 
 

Modified: xmlgraphics/site/trunk/content/fop/0.95/running.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/running.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/running.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/running.mdtext Mon Dec  3 15:46:33 2012
@@ -54,78 +54,78 @@ Some Mac OSX users have experienced file
 
 The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is `/Library/Java/Home` . **Caveat:** We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see [Java on Mac OSX FAQ](http://developer.apple.com/java/faq) for information as it becomes available.
 
-USAGE
-Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] <outfile>
- [OPTIONS]  
-  -d                debug mode   
-  -x                dump configuration settings  
-  -q                quiet mode  
-  -c cfg.xml        use additional configuration file cfg.xml
-  -l lang           the language to use for user information 
-  -r                relaxed/less strict validation (where available)
-  -dpi xxx          target resolution in dots per inch (dpi) where xxx is a number
-  -s                for area tree XML, down to block areas only
-  -v                to show FOP version being used
-
-  -o [password]     PDF file will be encrypted with option owner password
-  -u [password]     PDF file will be encrypted with option user password
-  -noprint          PDF file will be encrypted without printing permission
-  -nocopy           PDF file will be encrypted without copy content permission
-  -noedit           PDF file will be encrypted without edit content permission
-  -noannotations    PDF file will be encrypted without edit annotation permission
-  -pdfprofile prof  PDF file will be generated with the specified profile
-                    (Examples for prof: PDF/A-1b or PDF/X-3:2003)
-
- [INPUT]  
-  infile            xsl:fo input file (the same as the next) 
-  -fo  infile       xsl:fo input file  
-  -xml infile       xml input file, must be used together with -xsl 
-  -atin infile      area tree input file 
-  -xsl stylesheet   xslt stylesheet 
+    USAGE
+    Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl|-ps|-txt|-at [mime]|-print] <outfile>
+     [OPTIONS]  
+      -d                debug mode   
+      -x                dump configuration settings  
+      -q                quiet mode  
+      -c cfg.xml        use additional configuration file cfg.xml
+      -l lang           the language to use for user information 
+      -r                relaxed/less strict validation (where available)
+      -dpi xxx          target resolution in dots per inch (dpi) where xxx is a number
+      -s                for area tree XML, down to block areas only
+      -v                to show FOP version being used
+    
+      -o [password]     PDF file will be encrypted with option owner password
+      -u [password]     PDF file will be encrypted with option user password
+      -noprint          PDF file will be encrypted without printing permission
+      -nocopy           PDF file will be encrypted without copy content permission
+      -noedit           PDF file will be encrypted without edit content permission
+      -noannotations    PDF file will be encrypted without edit annotation permission
+      -pdfprofile prof  PDF file will be generated with the specified profile
+                        (Examples for prof: PDF/A-1b or PDF/X-3:2003)
+
+     [INPUT]  
+      infile            xsl:fo input file (the same as the next) 
+      -fo  infile       xsl:fo input file  
+      -xml infile       xml input file, must be used together with -xsl 
+      -atin infile      area tree input file 
+      -xsl stylesheet   xslt stylesheet 
  
-  -param name value <value> to use for parameter <name> in xslt stylesheet
-                    (repeat '-param name value' for each parameter)
+      -param name value <value> to use for parameter <name> in xslt stylesheet
+                        (repeat '-param name value' for each parameter)
  
- [OUTPUT] 
-  outfile           input will be rendered as PDF into outfile
-  -pdf outfile      input will be rendered as PDF (outfile req'd)
-  -pdfa1b outfile   input will be rendered as PDF/A-1b compliant PDF
-                    (outfile req'd, same as "-pdf outfile -pdfprofile PDF/A-1b")
-  -awt              input will be displayed on screen 
-  -rtf outfile      input will be rendered as RTF (outfile req'd)
-  -pcl outfile      input will be rendered as PCL (outfile req'd) 
-  -ps outfile       input will be rendered as PostScript (outfile req'd) 
-  -afp outfile      input will be rendered as AFP (outfile req'd)
-  -tiff outfile     input will be rendered as TIFF (outfile req'd)
-  -png outfile      input will be rendered as PNG (outfile req'd)
-  -txt outfile      input will be rendered as plain text (outfile req'd) 
-  -at [mime] out    representation of area tree as XML (outfile req'd) 
-                    specify optional mime output to allow AT to be converted
-                    to final format later
-  -print            input file will be rendered and sent to the printer 
-                    see options with "-print help" 
-  -out mime outfile input will be rendered using the given MIME type
-                    (outfile req'd) Example: "-out application/pdf D:\out.pdf"
-                    (Tip: "-out list" prints the list of supported MIME types)
-  -mif outfile      input will be rendered as MIF (FrameMaker) (outfile req'd)
-                    Experimental feature - requires additional fop-sandbox.jar.
-  -svg outfile      input will be rendered as an SVG slides file (outfile req'd) 
-                    Experimental feature - requires additional fop-sandbox.jar.
-
-  -foout outfile    input will only be XSL transformed. The intermediate 
-                    XSL-FO file is saved and no rendering is performed. 
-                    (Only available if you use -xml and -xsl parameters)
-
-
- [Examples]
-  Fop foo.fo foo.pdf 
-  Fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)
-  Fop -xml foo.xml -xsl foo.xsl -pdf foo.pdf
-  Fop -xml foo.xml -xsl foo.xsl -foout foo.fo
-  Fop foo.fo -mif foo.mif
-  Fop foo.fo -rtf foo.rtf
-  Fop foo.fo -print or Fop -print foo.fo 
-  Fop foo.fo -awt
+     [OUTPUT] 
+      outfile           input will be rendered as PDF into outfile
+      -pdf outfile      input will be rendered as PDF (outfile req'd)
+      -pdfa1b outfile   input will be rendered as PDF/A-1b compliant PDF
+                        (outfile req'd, same as "-pdf outfile -pdfprofile PDF/A-1b")
+      -awt              input will be displayed on screen 
+      -rtf outfile      input will be rendered as RTF (outfile req'd)
+      -pcl outfile      input will be rendered as PCL (outfile req'd) 
+      -ps outfile       input will be rendered as PostScript (outfile req'd) 
+      -afp outfile      input will be rendered as AFP (outfile req'd)
+      -tiff outfile     input will be rendered as TIFF (outfile req'd)
+      -png outfile      input will be rendered as PNG (outfile req'd)
+      -txt outfile      input will be rendered as plain text (outfile req'd) 
+      -at [mime] out    representation of area tree as XML (outfile req'd) 
+                        specify optional mime output to allow AT to be converted
+                        to final format later
+      -print            input file will be rendered and sent to the printer 
+                        see options with "-print help" 
+      -out mime outfile input will be rendered using the given MIME type
+                        (outfile req'd) Example: "-out application/pdf D:\out.pdf"
+                        (Tip: "-out list" prints the list of supported MIME types)
+      -mif outfile      input will be rendered as MIF (FrameMaker) (outfile req'd)
+                        Experimental feature - requires additional fop-sandbox.jar.
+      -svg outfile      input will be rendered as an SVG slides file (outfile req'd) 
+                        Experimental feature - requires additional fop-sandbox.jar.
+    
+      -foout outfile    input will only be XSL transformed. The intermediate 
+                        XSL-FO file is saved and no rendering is performed. 
+                        (Only available if you use -xml and -xsl parameters)
+
+
+     [Examples]
+      Fop foo.fo foo.pdf 
+      Fop -fo foo.fo -pdf foo.pdf (does the same as the previous line)
+      Fop -xml foo.xml -xsl foo.xsl -pdf foo.pdf
+      Fop -xml foo.xml -xsl foo.xsl -foout foo.fo
+      Fop foo.fo -mif foo.mif
+      Fop foo.fo -rtf foo.rtf
+      Fop foo.fo -print or Fop -print foo.fo 
+      Fop foo.fo -awt
 PDF encryption is only available if FOP was compiled with encryption support **and** if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the [Details](pdfencryption.html) .
 
 ### Writing your own script <a id="your-own-script"></a>

Modified: xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext?rev=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/servlets.mdtext Mon Dec  3 15:46:33 2012
@@ -22,38 +22,42 @@ The servlet is automatically built when 
 
 The source code for the servlet can be found under {fop-dir}/src/java/org/apache/fop/servlet/FopServlet.java.
 This example servlet should not be used on a public web server connected to the Internet as it does not contain any measures to prevent Denial-of-Service-Attacks. It is provided as an example and as a starting point for your own servlet.
-# Create your own Servlet <a id="servlet"></a>
+## Create your own Servlet <a id="servlet"></a>
 This section assumes you are familiar with [embedding FOP](embedding.html) .
-## A minimal Servlet <a id="minimal-servlet"></a>
+### A minimal Servlet <a id="minimal-servlet"></a>
 
 Here is a minimal code snippet to demonstrate the basics:
-private FopFactory fopFactory = FopFactory.newInstance();
-private TransformerFactory tFactory = TransformerFactory.newInstance();
+
+    private FopFactory fopFactory = FopFactory.newInstance();
+    private TransformerFactory tFactory = TransformerFactory.newInstance();
         
-public void doGet(HttpServletRequest request,
-                   HttpServletResponse response) throws ServletException {
-    try {
-        response.setContentType("application/pdf");
-        Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, response.getOutputStream());
-        Transformer transformer = tFactory.newTransformer();
-        Source src = new StreamSource("foo.fo");
-        Result res = new SAXResult(fop.getDefaultHandler());
-        transformer.transform(src, res);
-    } catch (Exception ex) {
-        throw new ServletException(ex);
+    public void doGet(HttpServletRequest request,
+                       HttpServletResponse response) throws ServletException {
+        try {
+            response.setContentType("application/pdf");
+            Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, response.getOutputStream());
+            Transformer transformer = tFactory.newTransformer();
+            Source src = new StreamSource("foo.fo");
+            Result res = new SAXResult(fop.getDefaultHandler());
+            transformer.transform(src, res);
+        } catch (Exception ex) {
+            throw new ServletException(ex);
+        }
     }
-}There are numerous problems with the code snippet above. Its purpose is only to demonstrate the basic concepts. See below for details.
-## Adding XSL tranformation (XSLT) <a id="xslt"></a>
+There are numerous problems with the code snippet above. Its purpose is only to demonstrate the basic concepts. See below for details.
+
+### Adding XSL tranformation (XSLT) <a id="xslt"></a>
 
 A common requirement is to transform an XML source to XSL-FO using an XSL transformation. It is recommended to use JAXP for this task. The following snippet shows the basic code:
-private FopFactory fopFactory = FopFactory.newInstance();
-private TransformerFactory tFactory = TransformerFactory.newInstance();
 
-public void init() throws ServletException {
-    //Optionally customize the FopFactory and TransformerFactory here
-}
+    private FopFactory fopFactory = FopFactory.newInstance();
+    private TransformerFactory tFactory = TransformerFactory.newInstance();
 
-[..]
+    public void init() throws ServletException {
+        //Optionally customize the FopFactory and TransformerFactory here
+    }
+    
+    [..]
 
     //Setup a buffer to obtain the content length
     ByteArrayOutputStream out = new ByteArrayOutputStream();
@@ -127,24 +131,24 @@ Further down, you can use the URIResolve
 
 Here are some example snippets:
 
-//Setting up the JAXP TransformerFactory
-this.transFactory = TransformerFactory.newInstance();
-this.transFactory.setURIResolver(this.uriResolver);
-
-[..]
-
-//Setting up the FOP factory
-this.fopFactory = FopFactory.newInstance();
-this.fopFactory.setURIResolver(this.uriResolver);
-
-[..]
-
-//The stylesheet for the JAXP Transfomer
-Source xsltSrc = this.uriResolver.resolve(
-    "servlet-context:/xslt/mystylesheet.xsl", null);
-Transformer transformer = this.transFactory.newTransformer(xsltSrc);
-transformer.setURIResolver(this.uriResolver);
-# Notes on Microsoft Internet Explorer <a id="ie"></a>
+    //Setting up the JAXP TransformerFactory
+    this.transFactory = TransformerFactory.newInstance();
+    this.transFactory.setURIResolver(this.uriResolver);
+    
+    [..]
+    
+    //Setting up the FOP factory
+    this.fopFactory = FopFactory.newInstance();
+    this.fopFactory.setURIResolver(this.uriResolver);
+    
+    [..]
+    
+    //The stylesheet for the JAXP Transfomer
+    Source xsltSrc = this.uriResolver.resolve(
+        "servlet-context:/xslt/mystylesheet.xsl", null);
+    Transformer transformer = this.transFactory.newTransformer(xsltSrc);
+    transformer.setURIResolver(this.uriResolver);
+## Notes on Microsoft Internet Explorer <a id="ie"></a>
 
 Some versions of Internet Explorer will not automatically show the PDF or call the servlet multiple times. These are well-known limitations of Internet Explorer and are not a problem of the servlet. However, Internet Explorer can still be used to download the PDF so that it can be viewed later. Here are some suggestions in this context:
 

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=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext Mon Dec  3 15:46:33 2012
@@ -14,21 +14,13 @@ Accessibility features are available onl
 There are 3 ways to enable accessibility:
 
 
-1.  **Command line:** The command line option -a turns on accessibility: `fop -a -fo mydocument.fo -pdf mydocument.pdf` 
-
-1.  **Embedding:**  `userAgent.setAccessibility(true);` 
-
-1.  **Optional setting in fop.xconf file:**  
-`
-          <fop version="1.0">
-              <accessibility>true</accessibility>
-              ...
-          </fop>
-          ` 
+1.  **Command line:** The command line option -a turns on accessibility:<br/>`fop -a -fo mydocument.fo -pdf mydocument.pdf`<br/>
+1.  **Embedding:**<br/>`userAgent.setAccessibility(true);`<br/>
+1.  **Optional setting in fop.xconf file:**<br/>`<fop version="1.0">`<br/>`<accessibility>true</accessibility>`<br/>`...`<br/>`</fop>`
 
 When accessibility is enabled, additional information relating to the logical structure of the document is added to the PDF. That information allows the PDF viewer (or a text-to-speech application) to retrieve the natural reading order of the document.
 The processing of the logical structure is memory-hungry. You may need to adjust the Java heap size in order to process larger files.
-# Changes to your XSL-FO input files <a id="source"></a>
+## Changes to your XSL-FO input files <a id="source"></a>
 
 Apache FOP cannot automatically generate accessible PDFs. Some of the work can only be performed by the content provider. Following are some changes that may be necessary to your XSL-FO content in order to generate really accessible documents:
 
@@ -48,12 +40,12 @@ The [PDF Reference](#PDFReference) defin
 FOP provides a default mapping of Formatting Objects to elements from that standard set. For example, `fo:page-sequence` is mapped to ‘Part’, `fo:block` is mapped to ‘P’, `fo:list-block` to ‘L’, etc.
 
 You may want to customize that mapping to improve the accuracy of the tagging or deal with particular FO constructs. For example, you may want to make use of the ‘H1’ to ‘H6’ tags to make the hierarchical structure of the document appear in the PDF. This is achieved by using the `role` XSL-FO property:
-...
 
+    ...
     <fo:block role="H1" font-weight="bold">I. A Level 1 Heading</fo:block>
     <fo:block>This is the first paragraph of the first section...</fo:block>
+    ...
 
-...
 If a non-standard structure type is specified, FOP will issue a warning and fall back to the default tag associated to the Formatting Object.
 
 ## Testing <a id="testing"></a>

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=1416565&r1=1416564&r2=1416565&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext Mon Dec  3 15:46:33 2012
@@ -11,26 +11,28 @@ The FOP Ant task will convert XSL-FO doc
 
 To call FOP tasks within Ant, first add a FOP task definition to your Ant build file. One method of defining the task is as follows:
 
-<property name="fop.home" value="....path to your FOP HOME directory..."/>
-
-<taskdef name="fop" 
-         classname="org.apache.fop.tools.anttasks.Fop">
-  <classpath>
-    <fileset dir="${fop.home}/lib">
-      <include name="*.jar"/>
-    </fileset>
-    <fileset dir="${fop.home}/build">
-      <include name="fop.jar"/>
-      <include name="fop-hyph.jar" />
-    </fileset>
-  </classpath>
-</taskdef>
+    <property name="fop.home" value="....path to your FOP HOME directory..."/>
+    
+    <taskdef name="fop" 
+             classname="org.apache.fop.tools.anttasks.Fop">
+      <classpath>
+        <fileset dir="${fop.home}/lib">
+          <include name="*.jar"/>
+        </fileset>
+        <fileset dir="${fop.home}/build">
+          <include name="fop.jar"/>
+          <include name="fop-hyph.jar" />
+        </fileset>
+      </classpath>
+    </taskdef>
     
 Then create FOP tasks within your Ant build file, using the FOP task parameters listed below.
 
 ## Parameters for FOP Ant task <a id="parameters"></a>
 
-<caption>Parameters specified as attributes</caption>| Attribute | Description | Required |
+<caption>Parameters specified as attributes</caption>
+
+| Attribute | Description | Required |
 |-----------|-------------|----------|
 | fofile | XSL-FO file to be rendered | Yes, if no fileset nested element is used |
 | xmlfile | XML input file | Yes, if no fofile is specified |
@@ -46,7 +48,7 @@ Then create FOP tasks within your Ant bu
 | 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/>
 
 <caption>Parameters specified as nested elements</caption>| Attribute | Description | Required |
 |-----------|-------------|----------|



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


Mime
View raw message