svn commit: r840149 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/trunk/configuration.html

[bu...@apache.org]

Author: buildbot
Date: Fri Nov 30 13:47:40 2012
New Revision: 840149

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 30 13:47:40 2012
@@ -1 +1 @@
-1415630
+1415634

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/configuration.html Fri Nov 30 13:47:40 2012
@@ -485,7 +485,7 @@ $(document).ready(function () {
 </pre></div>
 
 
-<h1 id="image-loading">Image Loading Customization</h1>
+<h2 id="image-loading">Image Loading Customization</h2>
 <p>Apache FOP uses the image loading framework from <a href="http://xmlgraphics.apache.org/commons/">Apache XML Graphics Commons</a> to load images using various plug-ins. Every image loader plug-in has a hard-coded usage penalty that influences which solution is chosen if there are multiple possibilities to load an image. Sometimes, though, these penalties need to be tweaked and this can be done in the FOP configuration. An example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;fop</span> <span class="na">version=</span><span class="s">&quot;1.0&quot;</span><span class="nt">&gt;</span>
   [..]



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