xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r840806 [12/19] - in /websites/staging/xmlgraphics/trunk/content: ./ batik/ batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Wed, 05 Dec 2012 08:23:58 GMT
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/intermediate.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/intermediate.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/intermediate.html Wed Dec  5 08:23:47 2012
@@ -344,7 +344,7 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="apachewzxhzdk2-fop-intermediate-format">Apache&trade; FOP: Intermediate Format</h1>
 <p>Please note that the intermediate formats described here are <strong>advanced features</strong> and can be ignored by most users of Apache&trade; FOP.</p>
 <h2 id="introduction-wzxhzdk4wzxhzdk5">Introduction <a id="introduction"></a></h2>
-<p>Apache&trade; FOP now provides two different so-called intermediate formats. The first one (let's call it the area tree XML format) is basically a 1:1 XML representation of FOP's area tree as generated by the layout engine. The area tree is conceptually defined in the <a href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting">XSL-FO specification in chapter 1.1.2</a> . Even though the area tree is mentioned in the XSL-FO specification, this part is not standardized. Therefore, the area tree XML format is a FOP-proprietary XML file format. The area tree XML can be generated through the area tree XML Renderer (the XMLRenderer).</p>
+<p>Apache&trade; FOP now provides two different so-called intermediate formats. The first one (let's call it the area tree XML format) is basically a 1:1 XML representation of FOP's area tree as generated by the layout engine. The area tree is conceptually defined in the <a href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting">XSL-FO specification in chapter 1.1.2</a>. Even though the area tree is mentioned in the XSL-FO specification, this part is not standardized. Therefore, the area tree XML format is a FOP-proprietary XML file format. The area tree XML can be generated through the area tree XML Renderer (the XMLRenderer).</p>
 <p>The second intermediate format (which we shall name exactly like this: the intermediate format) is a recent addition which tries to meet a slightly different set of goals. It is highly optimized for speed.</p>
 <p>The intermediate format can be used to generate intermediate documents that are modified before they are finally rendered to their ultimate output format. Modifications include adjusting and changing trait values, adding or modifying area objects, inserting prefabricated pages, overlays, imposition (n-up, rotation, scaling etc.). Multiple IF files can be combined to a single output file.</p>
 <h2 id="which-intermediate-format-to-choose-wzxhzdk7wzxhzdk8">Which Intermediate Format to choose? <a id="which-if"></a></h2>
@@ -379,7 +379,7 @@ $(document).ready(function () {
 <p>Recommended for use cases where documents are formatted concurrently and later concatenated to a single print job.</p>
 </li>
 </ul>
-<p>More technical information about the two formats can be found on the <a href="http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml/NewDesign">FOP Wiki</a> .</p>
+<p>More technical information about the two formats can be found on the <a href="http://wiki.apache.org/xmlgraphics-fop/AreaTreeIntermediateXml/NewDesign">FOP Wiki</a>.</p>
 <h2 id="architectural-overview-wzxhzdk13wzxhzdk14">Architectural Overview <a id="architecture"></a></h2>
 <p><img alt="Diagram with an architectural overview over the intermediate formats" src="images/if-architecture-overview.png" /></p>
 <h2 id="usage-of-the-area-tree-xml-format-at-xml-wzxhzdk15wzxhzdk16">Usage of the Area Tree XML format (AT XML) <a id="usage"></a></h2>
@@ -477,7 +477,7 @@ The area tree XML format is sensitive to
 <p>There is an XML Schema (located under <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/intermediate-format-ng/">src/documentation/intermediate-format-ng</a> ) that helps you verify that your modified content is correct.</p>
 <p>For certain output formats there's a caveat: Formats like AFP and PCL do not support arbitrary transformations on the IF's "viewport" and "g" elements. Possible are only rotations in 90 degree steps and translations.</p>
 <h3 id="advanced-use-wzxhzdk29wzxhzdk30">Advanced Use <a id="advanced-if"></a></h3>
-<p>The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. So rather than just passing in a StreamResult to IFSerializer's setResult() method, you can also use a SAXResult or a DOMResult. And as you've already seen , the IFParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to start the parsing process (see <code>getContentHandler()</code> ).</p></div>
+<p>The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. So rather than just passing in a StreamResult to IFSerializer's setResult() method, you can also use a SAXResult or a DOMResult. And as you've already seen, the IFParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to start the parsing process (see <code>getContentHandler()</code> ).</p></div>
       </div>
       
       <div class="clear"></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/knownissues_overview.html Wed Dec  5 08:23:47 2012
@@ -347,16 +347,16 @@ $(document).ready(function () {
 <p>For additional information on known issues in Apache&trade; FOP, please have a look at the following pages, too:</p>
 <ul>
 <li>
-<p><a href="../bugs.html">the bug list in Bugzilla</a> </p>
+<p><a href="../bugs.html">the bug list in Bugzilla</a></p>
 </li>
 <li>
-<p><a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks">the task list in the Wiki</a> </p>
+<p><a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks">the task list in the Wiki</a></p>
 </li>
 </ul>
 <p>Apache&trade; FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.</p>
 <h3 id="fo-tree-wzxhzdk5wzxhzdk6">FO Tree <a id="FO+Tree"></a></h3>
 <p>This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.</p>
-<p><strong>demo-test-failure.fo</strong> (demo test failure):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </p>
+<p><strong>demo-test-failure.fo</strong> (demo test failure):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em></p>
 <p><strong>from-table-column_marker.fo</strong> (Markers and core function evaluation):<br></br>The code currently evaluates this function according to the column in which the marker appears in the source document, rather than the column it is retrieved in.</p>
 <h3 id="layout-engine-wzxhzdk11wzxhzdk12">Layout Engine <a id="Layout+Engine"></a></h3>
 <p>This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.</p>
@@ -376,9 +376,9 @@ $(document).ready(function () {
 <p><strong>inline-container_border_padding.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed.</p>
 <p><strong>inline_letter-spacing.xml</strong> (inline letter-spacing):<br></br>Letter-spacing may not work as expected within fo:inline.</p>
 <p><strong>inline_word-spacing.xml</strong> (inline word-spacing):<br></br>Word-spacing may not work as expected within fo:inline.</p>
-<p><strong>inline_word-spacing_text-align_justify.xml</strong> (inline word-spacing text-align justify):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </p>
+<p><strong>inline_word-spacing_text-align_justify.xml</strong> (inline word-spacing text-align justify):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em></p>
 <p><strong>leader-alignment.xml</strong> (leader-alignment NYI):<br></br>Leader-alignment is not yet implemented.</p>
-<p><strong>leader_leader-pattern_use-content_bug.xml</strong> (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: <a href="http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html">http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html</a> </p>
+<p><strong>leader_leader-pattern_use-content_bug.xml</strong> (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: <a href="http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html">http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html</a></p>
 <p><strong>page-breaking_4.xml</strong> (Page breaking doesn't deal with IPD changes):<br></br>Page breaking currently doesn't support changing available IPD between pages of a single page-sequence. Element list generation has to be reset to redetermine line breaks in this case.</p>
 <p><strong>page-breaking_6.xml</strong> (Overflow handing is incomplete):<br></br>Line breaking is not 100% correct when there's too little space. Overflows are not detected and warned.</p>
 <p><strong>page-height_indefinite_simple.xml</strong> (Indefinite page height handling is imcomplete):<br></br>A RuntimeException is thrown for a page of indefinite height. Lots of warnings.</p>
@@ -395,13 +395,13 @@ $(document).ready(function () {
 <p><strong>block-container_reference-orientation_bug36391.xml</strong> (Block Container Reference Orientation Bug):<br></br>An assert is failing</p>
 <p><strong>simple-page-master_writing-mode_rl_region-body_writing-mode-lr.xml</strong> (Writing mode problems):<br></br>Test erroneously depends upon incorrect implementation of writing-mode trait derivation on fo:region-*.</p>
 <h3 id="other-known-issues-wzxhzdk83wzxhzdk84">Other known issues <a id="Other+known+issues"></a></h3>
-<p>This section lists some other issues that post-date the release of FOP 1.0. For known issues that pre-date FOP 1.0, see <a href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=2010-07-20&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2001-01-01&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">older bugs that remain open</a> . For all open issues that post-date FOP 1.0, see <a href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=Now&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2010-07-20&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">newer bugs that remain open</a> .</p>
+<p>This section lists some other issues that post-date the release of FOP 1.0. For known issues that pre-date FOP 1.0, see <a href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=2010-07-20&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2001-01-01&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">older bugs that remain open</a>. For all open issues that post-date FOP 1.0, see <a href="http://issues.apache.org/bugzilla/buglist.cgi?chfieldto=Now&amp;chfield=%5BBug%20creation%5D&amp;query_format=advanced&amp;chfieldfrom=2010-07-20&amp;bug_status=NEW&amp;bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;product=Fop">newer bugs that remain open</a>.</p>
 <ul>
 <li>
-<p>Support for Unicode characters outside of the Base Multilingual Plane (BMP), i.e., characters whose code points are greater than 65535, is not yet implemented. See <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51843">bug 51843</a> .</p>
+<p>Support for Unicode characters outside of the Base Multilingual Plane (BMP), i.e., characters whose code points are greater than 65535, is not yet implemented. See <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51843">bug 51843</a>.</p>
 </li>
 <li>
-<p>The writing-mode property does not produce the expected behavior when specified on <code>fo:simple-page-master</code> or <code>fo:region-*</code> elements. See <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53276">bug 53276</a> .</p>
+<p>The writing-mode property does not produce the expected behavior when specified on <code>fo:simple-page-master</code> or <code>fo:region-*</code> elements. See <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53276">bug 53276</a>.</p>
 </li>
 <li>
 <p>Support for Devanagari and other Indic scripts is not yet complete.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/metadata.html Wed Dec  5 08:23:47 2012
@@ -343,10 +343,10 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.1/">1.1</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk1-fop-metadata">Apache&trade; FOP: Metadata</h1>
 <h2 id="overview-wzxhzdk2wzxhzdk3">Overview <a id="overview"></a></h2>
-<p>Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP (eXtensible Metadata Platform, specified by Adobe)</a> . PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document and image formats. Given its flexibility it makes sense to make use this approach in the XSL-FO context. Unfortunately, unlike SVG which also refers to XMP, XSL-FO doesn't recommend a preferred way of specifying document and object metadata. Therefore, there's no portable way to represent metadata in XSL-FO documents. Each implementation does it differently.</p>
+<p>Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP (eXtensible Metadata Platform, specified by Adobe)</a>. PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document and image formats. Given its flexibility it makes sense to make use this approach in the XSL-FO context. Unfortunately, unlike SVG which also refers to XMP, XSL-FO doesn't recommend a preferred way of specifying document and object metadata. Therefore, there's no portable way to represent metadata in XSL-FO documents. Each implementation does it differently.</p>
 <h2 id="embedding-xmp-in-an-xsl-fo-document-wzxhzdk4wzxhzdk5">Embedding XMP in an XSL-FO document <a id="xmp-in-fo"></a></h2>
 <p>As noted above, there's no officially recommended way to embed metadata in XSL-FO. Apache&trade; FOP supports embedding XMP in XSL-FO. Currently, only support for document-level metadata is implemented. Object-level metadata will be implemented when there's interest.</p>
-<p>Document-level metadata can be specified in the <code>fo:declarations</code> element. XMP specification recommends to use <code>x:xmpmeta</code> , <code>rdf:RDF</code> , and <code>rdf:Description</code> elements as shown in example below. Both <code>x:xmpmeta</code> and <code>rdf:RDF</code> elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).</p>
+<p>Document-level metadata can be specified in the <code>fo:declarations</code> element. XMP specification recommends to use <code>x:xmpmeta</code>, <code>rdf:RDF</code>, and <code>rdf:Description</code> elements as shown in example below. Both <code>x:xmpmeta</code> and <code>rdf:RDF</code> elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).</p>
 <h3 id="example-wzxhzdk7wzxhzdk8">Example <a id="xmp-example"></a></h3>
 <div class="codehilite"><pre><span class="k">[..]</span>
 <span class="err">&lt;/fo:layout-master-set&gt;</span>
@@ -378,7 +378,7 @@ $(document).ready(function () {
 <p>Currently, XMP support is only available for PDF output.</p>
 <p>Originally, you could set some metadata information through FOP's FOUserAgent by using its set*() methods (like setTitle(String) or setAuthor(String). These values are directly used to set value in the PDF Info object. Since PDF 1.4, adding metadata as an XMP document to a PDF is possible. That means that there are now two mechanisms in PDF that hold metadata.</p>
 <p>Apache FOP now synchronizes the Info and the Metadata object in PDF, i.e. when you set the title and the author through the FOUserAgent, the two values will end up in the (old) Info object and in the new Metadata object as XMP content. If instead of FOUserAgent, you embed XMP metadata in the XSL-FO document (as shown above), the XMP metadata will be used as-is in the PDF Metadata object and some values from the XMP metadata will be copied to the Info object to maintain backwards-compatibility for PDF readers that don't support XMP metadata.</p>
-<p>The mapping between the Info and the Metadata object used by Apache FOP comes from the <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920">PDF/A-1 specification</a> . For convenience, here's the mapping table:</p>
+<p>The mapping between the Info and the Metadata object used by Apache FOP comes from the <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920">PDF/A-1 specification</a>. For convenience, here's the mapping table:</p>
 <table>
 <thead>
 <tr>
@@ -447,7 +447,7 @@ $(document).ready(function () {
 <td>Internal</td>
 </tr>
 <tr>
-<td>"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 <code>dc:subject</code> in the initial publication of PDF/A-1 (ISO 19005-1). In the <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613">Technical Corrigendum 1</a> this was changed to map to <code>dc:description["x-default"]</code> .</td>
+<td>"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 <code>dc:subject</code> in the initial publication of PDF/A-1 (ISO 19005-1). In the <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613">Technical Corrigendum 1</a> this was changed to map to <code>dc:description["x-default"]</code>.</td>
 <td></td>
 <td></td>
 <td></td>
@@ -489,16 +489,16 @@ $(document).ready(function () {
 <h2 id="links-wzxhzdk13wzxhzdk14">Links <a id="links"></a></h2>
 <ul>
 <li>
-<p><a href="http://www.adobe.com/products/xmp/">Adobe's Extensible Metadata Platform (XMP) website</a> </p>
+<p><a href="http://www.adobe.com/products/xmp/">Adobe's Extensible Metadata Platform (XMP) website</a></p>
 </li>
 <li>
-<p><a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">Adobe XMP Specification</a> </p>
+<p><a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">Adobe XMP Specification</a></p>
 </li>
 <li>
-<p><a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">Adobe XMP Specification</a> </p>
+<p><a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">Adobe XMP Specification</a></p>
 </li>
 <li>
-<p><a href="http://dublincore.org/">http://dublincore.org/</a> </p>
+<p><a href="http://dublincore.org/">http://dublincore.org/</a></p>
 </li>
 </ul></div>
       </div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html Wed Dec  5 08:23:47 2012
@@ -348,7 +348,7 @@ $(document).ready(function () {
 <h3 id="fonts-wzxhzdk52wzxhzdk53">Fonts <a id="general-fonts"></a></h3>
 <p>Most FOP renderers use a FOP-specific system for font registration. However, the Java2D/AWT and print renderers use the Java AWT package, which gets its font information from the operating system registration. This can result in several differences, including actually using different fonts, and having different font metrics for the same font. The net effect is that the layout of a given FO document can be quite different between renderers that do not use the same font information.</p>
 <p>Theoretically, there's some potential to make the output of the PDF/PS renderers match the output of the Java2D-based renderers. If FOP used the font metrics from its own font subsystem but still used Java2D for text painting in the Java2D-based renderers, this could probably be achieved. However, this approach hasn't been implemented, yet.</p>
-<p>With a work-around, it is possible to match the PDF/PS output in a Java2D-based renderer pretty closely. The clue is to use the <a href="intermediate.html">intermediate format</a> . The trick is to layout the document using FOP's own font subsystem but then render the document using Java2D. Here are the necessary steps (using the command-line):</p>
+<p>With a work-around, it is possible to match the PDF/PS output in a Java2D-based renderer pretty closely. The clue is to use the <a href="intermediate.html">intermediate format</a>. The trick is to layout the document using FOP's own font subsystem but then render the document using Java2D. Here are the necessary steps (using the command-line):</p>
 <ol>
 <li>
 <p>Produce an IF file: <code>fop -fo myfile.fo -at application/pdf myfile.at.xml</code> <br></br>Specifying "application/pdf" for the "-at" parameter causes FOP to use FOP's own font subsystem (which is used by the PDF renderer). Note that no PDF file is created in this step.</p>
@@ -370,7 +370,7 @@ $(document).ready(function () {
 </li>
 </ol>
 <h3 id="output-to-a-printer-or-other-device-wzxhzdk54wzxhzdk55">Output to a Printer or Other Device <a id="general-direct-output"></a></h3>
-<p>The most obvious way to print your document is to use the FOP <a href="#print">print renderer</a> , which uses the Java2D API (AWT). However, you can also send output from the Postscript renderer directly to a Postscript device, or output from the PCL renderer directly to a PCL device.</p>
+<p>The most obvious way to print your document is to use the FOP <a href="#print">print renderer</a>, which uses the Java2D API (AWT). However, you can also send output from the Postscript renderer directly to a Postscript device, or output from the PCL renderer directly to a PCL device.</p>
 <p>Here are Windows command-line examples for Postscript and PCL:
 fop ... -ps \computername\printerfop ... -pcl \computername\printer
 Here is some Java code to accomplish the task in UNIX:
@@ -379,14 +379,14 @@ out = proc.getOutputStream();
 Set the output MIME type to "application/x-pcl" (MimeConstants.MIME_PCL) and it happily sends the PCL to the UNIX printer queue.</p>
 <h2 id="pdf-wzxhzdk56wzxhzdk57">PDF <a id="pdf"></a></h2>
 <p>PDF is the best supported output format. It is also the most accurate with text and layout. This creates a PDF document that is streamed out as each page is rendered. This means that the internal page index information is stored near the end of the document. The PDF version supported is 1.4. PDF versions are forwards/backwards compatible.</p>
-<p>Note that FOP does not currently support PDF/A-1a. Support for <a href="accessibility.html">Tagged PDF</a> , <a href="pdfa.html">PDF/A-1b</a> and <a href="pdfx.html">PDF/X</a> has recently been added, however.</p>
+<p>Note that FOP does not currently support PDF/A-1a. Support for <a href="accessibility.html">Tagged PDF</a>, <a href="pdfa.html">PDF/A-1b</a> and <a href="pdfx.html">PDF/X</a> has recently been added, however.</p>
 <h3 id="fonts-wzxhzdk58wzxhzdk59">Fonts <a id="pdf-fonts"></a></h3>
 <p>PDF has a set of fonts that are always available to all PDF viewers; to quote from the PDF Specification: <em>"PDF prescribes a set of 14 standard fonts that can be used without prior definition. These include four faces each of three Latin text typefaces (Courier, Helvetica, and Times), as well as two symbolic fonts (Symbol and ITC Zapf Dingbats). These fonts, or suitable substitute fonts with the same metrics, are guaranteed to be available in all PDF viewer applications."</em></p>
 <h3 id="post-processing-wzxhzdk60wzxhzdk61">Post-processing <a id="pdf-postprocess"></a></h3>
 <p>FOP does not currently support several desirable PDF features: watermarks and signatures. One workaround is to use Adobe Acrobat (the full version, not the Reader) to process the file manually or with scripting that it supports.</p>
-<p>Another popular post-processing tool is <a href="http://www.lowagie.com/iText">iText</a> , which has tools for adding security features, document properties, watermarks, and many other features to PDF files.
+<p>Another popular post-processing tool is <a href="http://www.lowagie.com/iText">iText</a>, 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 <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37589">Jens Stavnstrup tells us</a> 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 <a href="pdfencryption.html">PDF encryption</a> . However the principles for using iText for other PDF features are similar.)</p>
+Here is some sample code that uses iText to encrypt a FOP-generated PDF. (Note that FOP now supports <a href="pdfencryption.html">PDF encryption</a>. However the principles for using iText for other PDF features are similar.)</p>
 <div class="codehilite"><pre><span class="kd">public</span> <span class="kd">static</span> <span class="kt">void</span> <span class="nf">main</span><span class="o">(</span><span class="n">String</span> <span class="n">args</span><span class="o">[])</span> <span class="o">{</span>
     <span class="k">try</span> <span class="o">{</span>
         <span class="n">ByteArrayOutputStream</span> <span class="n">fopout</span> <span class="o">=</span> <span class="k">new</span> <span class="n">ByteArrayOutputStream</span><span class="o">();</span>
@@ -458,8 +458,8 @@ Here is some sample code that uses iText
 </pre></div>
 
 
-<p><code>pdf:embedded-file</code> must be a child of <code>fo:declarations</code> . The "src" property is used to reference the file that is to be embedded. This property uses the "uri-specification" datatype from the XSL-FO specification. The "filename" property is optional. If it is missing the filename is automatically set from the URI/IRI of the "src" property. An optional description can also be added to further describe the file attachment.</p>
-<p>It is also possible to reference an embedded file from an <code>fo:basic-link</code> . Use the special "embedded-file:" URI scheme with the filename as single argument after the URI scheme. Example:</p>
+<p><code>pdf:embedded-file</code> must be a child of <code>fo:declarations</code>. The "src" property is used to reference the file that is to be embedded. This property uses the "uri-specification" datatype from the XSL-FO specification. The "filename" property is optional. If it is missing the filename is automatically set from the URI/IRI of the "src" property. An optional description can also be added to further describe the file attachment.</p>
+<p>It is also possible to reference an embedded file from an <code>fo:basic-link</code>. Use the special "embedded-file:" URI scheme with the filename as single argument after the URI scheme. Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;fo:basic-link</span> <span class="na">external-destination=</span><span class="s">&quot;url(embedded-file:image.jpg)&quot;</span><span class="nt">&gt;</span>Attached Image<span class="nt">&lt;/fo:basic-link&gt;</span>
 </pre></div>
 
@@ -795,7 +795,7 @@ A CID-keyed font (Type 0, double-byte ou
 </pre></div>
 
 
-<p>By default, all manually configured fonts are embedded, unless they are matched in the <a href="fonts.html#embedding">section of the configuration file</a> . However, the default fonts shown above will not be embedded.</p>
+<p>By default, all manually configured fonts are embedded, unless they are matched in the <a href="fonts.html#embedding">section of the configuration file</a>. However, the default fonts shown above will not be embedded.</p>
 <p>For double byte EBCDIC encoded character sets, there is an optional tag that must be set to prevent characters from being miscoded. This defaults to "false" if not specified.</p>
 <div class="codehilite"><pre><span class="nt">&lt;afp-font</span> <span class="na">type=</span><span class="s">&quot;CIDKeyed&quot;</span> <span class="na">codepage=</span><span class="s">&quot;T10835  &quot;</span> <span class="na">encoding=</span><span class="s">&quot;Cp937&quot;</span> <span class="na">characterset=</span><span class="s">&quot;CZTKAI&quot;</span> <span class="na">ebcdic-dbcs=</span><span class="s">&quot;true&quot;</span><span class="nt">/&gt;</span>
 </pre></div>
@@ -926,7 +926,7 @@ A CID-keyed font (Type 0, double-byte ou
 
 <p>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.</p>
 <p>The effect here is that whenever FOP encounters the URI specified in the extension, it will effectively generate code to include the page segment with the given name instead of embedding the image referenced by the URI. The URI is still required as the underlying image serves as a provider for the intrinsic size of the image (At the moment, FOP is unable to extract the intrinsic size of the page segment from an AFP resource file). For the image to appear in an AFP viewer or to be printed, the AFP resource must be available on the target device. FOP does not embed the page segment in the generated file. Please also note that page segments cannot be scaled. They are always rendered in their intrinsic size.</p>
-<p>The include-page-segment extension element has the optional attribute <em>resource-file</em> . The value of this is a URI to a resource containing a page segment with the declared name. In this case FOP embeds the page segment into the generated document so that the external resource does not have to be supplied in the print job.</p>
+<p>The include-page-segment extension element has the optional attribute <em>resource-file</em>. The value of this is a URI to a resource containing a page segment with the declared name. In this case FOP embeds the page segment into the generated document so that the external resource does not have to be supplied in the print job.</p>
 <h4 id="tag-logical-element-tle-extensionwzxhzdk129wzxhzdk130">Tag Logical Element (TLE) Extension<a id="afp-tag-logical-element"></a></h4>
 <p>The tag-logical-element extension element allows to injects TLEs into the AFP output stream. Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;fo:root</span> <span class="na">xmlns:fo=</span><span class="s">&quot;http://www.w3.org/1999/XSL/Format&quot;</span>
@@ -983,7 +983,7 @@ A CID-keyed font (Type 0, double-byte ou
 </pre></div>
 
 
-<p>The <code>afp:include-form-map</code> is to be placed as a direct child of <code>fo:declarations</code> . The <code>name</code> is an AFP resource name (max. 8 characters) and the <code>src</code> attribute is the URI identifying the external form map resource. When such a form map is embedded, you can use the <code>afp:invoke-medium-map</code> extension (described above) to invoke any medium map included in the form map.
+<p>The <code>afp:include-form-map</code> is to be placed as a direct child of <code>fo:declarations</code>. The <code>name</code> is an AFP resource name (max. 8 characters) and the <code>src</code> attribute is the URI identifying the external form map resource. When such a form map is embedded, you can use the <code>afp:invoke-medium-map</code> extension (described above) to invoke any medium map included in the form map.
 Apache FOP doesn't support a way to define a form map or medium map using XML means inside an XSL-FO document. You will have to build the form map with some third-party tool.</p>
 <h3 id="foreign-attributes-wzxhzdk137wzxhzdk138">Foreign Attributes <a id="afp-foreign-attributes"></a></h3>
 <h4 id="resourcewzxhzdk139wzxhzdk140">Resource<a id="afp-foreign-attributes-resource"></a></h4>
@@ -1050,7 +1050,7 @@ These are some known restrictions compar
 </ul>
 <h2 id="xml-area-tree-xml-wzxhzdk145wzxhzdk146">XML (Area Tree XML) <a id="xml"></a></h2>
 <p>This is primarily for testing and verification. The XML created is simply a representation of the internal area tree put into XML. We use that to verify the functionality of FOP's layout engine.</p>
-<p>The other use case of the Area Tree XML is as FOP's "intermediate format". More information on that can be found on the page dedicated to the <a href="intermediate.html">Intermediate Format</a> .</p>
+<p>The other use case of the Area Tree XML is as FOP's "intermediate format". More information on that can be found on the page dedicated to the <a href="intermediate.html">Intermediate Format</a>.</p>
 <h2 id="java2dawt-wzxhzdk147wzxhzdk148">Java2D/AWT <a id="awt"></a></h2>
 <p>The Java2DRenderer provides the basic functionality for all Java2D-based output formats (AWT viewer, direct print, PNG, TIFF).</p>
 <p>The AWT viewer shows a window with the pages displayed inside a Java graphic. It displays one page at a time. The fonts used for the formatting and viewing depend on the fonts available to your JRE.</p>
@@ -1078,23 +1078,23 @@ These are some known restrictions compar
 <p>The default value for the <code>"color-mode"</code> setting is <code>"rgba"</code> which is equivalent to a 24bit RGB image with an 8bit alpha channel for transparency. Valid values are:</p>
 <ul>
 <li>
-<p><code>rgba</code> : RGB with alpha channel (24bit + 8bit = 32bit)</p>
+<p><code>rgba</code>: RGB with alpha channel (24bit + 8bit = 32bit)</p>
 </li>
 <li>
-<p><code>rgb</code> : RGB (24bit)</p>
+<p><code>rgb</code>: RGB (24bit)</p>
 </li>
 <li>
-<p><code>gray</code> : gray (8bit)</p>
+<p><code>gray</code>: gray (8bit)</p>
 </li>
 <li>
 <p><code>bi-level</code> (or <code>binary</code> ): bi-level (1bit)</p>
 </li>
 </ul>
 <p>Please note that there is currently no dithering or error diffusion available for bi-level bitmap output.</p>
-<p>The default value for the <code>"transparent-page-background"</code> setting is <code>"false"</code> which paints an opaque, white background for the whole image. If you set this to <code>"true"</code> , no such background will be painted and you will get a transparent image if an alpha channel is available in the output format.</p>
-<p>The default value for the <code>"background-color"</code> setting is <code>"white"</code> . The color specifies in which color the page background is painted. It will only be painted if <code>"transparent-page-background"</code> is not set to <code>"true"</code> . All XSL-FO colors (including color functions) can be used.</p>
-<p>The default value for the <code>"anti-aliasing"</code> setting is <code>"true"</code> . You can set this value to <code>"false"</code> to disable anti-aliasing and thus improve rendering speeds a bit at the loss of some image quality.</p>
-<p>The default value for the <code>"rendering"</code> setting is <code>"true"</code> . You can set this value to <code>"false"</code> to improve rendering speeds a bit at the loss of some image quality. If this setting has an actual effect depends on the JVM's Java2D backend.</p>
+<p>The default value for the <code>"transparent-page-background"</code> setting is <code>"false"</code> which paints an opaque, white background for the whole image. If you set this to <code>"true"</code>, no such background will be painted and you will get a transparent image if an alpha channel is available in the output format.</p>
+<p>The default value for the <code>"background-color"</code> setting is <code>"white"</code>. The color specifies in which color the page background is painted. It will only be painted if <code>"transparent-page-background"</code> is not set to <code>"true"</code>. All XSL-FO colors (including color functions) can be used.</p>
+<p>The default value for the <code>"anti-aliasing"</code> setting is <code>"true"</code>. You can set this value to <code>"false"</code> to disable anti-aliasing and thus improve rendering speeds a bit at the loss of some image quality.</p>
+<p>The default value for the <code>"rendering"</code> setting is <code>"true"</code>. You can set this value to <code>"false"</code> to improve rendering speeds a bit at the loss of some image quality. If this setting has an actual effect depends on the JVM's Java2D backend.</p>
 <h3 id="tiff-specific-configuration-wzxhzdk157wzxhzdk158">TIFF-specific Configuration <a id="tiff-configuration"></a></h3>
 <p>In addition to the above values the TIFF renderer configuration allows some additional settings:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;image/tiff&quot;</span><span class="nt">&gt;</span>
@@ -1132,7 +1132,7 @@ These are some known restrictions compar
 <p><code>CCITT T.6</code> (Fax Group 4)</p>
 </li>
 </ul>
-<p>This setting may override any setting made using the <code>"color-mode"</code> . For example, if <code>"CCITT T.6"</code> is selected, the color mode is automatically forced to <code>"bi-level"</code> because this compression format only supports bi-level images.
+<p>This setting may override any setting made using the <code>"color-mode"</code>. For example, if <code>"CCITT T.6"</code> is selected, the color mode is automatically forced to <code>"bi-level"</code> because this compression format only supports bi-level images.
 If you want to use CCITT compression, please make sure you've got <a href="http://java.sun.com/products/java-media/jai/current.html">Java Advanced Imaging Image I/O Tools</a> 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.</p>
 <h3 id="runtime-rendering-options-wzxhzdk159wzxhzdk160">Runtime Rendering Options <a id="bitmap-rendering-options"></a></h3>
 <p>The IF-based bitmap output implementations support a rendering option with the key "target-bitmap-size" (value: java.awt.Dimension) that allows to force the pages to be proportionally fit into a bitmap of a given size. This can be used to produce thumbnails or little preview images of the individual pages. An example:</p>
@@ -1166,7 +1166,7 @@ This format creates an SVG document that
 <h2 id="wish-list-wzxhzdk173wzxhzdk174">Wish list <a id="wishlist"></a></h2>
 <p>Apache FOP is easily extensible and allows you to add new output formats to enhance FOP's functionality. There's a number of output formats which are on our wish list. We're looking for volunteers to help us implement them.</p>
 <ul>
-<li><a href="http://en.wikipedia.org/wiki/OpenDocument">ODF (Open Document Format)</a> : The standardized successor to OpenOffice's file format.</li>
+<li><a href="http://en.wikipedia.org/wiki/OpenDocument">ODF (Open Document Format)</a>: The standardized successor to OpenOffice's file format.</li>
 </ul></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfa.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfa.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfa.html Wed Dec  5 08:23:47 2012
@@ -344,12 +344,12 @@ $(document).ready(function () {
       	<div class="section-content"><h1 id="apachewzxhzdk1-fop-pdfa-iso-19005">Apache&trade; FOP: PDF/A (ISO 19005)</h1>
 <p><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
 <h2 id="overview-wzxhzdk6wzxhzdk7">Overview <a id="overview"></a></h2>
-<p>PDF/A is a standard which turns PDF into an "electronic document file format for long-term preservation". PDF/A-1 is the first part of the standard and is documented in <a href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38920&amp;ICS1=37&amp;ICS2=100&amp;ICS3=99">ISO 19005-1:2005(E)</a> . Work on PDF/A-2 is in progress at <a href="http://www.aiim.org/standards.asp?ID=25013">AIIM</a> .</p>
+<p>PDF/A is a standard which turns PDF into an "electronic document file format for long-term preservation". PDF/A-1 is the first part of the standard and is documented in <a href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=38920&amp;ICS1=37&amp;ICS2=100&amp;ICS3=99">ISO 19005-1:2005(E)</a>. Work on PDF/A-2 is in progress at <a href="http://www.aiim.org/standards.asp?ID=25013">AIIM</a>.</p>
 <p>Design documentation on PDF/A can be found on FOP's Wiki on the <a href="http://wiki.apache.org/xmlgraphics-fop/PDFA1ConformanceNotes">PDFA1ConformanceNotes</a> page.</p>
 <h2 id="implementation-status-wzxhzdk8wzxhzdk9">Implementation Status <a id="status"></a></h2>
 <p><strong>PDF/A-1b</strong> is implemented to the degree that FOP supports the creation of the elements described in ISO 19005-1.</p>
 <p>Tests have been performed against jHove and Adobe Acrobat 7.0.7 (Preflight function). FOP does not validate completely against Apago's PDF Appraiser. Reasons unknown due to lack of a full license to get a detailed error protocol.</p>
-<p><strong>PDF/A-1a</strong> is based on PDF-A-1b and adds accessibility features (such as Tagged PDF). This format is available within the limitation described on the <a href="accessibility.html">Accessibility page</a> .</p>
+<p><strong>PDF/A-1a</strong> is based on PDF-A-1b and adds accessibility features (such as Tagged PDF). This format is available within the limitation described on the <a href="accessibility.html">Accessibility page</a>.</p>
 <h2 id="usage-command-line-wzxhzdk10wzxhzdk11">Usage (command line) <a id="command-line"></a></h2>
 <p>To activate PDF/A-1b from the command-line, specify "-pdfprofile PDF/A-1b" as a parameter. If there is a violation of one of the validation rules for PDF/A, an error message is presented and the processing stops.</p>
 <p>PDF/A-1a is enabled by specifying "-pdfprofile PDF/A-1a".</p>
@@ -397,13 +397,13 @@ There are additional requirements if you
 <thead>
 <tr>
 <th>http://www.aiim.org/pdfa/ns/id.html</th>
-<th><strong>obsolete</strong> , from an early draft of ISO-19005-1, used by Adobe Acrobat 7.x</th>
+<th><strong>obsolete</strong>, from an early draft of ISO-19005-1, used by Adobe Acrobat 7.x</th>
 </tr>
 </thead>
 <tbody>
 <tr>
 <td>http://www.aiim.org/pdfa/ns/id/</td>
-<td><strong>correct</strong> , found in the technical corrigendum 1 of ISO 19005-1:2005</td>
+<td><strong>correct</strong>, found in the technical corrigendum 1 of ISO 19005-1:2005</td>
 </tr>
 </tbody>
 </table>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html Wed Dec  5 08:23:47 2012
@@ -569,7 +569,7 @@ $(document).ready(function () {
 <p>Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does <strong>not</strong> provide RC4. If you get a message saying
 "Cannot find any provider supporting RC4"
 then you don't have the needed infrastructure.</p>
-<p>There are several commercial and a few Open Source packages which provide RC4. A pure Java implementation is produced by <a href="http://www.bouncycastle.org/">The Legion of the Bouncy Castle</a> . <a href="http://www.mozilla.org/projects/security/pki/jss/">Mozilla JSS</a> is an interface to a native implementation.</p>
+<p>There are several commercial and a few Open Source packages which provide RC4. A pure Java implementation is produced by <a href="http://www.bouncycastle.org/">The Legion of the Bouncy Castle</a>. <a href="http://www.mozilla.org/projects/security/pki/jss/">Mozilla JSS</a> is an interface to a native implementation.</p>
 <h2 id="installing-a-crypto-provider-wzxhzdk17wzxhzdk18">Installing a crypto provider <a id="install_crypto"></a></h2>
 <p>The pure Java implementation from <a href="http://www.bouncycastle.org/">Bouncy Castle</a> is easy to install.</p>
 <ol>
@@ -577,10 +577,10 @@ then you don't have the needed infrastru
 <p>Download the binary distribution for your JDK version.</p>
 </li>
 <li>
-<p>Unpack the distribution. Add the jar file to your classpath. A convenient way to use the jar on Linux is to simply drop it into the FOP lib directory, it will be automatically picked up by <code>fop.sh</code> .</p>
+<p>Unpack the distribution. Add the jar file to your classpath. A convenient way to use the jar on Linux is to simply drop it into the FOP lib directory, it will be automatically picked up by <code>fop.sh</code>.</p>
 </li>
 <li>
-<p>Open the <code>java.security</code> file and add<br></br> <code>security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider</code> ,<br></br>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a> .</p>
+<p>Open the <code>java.security</code> file and add<br></br> <code>security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider</code>,<br></br>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a>.</p>
 </li>
 </ol>
 <p>If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfx.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfx.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfx.html Wed Dec  5 08:23:47 2012
@@ -345,7 +345,7 @@ $(document).ready(function () {
 <p><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
 <h2 id="overview-wzxhzdk6wzxhzdk7">Overview <a id="overview"></a></h2>
 <p><warning>Support for PDF/X is available beginning with version 0.93. This feature is new and may not be 100% complete, yet. Feedback is welcome.</warning>
-PDF/X is a standard which faciliates prepress digital data exchange using PDF. Currently, only PDF/X-3:2003 is implemented out of the many different flavours of PDF/X profiles. PDF/X-3:2003 is documented in <a href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&amp;ICS1=37&amp;ICS2=100&amp;ICS3=99">ISO 15930-6:2003(E)</a> . More info on PDF/X can be found on the <a href="http://www.pdfx.info/">PDF/X info site</a> .</p>
+PDF/X is a standard which faciliates prepress digital data exchange using PDF. Currently, only PDF/X-3:2003 is implemented out of the many different flavours of PDF/X profiles. PDF/X-3:2003 is documented in <a href="http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=39940&amp;ICS1=37&amp;ICS2=100&amp;ICS3=99">ISO 15930-6:2003(E)</a>. More info on PDF/X can be found on the <a href="http://www.pdfx.info/">PDF/X info site</a>.</p>
 <h2 id="implementation-status-wzxhzdk10wzxhzdk11">Implementation Status <a id="status"></a></h2>
 <p><strong>PDF/X-3:2003</strong> is implemented to the degree that FOP supports the creation of the elements described in ISO 15930-6.</p>
 <p>An important restriction of the current implementation is that all normal RGB colors specified in XSL-FO and SVG are left unchanged in the sRGB color space (XSL-FO and SVG both use sRGB as their default color space). There's no conversion to a CMYK color space. Although sRGB is a calibrated color space, its color space has a different size than a CMYK color space which makes the conversion a lossy conversion and can lead to unwanted results. Although the use of the calibrated sRGB has been promoted for years, print shops usually prefer to convert an sRGB PDF to CMYK prior to production. Until there's full CMYK support in FOP you will have to work closely with your print service provider to make sure you get the intended result.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/releaseNotes_1.1.html Wed Dec  5 08:23:47 2012
@@ -343,52 +343,52 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/1.1/">1.1</a></div> -->
       	<div class="section-content"><h1 id="release-notes-for-apache-fop-11">Release Notes for Apache FOP 1.1</h1>
 <h2 id="major-changes-in-version-11-wzxhzdk0wzxhzdk1">Major Changes in Version 1.1 <a id="version_1.1"></a></h2>
-<p>This is not a complete list of changes, just some of the more important ones. A full list of changes in this release <a href="changes_1.1.html">is available</a> .</p>
+<p>This is not a complete list of changes, just some of the more important ones. A full list of changes in this release <a href="changes_1.1.html">is available</a>.</p>
 <h2 id="changes-to-the-code-base-wzxhzdk2wzxhzdk3">Changes to the Code Base <a id="Changes+to+the+Code+Base"></a></h2>
 <ul>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Update to use of checkstyle-5.5 as default configuration. Remove checkstyle-4.0 configuration. Also, import environment build properties before local properties, so that latter can refer to former. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53083">53083</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Update to use of checkstyle-5.5 as default configuration. Remove checkstyle-4.0 configuration. Also, import environment build properties before local properties, so that latter can refer to former. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53083">53083</a>.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Invoke JVM in headless mode from FOP command scripts and JS shell to prevent stealing focus from GUI applications. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50062">50062</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Invoke JVM in headless mode from FOP command scripts and JS shell to prevent stealing focus from GUI applications. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50062">50062</a>.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Support list-block in marker, thus preventing NPE. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52763">52763</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Support list-block in marker, thus preventing NPE. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52763">52763</a>.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Allow https scheme URI for PDF external action target. Committed by GA. Thanks to Paul Huemer. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51599">51599</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Allow https scheme URI for PDF external action target. Committed by GA. Thanks to Paul Huemer. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51599">51599</a>.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Fixed incorrect rejection of fo:wrapper inside fo:inline inside fo:footnote-body. Committed by GA. Thanks to Alberto Simões. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53005">53005</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Fixed incorrect rejection of fo:wrapper inside fo:inline inside fo:footnote-body. Committed by GA. Thanks to Alberto Simões. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53005">53005</a>.</p>
 </li>
 <li>
 <p><img alt="add" src="/images/add.jpg" /> Added support for PDF Object Streams. When accessibility is enabled and PDF version 1.5 selected, the structure tree will be stored in object streams in order to reduce the size of the final PDF. Committed by VH. Thanks to Peter Hancock.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Fixed bug that caused a configured and installed SVG font to be stroked, also added an event indicating when fonts are stroked. Committed by MH. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52849">52849</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Fixed bug that caused a configured and installed SVG font to be stroked, also added an event indicating when fonts are stroked. Committed by MH. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52849">52849</a>.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Improved support for empty flow-name mapping. Committed by PH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50391">50391</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Improved support for empty flow-name mapping. Committed by PH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50391">50391</a>.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Add support for different flow-name of fo:region-body in FOP Committed by CB. Thanks to Peter Hancock. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50391">50391</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Add support for different flow-name of fo:region-body in FOP Committed by CB. Thanks to Peter Hancock. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50391">50391</a>.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Allow JPEG images to be embedded in an AFP document as is, without being decoded and encoded. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52089">52089</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Allow JPEG images to be embedded in an AFP document as is, without being decoded and encoded. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52089">52089</a>.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Fix for when the last simple-page-master referenced in a page-sequence-master is not chosen when force-page-count=odd. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51962">51962</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Fix for when the last simple-page-master referenced in a page-sequence-master is not chosen when force-page-count=odd. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51962">51962</a>.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Upgraded all tests to JUnit 4. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51928">51928</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Upgraded all tests to JUnit 4. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51928">51928</a>.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Added support for resolution of relative URIs against a specified xml:base during property refinement. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=48334">48334</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Added support for resolution of relative URIs against a specified xml:base during property refinement. Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=48334">48334</a>.</p>
 </li>
 </ul>
 <h3 id="changes-to-the-user-configuration-wzxhzdk4wzxhzdk5">Changes to the User Configuration <a id="Changes+to+the+User+Configuration"></a></h3>
 <ul>
-<li><img alt="add" src="/images/add.jpg" /> Added configuration option to set the version of the output PDF document. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51385">51385</a> .</li>
+<li><img alt="add" src="/images/add.jpg" /> Added configuration option to set the version of the output PDF document. Committed by VH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51385">51385</a>.</li>
 </ul>
 <h3 id="changes-to-the-font-subsystem-wzxhzdk6wzxhzdk7">Changes to the Font Subsystem <a id="Changes+to+the+Font+Subsystem"></a></h3>
 <ul>
@@ -396,10 +396,10 @@ $(document).ready(function () {
 <p><img alt="add" src="/images/add.jpg" /> Add support for OpenType advanced typographic tables (GDEF, GSUB, GPOS). Committed by GA.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Changes the way PostScript handles Graphics2D images such that if the language is set to level 3, the image is stored as an embedded file which has no length limit. Previously it was stored as an array which has a implementation limit of 65535 elements. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51760">51760</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Changes the way PostScript handles Graphics2D images such that if the language is set to level 3, the image is stored as an embedded file which has no length limit. Previously it was stored as an array which has a implementation limit of 65535 elements. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51760">51760</a>.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Improved support for EBCDIC encoded double byte fonts fo AFP. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51530">51530</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Improved support for EBCDIC encoded double byte fonts fo AFP. Committed by PH. Thanks to Mehdi Houshmand. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=51530">51530</a>.</p>
 </li>
 <li>
 <p><img alt="fix" src="/images/fix.jpg" /> Reinstated support for being able to specify a font cache filepath in the fop user configuration. Committed by AC.</p>
@@ -410,18 +410,18 @@ $(document).ready(function () {
 </ul>
 <h3 id="changes-to-the-image-support-wzxhzdk8wzxhzdk9">Changes to the Image Support <a id="Changes+to+the+Image+Support"></a></h3>
 <ul>
-<li><img alt="fix" src="/images/fix.jpg" /> Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecssary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40676">40676</a> .</li>
+<li><img alt="fix" src="/images/fix.jpg" /> Support use of ImageLoaderRawPNG decoder in order to prevent re-encoding of PNG images (and unnecssary output file bloat). Committed by GA. Thanks to Luis Bernardo, Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=40676">40676</a>.</li>
 </ul>
 <h3 id="changes-to-the-layout-engine-wzxhzdk10wzxhzdk11">Changes to the Layout Engine <a id="Changes+to+the+Layout+Engine"></a></h3>
 <ul>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Fix for break before (break-before) not respected on blocks nested in inlines. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45715">45715</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Fix for break before (break-before) not respected on blocks nested in inlines. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=45715">45715</a>.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Ensure square image is appropriately scaled. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52514">52514</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Ensure square image is appropriately scaled. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52514">52514</a>.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Add support for complex scripts, including: full bidi support, support for advanced typographic tables, advanced support for number conversion. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=32789">32789</a> , <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49008">49008</a> , <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49687">49687</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Add support for complex scripts, including: full bidi support, support for advanced typographic tables, advanced support for number conversion. Committed by GA. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=32789">32789</a>, <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49008">49008</a>, <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49687">49687</a>.</p>
 </li>
 <li>
 <p><img alt="fix" src="/images/fix.jpg" /> Implemented non-standard behavior for basic-link areas, such that they take into account the heights of their descendants areas. Committed by VH.</p>
@@ -433,19 +433,19 @@ $(document).ready(function () {
 <p><img alt="fix" src="/images/fix.jpg" /> Fix for keep-together on a table containing row-spanning cells that was not honored. Committed by VH.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Fix forpadding-start ignored when table-header/footer is repeated. Committed by VH. Thanks to Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50196">50196</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Fix forpadding-start ignored when table-header/footer is repeated. Committed by VH. Thanks to Matthias Reischenbacher. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=50196">50196</a>.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Fix for correct behavior of keep-together.within-line in case there are nested inlines Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49848">49848</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Fix for correct behavior of keep-together.within-line in case there are nested inlines Committed by AD. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49848">49848</a>.</p>
 </li>
 </ul>
 <h3 id="changes-to-renderers-output-formats-wzxhzdk12wzxhzdk13">Changes to Renderers (Output Formats) <a id="Changes+to+Renderers+%28Output+Formats%29"></a></h3>
 <ul>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Added possibility to embed TrueType fonts in PostScript. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52338">52338</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Added possibility to embed TrueType fonts in PostScript. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=52338">52338</a>.</p>
 </li>
 <li>
-<p><img alt="fix" src="/images/fix.jpg" /> Add extension to place code just before PostScript %PageTrailer. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53295">53295</a> .</p>
+<p><img alt="fix" src="/images/fix.jpg" /> Add extension to place code just before PostScript %PageTrailer. Committed by GA. Thanks to Luis Bernardo. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=53295">53295</a>.</p>
 </li>
 <li>
 <p><img alt="add" src="/images/add.jpg" /> Added support for 128bit encryption in PDF output. Committed by VH. Thanks to Michael Rubin.</p>
@@ -472,10 +472,10 @@ $(document).ready(function () {
 <p><img alt="add" src="/images/add.jpg" /> Added support for CIE Lab colors (from XSL-FO 2.0 WD). Committed by JM.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Initial work on spot colors (aka named colors) for PDF output. Committed by JM. Thanks to Patrick Jaromin. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49403">49403</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Initial work on spot colors (aka named colors) for PDF output. Committed by JM. Thanks to Patrick Jaromin. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49403">49403</a>.</p>
 </li>
 <li>
-<p><img alt="add" src="/images/add.jpg" /> Added ability to embed an external AFP page segment resource file (AFP output only). Committed by JM. Thanks to Peter Hancock. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49379">49379</a> .</p>
+<p><img alt="add" src="/images/add.jpg" /> Added ability to embed an external AFP page segment resource file (AFP output only). Committed by JM. Thanks to Peter Hancock. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=49379">49379</a>.</p>
 </li>
 </ul></div>
       </div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html Wed Dec  5 08:23:47 2012
@@ -355,19 +355,19 @@ $(document).ready(function () {
 <p>Apache&trade; FOP. The <a href="../download.html">FOP distribution</a> includes all libraries that you will need to run a basic FOP installation. These can be found in the [fop-root]/lib directory. These libraries include the following:</p>
 <ul>
 <li>
-<p><a href="http://xmlgraphics.apache.org/commons/">Apache XML Graphics Commons</a> , an shared library for Batik and FOP.</p>
+<p><a href="http://xmlgraphics.apache.org/commons/">Apache XML Graphics Commons</a>, an shared library for Batik and FOP.</p>
 </li>
 <li>
-<p><a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> , an SVG library.</p>
+<p><a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a>, an SVG library.</p>
 </li>
 <li>
-<p><a href="http://commons.apache.org/logging/">Apache Commons Logging</a> , a logger abstraction kit.</p>
+<p><a href="http://commons.apache.org/logging/">Apache Commons Logging</a>, a logger abstraction kit.</p>
 </li>
 <li>
-<p><a href="http://commons.apache.org/io/">Apache Commons IO</a> , a library with I/O utilities.</p>
+<p><a href="http://commons.apache.org/io/">Apache Commons IO</a>, a library with I/O utilities.</p>
 </li>
 <li>
-<p><a href="http://excalibur.apache.org/framework/">Apache Excalibur/Avalon Framework</a> , for XML configuration handling.</p>
+<p><a href="http://excalibur.apache.org/framework/">Apache Excalibur/Avalon Framework</a>, for XML configuration handling.</p>
 </li>
 </ul>
 </li>
@@ -392,7 +392,7 @@ $(document).ready(function () {
 <p>Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users have recommended that Mac OSX users use the shell command <code>tar -xzf</code> instead.</p>
 <h2 id="starting-fop-as-a-standalone-application-wzxhzdk10wzxhzdk11">Starting FOP as a Standalone Application <a id="standalone-start"></a></h2>
 <h3 id="using-the-fop-script-or-batch-file-wzxhzdk12wzxhzdk13">Using the fop script or batch file <a id="fop-script"></a></h3>
-<p>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 <code>/Library/Java/Home</code> . <strong>Caveat:</strong> 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 <a href="http://developer.apple.com/java/faq">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
+<p>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 <code>/Library/Java/Home</code>. <strong>Caveat:</strong> 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 <a href="http://developer.apple.com/java/faq">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
 <div class="codehilite"><pre><span class="n">USAGE</span>
 <span class="n">Fop</span> <span class="p">[</span><span class="n">options</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">fo</span><span class="o">|-</span><span class="n">xml</span><span class="p">]</span> <span class="n">infile</span> <span class="p">[</span><span class="o">-</span><span class="n">xsl</span> <span class="n">file</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">awt</span><span class="o">|-</span><span class="n">pdf</span><span class="o">|-</span><span class="n">mif</span><span class="o">|-</span><span class="n">rtf</span><span class="o">|-</span><span class="n">tiff</span><span class="o">|-</span><span class="n">png</span><span class="o">|-</span><span class="n">pcl</span><span class="o">|-</span><span class="n">ps</span><span class="o">|-</span><span class="n">txt</span><span class="o">|-</span><span class="n">at</span> <span class="p">[</span><span class="n">mime
 </span><span class="p">]</span><span class="o">|-</span><span class="k">print</span><span class="p">]</span> <span class="sr">&lt;outfile&gt;</span>
  <span class="p">[</span><span class="n">OPTIONS</span><span class="p">]</span>
@@ -487,27 +487,27 @@ $(document).ready(function () {
 </pre></div>
 
 
-<p>PDF encryption is only available if FOP was compiled with encryption support <strong>and</strong> if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the <a href="pdfencryption.html">Details</a> .</p>
+<p>PDF encryption is only available if FOP was compiled with encryption support <strong>and</strong> if compatible encryption support is available at run time. Currently, only the JCE is supported. Check the <a href="pdfencryption.html">Details</a>.</p>
 <h3 id="writing-your-own-script-wzxhzdk14wzxhzdk15">Writing your own script <a id="your-own-script"></a></h3>
-<p>FOP's entry point for your own scripts is the class <code>org.apache.fop.cli.Main</code> . The general pattern for the command line is: <code>java -classpath &lt;CLASSPATH&gt;
-        org.apache.fop.cli.Main &lt;arguments&gt;</code> . The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that you get your environment properly configured.</p>
+<p>FOP's entry point for your own scripts is the class <code>org.apache.fop.cli.Main</code>. The general pattern for the command line is: <code>java -classpath &lt;CLASSPATH&gt;
+        org.apache.fop.cli.Main &lt;arguments&gt;</code>. The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that you get your environment properly configured.</p>
 <h3 id="running-with-javas-jar-option-wzxhzdk16wzxhzdk17">Running with java's -jar option <a id="jar-option"></a></h3>
 <p>As an alternative to the start scripts you can run <code>java
-        -jar path/to/build/fop.jar &lt;arguments&gt;</code> , relying on FOP to build the classpath for running FOP dynamically, see <a href="#dynamical-classpath">below</a> . If you use hyphenation, you must put <code>fop-hyph.jar</code> in the <code>lib</code> directory.</p>
+        -jar path/to/build/fop.jar &lt;arguments&gt;</code>, relying on FOP to build the classpath for running FOP dynamically, see <a href="#dynamical-classpath">below</a>. If you use hyphenation, you must put <code>fop-hyph.jar</code> in the <code>lib</code> directory.</p>
 <p>You can also run <code>java -jar path/to/fop.jar
-      &lt;arguments&gt;</code> , relying on the <code>Class-Path</code> entry in the manifest file. This works if you put <code>fop.jar</code> and all jar files from the <code>lib</code> directory in a single directory. If you use hyphenation, you must also put <code>fop-hyph.jar</code> in that directory.</p>
+      &lt;arguments&gt;</code>, relying on the <code>Class-Path</code> entry in the manifest file. This works if you put <code>fop.jar</code> and all jar files from the <code>lib</code> directory in a single directory. If you use hyphenation, you must also put <code>fop-hyph.jar</code> in that directory.</p>
 <p>In both cases the arguments consist of the options and infile and outfile specifications as shown above for the standard scripts.</p>
 <h3 id="fops-dynamical-classpath-construction-wzxhzdk18wzxhzdk19">FOP's dynamical classpath construction <a id="dynamical-classpath"></a></h3>
-<p>If FOP is started without a proper classpath, it tries to add its dependencies dynamically. If the system property <code>fop.home</code> contains the name of a directory, then FOP uses that directory as the base directory for its search. Otherwise the current working directory is the base directory. If the base directory is called <code>build</code> , then its parent directory becomes the base directory.</p>
+<p>If FOP is started without a proper classpath, it tries to add its dependencies dynamically. If the system property <code>fop.home</code> contains the name of a directory, then FOP uses that directory as the base directory for its search. Otherwise the current working directory is the base directory. If the base directory is called <code>build</code>, then its parent directory becomes the base directory.</p>
 <p>FOP expects to find <code>fop.jar</code> in the <code>build</code> subdirectory of the base directory, and adds it to the classpath. Subsequently FOP adds all <code>jar</code> files in the lib directory to the classpath. The lib directory is either the <code>lib</code> subdirectory of the base directory, or, if that does not exist, the base directory itself.</p>
-<p>If the system property <code>fop.optional.lib</code> contains the name of a directory, then all <code>jar</code> files in that directory are also added to the classpath. See the methods <code>getJARList</code> and <code>checkDependencies</code> in <code>org.apache.fop.cli.Main</code> .</p>
+<p>If the system property <code>fop.optional.lib</code> contains the name of a directory, then all <code>jar</code> files in that directory are also added to the classpath. See the methods <code>getJARList</code> and <code>checkDependencies</code> in <code>org.apache.fop.cli.Main</code>.</p>
 <h2 id="using-xalan-to-check-xsl-fo-input-wzxhzdk20wzxhzdk21">Using Xalan to Check XSL-FO Input <a id="check-input"></a></h2>
-<p>FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Tranforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. Only the second is part of FOP's core processing. If a user has a problem running FOP, it is important to determine which of these two processes is causing the problem. If the problem is in the first process, the user's stylesheet is likely the cause. The FOP development team does not have resources to help with stylesheet issues, although we have included links to some useful <a href="../resources.html#specs">Specifications</a> and <a href="../resources.html#articles">Books/Articles</a> . If the problem is in the second process, FOP may have a bug or an unimplemented feature that does require attention from the FOP development team.
+<p>FOP sessions that use -xml and -xsl input instead of -fo input are actually controlling two distinct conversions: Tranforming XML to XSL-FO, then formatting the XSL-FO to PDF (or another FOP output format). Although FOP controls both of these processes, the first is included merely as a convenience and for performance reasons. Only the second is part of FOP's core processing. If a user has a problem running FOP, it is important to determine which of these two processes is causing the problem. If the problem is in the first process, the user's stylesheet is likely the cause. The FOP development team does not have resources to help with stylesheet issues, although we have included links to some useful <a href="../resources.html#specs">Specifications</a> and <a href="../resources.html#articles">Books/Articles</a>. If the problem is in the second process, FOP may have a bug or an unimplemented feature that does require attention from the FOP development team.
 The user is always responsible to provide correct XSL-FO code to FOP.
 In the case of using -xml and -xsl input, although the user is responsible for the XSL-FO code that is FOP's input, it is not visible to the user. To make the intermediate FO file visible, the FOP distribution includes the "-foout" option which causes FOP to run only the first (transformation) step, and write the results to a file. (See also the Xalan command-line below)
 When asking for help on the FOP mailing lists, <em>never</em> attach XML and XSL to illustrate the issue. Always run the XSLT step (-foout) and send the resulting XSL-FO file instead. Of course, be sure that the XSL-FO file is correct before sending it.
-The -foout option works the same way as if you would call the <a href="http://xml.apache.org/xalan-j/commandline.html">Xalan command-line</a> :</p>
-<p><code>java org.apache.xalan.xslt.Process -IN xmlfile -XSL file -OUT outfile</code> </p>
+The -foout option works the same way as if you would call the <a href="http://xml.apache.org/xalan-j/commandline.html">Xalan command-line</a>:</p>
+<p><code>java org.apache.xalan.xslt.Process -IN xmlfile -XSL file -OUT outfile</code></p>
 <p>Note that there are some subtle differences between the FOP and Xalan command-lines.</p>
 <h2 id="memory-usage-wzxhzdk22wzxhzdk23">Memory Usage <a id="memory"></a></h2>
 <p>FOP can consume quite a bit of memory, even though this has been continually improved. This is partly inherent to the formatting process and partly caused by implementation choices. All FO processors currently on the market have memory problems with certain layouts.</p>
@@ -527,7 +527,7 @@ The -foout option works the same way as 
 </li>
 </ul>
 <h2 id="problems-wzxhzdk24wzxhzdk25">Problems <a id="problems"></a></h2>
-<p>If you have problems running FOP, please see the <a href="../gethelp.html">"How to get Help" page</a> .</p></div>
+<p>If you have problems running FOP, please see the <a href="../gethelp.html">"How to get Help" page</a>.</p></div>
       </div>
       
       <div class="clear"></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html Wed Dec  5 08:23:47 2012
@@ -359,7 +359,7 @@ $(document).ready(function () {
 <p>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.</p>
 <h2 id="create-your-own-servlet-wzxhzdk13wzxhzdk14">Create your own Servlet <a id="servlet"></a></h2>
-<p>This section assumes you are familiar with <a href="embedding.html">embedding FOP</a> .</p>
+<p>This section assumes you are familiar with <a href="embedding.html">embedding FOP</a>.</p>
 <h3 id="a-minimal-servlet-wzxhzdk15wzxhzdk16">A minimal Servlet <a id="minimal-servlet"></a></h3>
 <p>Here is a minimal code snippet to demonstrate the basics:</p>
 <div class="codehilite"><pre><span class="kd">private</span> <span class="n">FopFactory</span> <span class="n">fopFactory</span> <span class="o">=</span> <span class="n">FopFactory</span><span class="o">.</span><span class="na">newInstance</span><span class="o">();</span>
@@ -424,10 +424,10 @@ This example servlet should not be used 
 
 <p>Buffering the generated PDF in a ByteArrayOutputStream is done to avoid potential problems with the Acrobat Reader Plug-in in Microsoft Internet Explorer.
 The <code>Source</code> instance used above is simply an example. If you have to read the XML from a string, supply a <code>new StreamSource(new
-          StringReader(xmlstring))</code> . Constructing and reparsing an XML string is generally less desirable than using a SAXSource if you generate your XML. You can alternatively supply a DOMSource as well. You may also use dynamically generated XSL if you like.</p>
+          StringReader(xmlstring))</code>. Constructing and reparsing an XML string is generally less desirable than using a SAXSource if you generate your XML. You can alternatively supply a DOMSource as well. You may also use dynamically generated XSL if you like.</p>
 <p>Because you have an explicit <code>Transformer</code> object, you can also use it to explicitely set parameters for the transformation run.</p>
 <h3 id="custom-configuration-wzxhzdk19wzxhzdk20">Custom configuration <a id="cfg"></a></h3>
-<p>You can easily set up your own FOUserAgent as demonstrated on the <a href="embedding.html">Embedding page</a> .</p>
+<p>You can easily set up your own FOUserAgent as demonstrated on the <a href="embedding.html">Embedding page</a>.</p>
 <h3 id="improving-performance-wzxhzdk21wzxhzdk22">Improving performance <a id="performance"></a></h3>
 <p>There are several options to consider:</p>
 <ul>
@@ -440,7 +440,7 @@ The <code>Source</code> instance used ab
 </ul>
 <p>Of course, the <a href="embedding.html#performance">performance hints from the Embedding page</a> apply here, too.</p>
 <h3 id="accessing-resources-in-your-web-application-wzxhzdk23wzxhzdk24">Accessing resources in your web application <a id="uriresolver"></a></h3>
-<p>Often, you will want to use resources (stylesheets, images etc.) which are bundled with your web application. FOP provides a URIResolver implementation that lets you access files via the Servlet's ServletContext. The class is called <code>org.apache.fop.servlet.ServletContextURIResolver</code> .</p>
+<p>Often, you will want to use resources (stylesheets, images etc.) which are bundled with your web application. FOP provides a URIResolver implementation that lets you access files via the Servlet's ServletContext. The class is called <code>org.apache.fop.servlet.ServletContextURIResolver</code>.</p>
 <p>Here's how to set it up in your servlet. Instantiate a new instance in the servlet's init() method:</p>
 <div class="codehilite"><pre><span class="cm">/** URIResolver for use by this servlet */</span>
 <span class="kd">protected</span> <span class="n">URIResolver</span> <span class="n">uriResolver</span><span class="o">;</span>
@@ -490,7 +490,7 @@ The <code>Source</code> instance used ab
 <p>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:</p>
 <ul>
 <li>
-<p>Use an URL ending in <code>.pdf</code> , like <code>http://myserver/servlet/stuff.pdf</code> . Yes, the servlet can be configured to handle this. If the URL has to contain parameters, try to have <strong>both</strong> the base URL as well as the last parameter end in <code>.pdf</code> , if necessary append a dummy parameter, like <code>http://myserver/servlet/stuff.pdf?par1=a&amp;par2=b&amp;d=.pdf</code> . The effect may depend on IEx version.</p>
+<p>Use an URL ending in <code>.pdf</code>, like <code>http://myserver/servlet/stuff.pdf</code>. Yes, the servlet can be configured to handle this. If the URL has to contain parameters, try to have <strong>both</strong> the base URL as well as the last parameter end in <code>.pdf</code>, if necessary append a dummy parameter, like <code>http://myserver/servlet/stuff.pdf?par1=a&amp;par2=b&amp;d=.pdf</code>. The effect may depend on IEx version.</p>
 </li>
 <li>
 <p>Give IEx the opportunity to cache. In particular, ensure the server does not set any headers causing IEx not to cache the content. This may be a real problem if the document is sent over HTTPS, because most IEx installations will by default <em>not</em> cache any content retrieved over HTTPS. Setting the <code>Expires</code> header entry may help in this case:<br></br> <code>response.setDateHeader("Expires",



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


Mime
View raw message