xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject svn commit: r1416347 [1/2] - in /xmlgraphics/site/trunk/content/fop: ./ 0.95/ 1.0/ 1.1/ dev/ dev/design/
Date Mon, 03 Dec 2012 04:58:51 GMT
Author: clay
Date: Mon Dec  3 04:58:47 2012
New Revision: 1416347

URL: http://svn.apache.org/viewvc?rev=1416347&view=rev
Log:
Fixing FOP code blocks.

Modified:
    xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/configuration.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/metadata.mdtext
    xmlgraphics/site/trunk/content/fop/0.95/output.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/configuration.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/metadata.mdtext
    xmlgraphics/site/trunk/content/fop/1.1/anttask.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/metadata.mdtext
    xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext
    xmlgraphics/site/trunk/content/fop/dev/design/embedding.mdtext
    xmlgraphics/site/trunk/content/fop/dev/doc.mdtext
    xmlgraphics/site/trunk/content/fop/dev/release.mdtext
    xmlgraphics/site/trunk/content/fop/dev/testing.mdtext
    xmlgraphics/site/trunk/content/fop/dev/tools.mdtext
    xmlgraphics/site/trunk/content/fop/fo.mdtext
    xmlgraphics/site/trunk/content/fop/fop-pdf-images.mdtext
    xmlgraphics/site/trunk/content/fop/gethelp.mdtext
    xmlgraphics/site/trunk/content/fop/index.mdtext
    xmlgraphics/site/trunk/content/fop/license.mdtext
    xmlgraphics/site/trunk/content/fop/maillist.mdtext
    xmlgraphics/site/trunk/content/fop/quickstartguide.mdtext
    xmlgraphics/site/trunk/content/fop/resources.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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/anttask.mdtext Mon Dec  3 04:58:47 2012
@@ -53,21 +53,21 @@ Then create FOP tasks within your Ant bu
 
 The following example converts a single XSL-FO file to a PDF document:
 
-<target name="generate-pdf" description="Generates a single PDF file">
-   <fop format="application/pdf" 
-        fofile="c:\working\foDirectory\foDocument.fo"
-        outfile="c:\working\pdfDirectory\pdfDocument.pdf" />
-</target>
+    <target name="generate-pdf" description="Generates a single PDF file">
+       <fop format="application/pdf" 
+            fofile="c:\working\foDirectory\foDocument.fo"
+            outfile="c:\working\pdfDirectory\pdfDocument.pdf" />
+    </target>
     
 This example converts all XSL-FO files within an entire directory to PostScript:
 
-<target name="generate-multiple-ps" 
-        description="Generates multiple PostScript files">
-   <fop format="application/postscript" 
-        outdir="${build.dir}" messagelevel="debug">
-        <fileset dir="${fo.examples.dir}">
-           <include name="*.fo"/>
-        </fileset>
-   </fop>
-</target>
+    <target name="generate-multiple-ps" 
+            description="Generates multiple PostScript files">
+       <fop format="application/postscript" 
+            outdir="${build.dir}" messagelevel="debug">
+            <fileset dir="${fo.examples.dir}">
+               <include name="*.fo"/>
+            </fileset>
+       </fop>
+    </target>
     
\ No newline at end of file

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/configuration.mdtext Mon Dec  3 04:58:47 2012
@@ -39,119 +39,127 @@ See [Setting the Configuration Programma
 
 This is an excerpt from the example configuration file coming with FOP:
 
-<fop version="1.0">
-
-  <!-- Strict user configuration -->
-  <strict-configuration>true</strict-configuration>
-
-  <!-- Strict FO validation -->
-  <strict-validation>true</strict-validation>
+    <fop version="1.0">
+    
+      <!-- Strict user configuration -->
+      <strict-configuration>true</strict-configuration>
+    
+      <!-- Strict FO validation -->
+      <strict-validation>true</strict-validation>
+    
+      <!-- Base URL for resolving relative URLs -->
+      <base>./</base>
+    
+      <!-- Font Base URL for resolving relative font URLs -->
+      <font-base>./</font-base>
+    
+      <!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi -->
+      <source-resolution>72</source-resolution>
+      <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi -->
+      <target-resolution>72</target-resolution>
+    
+      <!-- default page-height and page-width, in case
+           value is specified as auto -->
+      <default-page-settings height="11in" width="8.26in"/>
+      
+      <!-- etc. etc..... -->
+    </fop>
 
-  <!-- Base URL for resolving relative URLs -->
-  <base>./</base>
-
-  <!-- Font Base URL for resolving relative font URLs -->
-  <font-base>./</font-base>
-
-  <!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi -->
-  <source-resolution>72</source-resolution>
-  <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi -->
-  <target-resolution>72</target-resolution>
-
-  <!-- default page-height and page-width, in case
-       value is specified as auto -->
-  <default-page-settings height="11in" width="8.26in"/>
-  
-  <!-- etc. etc..... -->
-</fop>
 # 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.
 
 The configuration for the PDF Renderer could look like this:
 
-  <renderers>
-    <renderer mime="application/pdf">
-      <filterList>
-        <!-- provides compression using zlib flate (default is on) -->
-        <value>flate</value>
-      </filterList>
-      <fonts>
-        <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
-          <font-triplet name="Arial" style="normal" weight="normal"/>
-          <font-triplet name="ArialMT" style="normal" weight="normal"/>
-        </font>
-        <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
-          <font-triplet name="Arial" style="normal" weight="bold"/>
-          <font-triplet name="ArialMT" style="normal" weight="bold"/>
-        </font>
-      </fonts>
-    </renderer>
-    
-    <renderer mime="application/postscript">
-    <!-- etc. etc..... -->
+      <renderers>
+        <renderer mime="application/pdf">
+          <filterList>
+            <!-- provides compression using zlib flate (default is on) -->
+            <value>flate</value>
+          </filterList>
+          <fonts>
+            <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
+              <font-triplet name="Arial" style="normal" weight="normal"/>
+              <font-triplet name="ArialMT" style="normal" weight="normal"/>
+            </font>
+            <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
+              <font-triplet name="Arial" style="normal" weight="bold"/>
+              <font-triplet name="ArialMT" style="normal" weight="bold"/>
+            </font>
+          </fonts>
+        </renderer>
+        
+        <renderer mime="application/postscript">
+        <!-- etc. etc..... -->
+
 The details on the font configuration can be found on the separate [Fonts](fonts.html) page. Note especially the section entitled [Register Fonts with FOP](fonts.html#register) .
 
 ### Special Settings for the PDF Renderer <a id="pdf-renderer"></a>
 
 The configuration element for the PDF renderer contains two elements. One is for the font configuration (please follow the link above) and one is for the "filter list". The filter list controls how the individual objects in a PDF file are encoded. By default, all objects get "flate" encoded (i.e. simply compressed with the same algorithm that is also used in ZIP files). Most users don't need to change that setting. For debugging purposes, it may be desired not to compress the internal objects at all so the generated PDF commands can be read. In that case, you can simply use the following filter list. The second filter list (type="image") ensures that all images still get compressed but also ASCII-85 encoded so the produced PDF file is still easily readable in a text editor.
 
-    <renderer mime="application/pdf">
-      <filterList>
-        <value>null</value>
-      </filterList>
-      <filterList type="image">
-        <value>flate</value>
-        <value>ascii-85</value>
-      </filterList>
-      
-      <fonts....
-    </renderer>
+        <renderer mime="application/pdf">
+          <filterList>
+            <value>null</value>
+          </filterList>
+          <filterList type="image">
+            <value>flate</value>
+            <value>ascii-85</value>
+          </filterList>
+          
+          <fonts....
+        </renderer>
+
 Another (optional) setting specific to the PDF Renderer is an output color profile, an ICC color profile which indicates the target color space the PDF file is generated for. This setting is mainly used in conjunction with the [PDF/X](pdfx.html) feature. An example:
 
-    <renderer mime="application/pdf">
-      <filterList...
-      
-      <output-profile>C:\FOP\Color\EuropeISOCoatedFOGRA27.icc</output-profile>
-      
-      <fonts....
-      </renderer>
+        <renderer mime="application/pdf">
+          <filterList...
+          
+          <output-profile>C:\FOP\Color\EuropeISOCoatedFOGRA27.icc</output-profile>
+          
+          <fonts....
+          </renderer>
+
 Some people don't have high requirements on color fidelity but instead want the smallest PDF file sizes possible. In this case it's possible to disable the default sRGB color space which XSL-FO requires. This will cause RGB colors to be generated as device-specific RGB. Please note that this option is unavailable (and will cause an error) if you enable PDF/A or PDF/X functionality or if you specify an output profile. This setting will make the PDF about 4KB smaller. To disable the sRGB color space add the following setting:
 
-    <renderer mime="application/pdf">
-      <filterList...
-      
-      <disable-srgb-colorspace>true</disable-srgb-colorspace>
-      
-      <fonts....
-      </renderer>
+        <renderer mime="application/pdf">
+          <filterList...
+          
+          <disable-srgb-colorspace>true</disable-srgb-colorspace>
+          
+          <fonts....
+          </renderer>
+
 ## 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:
 
-    <renderer mime="application/postscript">
-      <auto-rotate-landscape>true</auto-rotate-landscape>
-      
-      <fonts>
-        <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
-          <font-triplet name="Arial" style="normal" weight="normal"/>
-          <font-triplet name="ArialMT" style="normal" weight="normal"/>
-        </font>
-        <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
-          <font-triplet name="Arial" style="normal" weight="bold"/>
-          <font-triplet name="ArialMT" style="normal" weight="bold"/>
-        </font>
-      </fonts>
-    </renderer>
+        <renderer mime="application/postscript">
+          <auto-rotate-landscape>true</auto-rotate-landscape>
+          
+          <fonts>
+            <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
+              <font-triplet name="Arial" style="normal" weight="normal"/>
+              <font-triplet name="ArialMT" style="normal" weight="normal"/>
+            </font>
+            <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
+              <font-triplet name="Arial" style="normal" weight="bold"/>
+              <font-triplet name="ArialMT" style="normal" weight="bold"/>
+            </font>
+          </fonts>
+        </renderer>
+
 ## 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.
 
 Additionally, there are certain settings that control how the renderer handles various elements.
-<renderer mime="application/vnd.hp-PCL">
-  <rendering>quality</rendering>
-  <text-rendering>bitmap</text-rendering>
-</renderer>
+
+    <renderer mime="application/vnd.hp-PCL">
+      <rendering>quality</rendering>
+      <text-rendering>bitmap</text-rendering>
+    </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.
@@ -165,10 +173,13 @@ Check the following possibilities:
 
 - The format of the configuration file has changed considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did you convert your file to the new format?
 
-- The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the `schema` element:<fop
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:noNamespaceSchemaLocation=
-"http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">
+- The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the `schema` element:
+
+	<fop
+		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+		xsi:noNamespaceSchemaLocation=
+		"http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">
+
 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.

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/extensions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/extensions.mdtext Mon Dec  3 04:58:47 2012
@@ -16,8 +16,10 @@ Please see the [SVG documentation](graph
 ### Namespace <a id="fox-namespace"></a>
 
 By convention, FO extensions in FOP use the "fox" namespace prefix. To use any of the FO extensions, add a namespace entry for `http://xmlgraphics.apache.org/fop/extensions` to the root element:
-<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
+
+    <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>
 
 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) .
@@ -25,9 +27,11 @@ In previous versions of Apache FOP there
 ### Anchors or Named Destinations <a id="named-destinations"></a>
 
 Use the fox:destination element to define "named destinations" inside a PDF document. These are useful as fragment identifiers, e.g. "http://server/document.pdf#anchor-name". fox:destination elements can be placed almost anywhere in the fo document, including a child of root, a block-level element, or an inline-level element. For the destination to actually work, it must correspond to an "id" attribute on some fo element within the document. In other words, the "id" attribute actually creates the "view" within the PDF document. The fox:destination simply gives that view an independent name.
-<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>
+
+    <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>
+
 ## Table Continuation Label <a id="table-continue-label"></a>
 
 This extension element hasn't been reimplemented for the redesigned code, yet.

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/fonts.mdtext Mon Dec  3 04:58:47 2012
@@ -52,17 +52,19 @@ Basic information about fonts can be fou
 
 If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). In the basic form, you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.
 
-<fonts>
-  <!-- register all the fonts found in a directory -->
-  <directory>C:\MyFonts1</directory>
-  
-  <!-- register all the fonts found in a directory
-       and all of its sub directories (use with care) -->
-  <directory recursive="true">C:\MyFonts2</directory>
-
-  <!-- automatically detect operating system installed fonts -->
-  <auto-detect/>  
-</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.
+    <fonts>
+      <!-- register all the fonts found in a directory -->
+      <directory>C:\MyFonts1</directory>
+      
+      <!-- register all the fonts found in a directory
+           and all of its sub directories (use with care) -->
+      <directory recursive="true">C:\MyFonts2</directory>
+    
+      <!-- automatically detect operating system installed fonts -->
+      <auto-detect/>  
+    </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>
 
 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.
@@ -118,23 +120,23 @@ java -cp build\fop.jar;lib\avalon-framew
 
 You must tell FOP how to find and use the font metrics files by registering them in the [FOP Configuration](configuration.html) . Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:
 
-<fonts>
-  <!-- register a particular font -->
-  <font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes"
-      embed-url="file:///C:/myfonts/FTL_____.pfb">
-     <font-triplet name="FrutigerLight" style="normal" weight="normal"/>
-  </font>
-  
-  <!-- register all the fonts found in a directory -->
-  <directory>C:\MyFonts1</directory>
-  
-  <!-- register all the fonts found in a directory
-       and all of its sub directories (use with care) -->
-  <directory recursive="true">C:\MyFonts2</directory>
-
-  <!-- automatically detect operating system installed fonts -->
-  <auto-detect/>  
-</fonts>
+    <fonts>
+      <!-- register a particular font -->
+      <font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes"
+          embed-url="file:///C:/myfonts/FTL_____.pfb">
+         <font-triplet name="FrutigerLight" style="normal" weight="normal"/>
+      </font>
+      
+      <!-- register all the fonts found in a directory -->
+      <directory>C:\MyFonts1</directory>
+      
+      <!-- register all the fonts found in a directory
+           and all of its sub directories (use with care) -->
+      <directory recursive="true">C:\MyFonts2</directory>
+    
+      <!-- automatically detect operating system installed fonts -->
+      <auto-detect/>  
+    </fonts>
 
 - URLs are used to access the font metric and font files. Relative URLs are resolved relative to the font-base property (or base) if available. See [FOP: Configuration](configuration.html) for more information.
 

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/metadata.mdtext Mon Dec  3 04:58:47 2012
@@ -14,28 +14,30 @@ As noted above, there's no officially re
 Document-level metadata can be specified in the `fo:declarations` element. XMP specification recommends to use `x:xmpmeta` , `rdf:RDF` , and `rdf:Description` elements as shown in example below. Both `x:xmpmeta` and `rdf:RDF` elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).
 
 ### Example <a id="xmp-example"></a>
-[..]
-</fo:layout-master-set>
-<fo:declarations>
-  <x:xmpmeta xmlns:x="adobe:ns:meta/">
-    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
-      <rdf:Description rdf:about=""
-          xmlns:dc="http://purl.org/dc/elements/1.1/">
-        <!-- Dublin Core properties go here -->
-        <dc:title>Document title</dc:title>
-        <dc:creator>Document author</dc:creator>
-        <dc:description>Document subject</dc:description>
-      </rdf:Description>
-      <rdf:Description rdf:about=""
-          xmlns:xmp="http://ns.adobe.com/xap/1.0/">
-        <!-- XMP properties go here -->
-        <xmp:CreatorTool>Tool used to make the PDF</xmp:CreatorTool>
-      </rdf:Description>
-    </rdf:RDF>
-  </x:xmpmeta>
-</fo:declarations>
-<fo:page-sequence ...
-[..] `fo:declarations`  **must** be declared after `fo:layout-master-set` and before the first `page-sequence` .
+
+	[..]
+	</fo:layout-master-set>
+	<fo:declarations>
+	  <x:xmpmeta xmlns:x="adobe:ns:meta/">
+		<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+		  <rdf:Description rdf:about=""
+			  xmlns:dc="http://purl.org/dc/elements/1.1/">
+			<!-- Dublin Core properties go here -->
+			<dc:title>Document title</dc:title>
+			<dc:creator>Document author</dc:creator>
+			<dc:description>Document subject</dc:description>
+		  </rdf:Description>
+		  <rdf:Description rdf:about=""
+			  xmlns:xmp="http://ns.adobe.com/xap/1.0/">
+			<!-- XMP properties go here -->
+			<xmp:CreatorTool>Tool used to make the PDF</xmp:CreatorTool>
+		  </rdf:Description>
+		</rdf:RDF>
+	  </x:xmpmeta>
+	</fo:declarations>
+	<fo: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>
 
 Currently, XMP support is only available for PDF output.

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/0.95/output.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/0.95/output.mdtext Mon Dec  3 04:58:47 2012
@@ -250,6 +250,7 @@ There are 3 font configuration variants 
 1. FOP built-in Base14 fonts
 
 A typical raster font configuration looks like:
+
       <!-- This is an example of mapping actual IBM raster fonts / code pages to a FOP font -->
         <font>
         <!-- The afp-font element defines the IBM code page, the matching Java encoding and the
@@ -276,7 +277,9 @@ A typical raster font configuration look
         <font-triplet name="Times-Roman" style="normal" weight="normal"/>
         <font-triplet name="TimesNewRoman" style="normal" weight="normal"/>
       </font>
+
 An outline font configuration is simpler as the individual font size entries are not required. However, the characterset definition is now required within the afp-font element.
+
       <font>
           <afp-font type="outline" codepage="T1V10500" encoding="Cp500" characterset="CZH200  "
              path="fonts/ibm" />
@@ -286,6 +289,7 @@ An outline font configuration is simpler
       </font>
 
 Experimentation has shown that the font metrics for the FOP built-in Base14 fonts are actually very similar to some of the IBM outline and raster fonts. In cases were the IBM font files are not available the path attribute in the afp-font element can be replaced by a base14-font attribute giving the name of the matching Base14 font. In this case the AFP Renderer will take the font metrics from the built-in font.
+
       <!-- The following are examples of defining outline fonts based on FOP built-in
            font metrics for the Adobe Base14 fonts -->
       <!-- sans-serif fonts based on Helvetica -->
@@ -326,7 +330,7 @@ Experimentation has shown that the font 
           <font-triplet name="Times" style="normal" weight="normal"/>
           <font-triplet name="Times-Roman" style="normal" weight="normal"/>
       </font>
-
+    
       <!-- The following are examples of defining raster fonts based on FOP built-in
            font metrics for the Adobe Base14 fonts -->
       <!-- monospaced fonts based on Courier -->
@@ -354,11 +358,13 @@ Experimentation has shown that the font 
         <font-triplet name="monospace" style="normal" weight="bold"/>
         <font-triplet name="Courier" style="normal" weight="bold"/>
       </font>
+
 ### 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>
 
 By default the AFP Renderer converts all images to 8 bit grey level. This can be overridden by the <images> configuration element. Example:
@@ -492,20 +498,24 @@ Currently, two output formats are suppor
 ### Configuration <a id="bitmap-configuration"></a>
 
 The TIFF and PNG renderer configuration currently allows the following settings:
-<renderer mime="image/png">
-  <transparent-page-background>true</transparent-page-background>
-  <fonts><!-- described elsewhere --></fonts>
-</renderer>
+
+    <renderer mime="image/png">
+      <transparent-page-background>true</transparent-page-background>
+      <fonts><!-- described elsewhere --></fonts>
+    </renderer>
+
 The default value for the "transparent-page-background" setting is "false" which paints an opaque, white background for the whole image. If you set this to true, no such background will be painted and you will get a transparent image if an alpha channel is available in the output format.
 
 ### TIFF-specific Configuration <a id="tiff-configuration"></a>
 
 In addition to the above values the TIFF renderer configuration allows some additional settings:
-<renderer mime="image/tiff">
-  <transparent-page-background>true</transparent-page-background>
-  <compression>CCITT T.6</compression>
-  <fonts><!-- described elsewhere --></fonts>
-</renderer>
+
+    <renderer mime="image/tiff">
+      <transparent-page-background>true</transparent-page-background>
+      <compression>CCITT T.6</compression>
+      <fonts><!-- described elsewhere --></fonts>
+    </renderer>
+
 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:
 
 

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/accessibility.mdtext Mon Dec  3 04:58:47 2012
@@ -18,7 +18,8 @@ There are 3 ways to enable accessibility
 
 1.  **Embedding:**  `userAgent.setAccessibility(true);` 
 
-1.  **Optional setting in fop.xconf file:**  `
+1.  **Optional setting in fop.xconf file:**  
+`
           <fop version="1.0">
               <accessibility>true</accessibility>
               ...
@@ -48,8 +49,10 @@ FOP provides a default mapping of Format
 
 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>
+
+    <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.
 

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/anttask.mdtext Mon Dec  3 04:58:47 2012
@@ -56,42 +56,42 @@ Then create FOP tasks within your Ant bu
 
 The following example converts a single XSL-FO file to a PDF document:
 
-<target name="generate-pdf" description="Generates a single PDF file">
-   <fop format="application/pdf" 
-        fofile="c:\working\foDirectory\foDocument.fo"
-        outfile="c:\working\pdfDirectory\pdfDocument.pdf" />
-</target>
+    <target name="generate-pdf" description="Generates a single PDF file">
+       <fop format="application/pdf" 
+            fofile="c:\working\foDirectory\foDocument.fo"
+            outfile="c:\working\pdfDirectory\pdfDocument.pdf" />
+    </target>
     
 This example converts all XSL-FO files within an entire directory to PostScript:
 
-<target name="generate-multiple-ps" 
-        description="Generates multiple PostScript files">
-   <fop format="application/postscript" 
-        outdir="${build.dir}" messagelevel="debug">
-        <fileset dir="${fo.examples.dir}">
-           <include name="*.fo"/>
-        </fileset>
-   </fop>
-</target>
+    <target name="generate-multiple-ps" 
+            description="Generates multiple PostScript files">
+       <fop format="application/postscript" 
+            outdir="${build.dir}" messagelevel="debug">
+            <fileset dir="${fo.examples.dir}">
+               <include name="*.fo"/>
+            </fileset>
+       </fop>
+    </target>
     
 The following example transforms and converts a single XML and XSLT file to an AFP document:
 
-<target name="generate-afp-from-transform" description="Generates a single AFP file from an XSLT stylesheet">
-   <fop format="application/x-afp" 
-        xmlfile="c:\working\foDirectory\Document.xml"
-        xsltfile="c:\working\foDirectory\Document.xslt"
-        outfile="c:\working\afpDirectory\Document.afp" />
-</target>
+    <target name="generate-afp-from-transform" description="Generates a single AFP file from an XSLT stylesheet">
+       <fop format="application/x-afp" 
+            xmlfile="c:\working\foDirectory\Document.xml"
+            xsltfile="c:\working\foDirectory\Document.xslt"
+            outfile="c:\working\afpDirectory\Document.afp" />
+    </target>
     
 This example transforms and converts all XML files within an entire directory to PostScript:
 
-<target name="generate-multiple-ps-from-transform" description="Generates multiple PostScript files using an XSLT stylesheet">
-   <fop format="application/postscript" 
-        xsltfile="c:\working\foDirectory\Document.xslt"
-        outdir="${build.dir}" messagelevel="debug">
-        <fileset dir="${test.dir}">
-           <include name="*.xml"/>
-        </fileset>
-   </fop>
-</target>
+    <target name="generate-multiple-ps-from-transform" description="Generates multiple PostScript files using an XSLT stylesheet">
+       <fop format="application/postscript" 
+            xsltfile="c:\working\foDirectory\Document.xslt"
+            outdir="${build.dir}" messagelevel="debug">
+            <fileset dir="${test.dir}">
+               <include name="*.xml"/>
+            </fileset>
+       </fop>
+    </target>
     
\ No newline at end of file

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/configuration.mdtext Mon Dec  3 04:58:47 2012
@@ -40,44 +40,47 @@ See [Setting the Configuration Programma
 
 This is an excerpt from the example configuration file coming with FOP:
 
-<fop version="1.0">
-
-  <!-- Strict user configuration -->
-  <strict-configuration>true</strict-configuration>
-
-  <!-- Strict FO validation -->
-  <strict-validation>true</strict-validation>
+    <fop version="1.0">
+    
+      <!-- Strict user configuration -->
+      <strict-configuration>true</strict-configuration>
+    
+      <!-- Strict FO validation -->
+      <strict-validation>true</strict-validation>
+    
+      <!-- Base URL for resolving relative URLs -->
+      <base>./</base>
+    
+      <!-- Font Base URL for resolving relative font URLs -->
+      <font-base>./</font-base>
+    
+      <!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi -->
+      <source-resolution>72</source-resolution>
+      <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi -->
+      <target-resolution>72</target-resolution>
+    
+      <!-- default page-height and page-width, in case
+           value is specified as auto -->
+      <default-page-settings height="11in" width="8.26in"/>
+      
+      <!-- etc. etc..... -->
+    </fop>
 
-  <!-- Base URL for resolving relative URLs -->
-  <base>./</base>
-
-  <!-- Font Base URL for resolving relative font URLs -->
-  <font-base>./</font-base>
-
-  <!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi -->
-  <source-resolution>72</source-resolution>
-  <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi -->
-  <target-resolution>72</target-resolution>
-
-  <!-- default page-height and page-width, in case
-       value is specified as auto -->
-  <default-page-settings height="11in" width="8.26in"/>
-  
-  <!-- etc. etc..... -->
-</fop>
 # Image Loading Customization <a id="image-loading"></a>
 
 Apache FOP uses the image loading framework from [Apache XML Graphics Commons](http://xmlgraphics.apache.org/commons/) to load images using various plug-ins. Every image loader plug-in has a hard-coded usage penalty that influences which solution is chosen if there are multiple possibilities to load an image. Sometimes, though, these penalties need to be tweaked and this can be done in the FOP configuration. An example:
-<fop version="1.0">
-  [..]
-  <image-loading>
-    <penalty value="10000"
-      class="org.apache.xmlgraphics.image.loader.impl.ImageLoaderRawCCITTFax"/>
-    <penalty value="INFINITE"
-      class="org.apache.xmlgraphics.image.loader.impl.ImageLoaderInternalTIFF"/>
-  </image-loading>
-  <renderers....
-</fop>
+
+    <fop version="1.0">
+      [..]
+      <image-loading>
+        <penalty value="10000"
+          class="org.apache.xmlgraphics.image.loader.impl.ImageLoaderRawCCITTFax"/>
+        <penalty value="INFINITE"
+          class="org.apache.xmlgraphics.image.loader.impl.ImageLoaderInternalTIFF"/>
+      </image-loading>
+      <renderers....
+    </fop>
+
 The first penalty element increases the penalty for the raw CCITT loader. This practically forces the decoding of CCITT compressed TIFF images except if there are no TIFF codecs available.
 
 The second penalty element sets an "infinite" penalty for the TIFF loader using the internal TIFF codec. This practically disables that plug-in as it will never be chosen as a possible solution.
@@ -90,26 +93,27 @@ Each Renderer has its own configuration 
 
 The configuration for the PDF Renderer could look like this:
 
-  <renderers>
-    <renderer mime="application/pdf">
-      <filterList>
-        <!-- provides compression using zlib flate (default is on) -->
-        <value>flate</value>
-      </filterList>
-      <fonts>
-        <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
-          <font-triplet name="Arial" style="normal" weight="normal"/>
-          <font-triplet name="ArialMT" style="normal" weight="normal"/>
-        </font>
-        <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
-          <font-triplet name="Arial" style="normal" weight="bold"/>
-          <font-triplet name="ArialMT" style="normal" weight="bold"/>
-        </font>
-      </fonts>
-    </renderer>
-    
-    <renderer mime="application/postscript">
-    <!-- etc. etc..... -->
+      <renderers>
+        <renderer mime="application/pdf">
+          <filterList>
+            <!-- provides compression using zlib flate (default is on) -->
+            <value>flate</value>
+          </filterList>
+          <fonts>
+            <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
+              <font-triplet name="Arial" style="normal" weight="normal"/>
+              <font-triplet name="ArialMT" style="normal" weight="normal"/>
+            </font>
+            <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
+              <font-triplet name="Arial" style="normal" weight="bold"/>
+              <font-triplet name="ArialMT" style="normal" weight="bold"/>
+            </font>
+          </fonts>
+        </renderer>
+        
+        <renderer mime="application/postscript">
+        <!-- etc. etc..... -->
+
 The details on the font configuration can be found on the separate [Fonts](fonts.html) page. Note especially the section entitled [Register Fonts with FOP](fonts.html#register) .
 
 ### Special Settings for the PDF Renderer <a id="pdf-renderer"></a>
@@ -127,6 +131,7 @@ The configuration element for the PDF re
       
       <fonts....
     </renderer>
+
 Another (optional) setting specific to the PDF Renderer is an output color profile, an ICC color profile which indicates the target color space the PDF file is generated for. This setting is mainly used in conjunction with the [PDF/X](pdfx.html) feature. An example:
 
     <renderer mime="application/pdf">
@@ -136,6 +141,7 @@ Another (optional) setting specific to t
       
       <fonts....
       </renderer>
+
 Some people don't have high requirements on color fidelity but instead want the smallest PDF file sizes possible. In this case it's possible to disable the default sRGB color space which XSL-FO requires. This will cause RGB colors to be generated as device-specific RGB. Please note that this option is unavailable (and will cause an error) if you enable PDF/A or PDF/X functionality or if you specify an output profile. This setting will make the PDF about 4KB smaller. To disable the sRGB color space add the following setting:
 
     <renderer mime="application/pdf">
@@ -145,6 +151,7 @@ Some people don't have high requirements
       
       <fonts....
       </renderer>
+
 FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited. For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.
 
     <renderer mime="application/pdf">
@@ -157,6 +164,7 @@ FOP supports encryption of PDF output, t
          <noannotations/>
       </encryption-params>
     </renderer>
+
 ## 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:
@@ -175,15 +183,18 @@ Besides the normal font configuration (t
         </font>
       </fonts>
     </renderer>
+
 ## 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.
 
 Additionally, there are certain settings that control how the renderer handles various elements.
-<renderer mime="application/vnd.hp-PCL">
-  <rendering>quality</rendering>
-  <text-rendering>bitmap</text-rendering>
-</renderer>
+
+    <renderer mime="application/vnd.hp-PCL">
+      <rendering>quality</rendering>
+      <text-rendering>bitmap</text-rendering>
+    </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.
@@ -193,13 +204,15 @@ The default value for the "text-renderin
 
 
 Additionally, there are certain settings that control how the renderer handles various elements.
-<renderer mime="application/x-afp">
-  <images mode="b+w" bits-per-pixel="8" native="true"/>
-  <renderer-resolution>240</renderer-resolution>
-  
-  <!-- a default external resource group file -->
-  <resource-group-file>resources.afp</resource-group-file>
-</renderer>
+
+    <renderer mime="application/x-afp">
+      <images mode="b+w" bits-per-pixel="8" native="true"/>
+      <renderer-resolution>240</renderer-resolution>
+      
+      <!-- a default external resource group file -->
+      <resource-group-file>resources.afp</resource-group-file>
+    </renderer>
+
 The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.
 
 The default value for the "renderer-resolution" is 240 dpi.
@@ -215,10 +228,13 @@ Check the following possibilities:
 
 - The format of the configuration file has changed considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did you convert your file to the new format?
 
-- The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the `schema` element:<fop
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:noNamespaceSchemaLocation=
-"http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">
+- The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the `schema` element:
+
+    <fop
+        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+        xsi:noNamespaceSchemaLocation=
+        "http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">
+
 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.

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/extensions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/extensions.mdtext Mon Dec  3 04:58:47 2012
@@ -16,8 +16,10 @@ Please see the [SVG documentation](graph
 ### Namespace <a id="fox-namespace"></a>
 
 By convention, FO extensions in FOP use the "fox" namespace prefix. To use any of the FO extensions, add a namespace entry for `http://xmlgraphics.apache.org/fop/extensions` to the root element:
-<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
+
+    <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>
 
 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) .
@@ -25,9 +27,10 @@ In previous versions of Apache FOP there
 ### Anchors or Named Destinations <a id="named-destinations"></a>
 
 Use the fox:destination element to define "named destinations" inside a PDF document. These are useful as fragment identifiers, e.g. "http://server/document.pdf#anchor-name". fox:destination elements can be placed almost anywhere in the fo document, including a child of root, a block-level element, or an inline-level element. For the destination to actually work, it must correspond to an "id" attribute on some fo element within the document. In other words, the "id" attribute actually creates the "view" within the PDF document. The fox:destination simply gives that view an independent name.
-<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>
+    <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>
+
 ## Table Continuation Label <a id="table-continue-label"></a>
 
 This extension element hasn't been reimplemented for the redesigned code, yet.

Modified: xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext?rev=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/fonts.mdtext Mon Dec  3 04:58:47 2012
@@ -66,20 +66,22 @@ Basic information about fonts can be fou
 
 If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). In the basic form, you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.
 
-<renderers>
-   <renderer mime="application/pdf">
-      <fonts>
-         <!-- register all the fonts found in a directory -->
-         <directory>C:\MyFonts1</directory>
-  
-         <!-- register all the fonts found in a directory and all of its sub directories (use with care) -->
-         <directory recursive="true">C:\MyFonts2</directory>
-
-         <!-- automatically detect operating system installed fonts -->
-         <auto-detect/>  
-      </fonts>
-   </renderer>
-</renderers>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.
+    <renderers>
+       <renderer mime="application/pdf">
+          <fonts>
+             <!-- register all the fonts found in a directory -->
+             <directory>C:\MyFonts1</directory>
+      
+             <!-- register all the fonts found in a directory and all of its sub directories (use with care) -->
+             <directory recursive="true">C:\MyFonts2</directory>
+    
+             <!-- automatically detect operating system installed fonts -->
+             <auto-detect/>  
+          </fonts>
+       </renderer>
+    </renderers>
+
+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>
 
 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.
@@ -132,34 +134,36 @@ java -cp build\fop.jar;lib\avalon-framew
           org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho"
           msmincho.ttc msminch.xml
 Alternatively, the individual sub-fonts of a TrueType Collections can be selected using the "sub-font" attribute on the "font" element. That means that generating an XML font metrics file for TrueType collections is not necessary anymore. Example:
-<font embed-url="gulim.ttc" sub-font="GulimChe">
-  <font-triplet name="GulimChe" style="normal" weight="normal"/>
-</font>
+
+    <font embed-url="gulim.ttc" sub-font="GulimChe">
+      <font-triplet name="GulimChe" style="normal" weight="normal"/>
+    </font>
+
 ## Register Fonts with FOP <a id="register"></a>
 
 You must tell FOP how to find and use the font metrics files by registering them in the [FOP Configuration](configuration.html) . Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:
 
-<renderers>
-   <renderer mime="application/pdf">
-      <fonts>
-         <!-- register a particular font -->
-         <font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes"
-           embed-url="file:///C:/myfonts/FTL_____.pfb"
-           encoding-mode="single-byte">
-            <font-triplet name="FrutigerLight" style="normal" weight="normal"/>
-         </font>
-  
-         <!-- register all the fonts found in a directory -->
-         <directory>C:\MyFonts1</directory>
-  
-         <!-- register all the fonts found in a directory and all of its sub directories (use with care) -->
-         <directory recursive="true">C:\MyFonts2</directory>
-
-         <!-- automatically detect operating system installed fonts -->
-         <auto-detect/>  
-      </fonts>
-   </renderer>
-</renderers>
+    <renderers>
+       <renderer mime="application/pdf">
+          <fonts>
+             <!-- register a particular font -->
+             <font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes"
+               embed-url="file:///C:/myfonts/FTL_____.pfb"
+               encoding-mode="single-byte">
+                <font-triplet name="FrutigerLight" style="normal" weight="normal"/>
+             </font>
+      
+             <!-- register all the fonts found in a directory -->
+             <directory>C:\MyFonts1</directory>
+      
+             <!-- register all the fonts found in a directory and all of its sub directories (use with care) -->
+             <directory recursive="true">C:\MyFonts2</directory>
+    
+             <!-- automatically detect operating system installed fonts -->
+             <auto-detect/>  
+          </fonts>
+       </renderer>
+    </renderers>
 
 - URLs are used to access the font metric and font files. Relative URLs are resolved relative to the font-base property (or base) if available. See [FOP: Configuration](configuration.html) for more information.
 
@@ -214,14 +218,15 @@ There are two different ways how you can
 
 1. For automatically configured fonts there's a different mechanism to specify which fonts should be referenced rather than embedded. This is done in the "referenced-fonts" element in the configuration. Here's an example:
 
-<fop version="1.0">
-   <fonts>
-      <referenced-fonts>
-        <match font-family="Helvetica"/>
-        <match font-family="DejaVu.*"/>
-      </referenced-fonts>
-   </fonts>
-</fop>
+    <fop version="1.0">
+       <fonts>
+          <referenced-fonts>
+            <match font-family="Helvetica"/>
+            <match font-family="DejaVu.*"/>
+          </referenced-fonts>
+       </fonts>
+    </fop>
+
 At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the [package](http://java.sun.com/j2se/1.4/docs/api/java/util/regex/package-summary.html) . So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify `font-family=".*"` .
 
 The `referenced-fonts` element can be placed either inside the general `fonts` element (right under the root) or in the `fonts` element under the renderer configuration. In the first case, matches apply to all renderers. In the second case, matches only apply to the renderer where the element was specified. Both cases can be used at the same time.
@@ -250,20 +255,21 @@ When a <substitutions/> section is defin
 
 For example you could make all FO font-family references to 'Arial' with weights between 700 and 900 reference the normal 'Arial Black' font.
 
-<fop version="1.0">
-   <fonts>
-      <substitutions>
-         <substitution>
-            <from font-family="Arial" font-weight="700..900"/>
-            <to font-family="Arial Black"/>
-         </substitution>
-         <substitution>
-            <from font-family="FrutigerLight"/>
-            <to font-family="Times" font-weight="bold" font-style="italic"/>
-         </substitution>
-      </substitutions>
-   </fonts>
-</fop>
+    <fop version="1.0">
+       <fonts>
+          <substitutions>
+             <substitution>
+                <from font-family="Arial" font-weight="700..900"/>
+                <to font-family="Arial Black"/>
+             </substitution>
+             <substitution>
+                <from font-family="FrutigerLight"/>
+                <to font-family="Times" font-weight="bold" font-style="italic"/>
+             </substitution>
+          </substitutions>
+       </fonts>
+    </fop>
+
 # Font Selection Strategies <a id="selection"></a>
 
 There are two font selection strategies: character-by-character or auto. The default is auto.

Modified: xmlgraphics/site/trunk/content/fop/1.0/metadata.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.0/metadata.mdtext?rev=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.0/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.0/metadata.mdtext Mon Dec  3 04:58:47 2012
@@ -14,28 +14,31 @@ As noted above, there's no officially re
 Document-level metadata can be specified in the `fo:declarations` element. XMP specification recommends to use `x:xmpmeta` , `rdf:RDF` , and `rdf:Description` elements as shown in example below. Both `x:xmpmeta` and `rdf:RDF` elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).
 
 ### Example <a id="xmp-example"></a>
-[..]
-</fo:layout-master-set>
-<fo:declarations>
-  <x:xmpmeta xmlns:x="adobe:ns:meta/">
-    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
-      <rdf:Description rdf:about=""
-          xmlns:dc="http://purl.org/dc/elements/1.1/">
-        <!-- Dublin Core properties go here -->
-        <dc:title>Document title</dc:title>
-        <dc:creator>Document author</dc:creator>
-        <dc:description>Document subject</dc:description>
-      </rdf:Description>
-      <rdf:Description rdf:about=""
-          xmlns:xmp="http://ns.adobe.com/xap/1.0/">
-        <!-- XMP properties go here -->
-        <xmp:CreatorTool>Tool used to make the PDF</xmp:CreatorTool>
-      </rdf:Description>
-    </rdf:RDF>
-  </x:xmpmeta>
-</fo:declarations>
-<fo:page-sequence ...
+
+	[..]
+	</fo:layout-master-set>
+	    :declarations>
+	  <x:xmpmeta xmlns:x="adobe:ns:meta/">
+		<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+		  <rdf:Description rdf:about=""
+			  xmlns:dc="http://purl.org/dc/elements/1.1/">
+			<!-- Dublin Core properties go here -->
+			<dc:title>Document title</dc:title>
+			<dc:creator>Document author</dc:creator>
+			<dc:description>Document subject</dc:description>
+		  </rdf:Description>
+		  <rdf:Description rdf:about=""
+			  xmlns:xmp="http://ns.adobe.com/xap/1.0/">
+			<!-- XMP properties go here -->
+			<xmp:CreatorTool>Tool used to make the PDF</xmp:CreatorTool>
+		  </rdf:Description>
+		</rdf:RDF>
+	  </x:xmpmeta>
+	</fo:declarations>
+	    :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>
 
 Currently, XMP support is only available for PDF output.

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/anttask.mdtext Mon Dec  3 04:58:47 2012
@@ -56,42 +56,42 @@ Then create FOP tasks within your Ant bu
 
 The following example converts a single XSL-FO file to a PDF document:
 
-<target name="generate-pdf" description="Generates a single PDF file">
-   <fop format="application/pdf" 
-        fofile="c:\working\foDirectory\foDocument.fo"
-        outfile="c:\working\pdfDirectory\pdfDocument.pdf" />
-</target>
+    <target name="generate-pdf" description="Generates a single PDF file">
+       <fop format="application/pdf" 
+            fofile="c:\working\foDirectory\foDocument.fo"
+            outfile="c:\working\pdfDirectory\pdfDocument.pdf" />
+    </target>
     
 This example converts all XSL-FO files within an entire directory to PostScript:
 
-<target name="generate-multiple-ps" 
-        description="Generates multiple PostScript files">
-   <fop format="application/postscript" 
-        outdir="${build.dir}" messagelevel="debug">
-        <fileset dir="${fo.examples.dir}">
-           <include name="*.fo"/>
-        </fileset>
-   </fop>
-</target>
+    <target name="generate-multiple-ps" 
+            description="Generates multiple PostScript files">
+       <fop format="application/postscript" 
+            outdir="${build.dir}" messagelevel="debug">
+            <fileset dir="${fo.examples.dir}">
+               <include name="*.fo"/>
+            </fileset>
+       </fop>
+    </target>
     
 The following example transforms and converts a single XML and XSLT file to an AFP document:
 
-<target name="generate-afp-from-transform" description="Generates a single AFP file from an XSLT stylesheet">
-   <fop format="application/x-afp" 
-        xmlfile="c:\working\foDirectory\Document.xml"
-        xsltfile="c:\working\foDirectory\Document.xslt"
-        outfile="c:\working\afpDirectory\Document.afp" />
-</target>
+    <target name="generate-afp-from-transform" description="Generates a single AFP file from an XSLT stylesheet">
+       <fop format="application/x-afp" 
+            xmlfile="c:\working\foDirectory\Document.xml"
+            xsltfile="c:\working\foDirectory\Document.xslt"
+            outfile="c:\working\afpDirectory\Document.afp" />
+    </target>
     
 This example transforms and converts all XML files within an entire directory to PostScript:
 
-<target name="generate-multiple-ps-from-transform" description="Generates multiple PostScript files using an XSLT stylesheet">
-   <fop format="application/postscript" 
-        xsltfile="c:\working\foDirectory\Document.xslt"
-        outdir="${build.dir}" messagelevel="debug">
-        <fileset dir="${test.dir}">
-           <include name="*.xml"/>
-        </fileset>
-   </fop>
-</target>
+    <target name="generate-multiple-ps-from-transform" description="Generates multiple PostScript files using an XSLT stylesheet">
+       <fop format="application/postscript" 
+            xsltfile="c:\working\foDirectory\Document.xslt"
+            outdir="${build.dir}" messagelevel="debug">
+            <fileset dir="${test.dir}">
+               <include name="*.xml"/>
+            </fileset>
+       </fop>
+    </target>
     
\ No newline at end of file

Modified: xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext?rev=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/complexscripts.mdtext Mon Dec  3 04:58:47 2012
@@ -26,10 +26,10 @@ Complex script features are enabled by d
 1.  **Embedding:**  `userAgent.setComplexScriptFeaturesEnabled(false);` 
 
 1.  **Optional setting in fop.xconf file:**  `
-<fop version="1.0">
-  <complex-scripts disabled="true"/>
-  ...
-</fop>
+    <fop version="1.0">
+      <complex-scripts disabled="true"/>
+      ...
+    </fop>
           ` 
 
 When complex scripts features are enabled, additional information related to bidirectional level resolution, the association between characters and glyphs, and glyph position adjustments are added to the internal, parsed representation of the XSL-FO tree and its corresponding formatted area tree. This additional information will somewhat increase the memory requirements for processing documents that use these features.

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=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/configuration.mdtext Mon Dec  3 04:58:47 2012
@@ -42,47 +42,50 @@ See [Setting the Configuration Programma
 
 This is an excerpt from the example configuration file coming with FOP:
 
-<fop version="1.0">
-
-  <!-- Strict user configuration -->
-  <strict-configuration>true</strict-configuration>
-
-  <!-- Strict FO validation -->
-  <strict-validation>true</strict-validation>
+    <fop version="1.0">
+    
+      <!-- Strict user configuration -->
+      <strict-configuration>true</strict-configuration>
+    
+      <!-- Strict FO validation -->
+      <strict-validation>true</strict-validation>
+    
+      <!-- Base URL for resolving relative URLs -->
+      <base>./</base>
+    
+      <!-- Font Base URL for resolving relative font URLs -->
+      <font-base>./</font-base>
+    
+      <!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi -->
+      <source-resolution>72</source-resolution>
+      <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi -->
+      <target-resolution>72</target-resolution>
+    
+      <!-- default page-height and page-width, in case
+           value is specified as auto -->
+      <default-page-settings height="11in" width="8.26in"/>
+    
+      <!-- Use file name nl_Bel instead of the default nl_BE -->
+      <hyphenation-pattern lang="nl" country="BE">nl_Bel</hyphenation-pattern>
+      
+      <!-- etc. etc..... -->
+    </fop>
 
-  <!-- Base URL for resolving relative URLs -->
-  <base>./</base>
-
-  <!-- Font Base URL for resolving relative font URLs -->
-  <font-base>./</font-base>
-
-  <!-- Source resolution in dpi (dots/pixels per inch) for determining the size of pixels in SVG and bitmap images, default: 72dpi -->
-  <source-resolution>72</source-resolution>
-  <!-- Target resolution in dpi (dots/pixels per inch) for specifying the target resolution for generated bitmaps, default: 72dpi -->
-  <target-resolution>72</target-resolution>
-
-  <!-- default page-height and page-width, in case
-       value is specified as auto -->
-  <default-page-settings height="11in" width="8.26in"/>
-
-  <!-- Use file name nl_Bel instead of the default nl_BE -->
-  <hyphenation-pattern lang="nl" country="BE">nl_Bel</hyphenation-pattern>
-  
-  <!-- etc. etc..... -->
-</fop>
 # Image Loading Customization <a id="image-loading"></a>
 
 Apache FOP uses the image loading framework from [Apache XML Graphics Commons](http://xmlgraphics.apache.org/commons/) to load images using various plug-ins. Every image loader plug-in has a hard-coded usage penalty that influences which solution is chosen if there are multiple possibilities to load an image. Sometimes, though, these penalties need to be tweaked and this can be done in the FOP configuration. An example:
-<fop version="1.0">
-  [..]
-  <image-loading>
-    <penalty value="10000"
-      class="org.apache.xmlgraphics.image.loader.impl.ImageLoaderRawCCITTFax"/>
-    <penalty value="INFINITE"
-      class="org.apache.xmlgraphics.image.loader.impl.ImageLoaderInternalTIFF"/>
-  </image-loading>
-  <renderers....
-</fop>
+
+    <fop version="1.0">
+      [..]
+      <image-loading>
+        <penalty value="10000"
+          class="org.apache.xmlgraphics.image.loader.impl.ImageLoaderRawCCITTFax"/>
+        <penalty value="INFINITE"
+          class="org.apache.xmlgraphics.image.loader.impl.ImageLoaderInternalTIFF"/>
+      </image-loading>
+      <renderers....
+    </fop>
+
 The first penalty element increases the penalty for the raw CCITT loader. This practically forces the decoding of CCITT compressed TIFF images except if there are no TIFF codecs available.
 
 The second penalty element sets an "infinite" penalty for the TIFF loader using the internal TIFF codec. This practically disables that plug-in as it will never be chosen as a possible solution.
@@ -95,26 +98,27 @@ Each Renderer has its own configuration 
 
 The configuration for the PDF Renderer could look like this:
 
-  <renderers>
-    <renderer mime="application/pdf">
-      <filterList>
-        <!-- provides compression using zlib flate (default is on) -->
-        <value>flate</value>
-      </filterList>
-      <fonts>
-        <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
-          <font-triplet name="Arial" style="normal" weight="normal"/>
-          <font-triplet name="ArialMT" style="normal" weight="normal"/>
-        </font>
-        <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
-          <font-triplet name="Arial" style="normal" weight="bold"/>
-          <font-triplet name="ArialMT" style="normal" weight="bold"/>
-        </font>
-      </fonts>
-    </renderer>
-    
-    <renderer mime="application/postscript">
-    <!-- etc. etc..... -->
+      <renderers>
+        <renderer mime="application/pdf">
+          <filterList>
+            <!-- provides compression using zlib flate (default is on) -->
+            <value>flate</value>
+          </filterList>
+          <fonts>
+            <font metrics-url="arial.xml" kerning="yes" embed-url="arial.ttf">
+              <font-triplet name="Arial" style="normal" weight="normal"/>
+              <font-triplet name="ArialMT" style="normal" weight="normal"/>
+            </font>
+            <font metrics-url="arialb.xml" kerning="yes" embed-url="arialb.ttf">
+              <font-triplet name="Arial" style="normal" weight="bold"/>
+              <font-triplet name="ArialMT" style="normal" weight="bold"/>
+            </font>
+          </fonts>
+        </renderer>
+        
+        <renderer mime="application/postscript">
+        <!-- etc. etc..... -->
+
 The details on the font configuration can be found on the separate [Fonts](fonts.html) page. Note especially the section entitled [Register Fonts with FOP](fonts.html#register) .
 
 ### Special Settings for the PDF Renderer <a id="pdf-renderer"></a>
@@ -132,6 +136,7 @@ The configuration element for the PDF re
       
       <fonts....
     </renderer>
+
 Another (optional) setting specific to the PDF Renderer is an output color profile, an ICC color profile which indicates the target color space the PDF file is generated for. This setting is mainly used in conjunction with the [PDF/X](pdfx.html) feature. An example:
 
     <renderer mime="application/pdf">
@@ -141,6 +146,7 @@ Another (optional) setting specific to t
       
       <fonts....
       </renderer>
+
 Some people don't have high requirements on color fidelity but instead want the smallest PDF file sizes possible. In this case it's possible to disable the default sRGB color space which XSL-FO requires. This will cause RGB colors to be generated as device-specific RGB. Please note that this option is unavailable (and will cause an error) if you enable PDF/A or PDF/X functionality or if you specify an output profile. This setting will make the PDF about 4KB smaller. To disable the sRGB color space add the following setting:
 
     <renderer mime="application/pdf">
@@ -149,7 +155,8 @@ Some people don't have high requirements
       <disable-srgb-colorspace>true</disable-srgb-colorspace>
       
       <fonts....
-      </renderer>
+    </renderer>
+
 FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited. For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.
 
     <renderer mime="application/pdf">
@@ -167,6 +174,7 @@ FOP supports encryption of PDF output, t
          <noprinthq/>
       </encryption-params>
     </renderer>
+
 By default FOP produces PDF files of version 1.4, but this can be changed in order to benefit from features that appeared in newer versions of PDF. At the moment, only a few features from PDF 1.5 have been implemented, but the configuration element will accept any value between 1.4 and 1.7. This is the value that will appear in the PDF header, although only features up to 1.5 will actually be used.
       <renderer mime="application/pdf">
         
@@ -196,10 +204,12 @@ Besides the normal font configuration (t
 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.
 
 Additionally, there are certain settings that control how the renderer handles various elements.
-<renderer mime="application/x-pcl">
-  <rendering>quality</rendering>
-  <text-rendering>bitmap</text-rendering>
-</renderer>
+
+    <renderer mime="application/x-pcl">
+      <rendering>quality</rendering>
+      <text-rendering>bitmap</text-rendering>
+    </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.
@@ -209,14 +219,16 @@ The default value for the "text-renderin
 
 
 Additionally, there are certain settings that control how the renderer handles various elements.
-<renderer mime="application/x-afp">
-  <images mode="b+w" bits-per-pixel="8" native="true"/>
-  <renderer-resolution>240</renderer-resolution>
-  <line-width-correction>2.5</line-width-correction>
-  
-  <!-- a default external resource group file -->
-  <resource-group-file>resources.afp</resource-group-file>
-</renderer>
+
+    <renderer mime="application/x-afp">
+      <images mode="b+w" bits-per-pixel="8" native="true"/>
+      <renderer-resolution>240</renderer-resolution>
+      <line-width-correction>2.5</line-width-correction>
+      
+      <!-- a default external resource group file -->
+      <resource-group-file>resources.afp</resource-group-file>
+    </renderer>
+
 The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.
 
 The default value for the "renderer-resolution" is 240 dpi.
@@ -234,10 +246,13 @@ Check the following possibilities:
 
 - The format of the configuration file has changed considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did you convert your file to the new format?
 
-- The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the `schema` element:<fop
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-xsi:noNamespaceSchemaLocation=
-"http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">
+- The FOP distribution contains a schema for configuration files, at src/foschema/fop-configuration.xsd. Did you validate your configuration file against it? Add the following schema location to the `schema` element:
+
+    <fop
+        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+        xsi:noNamespaceSchemaLocation=
+        "http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/foschema/fop-configuration.xsd?view=co">
+
 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.

Modified: xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext?rev=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/1.1/metadata.mdtext Mon Dec  3 04:58:47 2012
@@ -14,28 +14,31 @@ As noted above, there's no officially re
 Document-level metadata can be specified in the `fo:declarations` element. XMP specification recommends to use `x:xmpmeta` , `rdf:RDF` , and `rdf:Description` elements as shown in example below. Both `x:xmpmeta` and `rdf:RDF` elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).
 
 ### Example <a id="xmp-example"></a>
-[..]
-</fo:layout-master-set>
-<fo:declarations>
-  <x:xmpmeta xmlns:x="adobe:ns:meta/">
-    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
-      <rdf:Description rdf:about=""
-          xmlns:dc="http://purl.org/dc/elements/1.1/">
-        <!-- Dublin Core properties go here -->
-        <dc:title>Document title</dc:title>
-        <dc:creator>Document author</dc:creator>
-        <dc:description>Document subject</dc:description>
-      </rdf:Description>
-      <rdf:Description rdf:about=""
-          xmlns:xmp="http://ns.adobe.com/xap/1.0/">
-        <!-- XMP properties go here -->
-        <xmp:CreatorTool>Tool used to make the PDF</xmp:CreatorTool>
-      </rdf:Description>
-    </rdf:RDF>
-  </x:xmpmeta>
-</fo:declarations>
-<fo:page-sequence ...
+
+    [..]
+    </fo:layout-master-set>
+    <fo:declarations>
+      <x:xmpmeta xmlns:x="adobe:ns:meta/">
+        <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+          <rdf:Description rdf:about=""
+              xmlns:dc="http://purl.org/dc/elements/1.1/">
+            <!-- Dublin Core properties go here -->
+            <dc:title>Document title</dc:title>
+            <dc:creator>Document author</dc:creator>
+            <dc:description>Document subject</dc:description>
+          </rdf:Description>
+          <rdf:Description rdf:about=""
+              xmlns:xmp="http://ns.adobe.com/xap/1.0/">
+            <!-- XMP properties go here -->
+            <xmp:CreatorTool>Tool used to make the PDF</xmp:CreatorTool>
+          </rdf:Description>
+        </rdf:RDF>
+      </x:xmpmeta>
+    </fo:declarations>
+    <fo: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>
 
 Currently, XMP support is only available for PDF output.

Modified: xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext?rev=1416347&r1=1416346&r2=1416347&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/dev/conventions.mdtext Mon Dec  3 04:58:47 2012
@@ -39,9 +39,9 @@ For developers that dislike these conven
 
 ### Checkstyle <a id="java-checkstyle"></a>
 
-The java syntax checker "<jump href="http://checkstyle.sourceforge.net">Checkstyle</jump>" 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<jump href="http://checkstyle.sourceforge.net">Checkstyle web site</jump>, 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.
+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.
 
 Checkstyle is probably most useful when integrated into your IDE. See the Checkstyle web site for more information about IDE plugins.
 
@@ -64,7 +64,7 @@ The following general principles are a d
 
 - Try to catch exceptions as much as possible and rethrow higher level exceptions (meaning hiding the low level detailed and putting a message that is more related to the function of your code).
 
-- It is important not to lose the stack trace which contains important information. Use chained exception for that. Avalon Framework provides<jump href="http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/CascadingException.htm">CascadingException</jump>(and similar) for this. Exception class names and stack traces must be treated like gold. Do whatever is required so that this information is not lost. Printing error messages to System.err or System.out is useless in a server-side environment where this info is usually lost.
+- It is important not to lose the stack trace which contains important information. Use chained exception for that. Avalon Framework provides <a href="http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/CascadingException.htm">CascadingException</a> (and similar) for this. Exception class names and stack traces must be treated like gold. Do whatever is required so that this information is not lost. Printing error messages to System.err or System.out is useless in a server-side environment where this info is usually lost.
 
 - Always log the exception at the higher level (i.e. where it is handled and not rethrown).
 
@@ -75,14 +75,14 @@ The following general principles are a d
 
 - [book on code style] Code Complete by Steve McConnell.
 
-- [code formatting software]<jump href="http://jrefactory.sourceforge.net">JRefactory</jump>.
+- [code formatting software] <a href="http://jrefactory.sourceforge.net">JRefactory</a> .
 
 ### Related Links <a id="java-links"></a>
 
 
-- <jump href="http://xmlgraphics.apache.org/repo.html">Apache XML Graphics Code Repositories</jump>
+-  <a href="http://xmlgraphics.apache.org/repo.html">Apache XML Graphics Code Repositories</a> 
 
-- <jump href="http://jakarta.apache.org/site/faqs.html#Coding%20Conventions%20and%20Standards">Jakarta Code Conventions and Standards</jump>(see Coding Conventions and Standards section)
+-  <a href="http://jakarta.apache.org/site/faqs.html#Coding%20Conventions%20and%20Standards">Jakarta Code Conventions and Standards</a> (see Coding Conventions and Standards section)
 
 ## XML <a id="xml"></a>
 



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


Mime
View raw message