xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r835892 [15/17] - in /websites/staging/xmlgraphics/trunk/content: ./ batik/ batik/dev/ batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/ fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Date Tue, 23 Oct 2012 15:05:47 GMT
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 Tue Oct 23 15:05:41 2012
@@ -331,10 +331,10 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/trunk/">Trunk</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1302518 $</version></p>
-<h1 id="general">Configuration File Basics</h1>
+<h1 id="configuration-file-basics-wzxhzdk8wzxhzdk9">Configuration File Basics  <a id="#general"></a></h1>
 <p>The Apache&trade; FOP configuration file is an XML file containing a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use.</p>
 <p>The easiest way to get started using a FOP configuration file is to copy the sample found at <code>{fop-dir}/conf/fop.xconf</code> to a location of your choice, and then to edit it according to your needs. It contains templates for the various configuration options, most of which are commented out. Remove the comments and change the settings for entries that you wish to use. Be sure to follow any instructions, including comments which specify the value range. Also, since the configuration file is XML, be sure to keep it well-formed.</p>
-<h2 id="general-available">Making Configuration Available to FOP</h2>
+<h2 id="making-configuration-available-to-fop-wzxhzdk11wzxhzdk12">Making Configuration Available to FOP # <a id="#general-available"></a></h2>
 <p>After creating your configuration file, you must tell FOP how to find it:</p>
@@ -345,7 +345,7 @@ $(document).ready(function () {
 <p>See <a href="embedding.html#config-internal">Setting the Configuration Programmatically</a> for instructions on how to do so in an embedded environment.</p>
-<h1 id="general-elements">Summary of the General Configuration Options</h1>
+<h1 id="summary-of-the-general-configuration-options-wzxhzdk13wzxhzdk14">Summary of the General Configuration Options  <a id="#general-elements"></a></h1>
@@ -469,12 +469,12 @@ $(document).ready(function () {
   <hyphenation-pattern lang="nl" country="BE">nl_Bel</hyphenation-pattern></p>
 <p><!-- etc. etc..... -->
-<h1 id="image-loading">Image Loading Customization</h1>
+<h1 id="image-loading-customization-wzxhzdk41wzxhzdk42">Image Loading Customization  <a id="#image-loading"></a></h1>
 <p class=".">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:
 <fop version="1.0"></p>
 <p>The second penalty element sets an "infinite" penalty for the TIFF loader using the internal TIFF codec. This practically disables that plug-in as it will never be chosen as a possible solution.</p>
 <p>Negative penalties are possible to promote a plug-in but a negative penalty sum will be treated as zero penalty in most cases. For more details on the image loading framework, please consult the documentation there.</p>
-<h1 id="renderers">Renderer configuration</h1>
+<h1 id="renderer-configuration-wzxhzdk44wzxhzdk45">Renderer configuration  <a id="#renderers"></a></h1>
 <p>Each Renderer has its own configuration section which is identified by the MIME type the Renderer is written for, ex. "application/pdf" for the PDF Renderer.</p>
 <p>The configuration for the PDF Renderer could look like this:</p>
@@ -500,7 +500,7 @@ $(document).ready(function () {
 <p>The details on the font configuration can be found on the separate <a href="fonts.html">Fonts</a> page. Note especially the section entitled <a href="fonts.html#register">Register Fonts with FOP</a> .</p>
-<h2 id="pdf-renderer">Special Settings for the PDF Renderer</h2>
+<h2 id="special-settings-for-the-pdf-renderer-wzxhzdk64wzxhzdk65">Special Settings for the PDF Renderer # <a id="#pdf-renderer"></a></h2>
 <p>The configuration element for the PDF renderer contains two elements. One is for the font configuration (please follow the link above) and one is for the "filter list". The filter list controls how the individual objects in a PDF file are encoded. By default, all objects get "flate" encoded (i.e. simply compressed with the same algorithm that is also used in ZIP files). Most users don't need to change that setting. For debugging purposes, it may be desired not to compress the internal objects at all so the generated PDF commands can be read. In that case, you can simply use the following filter list. The second filter list (type="image") ensures that all images still get compressed but also ASCII-85 encoded so the produced PDF file is still easily readable in a text editor.</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/pdf&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;filterList&gt;</span>
@@ -562,7 +562,7 @@ $(document).ready(function () {
         <!-- Versions 1.4, 1.5, 1.6 and 1.7 are accepted, all other values are invalid -->
-<h2 id="ps-renderer">Special Settings for the PostScript Renderer</h2>
+<h2 id="special-settings-for-the-postscript-renderer-wzxhzdk71wzxhzdk72">Special Settings for the PostScript Renderer # <a id="#ps-renderer"></a></h2>
 <p>Besides the normal font configuration (the same "fonts" element as for the PDF renderer) the PostScript renderer has an additional setting to force landscape pages to be rotated to fit on a page inserted into the printer in portrait mode. Set the value to "true" to activate this feature. The default is "false". Example:</p>
 <div class="codehilite"><pre><span class="nt">&lt;renderer</span> <span class="na">mime=</span><span class="s">&quot;application/postscript&quot;</span><span class="nt">&gt;</span>
   <span class="nt">&lt;auto-rotate-landscape&gt;</span>true<span class="nt">&lt;/auto-rotate-landscape&gt;</span>
@@ -581,7 +581,7 @@ $(document).ready(function () {
-<h2 id="pcl-renderer">Special Settings for the PCL Renderer</h2>
+<h2 id="special-settings-for-the-pcl-renderer-wzxhzdk73wzxhzdk74">Special Settings for the PCL Renderer # <a id="#pcl-renderer"></a></h2>
 <p>Non-standard fonts for the PCL renderer are made available through the Java2D subsystem which means that you don't have to do any custom font configuration in this case but you have to use the font names offered by Java.</p>
 <p>Additionally, there are certain settings that control how the renderer handles various elements.
 <renderer mime="application/vnd.hp-PCL">
@@ -590,7 +590,7 @@ $(document).ready(function () {
 The default value for the "rendering" setting is "speed" which causes borders to be painted as plain rectangles. In this mode, no special borders (dotted, dashed etc.) are available. If you want support for all border modes, set the value to "quality" as indicated above. This will cause the borders to be painted as bitmaps.</p>
 <p>The default value for the "text-rendering" setting is "auto" which paints the base fonts using PCL fonts. Non-base fonts are painted as bitmaps through Java2D. If the mix of painting methods results in unwelcome output, you can set this to "bitmap" which causes all text to be rendered as bitmaps.</p>
-<h2 id="afp-renderer">Special Settings for the AFP Renderer</h2>
+<h2 id="special-settings-for-the-afp-renderer-wzxhzdk81wzxhzdk82">Special Settings for the AFP Renderer # <a id="#afp-renderer"></a></h2>
 <p>Additionally, there are certain settings that control how the renderer handles various elements.
 <renderer mime="application/x-afp">
   <images mode="b+w" bits-per-pixel="8" native="true"/>
@@ -601,7 +601,7 @@ The default value for the "rendering" se
 The default value for the images "mode" setting is "b+w" (black and white). When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process. With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form. When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.</p>
 <p>The default value for the "renderer-resolution" is 240 dpi.</p>
 <p>By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp.</p>
-<h1 id="when-it-does-not-work-whenitdoesnotwork">When it does not work # {#When+it+does+not+work}</h1>
+<h1 id="when-it-does-not-work-wzxhzdk91wzxhzdk92">When it does not work  <a id="#When+it+does+not+work"></a></h1>
 <p>FOP searches the configuration file for the information it expects, at the position it expects. When that information is not present, FOP will not complain, it will just continue. When there is other information in the file, FOP will not complain, it will just ignore it. That means that when your configuration information is in the file but in a different XML element, or in a different XML path, than FOP expects, it will be silently ignored.</p>
 <p>Check the following possibilities:</p>

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 Oct 23 15:05:41 2012
@@ -331,10 +331,10 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/trunk/">Trunk</a></div> -->
       	<div class="section-content"><p><subtitle>How to Embed FOP in a Java application</subtitle><version>$Revision: 1298724 $</version></p>
-<h1 id="overview">Overview</h1>
+<h1 id="overview-wzxhzdk4wzxhzdk5">Overview  <a id="#overview"></a></h1>
 <p>Review <a href="running.html">Running Apache&trade; FOP</a> for important information that applies to embedded applications as well as command-line use, such as options and performance.</p>
 <p>To embed Apache&trade; FOP in your application, first create a new org.apache.fop.apps.FopFactory instance. This object can be used to launch multiple rendering runs. For each run, create a new org.apache.fop.apps.Fop instance through one of the factory methods of FopFactory. In the method call you specify which output format (i.e. MIME type) to use and, if the selected output format requires an OutputStream, which OutputStream to use for the results of the rendering. You can customize FOP's behaviour in a rendering run by supplying your own FOUserAgent instance. The FOUserAgent can, for example, be used to set your own document handler instance (details below). Finally, you retrieve a SAX DefaultHandler instance from the Fop object and use that as the SAXResult of your transformation.</p>
-<h1 id="API">The API</h1>
+<h1 id="the-api-wzxhzdk8wzxhzdk9">The API  <a id="#API"></a></h1>
 <p>FOP has many classes which express the "public" access modifier, however, this is not indicative of their inclusion into the public API. Every attempt will be made to keep the public API static, to minimize regressions for existing users, however, since the API is not clearly defined, the list of classes below are the generally agreed public API:
@@ -352,7 +352,7 @@ org.apache.fop.render.intermediate.IFPar
-<h1 id="basics">Basic Usage Pattern</h1>
+<h1 id="basic-usage-pattern-wzxhzdk10wzxhzdk11">Basic Usage Pattern  <a id="#basics"></a></h1>
 <p>Apache FOP relies heavily on JAXP. It uses SAX events exclusively to receive the XSL-FO input document. It is therefore a good idea that you know a few things about JAXP (which is a good skill anyway). Let's look at the basic usage pattern for FOP...</p>
 <p>Here is the basic pattern to render an XSL-FO file to PDF:</p>
 <p>import org.apache.fop.apps.FopFactory;
@@ -405,7 +405,7 @@ Let's discuss these 5 steps in detail:</
 <p>If you're not totally familiar with JAXP Transformers, please have a look at the <a href="#examples">Embedding examples</a> below. The section contains examples for all sorts of use cases. If you look at all of them in turn you should be able to see the patterns in use and the flexibility this approach offers without adding too much complexity.</p>
 <p>This may look complicated at first, but it's really just the combination of an XSL transformation and a FOP run. It's also easy to comment out the FOP part for debugging purposes, for example when you're tracking down a bug in your stylesheet. You can easily write the XSL-FO output from the XSL transformation to a file to check if that part generates the expected output. An example for that can be found in the <a href="#examples">Embedding examples</a> (See "ExampleXML2FO").</p>
-<h2 id="basic-logging">Logging</h2>
+<h2 id="logging-wzxhzdk12wzxhzdk13">Logging # <a id="#basic-logging"></a></h2>
 <p>Logging is now a little different than it was in FOP 0.20.5. We've switched from Avalon Logging to <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a> . While with Avalon Logging the loggers were directly given to FOP, FOP now retrieves its logger(s) through a statically available LogFactory. This is similar to the general pattern that you use when you work with Apache Log4J directly, for example. We call this "static logging" (Commons Logging, Log4J) as opposed to "instance logging" (Avalon Logging). This has a consequence: You can't give FOP a logger for each processing run anymore. The log output of multiple, simultaneously running FOP instances is sent to the same logger.</p>
 <p>By default, <a href="http://commons.apache.org/logging/">Jakarta Commons Logging</a> uses JDK logging (available in JDKs 1.4 or higher) as its backend. You can configure Commons Logging to use an alternative backend, for example Log4J. Please consult the <a href="http://commons.apache.org/logging/">documentation for Jakarta Commons Logging</a> on how to configure alternative backends.</p>
 <p>As a result of the above we differentiate between two kinds of "logging":</p>
@@ -418,16 +418,16 @@ Let's discuss these 5 steps in detail:</
 <p>The use of "feedback" instead of "logging" is intentional. Most people were using log output as a means to get feedback from events within FOP. Therefore, FOP now includes an <code>event</code> package which can be used to receive feedback from the layout engine and other components within FOP <strong>per rendering run</strong> . This feedback is not just some text but event objects with parameters so these events can be interpreted by code. Of course, there is a facility to turn these events into normal human-readable messages. For details, please read on on the <a href="events.html">Events page</a> . This leaves normal logging to be mostly a thing used by the FOP developers although anyone can surely activate certain logging categories but the feedback from the loggers won't be separated by processing runs. If this is required, the <a href="events.html">Events subsystem</a> is the right approach.</p>
-<h2 id="render">Processing XSL-FO</h2>
+<h2 id="processing-xsl-fo-wzxhzdk14wzxhzdk15">Processing XSL-FO # <a id="#render"></a></h2>
 <p>Once the Fop instance is set up, call <code>getDefaultHandler()</code> to obtain a SAX DefaultHandler instance to which you can send the SAX events making up the XSL-FO document you'd like to render. FOP processing starts as soon as the DefaultHandler's <code>startDocument()</code> method is called. Processing stops again when the DefaultHandler's <code>endDocument()</code> method is called. Please refer to the basic usage pattern shown above to render a simple XSL-FO document.</p>
-<h2 id="render-with-xslt">Processing XSL-FO generated from XML+XSLT</h2>
+<h2 id="processing-xsl-fo-generated-from-xmlxslt-wzxhzdk16wzxhzdk17">Processing XSL-FO generated from XML+XSLT # <a id="#render-with-xslt"></a></h2>
 <p>If you want to process XSL-FO generated from XML using XSLT we recommend again using standard JAXP to do the XSLT part and piping the generated SAX events directly through to FOP. The only thing you'd change to do that on the basic usage pattern above is to set up the Transformer differently:</p>
 <p>//without XSLT:
   //Transformer transformer = factory.newTransformer(); // identity transformer</p>
 <p>//with XSLT:
   Source xslt = new StreamSource(new File("mystylesheet.xsl"));
   Transformer transformer = factory.newTransformer(xslt);</p>
-<h1 id="input">Input Sources</h1>
+<h1 id="input-sources-wzxhzdk18wzxhzdk19">Input Sources  <a id="#input"></a></h1>
 <p>The input XSL-FO document is always received by FOP as a SAX stream (see the <a href="../dev/design/parsing.html">Parsing Design Document</a> for the rationale).</p>
 <p>However, you may not always have your input document available as a SAX stream. But with JAXP it's easy to convert different input sources to a SAX stream so you can pipe it into FOP. That sounds more difficult than it is. You simply have to set up the right Source instance as input for the JAXP transformation. A few examples:</p>
@@ -454,9 +454,9 @@ Let's discuss these 5 steps in detail:</
 <p>There are a variety of upstream data manipulations possible. For example, you may have a DOM and an XSL stylesheet; or you may want to set variables in the stylesheet. Interface documentation and some cookbook solutions to these situations are provided in <a href="http://xml.apache.org/xalan-j/usagepatterns.html">Xalan Basic Usage Patterns</a> .</p>
-<h1 id="config-internal">Configuring Apache FOP Programmatically</h1>
+<h1 id="configuring-apache-fop-programmatically-wzxhzdk20wzxhzdk21">Configuring Apache FOP Programmatically  <a id="#config-internal"></a></h1>
 <p>Apache FOP provides two levels on which you can customize FOP's behaviour: the FopFactory and the user agent.</p>
-<h2 id="fop-factory">Customizing the FopFactory</h2>
+<h2 id="customizing-the-fopfactory-wzxhzdk22wzxhzdk23">Customizing the FopFactory # <a id="#fop-factory"></a></h2>
 <p>The FopFactory holds configuration data and references to objects which are reusable over multiple rendering runs. It's important to instantiate it only once (except in special environments) and reuse it every time to create new FOUserAgent and Fop instances.</p>
 <p>You can set all sorts of things on the FopFactory:</p>
@@ -489,7 +489,7 @@ fopFactory.addElementMapping(myElementMa
 fopFactory.setURIResolver(myResolver); // myResolver is a javax.xml.transform.URIResolverBoth the FopFactory and the FOUserAgent have a method to set a URIResolver. The URIResolver on the FopFactory is primarily used to resolve URIs on factory-level (hyphenation patterns, for example) and it is always used if no other URIResolver (for example on the FOUserAgent) resolved the URI first.</p>
-<h2 id="user-agent">Customizing the User Agent</h2>
+<h2 id="customizing-the-user-agent-wzxhzdk24wzxhzdk25">Customizing the User Agent # <a id="#user-agent"></a></h2>
 <p>The user agent is the entity that allows you to interact with a single rendering run, i.e. the processing of a single document. If you wish to customize the user agent's behaviour, the first step is to create your own instance of FOUserAgent using the appropriate factory method on FopFactory and pass that to the factory method that will create a new Fop instance:</p>
 <p>FopFactory fopFactory = FopFactory.newInstance(); // Reuse the FopFactory if possible!
   // do the following for each new rendering run
@@ -544,7 +544,7 @@ userAgent.setURIResolver(myResolver); //
 You should not reuse an FOUserAgent instance between FOP rendering runs although you can. Especially in multi-threaded environment, this is a bad idea.</p>
-<h1 id="config-external">Using a Configuration File</h1>
+<h1 id="using-a-configuration-file-wzxhzdk26wzxhzdk27">Using a Configuration File  <a id="#config-external"></a></h1>
 <p>Instead of setting the parameters manually in code as shown above you can also set many values from an XML configuration file:</p>
 <p>import org.apache.avalon.framework.configuration.Configuration;
 import org.apache.avalon.framework.configuration.DefaultConfigurationBuilder;</p>
@@ -555,7 +555,7 @@ fopFactory.setUserConfig(cfg);</p>
 <p>/<em> ..or.. </em>/</p>
 <p>fopFactory.setUserConfig(new File("C:/Temp/mycfg.xml"));
 The layout of the configuration file is described on the <a href="configuration.html">Configuration page</a> .</p>
-<h1 id="documenthandlers">Document Handlers</h1>
+<h1 id="document-handlers-wzxhzdk28wzxhzdk29">Document Handlers  <a id="#documenthandlers"></a></h1>
 <p>The document handlers are classes that inherit from <code>org.apache.fop.render.intermediate.IFDocumentHandler</code> . This is an interface for which a MIME type specific implementation can be created. This same handler is used either when XSL-FO is used as the input or when Intermediate Format is used. Since IF is output format agnostic, if custom fonts or other configuration information that affect layout (specific to a particular MIME type) are given then FOP needs that contextual information. The document handler provides that context so that when the IF is rendered, it is more visually consistent with FO rendering. The code below shows an example of how a document handler can be used to provide PDF configuration data to the IFSerializer.
 IFDocumentHandler targetHandler = userAgent.getRendererFactory().createDocumentHandler(userAgent, MimeConstants.MIME_PDF);</p>
 <p>IFSerializer ifSerializer = new IFSerializer();  //Create the IFSerializer to write the intermediate format
@@ -563,16 +563,16 @@ ifSerializer.setContext(new IFContext(us
 ifSerializer.mimicDocumentHandler(targetHandler);   //Tell the IFSerializer to mimic the target format</p>
 <p>userAgent.setDocumentHandlerOverride(ifSerializer);  //Make sure the prepared document handler is used
       The rest of the code is the same as in <a href="#basics">Basic Usage Patterns</a> .</p>
-<h1 id="hints">Hints</h1>
-<h2 id="object-reuse">Object reuse</h2>
+<h1 id="hints-wzxhzdk30wzxhzdk31">Hints  <a id="#hints"></a></h1>
+<h2 id="object-reuse-wzxhzdk32wzxhzdk33">Object reuse # <a id="#object-reuse"></a></h2>
 <p>Fop instances shouldn't (and can't) be reused. Please recreate Fop and FOUserAgent instances for each rendering run using the FopFactory. This is a cheap operation as all reusable information is held in the FopFactory. That's why it's so important to reuse the FopFactory instance.</p>
-<h2 id="awt">AWT issues</h2>
+<h2 id="awt-issues-wzxhzdk34wzxhzdk35">AWT issues # <a id="#awt"></a></h2>
 <p>If your XSL-FO files contain SVG then Apache Batik will be used. When Batik is initialised it uses certain classes in <code>java.awt</code> that intialise the Java AWT classes. This means that a daemon thread is created by the JVM and on Unix it will need to connect to a DISPLAY.</p>
 <p>The thread means that the Java application may not automatically quit when finished, you will need to call <code>System.exit()</code> . These issues should be fixed in the JDK 1.4.</p>
 <p>If you run into trouble running FOP on a head-less server, please see the <a href="graphics.html#batik">notes on Batik</a> .</p>
-<h2 id="render-info">Getting information on the rendering process</h2>
+<h2 id="getting-information-on-the-rendering-process-wzxhzdk36wzxhzdk37">Getting information on the rendering process # <a id="#render-info"></a></h2>
 <p>To get the number of pages that were rendered by FOP you can call <code>Fop.getResults()</code> . This returns a <code>FormattingResults</code> object where you can look up the number of pages produced. It also gives you the page-sequences that were produced along with their id attribute and their numbers of pages. This is particularly useful if you render multiple documents (each enclosed by a page-sequence) and have to know the number of pages of each document.</p>
-<h1 id="performance">Improving performance</h1>
+<h1 id="improving-performance-wzxhzdk38wzxhzdk39">Improving performance  <a id="#performance"></a></h1>
 <p>There are several options to consider:</p>
@@ -594,37 +594,37 @@ ifSerializer.mimicDocumentHandler(target
 <p>You may also wish to consider trying to reduce <a href="http://xmlgraphics.apache.org/fop/trunk/running.html#memory">memory usage</a> .</p>
-<h1 id="multithreading">Multithreading FOP</h1>
+<h1 id="multithreading-fop-wzxhzdk40wzxhzdk41">Multithreading FOP  <a id="#multithreading"></a></h1>
 <p>Apache FOP may currently not be completely thread safe. The code has not been fully tested for multi-threading issues, yet. If you encounter any suspicious behaviour, please notify us.</p>
 <p>There is also a known issue with fonts being jumbled between threads when using the Java2D/AWT renderer (which is used by the -awt and -print output options). In general, you cannot safely run multiple threads through the AWT renderer.</p>
-<h1 id="examples">Examples</h1>
+<h1 id="examples-wzxhzdk42wzxhzdk43">Examples  <a id="#examples"></a></h1>
 <p>The directory "{fop-dir}/examples/embedding" contains several working examples.</p>
-<h2 id="ExampleFO2PDF">ExampleFO2PDF.java</h2>
+<h2 id="examplefo2pdfjava-wzxhzdk44wzxhzdk45">ExampleFO2PDF.java # <a id="#ExampleFO2PDF"></a></h2>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleFO2PDF.java?view=markup">example</a> demonstrates the basic usage pattern to transform an XSL-FO file to PDF using FOP.
 <figure alt="Example XSL-FO to PDF" src="images/EmbeddingExampleFO2PDF.png"></figure></p>
-<h2 id="ExampleXML2FO">ExampleXML2FO.java</h2>
+<h2 id="examplexml2fojava-wzxhzdk48wzxhzdk49">ExampleXML2FO.java # <a id="#ExampleXML2FO"></a></h2>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2FO.java?view=markup">example</a> has nothing to do with FOP. It is there to show you how an XML file can be converted to XSL-FO using XSLT. The JAXP API is used to do the transformation. Make sure you've got a JAXP-compliant XSLT processor in your classpath (ex. <a href="http://xml.apache.org/xalan-j">Xalan</a> ).
 <figure alt="Example XML to XSL-FO" src="images/EmbeddingExampleXML2FO.png"></figure></p>
-<h2 id="ExampleXML2PDF">ExampleXML2PDF.java</h2>
+<h2 id="examplexml2pdfjava-wzxhzdk52wzxhzdk53">ExampleXML2PDF.java # <a id="#ExampleXML2PDF"></a></h2>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleXML2PDF.java?view=markup">example</a> demonstrates how you can convert an arbitrary XML file to PDF using XSLT and XSL-FO/FOP. It is a combination of the first two examples above. The example uses JAXP to transform the XML file to XSL-FO and FOP to transform the XSL-FO to PDF.
 <figure alt="Example XML to PDF (via XSL-FO)" src="images/EmbeddingExampleXML2PDF.png"></figure>
 The output (XSL-FO) from the XSL transformation is piped through to FOP using SAX events. This is the most efficient way to do this because the intermediate result doesn't have to be saved somewhere. Often, novice users save the intermediate result in a file, a byte array or a DOM tree. We strongly discourage you to do this if it isn't absolutely necessary. The performance is significantly higher with SAX.</p>
-<h2 id="ExampleObj2XML">ExampleObj2XML.java</h2>
+<h2 id="exampleobj2xmljava-wzxhzdk56wzxhzdk57">ExampleObj2XML.java # <a id="#ExampleObj2XML"></a></h2>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleObj2XML.java?view=markup">example</a> is a preparatory example for the next one. It's an example that shows how an arbitrary Java object can be converted to XML. It's an often needed task to do this. Often people create a DOM tree from a Java object and use that. This is pretty straightforward. The example here, however, shows how to do this using SAX, which will probably be faster and not even more complicated once you know how this works.
 <figure alt="Example Java object to XML" src="images/EmbeddingExampleObj2XML.png"></figure>
 For this example we've created two classes: ProjectTeam and ProjectMember (found in xml-fop/examples/embedding/java/embedding/model). They represent the same data structure found in xml-fop/examples/embedding/xml/xml/projectteam.xml. We want to serialize to XML a project team with several members which exist as Java objects. Therefore we created the two classes: ProjectTeamInputSource and ProjectTeamXMLReader (in the same place as ProjectTeam above).</p>
 <p>The XMLReader implementation (regard it as a special kind of XML parser) is responsible for creating SAX events from the Java object. The InputSource class is only used to hold the ProjectTeam object to be used.</p>
 <p>Have a look at the source of ExampleObj2XML.java to find out how this is used. For more detailed information see other resources on JAXP (ex. <a href="http://java.sun.com/xml/jaxp/dist/1.1/docs/tutorial/xslt/3_generate.html">An older JAXP tutorial</a> ).</p>
-<h2 id="ExampleObj2PDF">ExampleObj2PDF.java</h2>
+<h2 id="exampleobj2pdfjava-wzxhzdk60wzxhzdk61">ExampleObj2PDF.java # <a id="#ExampleObj2PDF"></a></h2>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleObj2PDF.java?view=markup">example</a> combines the previous and the third to demonstrate how you can transform a Java object to a PDF directly in one smooth run by generating SAX events from the Java object that get fed to an XSL transformation. The result of the transformation is then converted to PDF using FOP as before.
 <figure alt="Example Java object to PDF (via XML and XSL-FO)" src="images/EmbeddingExampleObj2PDF.png"></figure></p>
-<h2 id="ExampleDOM2PDF">ExampleDOM2PDF.java</h2>
+<h2 id="exampledom2pdfjava-wzxhzdk64wzxhzdk65">ExampleDOM2PDF.java # <a id="#ExampleDOM2PDF"></a></h2>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleDOM2PDF.java?view=markup">example</a> has FOP use a DOMSource instead of a StreamSource in order to use a DOM tree as input for an XSL transformation.</p>
-<h2 id="ExampleSVG2PDF">ExampleSVG2PDF.java (PDF Transcoder example)</h2>
+<h2 id="examplesvg2pdfjava-pdf-transcoder-example-wzxhzdk66wzxhzdk67">ExampleSVG2PDF.java (PDF Transcoder example) # <a id="#ExampleSVG2PDF"></a></h2>
 <p>This <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/ExampleSVG2PDF.java?view=markup">example</a> shows the usage of the PDF Transcoder, a sub-application within FOP. It is used to generate a PDF document from an SVG file.</p>
-<h2 id="ExampleConcat">ExampleConcat.java (IF Concatenation example)</h2>
+<h2 id="exampleconcatjava-if-concatenation-example-wzxhzdk68wzxhzdk69">ExampleConcat.java (IF Concatenation example) # <a id="#ExampleConcat"></a></h2>
 <p>This can be found in the <code>embedding.intermediate</code> package within the examples and describes how IF can be concatenated to produce a document. Because IF has been through FOPs layout engine, it should be visually consistent with FO rendered documents while allowing the user to merge numerous documents together.</p>
-<h2 id="example-notes">Final notes</h2>
+<h2 id="final-notes-wzxhzdk70wzxhzdk71">Final notes # <a id="#example-notes"></a></h2>
 <p>These examples should give you an idea of what's possible. It should be easy to adjust these examples to your needs. Also, if you have other examples that you think should be added here, please let us know via either the fop-users or fop-dev mailing lists. Finally, for more help please send your questions to the fop-users mailing list.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html Tue Oct 23 15:05:41 2012
@@ -331,11 +331,11 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/trunk/">Trunk</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="introduction">Introduction</h1>
+<h1 id="introduction-wzxhzdk6wzxhzdk7">Introduction  <a id="#introduction"></a></h1>
 <p>In versions until 0.20.5, Apache&trade; FOP used <a href="http://excalibur.apache.org/framework/index.html">Avalon-style Logging</a> where it was possible to supply a logger per processing run. During the redesign the logging infrastructure was switched over to <a href="http://commons.apache.org/logging/">Commons Logging</a> which is (like Log4J or java.util.logging) a "static" logging framework (the logger is accessed through static variables). This made it very difficult in a multi-threaded system to retrieve information for a single processing run.</p>
 <p>With FOP's event subsystem, we'd like to close this gap again and even go further. The first point is to realize that we have two kinds of "logging". Firstly, we have the logging infrastructure for the (FOP) developer who needs to be able to enable finer log messages for certain parts of FOP to track down a certain problem. Secondly, we have the user who would like to be informed about missing images, overflowing lines or substituted fonts. These messages (or events) are targeted at less technical people and may ideally be localized (translated). Furthermore, tool and solution builders would like to integrate FOP into their own solutions. For example, an FO editor should be able to point the user to the right place where a particular problem occurred while developing a document template. Finally, some integrators would like to abort processing if a resource (an image or a font) has not been found, while others would simply continue. The event system allows to react on the
 se events.</p>
 <p>On this page, we won't discuss logging as such. We will show how the event subsystem can be used for various tasks. We'll first look at the event subsystem from the consumer side. Finally, the production of events inside FOP will be discussed (this is mostly interesting for FOP developers only).</p>
-<h1 id="consumer">The consumer side</h1>
+<h1 id="the-consumer-side-wzxhzdk9wzxhzdk10">The consumer side  <a id="#consumer"></a></h1>
 <p>The event subsystem is located in the <code>org.apache.fop.events</code> package and its base is the <code>Event</code> class. An instance is created for each event and is sent to a set of <code>EventListener</code> instances by the <code>EventBroadcaster</code> . An <code>Event</code> contains:</p>
@@ -353,7 +353,7 @@ $(document).ready(function () {
 <p>The <code>EventFormatter</code> class can be used to translate the events into human-readable, localized messages.</p>
 <p>A full example of what is shown here can be found in the <code>examples/embedding/java/embedding/events</code> directory in the FOP distribution. The example can also be accessed <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/examples/embedding/java/embedding/events/">via the web</a> .</p>
-<h2 id="write-listener">Writing an EventListener</h2>
+<h2 id="writing-an-eventlistener-wzxhzdk11wzxhzdk12">Writing an EventListener # <a id="#write-listener"></a></h2>
 <p>The following code sample shows a very simple EventListener. It basically just sends all events to System.out (stdout) or System.err (stderr) depending on the event severity.
 import org.apache.fop.events.Event;
 import org.apache.fop.events.EventFormatter;
@@ -384,12 +384,12 @@ public class SysOutEventListener impleme
 You can see that for every event the method <code>processEvent</code> of the <code>EventListener</code> will be called. Inside this method you can do whatever processing you would like including throwing a <code>RuntimeException</code> , if you want to abort the current processing run.</p>
 <p>The code above also shows how you can turn an event into a human-readable, localized message that can be presented to a user. The <code>EventFormatter</code> class does this for you. It provides additional methods if you'd like to explicitly specify the locale.</p>
 <p>It is possible to gather all events for a whole processing run so they can be evaluated afterwards. However, care should be taken about memory consumption since the events provide references to objects inside FOP which may themselves have references to other objects. So holding on to these objects may mean that whole object trees cannot be released!</p>
-<h2 id="add-listener">Adding an EventListener</h2>
+<h2 id="adding-an-eventlistener-wzxhzdk13wzxhzdk14">Adding an EventListener # <a id="#add-listener"></a></h2>
 <p>To register the event listener with FOP, get the <code>EventBroadcaster</code> which is associated with the user agent ( <code>FOUserAgent</code> ) and add it there:
 FOUserAgent foUserAgent = fopFactory.newFOUserAgent();
 foUserAgent.getEventBroadcaster().addEventListener(new SysOutEventListener());
 Please note that this is done separately for each processing run, i.e. for each new user agent.</p>
-<h2 id="listener-example1">An additional listener example</h2>
+<h2 id="an-additional-listener-example-wzxhzdk15wzxhzdk16">An additional listener example # <a id="#listener-example1"></a></h2>
 <p>Here's an additional example of an event listener:</p>
 <p>By default, FOP continues processing even if an image wasn't found. If you have more strict requirements and want FOP to stop if an image is not available, you can do something like the following in the simplest case:
 public class MyEventListener implements EventListener {</p>
@@ -425,10 +425,10 @@ public class MyEventListener implements 
 This throws a <code>RuntimeException</code> with the <code>FileNotFoundException</code> as the cause. Further processing effectively stops in FOP. You can catch the exception in your code and react as you see necessary.</p>
-<h1 id="producer">The producer side (for FOP developers)</h1>
+<h1 id="the-producer-side-for-fop-developers-wzxhzdk17wzxhzdk18">The producer side (for FOP developers)  <a id="#producer"></a></h1>
 <p>This section is primarily for FOP and FOP plug-in developers. It describes how to use the event subsystem for producing events.
 The event package has been designed in order to be theoretically useful for use cases outside FOP. If you think this is interesting independently from FOP, please talk to <a href="mailto:fop-dev@xmlgraphics.apache.org">us</a> .</p>
-<h2 id="basic-event-production">Producing and sending an event</h2>
+<h2 id="producing-and-sending-an-event-wzxhzdk19wzxhzdk20">Producing and sending an event # <a id="#basic-event-production"></a></h2>
 <p>The basics are very simple. Just instantiate an <code>Event</code> object and fill it with the necessary parameters. Then pass it to the <code>EventBroadcaster</code> which distributes the events to the interested listeneners. Here's a code example:
 Event ev = new Event(this, "complain", EventSeverity.WARN,
@@ -438,7 +438,7 @@ Event ev = new Event(this, "complain", E
 EventBroadcaster broadcaster = [get it from somewhere];
 <p>The <code>Event.paramsBuilder()</code> is a <a href="http://en.wikipedia.org/wiki/Fluent_interface">fluent interface</a> to help with the build-up of the parameters. You could just as well instantiate a <code>Map</code> ( <code>Map&lt;String, Object&gt;</code> ) and fill it with values.</p>
-<h2 id="event-producer">The EventProducer interface</h2>
+<h2 id="the-eventproducer-interface-wzxhzdk21wzxhzdk22">The EventProducer interface # <a id="#event-producer"></a></h2>
 <p>To simplify event production, the event subsystem provides the <code>EventProducer</code> interface. You can create interfaces which extend <code>EventProducer</code> . These interfaces will contain one method per event to be generated. By contract, each event method must have as its first parameter a parameter named "source" (Type Object) which indicates the object that generated the event. After that come an arbitrary number of parameters of any type as needed by the event.</p>
 <p>The event producer interface does not need to have any implementation. The implementation is produced at runtime by a dynamic proxy created by <code>DefaultEventBroadcaster</code> . The dynamic proxy creates <code>Event</code> instances for each method call against the event producer interface. Each parameter (except "source") is added to the event's parameter map.</p>
 <p>To simplify the code needed to get an instance of the event producer interface it is suggested to create a public inner provider class inside the interface.</p>
@@ -467,13 +467,13 @@ To produce the same event as in the firs
 EventBroadcaster broadcaster = [get it from somewhere];
 TestEventProducer producer = TestEventProducer.Provider.get(broadcaster);
 producer.complain(this, "I'm tired", 23);</p>
-<h2 id="event-model">The event model</h2>
+<h2 id="the-event-model-wzxhzdk23wzxhzdk24">The event model # <a id="#event-model"></a></h2>
 <p>Inside an invocation handler for a dynamic proxy, there's no information about the names of each parameter. The JVM doesn't provide it. The only thing you know is the interface and method name. In order to properly fill the <code>Event</code> 's parameter map we need to know the parameter names. These are retrieved from an event object model. This is found in the <code>org.apache.fop.events.model</code> package. The data for the object model is retrieved from an XML representation of the event model that is loaded as a resource. The XML representation is generated using an Ant task at build time ( <code>ant resourcegen</code> ). The Ant task (found in <code>src/codegen/java/org/apache/fop/tools/EventProducerCollectorTask.java</code> ) scans FOP's sources for descendants of the <code>EventProducer</code> interface and uses <a href="http://qdox.codehaus.org/">QDox</a> to parse these interfaces.</p>
 <p>The event model XML files are generated during build by the Ant task mentioned above when running the "resourcegen" task. So just run <code>"ant resourcegen"</code> if you receive a <code>MissingResourceException</code> at runtime indicating that <code>"event-model.xml"</code> is missing.</p>
 <p>Primarily, the QDox-based collector task records the parameters' names and types. Furthermore, it extracts additional attributes embedded as Javadoc comments from the methods. At the moment, the only such attribute is "@event.severity" which indicates the default event severity (which can be changed by event listeners). The example event producer above shows the Javadocs for an event method.</p>
 <p>There's one more information that is extracted from the event producer information for the event model: an optional primary exception. The first exception in the "throws" declaration of an event method is noted. It is used to throw an exception from the invocation handler if the event has an event severity of "FATAL" when all listeners have been called (listeners can update the event severity). Please note that an implementation of <code>org.apache.fop.events.EventExceptionManager$ExceptionFactory</code> has to be registered for the <code>EventExceptionManager</code> to be able to construct the exception from an event.</p>
 <p>For a given application, there can be multiple event models active at the same time. In FOP, each renderer is considered to be a plug-in and provides its own specific event model. The individual event models are provided through an <code>EventModelFactory</code> . This interface is implemented for each event model and registered through the service provider mechanism (see the <a href="#plug-ins">plug-ins section</a> for details).</p>
-<h2 id="event-severity">Event severity</h2>
+<h2 id="event-severity-wzxhzdk25wzxhzdk26">Event severity # <a id="#event-severity"></a></h2>
 <p>Four different levels of severity for events has been defined:</p>
@@ -490,7 +490,7 @@ producer.complain(this, "I'm tired", 23)
 <p>Event listeners can choose to ignore certain events based on their event severity. Please note that you may recieve an event "twice" in a specific case: if there is a fatal error an event is generated and sent to the listeners. After that an exception is thrown with the same information and processing stops. If the fatal event is shown to the user and the following exception is equally presented to the user it may appear that the event is duplicated. Of course, the same information is just published through two different channels.</p>
-<h2 id="plug-ins">Plug-ins to the event subsystem</h2>
+<h2 id="plug-ins-to-the-event-subsystem-wzxhzdk27wzxhzdk28">Plug-ins to the event subsystem # <a id="#plug-ins"></a></h2>
 <p>The event subsystem is extensible. There are a number of extension points:</p>
@@ -501,7 +501,7 @@ producer.complain(this, "I'm tired", 23)
 <p>The names in bold above are used as filenames for the service provider files that are placed in the <code>META-INF/services</code> directory. That way, they are automatically detected. This is a mechanism defined by the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Service%20Provider">JAR file specification</a> .</p>
-<h2 id="l10n">Localization (L10n)</h2>
+<h2 id="localization-l10n-wzxhzdk29wzxhzdk30">Localization (L10n) # <a id="#l10n"></a></h2>
 <p>One goal of the event subsystem was to have localized (translated) event messages. The <code>EventFormatter</code> class can be used to convert an event to a human-readable message. Each <code>EventProducer</code> can provide its own XML-based translation file. If there is none, a central translation file is used, called "EventFormatter.xml" (found in the same directory as the <code>EventFormatter</code> class).</p>
 <p>The XML format used by the <code>EventFormatter</code> is the same as <a href="http://cocoon.apache.org/">Apache Cocoon's</a> catalog format. Here's an example:
 &lt;?xml version="1.0" encoding="UTF-8"?&gt;

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/extensions.html
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/extensions.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/extensions.html Tue Oct 23 15:05:41 2012
@@ -334,32 +334,32 @@ $(document).ready(function () {
 <p>By "extension", we mean any data that can be placed in the input XML document that is not addressed by the XSL-FO standard. By having a mechanism for supporting extensions, Apache&trade; FOP is able to add features that are not covered in the specification.</p>
 <p>The extensions documented here are included with FOP, and are automatically available to you. If you wish to add an extension of your own to FOP, please see the <a href="../dev/extensions.html">Developers' Extension Page</a> .
 All extensions require the correct use of an appropriate namespace in your input document.</p>
-<h1 id="svg">SVG</h1>
+<h1 id="svg-wzxhzdk3wzxhzdk4">SVG  <a id="#svg"></a></h1>
 <p>Please see the <a href="graphics.html#svg">SVG documentation</a> for more details.</p>
-<h1 id="fo-extensions">FO Extensions</h1>
-<h2 id="fox-namespace">Namespace</h2>
+<h1 id="fo-extensions-wzxhzdk5wzxhzdk6">FO Extensions  <a id="#fo-extensions"></a></h1>
+<h2 id="namespace-wzxhzdk7wzxhzdk8">Namespace # <a id="#fox-namespace"></a></h2>
 <p>By convention, FO extensions in FOP use the "fox" namespace prefix. To use any of the FO extensions, add a namespace entry for <code>http://xmlgraphics.apache.org/fop/extensions</code> to the root element:
 <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
-<h2 id="bookmarks">PDF Bookmarks</h2>
+<h2 id="pdf-bookmarks-wzxhzdk10wzxhzdk11">PDF Bookmarks # <a id="#bookmarks"></a></h2>
 <p>In old versions of Apache FOP there was a <code>fox:outline</code> element which was used to create outlines in PDF files. The redesigned code makes use of the <a href="http://www.w3.org/TR/xsl11/#fo_bookmark-tree">bookmark feature defined in the W3C XSL 1.1 standard</a> .</p>
-<h2 id="named-destinations">Anchors or Named Destinations</h2>
+<h2 id="anchors-or-named-destinations-wzxhzdk12wzxhzdk13">Anchors or Named Destinations # <a id="#named-destinations"></a></h2>
 <p>Use the fox:destination element to define "named destinations" inside a PDF document. These are useful as fragment identifiers, e.g. "http://server/document.pdf#anchor-name". fox:destination elements can be placed almost anywhere in the fo document, including a child of root, a block-level element, or an inline-level element. For the destination to actually work, it must correspond to an "id" attribute on some fo element within the document. In other words, the "id" attribute actually creates the "view" within the PDF document. The fox:destination simply gives that view an independent name.
 <fox:destination internal-destination="table-of-contents"/>
 <fo:block id="table-of-contents">Table of Contents</fo:block><warning>It is possible that in some future release of FOP, <em>all</em> elements with "id" attributes will generate named-destinations, which will eliminate the need for fox:destination.</warning></p>
-<h2 id="table-continue-label">Table Continuation Label</h2>
+<h2 id="table-continuation-label-wzxhzdk19wzxhzdk20">Table Continuation Label # <a id="#table-continue-label"></a></h2>
 <p>This extension element hasn't been reimplemented for the redesigned code, yet.</p>
 <h2 id="row-scope-for-header-table-cells">Row Scope for Header Table Cells</h2>
 <p>This feature is described in the <a href="accessibility.html#fox:header">Accessibility</a> section.</p>
-<h2 id="widow-orphan-content-limit">fox:orphan-content-limit and fox:widow-content-limit</h2>
+<h2 id="foxorphan-content-limit-and-foxwidow-content-limit-wzxhzdk21wzxhzdk22">fox:orphan-content-limit and fox:widow-content-limit # <a id="#widow-orphan-content-limit"></a></h2>
 <p>The two proprietary extension properties, fox:orphan-content-limit and fox:widow-content-limit, are used to improve the layout of list-blocks and tables. If you have a table with many entries, you don't want a single row to be left over on a page. You will want to make sure that at least two or three lines are kept together. The properties take an absolute length which specifies the area at the beginning (fox:widow-content-limit) or at the end (fox:orphan-content-limit) of a table or list-block. The properties are inherited and only have an effect on fo:table and fo:list-block. An example: fox:widow-content-limit="3 * 1.2em" would make sure the you'll have at least three lines (assuming line-height="1.2") together on a table or list-block.</p>
-<h2 id="external-document">fox:external-document</h2>
+<h2 id="foxexternal-document-wzxhzdk23wzxhzdk24">fox:external-document # <a id="#external-document"></a></h2>
 <p>This feature is incomplete. Support for multi-page documents will be added shortly. At the moment, only single-page images will work. And this will not work with RTF output.
 This is a proprietary extension element which allows to add whole images as pages to an FO document. For example, if you have a scanned document or a fax as multi-page TIFF file, you can append or insert this document using the <code>fox:external-document</code> element. Each page of the external document will create one full page in the target format.</p>
 <p>The <code>fox:external-document</code> element is structurally a peer to <code>fo:page-sequence</code> , so wherever you can put an <code>fo:page-sequence</code> you could also place a <code>fox:external-document</code> . Therefore, the specified contents for <code>fo:root</code> change to:</p>
 <p><code>(layout-master-set, declarations?, bookmark-tree?, (page-sequence|page-sequence-wrapper|fox:external-document|fox:destination)+)</code> </p>
-<h3 id="Specification">Specification</h3>
+<h3 id="specification-wzxhzdk25wzxhzdk26">Specification ## <a id="#Specification"></a></h3>
 <p>The <code>fox:external-document</code> extension formatting object is used to specify how to create a (sub-)sequence of pages within a document. The content of these pages comes from the individual subimages/pages of an image or paged document (for example: multi-page TIFF in the form of faxes or scanned documents, or PDF files). The formatting object creates the necessary areas to display one image per page.</p>
 <p>In terms of page numbers, the behaviour is the same as for <code>fo:page-sequence</code> . The placement of the image inside the page is similar to that of <code>fo:external-graphic</code> or <code>fo:instream-foreign-object</code> , i.e. the viewport (and therefore the page size) is defined by either the intrinsic size of the image or by the size properties that apply to this formatting object.</p>
 <p>Content: EMPTY</p>
@@ -422,16 +422,16 @@ This is a proprietary extension element 
 <p>Datatype "page-set": Value: auto | <integer-range>, Default: "auto" which means all pages/subimages of the document. <integer-range> allows values such as "7" or "1-3"
  <code>fox:external-document</code> is not suitable for concatenating FO documents. For this, XInclude is recommended.</p>
-<h2 id="transform">Free-form Transformation for fo:block-container</h2>
+<h2 id="free-form-transformation-for-foblock-container-wzxhzdk29wzxhzdk30">Free-form Transformation for fo:block-container # <a id="#transform"></a></h2>
 <p>For <code>fo:block-container</code> elements whose <code>absolute-position</code> set to "absolute" or "fixed" you can use the extension attribute <code>fox:transform</code> to apply a free-form transformation to the whole block-container. The content of the <code>fox:transform</code> attribute is the same as for <a href="http://www.w3.org/TR/SVG/coords.html#TransformAttribute">SVG's transform attribute</a> . The transformation specified here is performed in addition to other implicit transformations of the block-container (resulting from top, left and other properties) and after them.</p>
 <p>Examples: <code>fox:transform="rotate(45)"</code> would rotate the block-container by 45 degrees clock-wise around its upper-left corner. <code>fox:transform="translate(10000,0)"</code> would move the block-container to the right by 10 points (=10000 millipoints, FOP uses millipoints internally!).
 This extension attribute doesn't work for all output formats! It's currently only supported for PDF, PS and Java2D-based renderers.</p>
-<h2 id="color-functions">Color functions</h2>
+<h2 id="color-functions-wzxhzdk31wzxhzdk32">Color functions # <a id="#color-functions"></a></h2>
 <p>XSL-FO supports specifying color using the rgb(), rgb-icc() and system-color() functions. Apache FOP provides additional color functions for special use cases. Please note that using these functions compromises the interoperability of an FO document.</p>
-<h3 id="color-function-cmyk">cmyk()</h3>
+<h3 id="cmyk-wzxhzdk33wzxhzdk34">cmyk() ## <a id="#color-function-cmyk"></a></h3>
 <p><code>color cmyk(numeric, numeric, numeric, numeric)</code> </p>
 <p>This function will construct a color in device-specific CMYK color space. The numbers must be between 0.0 and 1.0. For output formats that don't support device-specific color space the CMYK value is converted to an sRGB value.</p>
-<h3 id="pseudo-color-profiles">#CMYK pseudo-profile</h3>
+<h3 id="cmyk-pseudo-profile-wzxhzdk35wzxhzdk36">#CMYK pseudo-profile ## <a id="#pseudo-color-profiles"></a></h3>
 <p><code>color rgb-icc(numeric, numeric, numeric, #CMYK, numeric, numeric, numeric, numeric)</code> </p>
 <p>The <code>rgb-icc</code> function will respond to a pseudo-profile called "#CMYK" which indicates a device-specific CMYK color space. The "#CMYK" profile is implicitely available and doesn't have to be (and cannot be) defined through an <code>fo:color-profile</code> element. It is provided for compatibility with certain commercial XSL-FO implementations. Please note that this is not part of the official specification but rather a convention. The following two color specifications are equivalent:</p>
@@ -442,7 +442,7 @@ This extension attribute doesn't work fo
 <p><code>rgb-icc(153, 153, 102, #CMYK, 0, 0, 0.2, 0.4)</code> </p>
-<h2 id="rounded-corners">Rounded Corners</h2>
+<h2 id="rounded-corners-wzxhzdk37wzxhzdk38">Rounded Corners # <a id="#rounded-corners"></a></h2>
 <p>Rounded corners on block areas can be specified with the <code>fox:border-*-*-radius</code> properties. Each corner can be specified with two radii that define a quarter ellipse that defines the shape of the corner of the outer border edge (in accordance with the <a href="http://www.w3.org/TR/css3-background/#the-border-radius">W3 CSS3 Recommendation</a>).
 The property <code>fox:border-BP-IP-radius</code> specifies the radius of the corner connecting border segment <em>BP</em> is one of '<em>before|after</em>' and <em>IP</em> is one of 'start|end<em>', and takes one or two values.  A single value will generate circular corners.  Two values define elliptic corners where the first value defines the radius in the </em>Inline Progression Direction<em>, and the second the radius in the </em>Block Progression Direction*.</p>
 <p>The shorthand property <code>fox:border-radius</code> can be used to specify uniform corners and takes 1 or 2 values, as above.</p>
@@ -452,27 +452,27 @@ The property <code>fox:border-BP-IP-radi
 <li>CSS3-style absolute properties, e.g <code>border-top-left-radius</code>, are not supported</li>
 <li>Rounded corners on tables are not directly supported.  To set rounded corners at the table level the table must have the property <code>border-collapse</code> property set to <code>separate</code></li>
-<h2 id="prepress">Prepress Support</h2>
+<h2 id="prepress-support-wzxhzdk39wzxhzdk40">Prepress Support # <a id="#prepress"></a></h2>
 <p>This section defines a number of extensions related to <a href="http://en.wikipedia.org/wiki/Prepress">prepress</a> support. <code>fox:scale</code> defines a general scale factor for the generated pages. <code>fox:bleed</code> defines the <a href="http://en.wikipedia.org/wiki/Bleed_%28printing%29">bleed area</a> for a page. <code>fox:crop-offset</code> defines the outer edges of the area in which crop marks, registration marks, color bars and page information are placed. For details, please read on below.
 Those extensions have been implemented in the PDF and Java2D renderers only.</p>
-<h3 id="scale">fox:scale</h3>
+<h3 id="foxscale-wzxhzdk41wzxhzdk42">fox:scale ## <a id="#scale"></a></h3>
 <p>Value: <number>{1,2}</p>
 <p>Initial: 1</p>
 <p>Applies to: fo:simple-page-master</p>
 <p>This property specifies a scale factor along resp. the x and y axes. If only one number is provided it is used for both the x and y scales. A scale factor smaller than 1 shrinks the page. A scale factor greater than 1 enlarges the page.</p>
-<h3 id="bleed">fox:bleed</h3>
+<h3 id="foxbleed-wzxhzdk44wzxhzdk45">fox:bleed ## <a id="#bleed"></a></h3>
 <p>Value: <length>{1,4}</p>
 <p>Initial: 0pt</p>
 <p>Applies to: fo:simple-page-master</p>
 <p>If there is only one value, it applies to all sides. If there are two values, the top and bottom bleed widths are set to the first value and the right and left bleed widths are set to the second. If there are three values, the top is set to the first value, the left and right are set to the second, and the bottom is set to the third. If there are four values, they apply to the top, right, bottom, and left, respectively. (Corresponds to <a href="http://www.w3.org/TR/xsl11/#padding">the definition of padding</a> ).</p>
 <p>This extension indirectly defines the BleedBox and is calculated by expanding the TrimBox by the bleed widths. The lengths must be non-negative.</p>
-<h3 id="cropOffset">fox:crop-offset</h3>
+<h3 id="foxcrop-offset-wzxhzdk47wzxhzdk48">fox:crop-offset ## <a id="#cropOffset"></a></h3>
 <p>Value: <length>{1,4}</p>
 <p>Initial: bleed (see below)</p>
 <p>Applies to: fo:simple-page-master</p>
 <p>Same behaviour as with fox:bleed. The initial value is set to the same values as the fox:bleed property.</p>
 <p>This extension indirectly defines the MediaBox and is calculated by expanding the TrimBox by the crop offsets. The lengths must be non-negative.</p>
-<h3 id="cropBox">fox:crop-box</h3>
+<h3 id="foxcrop-box-wzxhzdk50wzxhzdk51">fox:crop-box ## <a id="#cropBox"></a></h3>
 <p>Value: [trim-box | bleed-box | media-box]</p>
 <p>Initial: media-box</p>
 <p>Applies to: fo:simple-page-master</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html Tue Oct 23 15:05:41 2012
@@ -331,7 +331,7 @@ $(document).ready(function () {
       <div id="content" class="grid_16">
       	<!-- <div id="breadcrumb"><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/trunk/">Trunk</a></div> -->
       	<div class="section-content"><p><version>$Revision: 1298724 $</version><authors><person email="" name="Jeremias Märki"></person><person email="" name="Tore Engvig"></person><person email="" name="Adrian Cumiskey"></person><person email="" name="Max Berger"></person></authors></p>
-<h1 id="intro">Summary</h1>
+<h1 id="summary-wzxhzdk15wzxhzdk16">Summary  <a id="#intro"></a></h1>
 <p>The following table summarizes the font capabilities of the various Apache� FOP renderers:</p>
@@ -409,7 +409,7 @@ $(document).ready(function () {
-<h1 id="base-14-fonts-base-14fonts">Base-14 Fonts # {#Base-14+Fonts}</h1>
+<h1 id="base-14-fonts-wzxhzdk17wzxhzdk18">Base-14 Fonts  <a id="#Base-14+Fonts"></a></h1>
 <p>The Adobe PostScript and PDF Specification specify a set of 14 fonts that must be available to every PostScript interpreter and PDF reader: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats.</p>
 <p>The following font family names are hard-coded into FOP for the Base-14 font set:</p>
@@ -443,14 +443,14 @@ $(document).ready(function () {
 <p>Please note that recent versions of Adobe Acrobat Reader replace "Helvetica" with "Arial" and "Times" with "Times New Roman" internally. GhostScript replaces "Helvetica" with "Nimbus Sans L" and "Times" with "Nimbus Roman No9 L". Other document viewers may do similar font substitutions. If you need to make sure that there are no such substitutions, you need to specify an explicit font and embed it in the target document.</p>
-<h1 id="missing-fonts">Missing Fonts</h1>
+<h1 id="missing-fonts-wzxhzdk19wzxhzdk20">Missing Fonts  <a id="#missing-fonts"></a></h1>
 <p>When FOP does not have a specific font at its disposal (because it's not installed in the operating system or set up in FOP's configuration), the font is replaced with "any". "any" is internally mapped to the Base-14 font "Times" (see above).</p>
-<h1 id="missing-glyphs">Missing Glyphs</h1>
+<h1 id="missing-glyphs-wzxhzdk21wzxhzdk22">Missing Glyphs  <a id="#missing-glyphs"></a></h1>
 <p>Every font contains a particular set of <a href="http://en.wikipedia.org/wiki/Glyph">glyphs</a> . If no glyph can be found for a given character, FOP will issue a warning and use the glpyh for "#" (if available) instead. Before it does that, it consults a (currently hard-coded) registry of glyph substitution groups (see Glyphs.java in Apache XML Graphics Commons). This registry can supply alternative glyphs in some cases (like using space when a no-break space is requested). But there's no guarantee that the result will be as expected (for example, in the case of hyphens and similar glyphs). A better way is to use a font that has all the necessary glyphs. This glyph substitution is only a last resort.</p>
-<h1 id="awt">Java2D/AWT/Operating System Fonts</h1>
+<h1 id="java2dawtoperating-system-fonts-wzxhzdk23wzxhzdk24">Java2D/AWT/Operating System Fonts  <a id="#awt"></a></h1>
 <p>The Java2D family of renderers (Java2D, AWT, Print, TIFF, PNG), use the Java AWT subsystem for font metric information. Through operating system registration, the AWT subsystem knows what fonts are available on the system, and the font metrics for each one.</p>
 <p>When working with one of these output formats and you're missing a font, just install it in your operating system and they should be available for these renderers. Please note that this is not true for other output formats such as PDF or PostScript.</p>
-<h1 id="custom">Custom Fonts</h1>
+<h1 id="custom-fonts-wzxhzdk25wzxhzdk26">Custom Fonts  <a id="#custom"></a></h1>
 <p>Support for custom fonts is highly output format dependent (see above table). This section shows how to add Type 1 and TrueType fonts to the PDF, PostScript and Java2D-based renderers. Other renderers (like AFP) support other font formats. Details in this case can be found on the page about <a href="output.html">output formats</a> .</p>
 <p>In earlier FOP versions, it was always necessary to create an XML font metrics file if you wanted to add a custom font. This unconvenient step has been removed and in addition to that, FOP supports auto-registration of fonts, i.e. FOP can find fonts installed in your operating system or can scan user-specified directories for fonts. Font registration via XML font metrics file is still supported and may still be necessary for some very special cases as fallback variant while we stabilize font auto-detection.</p>
 <p>Basic information about fonts can be found at:</p>
@@ -462,7 +462,7 @@ $(document).ready(function () {
 <p><a href="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</a> </p>
-<h1 id="basics">Basic font configuration</h1>
+<h1 id="basic-font-configuration-wzxhzdk27wzxhzdk28">Basic font configuration  <a id="#basics"></a></h1>
 <p>If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). In the basic form, you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.</p>
    <renderer mime="application/pdf">
@@ -480,9 +480,9 @@ $(document).ready(function () {
 </renderers>Review the documentation for <a href="configuration.html">FOP Configuration</a> for instructions on making the FOP configuration available to FOP when it runs. Otherwise, FOP has no way of finding your custom font information. It is currently not possible to easily configure fonts from Java code.</p>
-<h1 id="advanced">Advanced font configuration</h1>
+<h1 id="advanced-font-configuration-wzxhzdk37wzxhzdk38">Advanced font configuration  <a id="#advanced"></a></h1>
 <p>The instructions found above should be sufficient for most users. Below are some additional instructions in case the basic font configuration doesn't lead to the desired results.</p>
-<h2 id="type1-metrics">Type 1 Font Metrics</h2>
+<h2 id="type-1-font-metrics-wzxhzdk39wzxhzdk40">Type 1 Font Metrics # <a id="#type1-metrics"></a></h2>
 <p>FOP includes PFMReader, which reads the PFM file that normally comes with a Type 1 font, and generates an appropriate font metrics file for it. To use it, run the class org.apache.fop.fonts.apps.PFMReader:</p>
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
@@ -495,7 +495,7 @@ PFMReader [options]:</p>
 <li><strong>-fn <fontname></strong> By default, FOP uses the fontname from the .pfm file when embedding the font. Use the "-fn" option to override this name with one you have chosen. This may be useful in some cases to ensure that applications using the output document (Acrobat Reader for example) use the embedded font instead of a local font with the same name.
 The classpath in the above example has been simplified for readability. You will have to adjust the classpath to the names of the actual JAR files in the lib directory. xml-apis.jar, xercesImpl.jar, xalan.jar and serializer.jar are not necessary for JDK version 1.4 or later.The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and calculations which are only an approximation to the real values. FontBBox and Italic Angle can be found in the human-readable part of the PFB file or in the AFM file. The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually. The constructed values however appear to have no visible influence.</li>
-<h2 id="truetype-metrics">TrueType Font Metrics</h2>
+<h2 id="truetype-font-metrics-wzxhzdk41wzxhzdk42">TrueType Font Metrics # <a id="#truetype-metrics"></a></h2>
 <p>FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it. Use it in a similar manner to PFMReader. For example, to create such a metrics file in Windows from the TrueType font at c:\myfonts\cmr10.ttf:
 java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
           org.apache.fop.fonts.apps.TTFReader [options]
@@ -540,7 +540,7 @@ TTFReader [options]:</p>
-<td id="truetype-collections-metrics">## TrueType Collections</td>
+<td>## TrueType Collections # <a id="#truetype-collections-metrics"></a></td>
@@ -556,7 +556,7 @@ Alternatively, the individual sub-fonts 
 <font embed-url="gulim.ttc" sub-font="GulimChe">
   <font-triplet name="GulimChe" style="normal" weight="normal"/>
-<h2 id="register">Register Fonts with FOP</h2>
+<h2 id="register-fonts-with-fop-wzxhzdk46wzxhzdk47">Register Fonts with FOP # <a id="#register"></a></h2>
 <p>You must tell FOP how to find and use the font metrics files by registering them in the <a href="configuration.html">FOP Configuration</a> . Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:</p>
    <renderer mime="application/pdf">
@@ -630,7 +630,7 @@ Alternatively, the individual sub-fonts 
 <p>If relative URLs are specified, they are evaluated relative to the value of the "font-base" setting. If there is no "font-base" setting, the fonts are evaluated relative to the base directory.</p>
-<h2 id="autodetect">Auto-Detect and auto-embed feature</h2>
+<h2 id="auto-detect-and-auto-embed-feature-wzxhzdk57wzxhzdk58">Auto-Detect and auto-embed feature # <a id="#autodetect"></a></h2>
 <p>When the "auto-detect" flag is set in the configuration, FOP will automatically search for fonts in the default paths for your operating system.</p>
 <p>FOP will also auto-detect fonts which are available in the classpath, if they are described as "application/x-font" in the MANIFEST.MF file. For example, if your .jar file contains font/myfont.ttf:
 Manifest-Version: 1.0</p>
@@ -640,10 +640,10 @@ Manifest-Version: 1.0</p>
 <p>This feature allows you to create JAR files containing fonts. The JAR files can be added to fop by providem them in the classpath, e.g. copying them into the lib/ directory.</p>
-<h3 id="font-cache">The font cache</h3>
+<h3 id="the-font-cache-wzxhzdk59wzxhzdk60">The font cache ## <a id="#font-cache"></a></h3>
 <p>Apache FOP maintains a cache file that is used to speed up auto-detection. This file is usually found in the ".fop" directory under the user's home directory. It's called "fop-fonts.cache". When the user's home directory is not writable, the font cache file is put in the directory for temporary files.</p>
 <p>If there was a problem loading a particular font, it is flagged in the cache file so it is not loaded anymore. So, if a font is actually around but is still not found by Apache FOP, it's worth a try to delete the font cache file which forces Apache FOP to reparse all fonts.</p>
-<h2 id="embedding">Embedding</h2>
+<h2 id="embedding-wzxhzdk61wzxhzdk62">Embedding # <a id="#embedding"></a></h2>
 <p>By default, all fonts are embedded if an output format supports font embedding. In some cases, however, it is preferred that some fonts are only referenced. When working with referenced fonts it is important to be in control of the target environment where the produced document is consumed, i.e. the necessary fonts have to be installed there.</p>
 <p>There are two different ways how you can specify that a font should be referenced:</p>
@@ -682,7 +682,7 @@ At the moment, you can only match fonts 
 <p>When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document. That's the default, but if you specify encoding-mode="single-byte" (see above), the complete font is embedded.</p>
-<h2 id="substitution">Substitution</h2>
+<h2 id="substitution-wzxhzdk71wzxhzdk72">Substitution # <a id="#substitution"></a></h2>
 <p>When a <substitutions/> section is defined in the configuration, FOP will re-map any font-family references found in your FO input to a given substitution font.</p>
@@ -707,7 +707,7 @@ At the moment, you can only match fonts 
-<h1 id="selection">Font Selection Strategies</h1>
+<h1 id="font-selection-strategies-wzxhzdk88wzxhzdk89">Font Selection Strategies  <a id="#selection"></a></h1>
 <p>There are two font selection strategies: character-by-character or auto. The default is auto.</p>
 <p>Auto selected the first font from the list which is able to display the most characters in a given word. This means (assume font A has characters for abclmn, font B for lnmxyz, fontlist is A,B):</p>
@@ -725,7 +725,7 @@ At the moment, you can only match fonts 
 <p>Character-by-Character is NOT yet supported!</p>
-<h1 id="font-list">Font List Command-Line Tool</h1>
+<h1 id="font-list-command-line-tool-wzxhzdk90wzxhzdk91">Font List Command-Line Tool  <a id="#font-list"></a></h1>
 <p>FOP contains a small command-line tool that lets you generate a list of all configured fonts. Its class name is: <code>org.apache.fop.tools.fontlist.FontListMain</code> . Run it with the "-?" parameter to get help for the various options.</p></div>

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

View raw message