xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r841677 [2/2] - in /websites/staging/xmlgraphics/trunk/content: ./ batik/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Tue, 11 Dec 2012 12:12:29 GMT
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 Tue Dec 11 12:12:25 2012
@@ -351,14 +351,15 @@ $(document).ready(function () {
 <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>
+<p>Produce an IF file: <code>fop -fo myfile.fo -at application/pdf myfile.at.xml</code></p>
+<p>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>
 </li>
 <li>
 <p>Render to a PDF file: <code>fop -atin myfile.at.xml -pdf myfile.pdf</code></p>
 </li>
 <li>
 <p>Render to a Java2D-based renderer:</p>
-</li>
+<ul>
 <li>
 <p><code>fop -atin myfile.at.xml -print</code></p>
 </li>
@@ -368,6 +369,8 @@ $(document).ready(function () {
 <li>
 <p><code>fop -atin myfile.at.xml -tiff myfile.tiff</code></p>
 </li>
+</ul>
+</li>
 </ol>
 <h3 id="general-direct-output">Output to a Printer or Other Device</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>

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 Tue Dec 11 12:12:25 2012
@@ -580,7 +580,9 @@ then you don't have the needed infrastru
 <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</p>
+<p><code>security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider</code>,</p>
+<p>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/servlets.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/servlets.html Tue Dec 11 12:12:25 2012
@@ -493,9 +493,9 @@ The <code>Source</code> instance used ab
 <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",
-          System.currentTimeMillis() + cacheExpiringDuration *
-          1000);</code> <br></br>Consult your server manual and the relevant RFCs for further details on HTTP headers and caching.</p>
+<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:</p>
+<p><code>response.setDateHeader("Expires", System.currentTimeMillis() + cacheExpiringDuration * 1000);</code></p>
+<p>Consult your server manual and the relevant RFCs for further details on HTTP headers and caching.</p>
 </li>
 <li>
 <p>Cache in the server. It may help to include a parameter in the URL which has a timestamp as the value min order to decide whether a request is repeated. IEx is reported to retrieve a document up to three times, but never more often.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/changes.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/changes.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/changes.html Tue Dec 11 12:12:25 2012
@@ -691,8 +691,10 @@ $(document).ready(function () {
 </ul>
 <h3 id="contributors_FOP Trunk">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Andreas Delmelle (AD), Chris Bowditch (CB), Glenn Adams (GA), Jeremias Märki (JM), Mehdi Houshmand (MH), Peter Hancock (PH), (PH,VH), Simon Pepping (SP), Vincent Hennebert (VH).</p>
-<p>This is a list of other contributors:<br></br>Adrian Buza, Alberto Simões, Alexandros Papadakis, Alexios Giotis, Alexis Giotis, Andrejus Chaliapinas, Armin Haaf, Carsten Pfeiffer, Georg Datterl, Glenn Adams, JM, Mehdi Houshmand, Joshua Marquart, Julien Aymé, Luis Bernardo, Martin Koegler, Matthias Reischenbacher, Max Aster, Maximilian Aster, Mehdi Houshmand, Melanie Drake, mkoegler.AT.auto.tuwien.ac.at, Pascal Sancho, Patrick Jaromin, Paul Huemer, Peter Hancock, Sergey Vladimirov, Simon Pepping, VH and PH.</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>Adrian Cumiskey (AC), Andreas Delmelle (AD), Chris Bowditch (CB), Glenn Adams (GA), Jeremias Märki (JM), Mehdi Houshmand (MH), Peter Hancock (PH), (PH,VH), Simon Pepping (SP), Vincent Hennebert (VH).</p>
+<p>This is a list of other contributors:</p>
+<p>Adrian Buza, Alberto Simões, Alexandros Papadakis, Alexios Giotis, Alexis Giotis, Andrejus Chaliapinas, Armin Haaf, Carsten Pfeiffer, Georg Datterl, Glenn Adams, JM, Mehdi Houshmand, Joshua Marquart, Julien Aymé, Luis Bernardo, Martin Koegler, Matthias Reischenbacher, Max Aster, Maximilian Aster, Mehdi Houshmand, Melanie Drake, mkoegler.AT.auto.tuwien.ac.at, Pascal Sancho, Patrick Jaromin, Paul Huemer, Peter Hancock, Sergey Vladimirov, Simon Pepping, VH and PH.</p>
 <h2 id="version_1.0">Version 1.0 (21 July 2010)</h2>
 <h3 id="API_1.0">Changes to the End-User API</h3>
 <ul>
@@ -1139,8 +1141,10 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_1.0">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Andreas Delmelle (AD), Chris Bowditch (CB), Jeremias Märki (JM), (JM,VH), Luca Furini (LF), Max Berger (MB), Simon Pepping (SP), Vincent Hennebert (VH).</p>
-<p>This is a list of other contributors:<br></br>Alexander Stamenov, Alok Singh, Antti Karanta, Bharat Attaluri, Carsten Siedentop, D.W. Harks, Dario Laera, Emil Maskovsky, Francois Fernandes, Georg Datterl, Harald G. Henne, J. Frantzius, Jason Harrop, Jonathan Levinson, Jost Klopfstein, Martin Edge, Maxim Wirt, Nicolas Peninguy, Pavel Kysilka, Peter Coppens, Peter Hancock, Richard Wheeldon, rogov.AT.devexperts.com, Thomas Stieler, Tow Browder, Venkat Reddy, Yegor Kozlov.</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>Adrian Cumiskey (AC), Andreas Delmelle (AD), Chris Bowditch (CB), Jeremias Märki (JM), (JM,VH), Luca Furini (LF), Max Berger (MB), Simon Pepping (SP), Vincent Hennebert (VH).</p>
+<p>This is a list of other contributors:</p>
+<p>Alexander Stamenov, Alok Singh, Antti Karanta, Bharat Attaluri, Carsten Siedentop, D.W. Harks, Dario Laera, Emil Maskovsky, Francois Fernandes, Georg Datterl, Harald G. Henne, J. Frantzius, Jason Harrop, Jonathan Levinson, Jost Klopfstein, Martin Edge, Maxim Wirt, Nicolas Peninguy, Pavel Kysilka, Peter Coppens, Peter Hancock, Richard Wheeldon, rogov.AT.devexperts.com, Thomas Stieler, Tow Browder, Venkat Reddy, Yegor Kozlov.</p>
 <h2 id="version_0.95">Version 0.95 (05 August 2008)</h2>
 <h3 id="API_0.95">Changes to the End-User API</h3>
 <ul>
@@ -1215,8 +1219,10 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_0.95">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Jeremias Märki (JM), Vincent Hennebert (VH).</p>
-<p>This is a list of other contributors:<br></br>Maximilian Aster.</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>Andreas Delmelle (AD), Jeremias Märki (JM), Vincent Hennebert (VH).</p>
+<p>This is a list of other contributors:</p>
+<p>Maximilian Aster.</p>
 <h2 id="version_0.95beta">Version 0.95beta (26 March 2008)</h2>
 <h3 id="API_0.95beta">Changes to the End-User API</h3>
 <ul>
@@ -1409,10 +1415,22 @@ Committed by AD.</p>
 <p>![fix" src="images/fix.jpg)Fixed erroneous usage of inherited color-values in SVG. Committed by AD. Thanks to ckohrn.at.tng.de. See Issue <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=43274">43274</a>.</p>
 </li>
 <li>
-<p>![update" src="images/update.jpg)Facilitate the implementation for font-selection-strategy:<br></br>• Changed FontInfo.fontLookup to always return an array of FontTriplet.<br></br>• Changed CommonFont.getFontState to return an array of FontTriplet.<br></br>• Initial modifications to the related LMs: initialized with the font corresponding to the first of the triplets.<br></br>Committed by AD.</p>
+<p>![update" src="images/update.jpg)Facilitate the implementation for font-selection-strategy:</p>
+<ul>
+<li>Changed FontInfo.fontLookup to always return an array of FontTriplet.</li>
+<li>Changed CommonFont.getFontState to return an array of FontTriplet.</li>
+<li>Initial modifications to the related LMs: initialized with the font corresponding to the first of the triplets.</li>
+</ul>
+<p>Committed by AD.</p>
 </li>
 <li>
-<p>![update" src="images/update.jpg)PropertyCache phase 2:<br></br>• improvement of the PropertyCache itself should now guarantee acceptable performance of the static caches in multi-session environments, which is a possible problem with synchronizedMap.<br></br>• changed CommonFont to use the cache: added CachedCommonFont to contain the properties that are always cacheable CommonFont itself is only cached if the remaining properties are absolutes.<br></br>• changed CommonHyphenation, KeepProperty, ColorProperty and FontFamilyProperty to use the cache.<br></br>Committed by AD.</p>
+<p>![update" src="images/update.jpg)PropertyCache phase 2:</p>
+<ul>
+<li>improvement of the PropertyCache itself should now guarantee acceptable performance of the static caches in multi-session environments, which is a possible problem with synchronizedMap.</li>
+<li>changed CommonFont to use the cache: added CachedCommonFont to contain the properties that are always cacheable CommonFont itself is only cached if the remaining properties are absolutes.</li>
+<li>changed CommonHyphenation, KeepProperty, ColorProperty and FontFamilyProperty to use the cache.</li>
+</ul>
+<p>Committed by AD.</p>
 </li>
 </ul>
 <h3 id="Renderers_0.95beta">Changes to Renderers (Output Formats)</h3>
@@ -1477,8 +1495,10 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_0.95beta">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>Adrian Cumiskey (AC), Andreas Delmelle (AD), Jeremias Märki (JM), Max Berger (MB), Vincent Hennebert (VH).</p>
-<p>This is a list of other contributors:<br></br>Adrian Cumiskey, Andrejus Chaliapinas, Bruno Feurer, ckohrn.at.tng.de, David Churavy, David Delbecq, Gordon Cooke, Justus Piater, Max Berger, Patrick Jaromin, Stefan Ziel, V. Schappert.</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>Adrian Cumiskey (AC), Andreas Delmelle (AD), Jeremias Märki (JM), Max Berger (MB), Vincent Hennebert (VH).</p>
+<p>This is a list of other contributors:</p>
+<p>Adrian Cumiskey, Andrejus Chaliapinas, Bruno Feurer, ckohrn.at.tng.de, David Churavy, David Delbecq, Gordon Cooke, Justus Piater, Max Berger, Patrick Jaromin, Stefan Ziel, V. Schappert.</p>
 <h2 id="version_0.94">Version 0.94 (24th August 2007)</h2>
 <h3 id="Code_0.94">Changes to the Code Base</h3>
 <ul>
@@ -1605,8 +1625,10 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_0.94">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Jay Bryant (JB), Jeremias Märki (JM), Luca Furini (LF), Manuel Mall (MM), Simon Pepping (SP), Vincent Hennebert (VH), (VH, JM).</p>
-<p>This is a list of other contributors:<br></br>Adrian Cumiskey, Erwin Tratar, Hussein Shafie, Martin Kögler, Max Berger, Paul Vinkenoog, Richard Wheeldon.</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>Andreas Delmelle (AD), Jay Bryant (JB), Jeremias Märki (JM), Luca Furini (LF), Manuel Mall (MM), Simon Pepping (SP), Vincent Hennebert (VH), (VH, JM).</p>
+<p>This is a list of other contributors:</p>
+<p>Adrian Cumiskey, Erwin Tratar, Hussein Shafie, Martin Kögler, Max Berger, Paul Vinkenoog, Richard Wheeldon.</p>
 <h2 id="version_0.93">Version 0.93 (9 January 2007)</h2>
 <h3 id="Code_0.93">Changes to the Code Base</h3>
 <ul>
@@ -1790,8 +1812,10 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_0.93">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Bertrand Delacrétaz (BD), Jeremias Märki (JM), Manuel Mall (MM), Simon Pepping (SP).</p>
-<p>This is a list of other contributors:<br></br>Adam Strzelecki, Victor Mote, Dominic Brügger, Gary Reed, Gerhard Oettl, Gilles Beaugeais, Igor Istomin, Jeroen Meijer, Julien Aymé, Max Berger, Oliver Hernàndez Valls, Peter Coppens, Pierre-Henri Kraus, Richard Wheeldon.</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>Andreas Delmelle (AD), Bertrand Delacrétaz (BD), Jeremias Märki (JM), Manuel Mall (MM), Simon Pepping (SP).</p>
+<p>This is a list of other contributors:</p>
+<p>Adam Strzelecki, Victor Mote, Dominic Brügger, Gary Reed, Gerhard Oettl, Gilles Beaugeais, Igor Istomin, Jeroen Meijer, Julien Aymé, Max Berger, Oliver Hernàndez Valls, Peter Coppens, Pierre-Henri Kraus, Richard Wheeldon.</p>
 <h2 id="version_0.92beta">Version 0.92beta (18 Apr 2006)</h2>
 <h3 id="Code_0.92beta">Changes to the Code Base</h3>
 <ul>
@@ -1951,8 +1975,10 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_0.92beta">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>Andreas Delmelle (AD), Jeremias Märki (JM), Luca Furini (LF), Manuel Mall (MM), Simon Pepping (SP).</p>
-<p>This is a list of other contributors:<br></br>Gerhard Oettl, Gerhard Oettl (gerhard.oettl.at.oesoft.at), Jirí Mareš, Max Berger, Richard Wheeldon.</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>Andreas Delmelle (AD), Jeremias Märki (JM), Luca Furini (LF), Manuel Mall (MM), Simon Pepping (SP).</p>
+<p>This is a list of other contributors:</p>
+<p>Gerhard Oettl, Gerhard Oettl (gerhard.oettl.at.oesoft.at), Jirí Mareš, Max Berger, Richard Wheeldon.</p>
 <h2 id="version_0.91beta">Version 0.91beta (23 Dec 2005)</h2>
 <h3 id="Code_0.91beta">Changes to the Code Base</h3>
 <ul>
@@ -2067,8 +2093,10 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_0.91beta">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>Jeremias Märki (JM), (LF, MM), Manuel Mall (MM).</p>
-<p>This is a list of other contributors:<br></br>Tom Craddock.</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>Jeremias Märki (JM), (LF, MM), Manuel Mall (MM).</p>
+<p>This is a list of other contributors:</p>
+<p>Tom Craddock.</p>
 <h2 id="version_0.90alpha1">Version 0.90alpha1 (22 Nov 2005)</h2>
 <h3 id="Code_0.90alpha1">Changes to the Code Base</h3>
 <ul>
@@ -2076,7 +2104,8 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_0.90alpha1">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>the FOP committers (all).</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>the FOP committers (all).</p>
 <h2 id="version_0.20.5">Version 0.20.5 (18 July 2003)</h2>
 <h3 id="Code_0.20.5">Changes to the Code Base</h3>
 <ul>
@@ -2084,7 +2113,8 @@ Committed by AD.</p>
 </ul>
 <h3 id="contributors_0.20.5">Contributors to this release</h3>
 <p>We thank the following people for their contributions to this release.</p>
-<p>This is a list of all people who participated as committers:<br></br>the FOP committers (all).</p>
+<p>This is a list of all people who participated as committers:</p>
+<p>the FOP committers (all).</p>
 <h2 id="all-committers">All Committers</h2>
 <p>This is a list of all people who have ever participated as committers on this project.</p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html Tue Dec 11 12:12:25 2012
@@ -343,7 +343,8 @@ $(document).ready(function () {
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/design/">Design</a></div> -->
       	<div class="section-content"><h1 id="apachewzxhzdk0-fop-design-images">Apache&trade; FOP Design: Images</h1>
 <h2 id="intro">Introduction</h2>
-<p>Images may only be needed to be loaded when the image is rendered to the output or to find the dimensions.<br></br>An image url may be invalid, this can be costly to find out so we need to keep a list of invalid image urls.</p>
+<p>Images may only be needed to be loaded when the image is rendered to the output or to find the dimensions.</p>
+<p>An image url may be invalid, this can be costly to find out so we need to keep a list of invalid image urls.</p>
 <p>We have a number of different caching schemes that are possible.</p>
 <p>All images are referred to using the url given in the XSL:FO after removing "url('')" wrapping. This does not include any sort of resolving such as relative -&gt; absolute. The external graphic in the FO Tree and the image area in the Area Tree only have the url as a reference. The images are handled through a static interface in ImageFactory.</p>
 <h2 id="Threading">Threading</h2>
@@ -357,7 +358,8 @@ $(document).ready(function () {
 <p>If images are to be used commonly then we cannot dispose of data in the FopImage when cached by the renderer. Also if different contexts have different base directories for resolving relative url's then the loading and caching must be separate. We can have a cache that shares images among all contexts or only loads an image for a context.</p>
 <p>The cache uses an image loader so that it can synchronize the image loading on an image by image basis. Finding and adding an image loader to the cache is also synchronized to prevent thread problems.</p>
 <h2 id="Invalid-Images">Invalid Images</h2>
-<p>If an image cannot be loaded for some reason, for example the url is invalid or the image data is corrupt or an unknown type. Then it should only attempt to load the image once. All other attempts to get the image should return null so that it can be easily handled.<br></br>This will prevent any extra processing or waiting.</p>
+<p>If an image cannot be loaded for some reason, for example the url is invalid or the image data is corrupt or an unknown type. Then it should only attempt to load the image once. All other attempts to get the image should return null so that it can be easily handled.</p>
+<p>This will prevent any extra processing or waiting.</p>
 <h2 id="Reading">Reading</h2>
 <p>Once a stream is opened for the image url then a set of image readers is used to determine what type of image it is. The reader can peek at the image header or if necessary load the image. The reader can also get the image size at this stage. The reader then can provide the mime type to create the image object to load the rest of the information.</p>
 <h2 id="Data">Data</h2>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/properties.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/properties.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/properties.html Tue Dec 11 12:12:25 2012
@@ -428,7 +428,9 @@ $(document).ready(function () {
 <h2 id="property-list-struct">Structure of the PropertyList</h2>
 <p>The PropertyList extends HashMap and its basic function is to associate Property value objects with Property names. The Property objects are all subclasses of the base Property class. Each one simply contains a reference to one of the property datatype objects. Property provides accessors for all known datatypes and various subclasses override the accessor(s) which are reasonable for the datatype they store.</p>
 <p>The PropertyList itself provides various ways of looking up Property values to handle such issues as inheritance and corresponding properties.</p>
-<p>The main logic is:<br></br>If the property is a writing-mode relative property (using start, end, before or after in its name), the corresponding absolute property value is returned if it's explicitly set on this FO.<br></br>Otherwise, the writing-mode relative value is returned if it's explicitly set. If the property is inherited, the process repeats using the PropertyList of the FO's parent object. (This is easy because each PropertyList points to the PropertyList of the nearest ancestor FO.) If the property isn't inherited or no value is found at any level, the initial value is returned.</p>
+<p>The main logic is:
+If the property is a writing-mode relative property (using start, end, before or after in its name), the corresponding absolute property value is returned if it's explicitly set on this FO.</p>
+<p>Otherwise, the writing-mode relative value is returned if it's explicitly set. If the property is inherited, the process repeats using the PropertyList of the FO's parent object. (This is easy because each PropertyList points to the PropertyList of the nearest ancestor FO.) If the property isn't inherited or no value is found at any level, the initial value is returned.</p>
 <h2 id="property-spec">Implementing Standard Properties</h2>
 <p>Because the properties defined in the standard are basically static, FOP currently builds the source code for the related Property classes from an XML data file. All properties are specified in src/codegen/foproperties.xml. The related classes are created automatically during the build process by applying an XSLT stylesheet to the foproperties.xml file.</p>
 <h3 id="generic">Generic properties</h3>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html Tue Dec 11 12:12:25 2012
@@ -427,13 +427,16 @@ You will need Acrobat 5.0 to see transpa
 <p>These are the relevant classes, found in the package org.apache.fop.svg:</p>
 <ul>
 <li>
-<p><em>PDFGraphics2D</em> <br></br>used for drawing onto a Graphics2D into an existing pdf document, used internally to draw the svg.</p>
+<p><em>PDFGraphics2D</em></p>
+<p>used for drawing onto a Graphics2D into an existing pdf document, used internally to draw the svg.</p>
 </li>
 <li>
-<p><em>PDFDocumentGraphics2D</em> <br></br>used to create a pdf document and inherits from PDFGraphics2D to do the rest of the drawing. Used by the transcoder to create a standalone pdf document from an svg. Can be used independantly the same as any Graphics2D.</p>
+<p><em>PDFDocumentGraphics2D</em></p>
+<p>used to create a pdf document and inherits from PDFGraphics2D to do the rest of the drawing. Used by the transcoder to create a standalone pdf document from an svg. Can be used independantly the same as any Graphics2D.</p>
 </li>
 <li>
-<p><em>PDFTranscoder</em> <br></br>used by Batik to transcode an svg document into a standalone pdf, via PDFDocumentGraphics2D.</p>
+<p><em>PDFTranscoder</em></p>
+<p>used by Batik to transcode an svg document into a standalone pdf, via PDFDocumentGraphics2D.</p>
 </li>
 </ul>
 <h3 id="Ideas">Ideas</h3>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html Tue Dec 11 12:12:25 2012
@@ -373,7 +373,9 @@ $(document).ready(function () {
 <p>If you have a test which you think would be useful you should supply the test and a diff to the appropriate test suite xml file. Make sure that the test works as would be expected against the current build.</p>
 <h3 id="How-Testing-Works">How Testing Works</h3>
 <p>The tests are stored in the "<svn_repository>/test" directory.</p>
-<p>You can run the tests by specifying the build target "test" ie:<br></br> <code>ant.sh test</code> (Unix)<br></br> <code>ant test</code> (Windows)<br></br></p>
+<p>You can run the tests by specifying the build target "test" ie:</p>
+<p><code>ant.sh test</code> (Unix)</p>
+<p><code>ant test</code> (Windows)</p>
 <p>This will then compare the current code in the local src directory to a specified release of FOP. Any differences between the current code and the output from the reference version will be reported. If the test previously passed then the test run will have failed.</p>
 <p>The testing is done by reading a test suite xml file, which corresponds to the standard testsuite.dtd supplied from w3c. This xml file contains a test xml file and an xsl file (which may simply copy the file). It also contains information such as if the test has passed and any comments.</p>
 <p>For FOP the testing is done by rendering all the testing documents using the XML renderer. The XML files are then compared to see if there are any differences.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html Tue Dec 11 12:12:25 2012
@@ -396,7 +396,8 @@ $(document).ready(function () {
 <p>Run: <code>svn up</code> to make sure the diff is created against the latest sources.</p>
 </li>
 <li>
-<p>Run: <code>svn diff &gt;mypatch.diff</code> <br></br>This will write the patch to the file "mypatch.diff".</p>
+<p>Run: <code>svn diff &gt;mypatch.diff</code></p>
+<p>This will write the patch to the file "mypatch.diff".</p>
 </li>
 <li>
 <p>If you are running TortoiseSVN, you can select "Create Patch..." in the TortoiseSVN context menu.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/download.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/download.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/download.html Tue Dec 11 12:12:25 2012
@@ -381,7 +381,8 @@ $(document).ready(function () {
 <p><em>Main Repository:</em> <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/">http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/</a>
 <em>European Mirror:</em> <a href="http://svn.eu.apache.org/repos/asf/xmlgraphics/fop/trunk/">http://svn.eu.apache.org/repos/asf/xmlgraphics/fop/trunk/</a></p>
 <h4 id="web-view">Web View</h4>
-<p><em>Main Repository:</em> <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/">http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/</a> <br></br>European Mirror: <a href="http://svn.eu.apache.org/viewvc/xmlgraphics/fop/trunk/">http://svn.eu.apache.org/viewvc/xmlgraphics/fop/trunk/</a></p>
+<p><em>Main Repository:</em> <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/">http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/</a></p>
+<p>European Mirror: <a href="http://svn.eu.apache.org/viewvc/xmlgraphics/fop/trunk/">http://svn.eu.apache.org/viewvc/xmlgraphics/fop/trunk/</a></p>
 <p>With any source distribution, you will need to build FOP from the source files. For details please see the "Build" page on the documentation tab for the version you've downloaded.</p>
 <h2 id="archives">Archive Download</h2>
 <p>FOP Archive distributions are linked from the upper portion of the Apache FOP Download Mirror Page and can be downloaded from the FOP Archives <a href="http://archive.apache.org/dist/xmlgraphics/fop/binaries/">binaries</a> &amp; <a href="http://archive.apache.org/dist/xmlgraphics/fop/source/">source</a> links.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/knownissues.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/knownissues.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/knownissues.html Tue Dec 11 12:12:25 2012
@@ -356,44 +356,81 @@ $(document).ready(function () {
 <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">FO Tree</h3>
 <p>This section lists currently disabled test cases in the test suite for the FO tree tests. The data for this section comes from <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/fotree/disabled-testcases.xml">test/fotree/disabled-testcases.xml</a>.</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>
+<p><strong>demo-test-failure.fo</strong> (demo test failure):</p>
+<p><em>TODO: Add missing description in disabled-testcases.xml!</em></p>
+<p><strong>from-table-column_marker.fo</strong> (Markers and core function evaluation):</p>
+<p>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">Layout Engine</h3>
 <p>This section lists currently disabled test cases in the test suite for the layout engine tests. The data for this section comes from <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/test/layoutengine/disabled-testcases.xml">test/layoutengine/disabled-testcases.xml</a>.</p>
-<p><strong>block-container_space-before_space-after_3.xml</strong> (Auto-height block-containers produce fences):<br></br>Block-containers with no height currently don't create a fence for spaces as they should (they behave like a normal block).</p>
-<p><strong>block_font-stretch.xml</strong> (font-stretch NYI):<br></br>Font-stretch is not implemented, yet.</p>
-<p><strong>block_linefeed-treatment.xml</strong> (linefeed-treatment):<br></br>Preserved linefeeds in a fo:character are not handled correctly.</p>
-<p><strong>block_white-space-treatment_3.xml</strong> (white-space-treatment):<br></br>White space handling incorrectly stops at fo:inline boundaries when it comes to formatter generated line breaks.</p>
-<p><strong>block_space-before_space-after_8.xml</strong> (Empty blocks produce fences):<br></br>An empty block currently produces a fence for stacking constraints which it shouldn't.</p>
-<p><strong>block_white-space_nbsp_2.xml</strong> (block white-space nbsp 2):<br></br>The nbsp given as an fo:character is not adjustable and therefore the justification does not work in this case.</p>
-<p><strong>block_word-spacing.xml</strong> (block word-spacing):<br></br>Word-spacing may not work as expected.</p>
-<p><strong>block_word-spacing_text-align_justify.xml</strong> (block word-spacing text-align justify):<br></br>Word-spacing may not work as expected.</p>
-<p><strong>external-graphic_oversized.xml</strong> (external-graphic don't shrink):<br></br>Images currently don't shrink so they fit on a page when they are too big and shrinking is allowed to happen (min/opt/max).</p>
-<p><strong>external-graphic_src_uri.xml</strong> (Test case with HTTP URL):<br></br>Doesn't work behind a proxy which requires authorization.</p>
-<p><strong>footnote_space-resolution.xml</strong> (Space Resolution in foot note area):<br></br>Space resolution does not work between footnote regions.</p>
-<p><strong>inline_block_nested_3.xml</strong> (NPE for table inside an inline):<br></br>Placing a table as a child of an fo:inline produces a NullPointerException.</p>
-<p><strong>inline-container_block_nested.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed. The test case contains no checks.</p>
-<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>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>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>
-<p><strong>page-number-citation_background-image.xml</strong> (page-number-citation: Problem with background-image):<br></br>Background-images on page-number-citations are not placed correctly.</p>
-<p><strong>page-number-citation_complex_1.xml</strong> (IDs are not working on all FO elements):<br></br>The "id" attributes are not properly handled for all block-level FO elements.</p>
-<p><strong>page-number-citation_complex_2.xml</strong> (IDs are not working on all FO elements):<br></br>The "id" attributes are not properly handled for all inline-level FO elements.</p>
-<p><strong>region-body_column-count_footnote.xml</strong> (Footnotes in multi-column documents):<br></br>Footnotes may overlap with text of the region-body in multi-column documents.</p>
-<p><strong>region-body_column-count_balance_4col.xml</strong> (Column Balancing problems):<br></br>Situation in a 4-column document where the column balancing doesn't work and even causes some content to disappear.</p>
-<p><strong>region-body_column-count_bug36356.xml</strong> (Column Balancing problems):<br></br>Column balancing doesn't work as expected.</p>
-<p><strong>table-cell_empty_area_with_marker.xml</strong> (table-cell empty area with marker.xml):<br></br>A table-cell producing an empty area does currently not add any markers to a page. See TODO entry in AreaAdditionUtil.</p>
-<p><strong>table_border-width_conditionality.xml</strong> (Border conditionality on table):<br></br>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the indended outcome according to the spec. The test case should be revisited.</p>
-<p><strong>block_shy_linebreaking_hyph.xml</strong> (Soft hyphen with normal hyphenation enabled):<br></br>A soft hyphen should be a preferred as break compared to a normal hyphenation point but is not.</p>
-<p><strong>keep_within-page_multi-column_overflow.xml</strong> (Page-keep not respected in multi-column layout):<br></br>The block should cause overflow in the last column on the page, rather than be broken.</p>
-<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>
+<p><strong>block-container_space-before_space-after_3.xml</strong> (Auto-height block-containers produce fences):</p>
+<p>Block-containers with no height currently don't create a fence for spaces as they should (they behave like a normal block).</p>
+<p><strong>block_font-stretch.xml</strong> (font-stretch NYI):</p>
+<p>Font-stretch is not implemented, yet.</p>
+<p><strong>block_linefeed-treatment.xml</strong> (linefeed-treatment):</p>
+<p>Preserved linefeeds in a fo:character are not handled correctly.</p>
+<p><strong>block_white-space-treatment_3.xml</strong> (white-space-treatment):</p>
+<p>White space handling incorrectly stops at fo:inline boundaries when it comes to formatter generated line breaks.</p>
+<p><strong>block_space-before_space-after_8.xml</strong> (Empty blocks produce fences):</p>
+<p>An empty block currently produces a fence for stacking constraints which it shouldn't.</p>
+<p><strong>block_white-space_nbsp_2.xml</strong> (block white-space nbsp 2):</p>
+<p>The nbsp given as an fo:character is not adjustable and therefore the justification does not work in this case.</p>
+<p><strong>block_word-spacing.xml</strong> (block word-spacing):</p>
+<p>Word-spacing may not work as expected.</p>
+<p><strong>block_word-spacing_text-align_justify.xml</strong> (block word-spacing text-align justify):</p>
+<p>Word-spacing may not work as expected.</p>
+<p><strong>external-graphic_oversized.xml</strong> (external-graphic don't shrink):</p>
+<p>Images currently don't shrink so they fit on a page when they are too big and shrinking is allowed to happen (min/opt/max).</p>
+<p><strong>external-graphic_src_uri.xml</strong> (Test case with HTTP URL):</p>
+<p>Doesn't work behind a proxy which requires authorization.</p>
+<p><strong>footnote_space-resolution.xml</strong> (Space Resolution in foot note area):</p>
+<p>Space resolution does not work between footnote regions.</p>
+<p><strong>inline_block_nested_3.xml</strong> (NPE for table inside an inline):</p>
+<p>Placing a table as a child of an fo:inline produces a NullPointerException.</p>
+<p><strong>inline-container_block_nested.xml</strong> (inline-container is not implemented, yet.):</p>
+<p>inline-container is not implemented, yet. Content of an inline-container will get swallowed. The test case contains no checks.</p>
+<p><strong>inline-container_border_padding.xml</strong> (inline-container is not implemented, yet.):</p>
+<p>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):</p>
+<p>Letter-spacing may not work as expected within fo:inline.</p>
+<p><strong>inline_word-spacing.xml</strong> (inline word-spacing):</p>
+<p>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):</p>
+<p><em>TODO: Add missing description in disabled-testcases.xml!</em></p>
+<p><strong>leader-alignment.xml</strong> (leader-alignment NYI):</p>
+<p>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):</p>
+<p>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.</p>
+<p>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):</p>
+<p>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):</p>
+<p>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):</p>
+<p>A RuntimeException is thrown for a page of indefinite height. Lots of warnings.</p>
+<p><strong>page-number-citation_background-image.xml</strong> (page-number-citation: Problem with background-image):</p>
+<p>Background-images on page-number-citations are not placed correctly.</p>
+<p><strong>page-number-citation_complex_1.xml</strong> (IDs are not working on all FO elements):</p>
+<p>The "id" attributes are not properly handled for all block-level FO elements.</p>
+<p><strong>page-number-citation_complex_2.xml</strong> (IDs are not working on all FO elements):</p>
+<p>The "id" attributes are not properly handled for all inline-level FO elements.</p>
+<p><strong>region-body_column-count_footnote.xml</strong> (Footnotes in multi-column documents):</p>
+<p>Footnotes may overlap with text of the region-body in multi-column documents.</p>
+<p><strong>region-body_column-count_balance_4col.xml</strong> (Column Balancing problems):</p>
+<p>Situation in a 4-column document where the column balancing doesn't work and even causes some content to disappear.</p>
+<p><strong>region-body_column-count_bug36356.xml</strong> (Column Balancing problems):</p>
+<p>Column balancing doesn't work as expected.</p>
+<p><strong>table-cell_empty_area_with_marker.xml</strong> (table-cell empty area with marker.xml):</p>
+<p>A table-cell producing an empty area does currently not add any markers to a page. See TODO entry in AreaAdditionUtil.</p>
+<p><strong>table_border-width_conditionality.xml</strong> (Border conditionality on table):</p>
+<p>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the indended outcome according to the spec. The test case should be revisited.</p>
+<p><strong>block_shy_linebreaking_hyph.xml</strong> (Soft hyphen with normal hyphenation enabled):</p>
+<p>A soft hyphen should be a preferred as break compared to a normal hyphenation point but is not.</p>
+<p><strong>keep_within-page_multi-column_overflow.xml</strong> (Page-keep not respected in multi-column layout):</p>
+<p>The block should cause overflow in the last column on the page, rather than be broken.</p>
+<p><strong>block-container_reference-orientation_bug36391.xml</strong> (Block Container Reference Orientation Bug):</p>
+<p>An assert is failing</p>
+<p><strong>simple-page-master_writing-mode_rl_region-body_writing-mode-lr.xml</strong> (Writing mode problems):</p>
+<p>Test erroneously depends upon incorrect implementation of writing-mode trait derivation on fo:region-*.</p>
 <h3 id="Other-known-issues">Other known issues</h3>
 <p>This section lists other known issues.</p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/embedding.html Tue Dec 11 12:12:25 2012
@@ -657,7 +657,8 @@ Set a <strong>URIResolver</strong> for c
 <p>Whenever possible, try to use SAX to couple the individual components involved (parser, XSL transformer, SQL datasource etc.).</p>
 </li>
 <li>
-<p>Depending on the target OutputStream (in case of a FileOutputStream, but not for a ByteArrayOutputStream, for example) it may improve performance considerably if you buffer the OutputStream using a BufferedOutputStream: <code>out = new java.io.BufferedOutputStream(out);</code> <br></br>Make sure you properly close the OutputStream when FOP is finished.</p>
+<p>Depending on the target OutputStream (in case of a FileOutputStream, but not for a ByteArrayOutputStream, for example) it may improve performance considerably if you buffer the OutputStream using a BufferedOutputStream: <code>out = new java.io.BufferedOutputStream(out);</code></p>
+<p>Make sure you properly close the OutputStream when FOP is finished.</p>
 </li>
 <li>
 <p>Cache the stylesheet. If you use the same stylesheet multiple times you can set up a JAXP <code>Templates</code> object and reuse it each time you do the XSL transformation. (More information can be found <a href="http://www.javaworld.com/javaworld/jw-05-2003/jw-0502-xsl.html">here</a>.)</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html Tue Dec 11 12:12:25 2012
@@ -351,14 +351,15 @@ $(document).ready(function () {
 <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>
+<p>Produce an IF file: <code>fop -fo myfile.fo -at application/pdf myfile.at.xml</code></p>
+<p>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>
 </li>
 <li>
 <p>Render to a PDF file: <code>fop -atin myfile.at.xml -pdf myfile.pdf</code></p>
 </li>
 <li>
 <p>Render to a Java2D-based renderer:</p>
-</li>
+<ul>
 <li>
 <p><code>fop -atin myfile.at.xml -print</code></p>
 </li>
@@ -368,6 +369,8 @@ $(document).ready(function () {
 <li>
 <p><code>fop -atin myfile.at.xml -tiff myfile.tiff</code></p>
 </li>
+</ul>
+</li>
 </ol>
 <h3 id="general-direct-output">Output to a Printer or Other Device</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>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/pdfencryption.html Tue Dec 11 12:12:25 2012
@@ -580,9 +580,11 @@ then you don't have the needed infrastru
 <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</p>
 </li>
 </ol>
+<p><code>security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider</code>,</p>
+<p>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>If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.</p></div>
       </div>
       

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/servlets.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/servlets.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/servlets.html Tue Dec 11 12:12:25 2012
@@ -493,9 +493,9 @@ The <code>Source</code> instance used ab
 <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",
-          System.currentTimeMillis() + cacheExpiringDuration *
-          1000);</code> <br></br>Consult your server manual and the relevant RFCs for further details on HTTP headers and caching.</p>
+<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:</p>
+<p><code>response.setDateHeader("Expires", System.currentTimeMillis() + cacheExpiringDuration * 1000);</code></p>
+<p>Consult your server manual and the relevant RFCs for further details on HTTP headers and caching.</p>
 </li>
 <li>
 <p>Cache in the server. It may help to include a parameter in the URL which has a timestamp as the value min order to decide whether a request is repeated. IEx is reported to retrieve a document up to three times, but never more often.</p>



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


Mime
View raw message