You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2012/12/05 09:23:58 UTC
svn commit: r840806 [7/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/
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html Wed Dec 5 08:23:47 2012
@@ -344,7 +344,7 @@ $(document).ready(function () {
<div class="section-content"><h1 id="apachewzxhzdk1-fop-intermediate-format">Apache™ FOP: Intermediate Format</h1>
<p>Please note that the intermediate format is an <strong>advanced feature</strong> and can be ignored by most users of Apache™ FOP.</p>
<h2 id="introduction-wzxhzdk3wzxhzdk4">Introduction <a id="introduction"></a></h2>
-<p>The intermediate format (IF) is a proprietary XML format that represents the area tree generated by the layout engine. The area tree is conceptually defined in the <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> . The IF can be generated through the area tree XML Renderer (the XMLRenderer).</p>
+<p>The intermediate format (IF) is a proprietary XML format that represents the area tree generated by the layout engine. The area tree is conceptually defined in the <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>. The IF can be generated through the area tree XML Renderer (the XMLRenderer).</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="usage-of-the-intermediate-format-wzxhzdk5wzxhzdk6">Usage of the Intermediate Format <a id="usage"></a></h2>
<p>As already mentioned, the IF is generated by using the <strong>XMLRenderer</strong> (MIME type: <strong>application/X-fop-areatree</strong> ). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file. However, there is an important detail to consider: The various Renderers don't all use the same font sources. To be able to create the right area tree for the ultimate output file, you need to create the IF file using the right font setup. This is achieved by telling the XMLRenderer to mimic another renderer. This is done by calling the XMLRenderer's mimicRenderer() method with an instance of the ultimate target renderer as the single parameter. This has a consequence: An IF file rendered with the Java2DRenderer may not look as expected when it was actually generated for the PDF renderer. For renderers that use the same font setup, this restriction does not apply (PDF and PS, for example). Generating the inte
rmediate format file is the first step.</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html Wed Dec 5 08:23:47 2012
@@ -343,10 +343,10 @@ $(document).ready(function () {
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/0.95/">0.95</a></div> -->
<div class="section-content"><h1 id="apachewzxhzdk1-fop-metadata">Apache™ 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™ 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="nt"></fo:layout-master-set></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>
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html Wed Dec 5 08:23:47 2012
@@ -348,7 +348,7 @@ $(document).ready(function () {
<h3 id="fonts-wzxhzdk29wzxhzdk30">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-wzxhzdk31wzxhzdk32">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:
@@ -384,9 +384,9 @@ Set the output MIME type to "application
<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-wzxhzdk37wzxhzdk38">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>
@@ -820,7 +820,7 @@ These are some known restrictions compar
</ul>
<h2 id="xml-area-tree-xml-wzxhzdk91wzxhzdk92">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-wzxhzdk93wzxhzdk94">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>
@@ -905,7 +905,7 @@ This format creates an SVG document that
<h2 id="wish-list-wzxhzdk117wzxhzdk118">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/0.95/pdfa.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfa.html Wed Dec 5 08:23:47 2012
@@ -344,7 +344,7 @@ $(document).ready(function () {
<div class="section-content"><h1 id="apachewzxhzdk0-fop-pdfa-iso-19005">Apache™ FOP: PDF/A (ISO 19005)</h1>
<p><authors><person email="jeremias@apache.org" name="Jeremias Märki"></person></authors></p>
<h2 id="overview-wzxhzdk5wzxhzdk6">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&ICS1=37&ICS2=100&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&ICS1=37&ICS2=100&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-wzxhzdk7wzxhzdk8">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>
@@ -390,13 +390,13 @@ Fop fop = fopFactory.newFop(MimeConstant
<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/0.95/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html Wed Dec 5 08:23:47 2012
@@ -351,7 +351,7 @@ $(document).ready(function () {
<p>An owner password is set with the <code>-o</code> option. This password is actually used as encryption key. Many tools for PDF processing ask for this password to disregard any restriction imposed on the PDF document.</p>
<p>If no owner password has been supplied but FOP was asked to apply some restrictions, a random password is used. In this case it is obviously impossiible to disregard restrictions in PDF processing tools.</p>
<p>A user password, supplied with the <code>-u</code> option, will cause the PDF display software to ask the reader for this password in order to view the contents of the document. If no user password was supplied, viewing the content is not restricted.</p>
-<p>Further restrictions can be imposed by using the <code>-noprint</code> , <code>-nocopy</code> , <code>-noedit</code> and <code>-noannotations</code> options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.</p>
+<p>Further restrictions can be imposed by using the <code>-noprint</code>, <code>-nocopy</code>, <code>-noedit</code> and <code>-noannotations</code> options, which disable printing, copying text, editing in Adobe Acrobat and making annotations, respectively.</p>
<h2 id="usage-embedded-wzxhzdk13wzxhzdk14">Usage (embedded) <a id="Usage+%28embedded%29"></a></h2>
<p>When FOP is embedded in another Java application you need to set an options map on the renderer. These are the supported options:</p>
<table>
@@ -473,15 +473,15 @@ $(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>
<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/0.95/pdfx.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfx.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/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-wzxhzdk5wzxhzdk6">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&ICS1=37&ICS2=100&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&ICS1=37&ICS2=100&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-wzxhzdk9wzxhzdk10">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/0.95/releaseNotes_0.95.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html Wed Dec 5 08:23:47 2012
@@ -355,28 +355,25 @@ Besides the important changes listed bel
<p>Performance improvements and memory optimizations for the property handling in the FO tree.</p>
</li>
</ul>
-<p>Please note that with this release, we've dropped support for Java 1.3. FOP will, from now on, <strong>require at least Java 1.4</strong> .</p>
+<p>Please note that with this release, we've dropped support for Java 1.3. FOP will, from now on, <strong>require at least Java 1.4</strong>.</p>
<p>There have been a few changes in tables that make FOP both more strict and more compliant to the Recommendation:</p>
<ul>
-<li>
-<p>XSL-FO 1.1 explicitly states that a row-spanning fo:table-cell element is not allowed to span further than its enclosing fo:table-header/footer/body element (see bottom of <a href="http://www.w3.org/TR/xsl11/#fo_table">section 6.7.3</a> ). From now on FOP will give a validation error if a document contains such an erroneous cell.</p>
-</li>
-<li>
-<p>If an fo:table element contains explicit fo:table-column children, then those elements set the total number of columns in the table. This means that a validation error will now occur if a row contains more cells than available columns. This change allows to improve performance, since the rendering of the table may start as soon as the table-column elements have been parsed.</p>
-</li>
+<li>XSL-FO 1.1 explicitly states that a row-spanning fo:table-cell element is not allowed to span further than its enclosing fo:table-header/footer/body element (see bottom of <a href="http://www.w3.org/TR/xsl11/#fo_table">section 6.7.3</a> ). From now on FOP will give a validation error if a document contains such an erroneous cell.</li>
</ul>
+<p>-
+If an fo:table element contains explicit fo:table-column children, then those elements set the total number of columns in the table. This means that a validation error will now occur if a row contains more cells than available columns. This change allows to improve performance, since the rendering of the table may start as soon as the table-column elements have been parsed.</p>
<p>If more flexibility is needed, then the fo:table-column elements may be just omitted. The final number of columns will then be set by the row that has the most cells.</p>
<p>The image libraries Jimi and JAI are no longer needed (and used) for image loading. Instead we rely completely on the Image I/O API that has been introduced with Java 1.4. If you still need support for bitmap image formats that do not work out-of-the-box, we recommend adding <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> (an Image I/O compatible image codec package) to the classpath. JAI is still required for building the FOP distribution but it is optional for normal builds and at run-time.
-This final 0.95 release also includes all of the <a href="changes_0.95beta.html">changes made for Apache FOP 0.95beta</a> .</section></notes></p>
+This final 0.95 release also includes all of the <a href="changes_0.95beta.html">changes made for Apache FOP 0.95beta</a>.</section></notes></p>
<h1 id="major-changes-in-version-095-wzxhzdk4wzxhzdk5">Major Changes in Version 0.95 <a id="version_0.95"></a></h1>
-<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_0.95.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_0.95.html">is available</a>.</p>
<h2 id="changes-to-the-code-base-wzxhzdk6wzxhzdk7">Changes to the Code Base <a id="Changes+to+the+Code+Base"></a></h2>
<ul>
-<li><img alt="fix" src="/images/fix.jpg" />Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44887">44887</a> .</li>
+<li><img alt="fix" src="/images/fix.jpg" />Fixed potential multi-threading problem concerning the use of DecimalFormat. Committed by JM. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44887">44887</a>.</li>
</ul>
<h3 id="changes-to-the-layout-engine-wzxhzdk8wzxhzdk9">Changes to the Layout Engine <a id="Changes+to+the+Layout+Engine"></a></h3>
<ul>
-<li><img alt="fix" src="/images/fix.jpg" />Various bugfixes for table layout. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44621">44621</a> .</li>
+<li><img alt="fix" src="/images/fix.jpg" />Various bugfixes for table layout. Committed by VH. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=44621">44621</a>.</li>
</ul>
<h3 id="changes-to-renderers-output-formats-wzxhzdk10wzxhzdk11">Changes to Renderers (Output Formats) <a id="Changes+to+Renderers+%28Output+Formats%29"></a></h3>
<ul>
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html Wed Dec 5 08:23:47 2012
@@ -355,19 +355,19 @@ $(document).ready(function () {
<p>Apache™ 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"><outfile></span>
<span class="p">[</span><span class="n">OPTIONS</span><span class="p">]</span>
@@ -467,26 +467,26 @@ $(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 <CLASSPATH>
- org.apache.fop.cli.Main <arguments></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 <CLASSPATH>
+ org.apache.fop.cli.Main <arguments></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 <arguments></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 <arguments></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
- <arguments></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>
+ <arguments></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>
+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>
@@ -507,7 +507,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/0.95/servlets.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/servlets.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/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&par2=b&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&par2=b&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",
Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/upgrading.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/upgrading.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/upgrading.html Wed Dec 5 08:23:47 2012
@@ -346,10 +346,10 @@ $(document).ready(function () {
<p>If you're planning to upgrade to the latest Apache™ FOP version there are a few very important things to consider:</p>
<ul>
<li>
-<p>More than half of the codebase has been rewritten over the last four years. With version 0.93 the code has reached <strong>production level</strong> , and continues to improve with version 0.94 and 0.95.</p>
+<p>More than half of the codebase has been rewritten over the last four years. With version 0.93 the code has reached <strong>production level</strong>, and continues to improve with version 0.94 and 0.95.</p>
</li>
<li>
-<p>The API of FOP has changed considerably and is not backwards-compatible with versions 0.20.5 and 0.91beta. Version 0.92 introduced the <strong>new stable API</strong> .</p>
+<p>The API of FOP has changed considerably and is not backwards-compatible with versions 0.20.5 and 0.91beta. Version 0.92 introduced the <strong>new stable API</strong>.</p>
</li>
<li>
<p>Since version 0.92 some deprecated methods which were part of the old API have been removed. If you upgrade from 0.91 beta, you will need to adjust your Java code. Similarly if you upgrade from 0.92 and use deprecated methods.</p>
@@ -360,10 +360,11 @@ $(document).ready(function () {
<li>
<p>Beginning with version 0.94 you can skip the generation of font metric files and remove the "font-metrics" attribute in the font configuration. The font metrics files are, for the moment, still required if you use a TrueType Collection (*.ttc) and in that case you need to regenerate the font metrics file if yours are from a FOP version before 0.93.</p>
</li>
-<li>
-<p>The new code is much more strict about the interpretation of the XSL-FO 1.1 specification. Things that worked fine in version 0.20.5 might start to produce warnings or even errors now. FOP 0.20.5 contains many bugs which have been corrected in the new code.
-While FOP 0.20.5 allowed you to have empty <code>fo:table-cell</code> elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element ( <code>(%block;)+</code> , see <a href="http://www.w3.org/TR/xsl/#fo_table-cell">XSL-FO 1.1, 6.7.10</a> ) inside an <code>fo:table-cell</code> element.</p>
-</li>
+</ul>
+<p>-
+The new code is much more strict about the interpretation of the XSL-FO 1.1 specification. Things that worked fine in version 0.20.5 might start to produce warnings or even errors now. FOP 0.20.5 contains many bugs which have been corrected in the new code.
+While FOP 0.20.5 allowed you to have empty <code>fo:table-cell</code> elements, the new code will complain about that (unless relaxed validation is enabled) because the specification demands at least one block-level element ( <code>(%block;)+</code>, see <a href="http://www.w3.org/TR/xsl/#fo_table-cell">XSL-FO 1.1, 6.7.10</a> ) inside an <code>fo:table-cell</code> element.</p>
+<ul>
<li>
<p>Extensions and Renderers written for version 0.20.5 will not work with the new code! The new FOP extension for <a href="http://barcode4j.sourceforge.net">Barcode4J</a> is available since January 2007.</p>
</li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/accessibility.html Wed Dec 5 08:23:47 2012
@@ -394,7 +394,7 @@ The processing of the logical structure
<p>It's currently not possible to specify the expanded form of an abbreviation or acronym.</p>
</li>
<li>
-<p>SVG graphics (or images in general) are treated as a single figure. Text contained in SVGs is not accessible. It's only possible to work with <code>fox:alt-text</code> .</p>
+<p>SVG graphics (or images in general) are treated as a single figure. Text contained in SVGs is not accessible. It's only possible to work with <code>fox:alt-text</code>.</p>
</li>
<li>
<p>The side regions (region-before, region-after etc.) are currently not specially identified. Screen readers may read their content at page changes.</p>
@@ -404,22 +404,22 @@ The processing of the logical structure
<p>Many resources providing guidance about creating accessible documents can be found on the web. Here are a few links, along with additional resources around the topic:</p>
<ul>
<li>
-<p><a href="http://www.section508.gov/">US Government - Website on Section 508</a> </p>
+<p><a href="http://www.section508.gov/">US Government - Website on Section 508</a></p>
</li>
<li>
-<p><a href="http://en.wikipedia.org/wiki/Accessibility">Wikipedia on Accessibility in general</a> </p>
+<p><a href="http://en.wikipedia.org/wiki/Accessibility">Wikipedia on Accessibility in general</a></p>
</li>
<li>
-<p><a href="http://en.wikipedia.org/wiki/Portable_Document_Format#Accessibility">Wikipedia on Accessibility in PDF</a> </p>
+<p><a href="http://en.wikipedia.org/wiki/Portable_Document_Format#Accessibility">Wikipedia on Accessibility in PDF</a></p>
</li>
<li>
<p><a href="http://partners.adobe.com/public/developer/en/pdf/PDFReference.pdf">PDF Reference 1.4</a> (look up chapters 9.7 "Tagged PDF" and 9.8 "Accessibility Support")</p>
</li>
<li>
-<p><a href="pdfa.html">PDF/A support in Apache FOP</a> </p>
+<p><a href="pdfa.html">PDF/A support in Apache FOP</a></p>
</li>
<li>
-<p><a href="http://wiki.apache.org/xmlgraphics-fop/PDF_Accessibility">Developer-oriented details on the accessibility features (on the Wiki)</a> </p>
+<p><a href="http://wiki.apache.org/xmlgraphics-fop/PDF_Accessibility">Developer-oriented details on the accessibility features (on the Wiki)</a></p>
</li>
</ul></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/anttask.html Wed Dec 5 08:23:47 2012
@@ -397,7 +397,7 @@ $(document).ready(function () {
</tr>
<tr>
<td>format</td>
-<td>Possible output formats:<br></br> <code>application/X-fop-awt-preview</code> <br></br> <code>application/X-fop-print</code> <br></br> <code>application/X-fop-areatree</code> <br></br> <code>application/pdf</code> <br></br> <code>application/postscript</code> <br></br> <code>application/mif</code> <br></br> <code>application/rtf</code> , <code>text/richtext</code> , <code>text/rtf</code> <br></br> <code>application/x-pcl</code> , <code>application/vnd.hp-PCL</code> <br></br> <code>application/x-afp</code> , <code>application/vnd.ibm.modcap</code> <br></br> <code>text/plain</code> <br></br> <code>image/svg+xml</code> <br></br> <code>image/gif</code> <br></br> <code>image/png</code> <br></br> <code>image/tiff</code> <br></br></td>
+<td>Possible output formats:<br></br> <code>application/X-fop-awt-preview</code> <br></br> <code>application/X-fop-print</code> <br></br> <code>application/X-fop-areatree</code> <br></br> <code>application/pdf</code> <br></br> <code>application/postscript</code> <br></br> <code>application/mif</code> <br></br> <code>application/rtf</code>, <code>text/richtext</code>, <code>text/rtf</code> <br></br> <code>application/x-pcl</code>, <code>application/vnd.hp-PCL</code> <br></br> <code>application/x-afp</code>, <code>application/vnd.ibm.modcap</code> <br></br> <code>text/plain</code> <br></br> <code>image/svg+xml</code> <br></br> <code>image/gif</code> <br></br> <code>image/png</code> <br></br> <code>image/tiff</code> <br></br></td>
<td>No, defaults to <code>application/pdf</code></td>
</tr>
<tr>
@@ -418,7 +418,7 @@ $(document).ready(function () {
<tr>
<td>relativebase</td>
<td>For fileset usage only. A value of <code>true</code> specifies using the location of each .fo file as the base directory for resolving relative file references located within that .fo file. A value of <code>false</code> specifies using the value of basedir for all files within the fileset, or just the current working directory if basedir is not specified.</td>
-<td>No, default is <code>false</code> .</td>
+<td>No, default is <code>false</code>.</td>
</tr>
<tr>
<td>userconfig</td>
@@ -427,7 +427,7 @@ $(document).ready(function () {
</tr>
<tr>
<td>messagelevel</td>
-<td>Logging level<br></br>Possible values: <code>error</code> , <code>warn</code> , <code>info</code> , <code>verbose</code> , <code>debug</code> . <strong>Currently doesn't work in FOP Trunk!!!</strong></td>
+<td>Logging level<br></br>Possible values: <code>error</code>, <code>warn</code>, <code>info</code>, <code>verbose</code>, <code>debug</code>. <strong>Currently doesn't work in FOP Trunk!!!</strong></td>
<td>No, defaults to <code>verbose</code></td>
</tr>
<tr>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org