You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2017/02/16 13:05:57 UTC
svn commit: r1006883 [2/2] - in /websites/staging/xmlgraphics/trunk/content:
./ batik/ batik/dev/ batik/tools/ batik/using/ commons/ fop/ fop/0.95/
fop/1.0/ fop/1.1/ fop/2.0/ fop/2.1/ fop/dev/ fop/trunk/
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.0/events.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.0/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.0/events.html Thu Feb 16 13:05:56 2017
@@ -618,7 +618,7 @@ h2:hover > .headerlink, h3:hover > .head
<h3 id="event-model">The event model<a class="headerlink" href="#event-model" title="Permanent link">¶</a></h3>
-<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>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="https://github.com/codehaus/qdox">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>
@@ -650,7 +650,7 @@ h2:hover > .headerlink, h3:hover > .head
<p><strong><code>org.apache.fop.events.EventExceptionManager$ExceptionFactory</code>:</strong> Creates exceptions for events, i.e. turns an event into a specific exception.</p>
</li>
</ul>
-<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>
+<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://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider">JAR file specification</a>.</p>
<h3 id="l10n">Localization (L10n)<a class="headerlink" href="#l10n" title="Permanent link">¶</a></h3>
<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:</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.0/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.0/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.0/fonts.html Thu Feb 16 13:05:56 2017
@@ -719,7 +719,7 @@ h2:hover > .headerlink, h3:hover > .head
</li>
</ol>
-<p>At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the <a href="http://java.sun.com/j2se/1.4/docs/api/java/util/regex/package-summary.html">package</a>. So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify <code>font-family=".*"</code>.</p>
+<p>At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the <a href="https://docs.oracle.com/javase/7/docs/api/java/util/regex/package-summary.html">package</a>. So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify <code>font-family=".*"</code>.</p>
<p>The <code>referenced-fonts</code> element can be placed either inside the general <code>fonts</code> element (right under the root) or in the <code>fonts</code> element under the renderer configuration. In the first case, matches apply to all renderers. In the second case, matches only apply to the renderer where the element was specified. Both cases can be used at the same time.</p>
<h3 id="embedding_fonts">Embedding Fonts<a class="headerlink" href="#embedding_fonts" title="Permanent link">¶</a></h3>
<p>Some notes related to embedded fonts:</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.0/graphics.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.0/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.0/graphics.html Thu Feb 16 13:05:56 2017
@@ -562,10 +562,10 @@ h2:hover > .headerlink, h3:hover > .head
<p>"(X)" means restricted support. Please see the details below.</p>
</li>
<li>
-<p>[1]: Requires the presence of <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.</p>
+<p>[1]: Requires the presence of <a href="https://github.com/jai-imageio/jai-imageio-core">JAI Image I/O Tools</a> (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.</p>
</li>
</ul>
-<p><note><a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a> ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note></p>
+<p><note><a href="https://github.com/jai-imageio/jai-imageio-core">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a> ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note></p>
<h3 id="format-map">Map of supported image formats by output format<a class="headerlink" href="#format-map" title="Permanent link">¶</a></h3>
<p>Not all image formats are supported for all output formats! For example, while you can use EPS (Encapsulated PostScript) files when you generate PostScript output, this format will not be supported by any other output format. Here's an overview of which image formats are supported by which output format:</p>
<table class="table">
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.0/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.0/hyphenation.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.0/hyphenation.html Thu Feb 16 13:05:56 2017
@@ -467,7 +467,7 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="support">Hyphenation Support<a class="headerlink" href="#support" title="Permanent link">¶</a></h2>
<h3 id="intro">Introduction<a class="headerlink" href="#intro" title="Permanent link">¶</a></h3>
<p>Apache™ FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.</p>
-<p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a href="http://offo.sourceforge.net/hyphenation/index.html">Objects For Formatting Objects</a> project.</p>
+<p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a href="http://offo.sourceforge.net">Objects For Formatting Objects</a> project.</p>
<p><note>If you have made improvements to an existing Apache™ FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the <a href="../maillist.html#fop-user">FOP User mailing list</a>.</note></p>
<h3 id="license-issues">License Issues<a class="headerlink" href="#license-issues" title="Permanent link">¶</a></h3>
<p>Many of the hyphenation files distributed with TeX and its offspring are licenced under the <a href="http://www.latex-project.org/lppl">LaTeX Project Public License (LPPL)</a>, which prevents them from being distributed with Apache software. The LPPL puts restrictions on file names in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files have other or additional restrictions, for example against use for commercial purposes.</p>
@@ -517,7 +517,7 @@ and run Ant with build target <code>jar-
</ol>
<p><warning>Either of these three options will ensure hyphenation is working when using FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the <a href="configuration.html#hyphenation-dir"><hyphenation-dir></a> configuration option programmatically (option 3).</warning></p>
<h2 id="patterns">Hyphenation Patterns<a class="headerlink" href="#patterns" title="Permanent link">¶</a></h2>
-<p>If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See <a href="http://offo.sourceforge.net/hyphenation/index.html">OFFO's Hyphenation page</a> for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
+<p>If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See <a href="http://offo.sourceforge.net">OFFO's Hyphenation page</a> for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
<warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the <a href="../maillist.html#fop-user">FOP User mailing list</a>, either confirming their accuracy, or raising specific problems that we can address.</warning></p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.0/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.0/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.0/output.html Thu Feb 16 13:05:56 2017
@@ -670,7 +670,7 @@ FO document using the <code>pdf:info</co
<p><a href="http://en.wikipedia.org/wiki/Printer_Control_Language">WikiPedia entry on PCL</a></p>
</li>
<li>
-<p><a href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpl04568">Technical reference documents on PCL from Hewlett-Packard</a></p>
+<p><a href="http://www.hp.com/ctg/Manual/bpl13210.pdf">Technical reference documents on PCL from Hewlett-Packard</a></p>
</li>
</ul>
<h3 id="pcl-limitations">Limitations<a class="headerlink" href="#pcl-limitations" title="Permanent link">¶</a></h3>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.0/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.0/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.0/running.html Thu Feb 16 13:05:56 2017
@@ -511,7 +511,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users have recommended that Mac OSX users use the shell command <code>tar -xzf</code> instead.</p>
<h2 id="standalone-start">Starting FOP as a Standalone Application<a class="headerlink" href="#standalone-start" title="Permanent link">¶</a></h2>
<h3 id="fop-script">Using the fop script or batch file<a class="headerlink" href="#fop-script" title="Permanent link">¶</a></h3>
-<p>The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is <code>/Library/Java/Home</code>. <strong>Caveat:</strong> We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see <a href="http://developer.apple.com/java/faq">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
+<p>The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is <code>/Library/Java/Home</code>. <strong>Caveat:</strong> We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see <a href="https://java.com/en/download/faq/java_mac.xml">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
<div class="codehilite"><pre><span class="n">USAGE</span>
<span class="n">Fop</span> <span class="p">[</span><span class="n">options</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">fo</span><span class="o">|-</span><span class="n">xml</span><span class="p">]</span> <span class="n">infile</span> <span class="p">[</span><span class="o">-</span><span class="n">xsl</span> <span class="n">file</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">awt</span><span class="o">|-</span><span class="n">pdf</span><span class="o">|-</span><span class="n">mif</span><span class="o">|-</span><span class="n">rtf</span><span class="o">|-</span><span class="n">tiff</span><span class="o">|-</span><span class="n">png</span><span class="o">|-</span><span class="n">pcl</span><span class="o">|-</span><span class="n">ps</span><span class="o">|-</span><span class="n">txt</span><span class="o">|-</span><span class="n">at</span> <span class="p">[</span><span class="n">mime</span><
span class="p">]</span><span class="o">|-</span><span class="n">print</span><span class="p">]</span> <span class="o"><</span><span class="n">outfile</span><span class="o">></span>
<span class="p">[</span><span class="n">OPTIONS</span><span class="p">]</span>
@@ -634,7 +634,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>If you are running out of memory when using FOP, here are some ideas that may help:</p>
<ul>
<li>
-<p>Increase memory available to the JVM. See <a href="http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html">the -Xmx option</a> for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning></p>
+<p>Increase memory available to the JVM. See <a href="http://docs.oracle.com/javase/1.5.0/docs/tooldocs/solaris/java.html">the -Xmx option</a> for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning></p>
</li>
<li>
<p>Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (<a href="../faq.html#pagenum">"page N of TOTAL"</a>). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.1/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.1/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.1/anttask.html Thu Feb 16 13:05:56 2017
@@ -579,7 +579,7 @@ h2:hover > .headerlink, h3:hover > .head
<tr>
<td></td>
<td>fileset</td>
-<td><a href="http://ant.apache.org/manual/CoreTypes/fileset.html">FileSets</a> are used to specify multiple XSL-FO files to be rendered.</td>
+<td><a href="https://ant.apache.org/manual/Types/fileset.html">FileSets</a> are used to specify multiple XSL-FO files to be rendered.</td>
<td>Yes, if no fofile attribute is supplied</td>
<td></td>
</tr>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.1/events.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.1/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.1/events.html Thu Feb 16 13:05:56 2017
@@ -618,7 +618,7 @@ h2:hover > .headerlink, h3:hover > .head
<h3 id="event-model">The event model<a class="headerlink" href="#event-model" title="Permanent link">¶</a></h3>
-<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>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="https://github.com/codehaus/qdox">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>
@@ -650,7 +650,7 @@ h2:hover > .headerlink, h3:hover > .head
<p><strong><code>org.apache.fop.events.EventExceptionManager$ExceptionFactory</code>:</strong> Creates exceptions for events, i.e. turns an event into a specific exception.</p>
</li>
</ul>
-<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>
+<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://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider">JAR file specification</a>.</p>
<h3 id="l10n">Localization (L10n)<a class="headerlink" href="#l10n" title="Permanent link">¶</a></h3>
<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:</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.1/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.1/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.1/fonts.html Thu Feb 16 13:05:56 2017
@@ -719,7 +719,7 @@ h2:hover > .headerlink, h3:hover > .head
</li>
</ol>
-<p>At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the <a href="http://java.sun.com/j2se/1.4/docs/api/java/util/regex/package-summary.html">package</a>. So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify <code>font-family=".*"</code>.</p>
+<p>At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the <a href="https://docs.oracle.com/javase/7/docs/api/java/util/regex/package-summary.html">package</a>. So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify <code>font-family=".*"</code>.</p>
<p>The <code>referenced-fonts</code> element can be placed either inside the general <code>fonts</code> element (right under the root) or in the <code>fonts</code> element under the renderer configuration. In the first case, matches apply to all renderers. In the second case, matches only apply to the renderer where the element was specified. Both cases can be used at the same time.</p>
<h3 id="embedding_fonts">Embedding Fonts<a class="headerlink" href="#embedding_fonts" title="Permanent link">¶</a></h3>
<p>Some notes related to embedded fonts:</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.1/graphics.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.1/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.1/graphics.html Thu Feb 16 13:05:56 2017
@@ -562,10 +562,10 @@ h2:hover > .headerlink, h3:hover > .head
<p>"(X)" means restricted support. Please see the details below.</p>
</li>
<li>
-<p>[1]: Requires the presence of <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.</p>
+<p>[1]: Requires the presence of <a href="https://github.com/jai-imageio/jai-imageio-core">JAI Image I/O Tools</a> (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.</p>
</li>
</ul>
-<p><note><a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a> ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note></p>
+<p><note><a href="https://github.com/jai-imageio/jai-imageio-core">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a> ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note></p>
<h3 id="format-map">Map of supported image formats by output format<a class="headerlink" href="#format-map" title="Permanent link">¶</a></h3>
<p>Not all image formats are supported for all output formats! For example, while you can use EPS (Encapsulated PostScript) files when you generate PostScript output, this format will not be supported by any other output format. Here's an overview of which image formats are supported by which output format:</p>
<table class="table">
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.1/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.1/hyphenation.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.1/hyphenation.html Thu Feb 16 13:05:56 2017
@@ -467,7 +467,7 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="support">Hyphenation Support<a class="headerlink" href="#support" title="Permanent link">¶</a></h2>
<h3 id="intro">Introduction<a class="headerlink" href="#intro" title="Permanent link">¶</a></h3>
<p>Apache™ FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.</p>
-<p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a href="http://offo.sourceforge.net/hyphenation/index.html">Objects For Formatting Objects</a> project.</p>
+<p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a href="http://offo.sourceforge.net">Objects For Formatting Objects</a> project.</p>
<p><note>If you have made improvements to an existing Apache™ FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the <a href="../maillist.html#fop-user">FOP User mailing list</a>.</note></p>
<h3 id="license-issues">License Issues<a class="headerlink" href="#license-issues" title="Permanent link">¶</a></h3>
<p>Many of the hyphenation files distributed with TeX and its offspring are licenced under the <a href="http://www.latex-project.org/lppl">LaTeX Project Public License (LPPL)</a>, which prevents them from being distributed with Apache software. The LPPL puts restrictions on file names in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files have other or additional restrictions, for example against use for commercial purposes.</p>
@@ -517,7 +517,7 @@ and run Ant with build target <code>jar-
</ol>
<p><warning>Either of these three options will ensure hyphenation is working when using FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the <a href="configuration.html#hyphenation-dir"><hyphenation-dir></a> configuration option programmatically (option 3).</warning></p>
<h2 id="patterns">Hyphenation Patterns<a class="headerlink" href="#patterns" title="Permanent link">¶</a></h2>
-<p>If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See <a href="http://offo.sourceforge.net/hyphenation/index.html">OFFO's Hyphenation page</a> for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
+<p>If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See <a href="http://offo.sourceforge.net">OFFO's Hyphenation page</a> for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
<warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the <a href="../maillist.html#fop-user">FOP User mailing list</a>, either confirming their accuracy, or raising specific problems that we can address.</warning></p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.1/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.1/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.1/output.html Thu Feb 16 13:05:56 2017
@@ -667,7 +667,7 @@ FO document using the <code>pdf:info</co
<p><a href="http://en.wikipedia.org/wiki/Printer_Control_Language">WikiPedia entry on PCL</a></p>
</li>
<li>
-<p><a href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpl04568">Technical reference documents on PCL from Hewlett-Packard</a></p>
+<p><a href="http://www.hp.com/ctg/Manual/bpl13210.pdf">Technical reference documents on PCL from Hewlett-Packard</a></p>
</li>
</ul>
<h3 id="pcl-limitations">Limitations<a class="headerlink" href="#pcl-limitations" title="Permanent link">¶</a></h3>
Modified: websites/staging/xmlgraphics/trunk/content/fop/2.1/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.1/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.1/running.html Thu Feb 16 13:05:56 2017
@@ -511,7 +511,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users have recommended that Mac OSX users use the shell command <code>tar -xzf</code> instead.</p>
<h2 id="standalone-start">Starting FOP as a Standalone Application<a class="headerlink" href="#standalone-start" title="Permanent link">¶</a></h2>
<h3 id="fop-script">Using the fop script or batch file<a class="headerlink" href="#fop-script" title="Permanent link">¶</a></h3>
-<p>The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is <code>/Library/Java/Home</code>. <strong>Caveat:</strong> We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see <a href="http://developer.apple.com/java/faq">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
+<p>The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is <code>/Library/Java/Home</code>. <strong>Caveat:</strong> We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see <a href="https://java.com/en/download/faq/java_mac.xml">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
<div class="codehilite"><pre><span class="n">USAGE</span>
<span class="n">Fop</span> <span class="p">[</span><span class="n">options</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">fo</span><span class="o">|-</span><span class="n">xml</span><span class="p">]</span> <span class="n">infile</span> <span class="p">[</span><span class="o">-</span><span class="n">xsl</span> <span class="n">file</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">awt</span><span class="o">|-</span><span class="n">pdf</span><span class="o">|-</span><span class="n">mif</span><span class="o">|-</span><span class="n">rtf</span><span class="o">|-</span><span class="n">tiff</span><span class="o">|-</span><span class="n">png</span><span class="o">|-</span><span class="n">pcl</span><span class="o">|-</span><span class="n">ps</span><span class="o">|-</span><span class="n">txt</span><span class="o">|-</span><span class="n">at</span> <span class="p">[</span><span class="n">mime</span><
span class="p">]</span><span class="o">|-</span><span class="n">print</span><span class="p">]</span> <span class="o"><</span><span class="n">outfile</span><span class="o">></span>
<span class="p">[</span><span class="n">OPTIONS</span><span class="p">]</span>
@@ -634,7 +634,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>If you are running out of memory when using FOP, here are some ideas that may help:</p>
<ul>
<li>
-<p>Increase memory available to the JVM. See <a href="http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html">the -Xmx option</a> for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning></p>
+<p>Increase memory available to the JVM. See <a href="http://docs.oracle.com/javase/1.5.0/docs/tooldocs/solaris/java.html">the -Xmx option</a> for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning></p>
</li>
<li>
<p>Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (<a href="../faq.html#pagenum">"page N of TOTAL"</a>). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).</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 Thu Feb 16 13:05:56 2017
@@ -3064,7 +3064,7 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="version_0.20.5">Version 0.20.5 (18 July 2003)<a class="headerlink" href="#version_0.20.5" title="Permanent link">¶</a></h2>
<h3 id="Code_0.20.5">Changes to the Code Base<a class="headerlink" href="#Code_0.20.5" title="Permanent link">¶</a></h3>
<ul>
-<li><img alt="update" src="/images/update.jpg" /> For the change log for the maintenance branch (where FOP 0.20.5 came from), please see the "CHANGES" file in the distribution, or <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/branches/fop-0_20_2-maintain/CHANGES?view=markup">the CHANGES file in the SVN repository</a>. Committed by all.</li>
+<li><img alt="update" src="/images/update.jpg" /> For the change log for the maintenance branch (where FOP 0.20.5 came from), please see the "CHANGES" file in the distribution, or <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/tags/fop-0_20_5/CHANGES?view=markup">the CHANGES file in the SVN repository</a>. Committed by all.</li>
</ul>
<h3 id="contributors_0.20.5">Contributors to this release<a class="headerlink" href="#contributors_0.20.5" title="Permanent link">¶</a></h3>
<p>We thank the following people for their contributions to this release.</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html Thu Feb 16 13:05:56 2017
@@ -483,7 +483,7 @@ h2:hover > .headerlink, h3:hover > .head
<warning>This documentation is a work in progress. If you see errors or omissions, please report them to the <a href="index.html#mail-fop-dev">fop-dev mailing list</a>.</warning></p>
<h1 id="userdoc">User Documentation<a class="headerlink" href="#userdoc" title="Permanent link">¶</a></h1>
<h3 id="userdoc-overview">Overview<a class="headerlink" href="#userdoc-overview" title="Permanent link">¶</a></h3>
-<p>Perhaps the easiest way to see how to use RTFLib is by looking at an example. A set of test documents is part of the package, and can be <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/">viewed online</a>. A quick look at the Abstract <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/TestDocument.java?rev=HEAD&content-type=text/vnd.viewcvs-markup">TestDocument</a> class, and one of the Concrete subclasses, <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/SimpleDocument.java?rev=HEAD&content-type=text/vnd.viewcvs-markup">SimpleDocument</a> will provide the basics of how to use the package.</p>
+<p>Perhaps the easiest way to see how to use RTFLib is by looking at an example. A set of test documents is part of the package, and can be <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/fop-core/src/test/java/org/apache/fop/render/rtf/rtflib/testdocs/">viewed online</a>. A quick look at the Abstract <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/fop-core/src/test/java/org/apache/fop/render/rtf/rtflib/testdocs/TestDocument.java?rev=HEAD&content-type=text/vnd.viewcvs-markup">TestDocument</a> class, and one of the Concrete subclasses, <a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/fop-core/src/test/java/org/apache/fop/render/rtf/rtflib/testdocs/SimpleDocument.java?rev=HEAD&content-type=text/vnd.viewcvs-markup">SimpleDocument</a> will provide the basics of how to use the package.</p>
<p>There are two basic concepts you will need to understand in order to use RTFLib:</p>
<ul>
<li>
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 Thu Feb 16 13:05:56 2017
@@ -489,7 +489,7 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="svn">Subversion (SVN)<a class="headerlink" href="#svn" title="Permanent link">¶</a></h2>
<h3 id="svn_general">General<a class="headerlink" href="#svn_general" title="Permanent link">¶</a></h3>
<p>Visit <a href="http://xmlgraphics.apache.org/repo.html">Apache XML Graphics Code Repositories</a> for useful information.</p>
-<p>You will need a SVN client to be able to gain access to the FOP repository. For general SVN information, visit <a href="http://subversion.tigris.org">Subversion Home</a>. A comprehensive list of clients for all operating systems and many IDEs can be found at <a href="http://subversion.tigris.org/project_links.html">the Subversion Links page</a>. For Microsoft Windows we recommend <a href="http://tortoisesvn.tigris.org">TortoiseSVN</a>. The command-line client that comes with Subversion is also very easy to use.</p>
+<p>You will need a SVN client to be able to gain access to the FOP repository. For general SVN information, visit <a href="http://subversion.tigris.org">Subversion Home</a>. A comprehensive list of clients for all operating systems and many IDEs can be found at <a href="https://en.wikipedia.org/wiki/Comparison_of_Subversion_clients">the Subversion Links page</a>. For Microsoft Windows we recommend <a href="http://tortoisesvn.tigris.org">TortoiseSVN</a>. The command-line client that comes with Subversion is also very easy to use.</p>
<h3 id="svn_download">Step-by-step instruction for downloading FOP using the SVN command-line client<a class="headerlink" href="#svn_download" title="Permanent link">¶</a></h3>
<p>On the command-line (Windows or Unix), simply run:</p>
<p><code>svn co http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ fop-trunk</code></p>
@@ -534,7 +534,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>[electronic manual] <a href="http://svnbook.red-bean.com">Version Control with Subversion</a> (official Subversion manual). Note that this manual applies to the command-line version of SVN.</p>
</li>
<li>
-<p>[online resource] <a href="http://subversion.tigris.org/project_links.html">Comprehensive list of links to documentation and Subversion clients and plugins.</a></p>
+<p>[online resource] <a href="https://en.wikipedia.org/wiki/Comparison_of_Subversion_clients">Comprehensive list of links to documentation and Subversion clients and plugins.</a></p>
</li>
</ul>
<h2 id="ide">Integrated Development Environments (IDEs)<a class="headerlink" href="#ide" title="Permanent link">¶</a></h2>
Modified: websites/staging/xmlgraphics/trunk/content/fop/faq.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/faq.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/faq.html Thu Feb 16 13:05:56 2017
@@ -732,7 +732,7 @@ then please <a href="bugs.html#issues_ne
<h3 id="svg-attribute-required">5.6. FOP fails with something like "The attribute "width" of the element <rect> is required". What's wrong?<a class="headerlink" href="#svg-attribute-required" title="Permanent link">¶</a></h3>
<p>This phenomenon is not a bug in FOP, but rather in the dependent packages: Apache Batik, Apache Xalan-J and SAXON. The bug in Apache Batik will be fixed in the next release. In the latest release of Apache Xalan-J, the bug is already fixed. It only occurs in the Xalan version bundled with Sun's JVM, because Sun uses a rather old version.</p>
<p>Bug description: In a namespace-enabled Level 3 DOM, an attribute in the default namespace must be set with <code>"null"</code> as the value for the namespace URI. SAX, on the other side, uses an empty string ("") to designate the default namespace. Many packages appear to not properly handle this difference in which case they still use the empty string as the namespace URI parameter for <code>org.w3c.dom.Element.setAttributeNS()</code>.</p>
-<p>Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</a>, i.e. you must place Xalan-J in the <code>"lib/endorsed"</code> directory of your JRE.</p>
+<p>Work-around: Use the latest version of Apache Xalan-J. Note that starting with JDK 1.4 it's not enough to replace Xalan-J on the normal application classpath and you need to override the Xalan-J version bundled with the Sun JVM using the <a href="https://docs.oracle.com/javase/6/docs/technotes/guides/standards/">Endorsed Standards Override Mechanism</a>, i.e. you must place Xalan-J in the <code>"lib/endorsed"</code> directory of your JRE.</p>
<h2 id="part-pdf">6. PDF specific (includes Acrobat peculiarities)<a class="headerlink" href="#part-pdf" title="Permanent link">¶</a></h2>
<h3 id="pdf-embed-font">6.1. How do I embed fonts in PDF?<a class="headerlink" href="#pdf-embed-font" title="Permanent link">¶</a></h3>
<p>See the <a href="1.1/fonts.html">Fonts</a> page for information about embedding fonts.</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/resources.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/resources.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/resources.html Thu Feb 16 13:05:56 2017
@@ -767,7 +767,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>[software] <a href="http://xmlroff.org/">xmlroff</a> an open source XSL-FO implementation written in C (BSD-style license)</p>
</li>
<li>
-<p>[commercial software developer] <a href="http://antennahouse.com/product.htm">Antenna House</a> - XSL Formatter, WordMLToFo, XML Editor...</p>
+<p>[commercial software developer] <a href="https://www.antennahouse.com/antenna1/products/">Antenna House</a> - XSL Formatter, WordMLToFo, XML Editor...</p>
</li>
<li>
<p>[commercial software developer] <a href="http://www.renderx.com/tools/index.html">RenderX</a> XEP, EnMasse, Docbench...</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html Thu Feb 16 13:05:56 2017
@@ -579,7 +579,7 @@ h2:hover > .headerlink, h3:hover > .head
<tr>
<td></td>
<td>fileset</td>
-<td><a href="http://ant.apache.org/manual/CoreTypes/fileset.html">FileSets</a> are used to specify multiple XSL-FO files to be rendered.</td>
+<td><a href="https://ant.apache.org/manual/Types/fileset.html">FileSets</a> are used to specify multiple XSL-FO files to be rendered.</td>
<td>Yes, if no fofile attribute is supplied</td>
<td></td>
</tr>
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 Thu Feb 16 13:05:56 2017
@@ -618,7 +618,7 @@ h2:hover > .headerlink, h3:hover > .head
<h3 id="event-model">The event model<a class="headerlink" href="#event-model" title="Permanent link">¶</a></h3>
-<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>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="https://github.com/codehaus/qdox">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>
@@ -650,7 +650,7 @@ h2:hover > .headerlink, h3:hover > .head
<p><strong><code>org.apache.fop.events.EventExceptionManager$ExceptionFactory</code>:</strong> Creates exceptions for events, i.e. turns an event into a specific exception.</p>
</li>
</ul>
-<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>
+<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://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider">JAR file specification</a>.</p>
<h3 id="l10n">Localization (L10n)<a class="headerlink" href="#l10n" title="Permanent link">¶</a></h3>
<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:</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 Thu Feb 16 13:05:56 2017
@@ -779,7 +779,7 @@ h2:hover > .headerlink, h3:hover > .head
</li>
</ol>
-<p>At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the <a href="http://java.sun.com/j2se/1.4/docs/api/java/util/regex/package-summary.html">package</a>. So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify <code>font-family=".*"</code>.</p>
+<p>At the moment, you can only match fonts against their font-family. It is possible to use regular expressions as is shown in the second example above ("DejaVu.*"). The syntax for the regular expressions used here are the one used by the <a href="https://docs.oracle.com/javase/7/docs/api/java/util/regex/package-summary.html">package</a>. So, in the above snippet "Helvetica" and all variants of the "DejaVu" font family are referenced. If you want to reference all fonts, just specify <code>font-family=".*"</code>.</p>
<p>The <code>referenced-fonts</code> element can be placed either inside the general <code>fonts</code> element (right under the root) or in the <code>fonts</code> element under the renderer configuration. In the first case, matches apply to all renderers. In the second case, matches only apply to the renderer where the element was specified. Both cases can be used at the same time.</p>
<h3 id="embedding_fonts">Embedding Fonts<a class="headerlink" href="#embedding_fonts" title="Permanent link">¶</a></h3>
<p>Some notes related to embedded fonts:</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/graphics.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/graphics.html Thu Feb 16 13:05:56 2017
@@ -562,10 +562,10 @@ h2:hover > .headerlink, h3:hover > .head
<p>"(X)" means restricted support. Please see the details below.</p>
</li>
<li>
-<p>[1]: Requires the presence of <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.</p>
+<p>[1]: Requires the presence of <a href="https://github.com/jai-imageio/jai-imageio-core">JAI Image I/O Tools</a> (or an equivalent Image I/O compatible codec) in the classpath. JAI Image I/O Tools also adds support for JPEG 2000, WBMP, RAW and PNM. Other Image I/O codecs may provide support for additional formats.</p>
</li>
</ul>
-<p><note><a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a> ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note></p>
+<p><note><a href="https://github.com/jai-imageio/jai-imageio-core">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a> ! The former simply exposes JAI's codecs using the Image I/O API but does not include all the image manipulation functionality.</note></p>
<h3 id="format-map">Map of supported image formats by output format<a class="headerlink" href="#format-map" title="Permanent link">¶</a></h3>
<p>Not all image formats are supported for all output formats! For example, while you can use EPS (Encapsulated PostScript) files when you generate PostScript output, this format will not be supported by any other output format. Here's an overview of which image formats are supported by which output format:</p>
<table class="table">
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/hyphenation.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/hyphenation.html Thu Feb 16 13:05:56 2017
@@ -467,7 +467,7 @@ h2:hover > .headerlink, h3:hover > .head
<h2 id="support">Hyphenation Support<a class="headerlink" href="#support" title="Permanent link">¶</a></h2>
<h3 id="intro">Introduction<a class="headerlink" href="#intro" title="Permanent link">¶</a></h3>
<p>Apache™ FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.</p>
-<p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a href="http://offo.sourceforge.net/hyphenation/index.html">Objects For Formatting Objects</a> project.</p>
+<p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a href="http://offo.sourceforge.net">Objects For Formatting Objects</a> project.</p>
<p><note>If you have made improvements to an existing Apache™ FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the <a href="../maillist.html#fop-user">FOP User mailing list</a>.</note></p>
<h3 id="license-issues">License Issues<a class="headerlink" href="#license-issues" title="Permanent link">¶</a></h3>
<p>Many of the hyphenation files distributed with TeX and its offspring are licenced under the <a href="http://www.latex-project.org/lppl">LaTeX Project Public License (LPPL)</a>, which prevents them from being distributed with Apache software. The LPPL puts restrictions on file names in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files have other or additional restrictions, for example against use for commercial purposes.</p>
@@ -517,7 +517,7 @@ and run Ant with build target <code>jar-
</ol>
<p><warning>Either of these three options will ensure hyphenation is working when using FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the <a href="configuration.html#hyphenation-dir"><hyphenation-dir></a> configuration option programmatically (option 3).</warning></p>
<h2 id="patterns">Hyphenation Patterns<a class="headerlink" href="#patterns" title="Permanent link">¶</a></h2>
-<p>If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See <a href="http://offo.sourceforge.net/hyphenation/index.html">OFFO's Hyphenation page</a> for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
+<p>If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See <a href="http://offo.sourceforge.net">OFFO's Hyphenation page</a> for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
<warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the <a href="../maillist.html#fop-user">FOP User mailing list</a>, either confirming their accuracy, or raising specific problems that we can address.</warning></p>
<ul>
<li>
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 Thu Feb 16 13:05:56 2017
@@ -668,7 +668,7 @@ FO document using the <code>pdf:info</co
<p><a href="http://en.wikipedia.org/wiki/Printer_Control_Language">WikiPedia entry on PCL</a></p>
</li>
<li>
-<p><a href="http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=bpl04568">Technical reference documents on PCL from Hewlett-Packard</a></p>
+<p><a href="http://www.hp.com/ctg/Manual/bpl13210.pdf">Technical reference documents on PCL from Hewlett-Packard</a></p>
</li>
</ul>
<h3 id="pcl-limitations">Limitations<a class="headerlink" href="#pcl-limitations" title="Permanent link">¶</a></h3>
Modified: websites/staging/xmlgraphics/trunk/content/fop/trunk/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/trunk/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/trunk/running.html Thu Feb 16 13:05:56 2017
@@ -511,7 +511,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>Some Mac OSX users have experienced filename truncation problems using Stuffit to unzip and unarchive their distribution media. This is a legacy of older Mac operating systems, which had a 31-character pathname limit. Several Mac OSX users have recommended that Mac OSX users use the shell command <code>tar -xzf</code> instead.</p>
<h2 id="standalone-start">Starting FOP as a Standalone Application<a class="headerlink" href="#standalone-start" title="Permanent link">¶</a></h2>
<h3 id="fop-script">Using the fop script or batch file<a class="headerlink" href="#fop-script" title="Permanent link">¶</a></h3>
-<p>The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is <code>/Library/Java/Home</code>. <strong>Caveat:</strong> We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see <a href="http://developer.apple.com/java/faq">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
+<p>The usual and recommended practice for starting FOP from the command line is to run the batch file fop.bat (Windows) or the shell script fop (Unix/Linux). These scripts require that the environment variable JAVA_HOME be set to a path pointing to the appropriate Java installation on your system. Macintosh OSX includes a Java environment as part of its distribution. We are told by Mac OSX users that the path to use in this case is <code>/Library/Java/Home</code>. <strong>Caveat:</strong> We suspect that, as Apple releases new Java environments and as FOP upgrades the minimum Java requirements, the two will inevitably not match on some systems. Please see <a href="https://java.com/en/download/faq/java_mac.xml">Java on Mac OSX FAQ</a> for information as it becomes available.</p>
<div class="codehilite"><pre><span class="n">USAGE</span>
<span class="n">Fop</span> <span class="p">[</span><span class="n">options</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">fo</span><span class="o">|-</span><span class="n">xml</span><span class="p">]</span> <span class="n">infile</span> <span class="p">[</span><span class="o">-</span><span class="n">xsl</span> <span class="n">file</span><span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">awt</span><span class="o">|-</span><span class="n">pdf</span><span class="o">|-</span><span class="n">mif</span><span class="o">|-</span><span class="n">rtf</span><span class="o">|-</span><span class="n">tiff</span><span class="o">|-</span><span class="n">png</span><span class="o">|-</span><span class="n">pcl</span><span class="o">|-</span><span class="n">ps</span><span class="o">|-</span><span class="n">txt</span><span class="o">|-</span><span class="n">at</span> <span class="p">[</span><span class="n">mime</span><
span class="p">]</span><span class="o">|-</span><span class="n">print</span><span class="p">]</span> <span class="o"><</span><span class="n">outfile</span><span class="o">></span>
<span class="p">[</span><span class="n">OPTIONS</span><span class="p">]</span>
@@ -634,7 +634,7 @@ h2:hover > .headerlink, h3:hover > .head
<p>If you are running out of memory when using FOP, here are some ideas that may help:</p>
<ul>
<li>
-<p>Increase memory available to the JVM. See <a href="http://java.sun.com/j2se/1.4/docs/tooldocs/solaris/java.html">the -Xmx option</a> for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning></p>
+<p>Increase memory available to the JVM. See <a href="http://docs.oracle.com/javase/1.5.0/docs/tooldocs/solaris/java.html">the -Xmx option</a> for more information.<warning>It is usually unwise to increase the memory allocated to the JVM beyond the amount of physical RAM, as this will generally cause significantly slower performance.</warning></p>
</li>
<li>
<p>Avoid forward references. Forward references are references to some later part of a document. Examples include page number citations which refer to pages which follow the citation, tables of contents at the beginning of a document, and page numbering schemes that include the total number of pages in the document (<a href="../faq.html#pagenum">"page N of TOTAL"</a>). Forward references cause all subsequent pages to be held in memory until the reference can be resolved, i.e. until the page with the referenced element is encountered. Forward references may be required by the task, but if you are getting a memory overflow, at least consider the possibility of eliminating them. A table of contents could be replaced by PDF bookmarks instead or moved to the end of the document (reshuffle the paper could after printing).</p>
Modified: websites/staging/xmlgraphics/trunk/content/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/index.html (original)
+++ websites/staging/xmlgraphics/trunk/content/index.html Thu Feb 16 13:05:56 2017
@@ -189,14 +189,14 @@ h2:hover > .headerlink, h3:hover > .head
</ul>
<h1 id="apache-batik-a-java-based-svg-toolkit">Apache™ Batik: a Java-based SVG toolkit<a class="headerlink" href="#apache-batik-a-java-based-svg-toolkit" title="Permanent link">¶</a></h1>
<p>Batik is a Java(tm) technology based toolkit for applications or applets that want to use images in the <a href="http://www.w3.org/TR/SVG/">Scalable Vector Graphics (SVG)</a> format for various purposes, such as viewing, generation or manipulation.</p>
-<p>The project's ambition is to give developers a set of <a href="http://xmlgraphics.apache.org/batik/architecture.html#coreComponents">core modules</a> which can be used together or individually to support specific SVG solutions. Here are some examples of <a href="http://xmlgraphics.apache.org/batik/architecture.html">modules</a>.</p>
+<p>The project's ambition is to give developers a set of <a href="http://xmlgraphics.apache.org/batik/using/architecture.html#coreComponents">core modules</a> which can be used together or individually to support specific SVG solutions. Here are some examples of <a href="http://xmlgraphics.apache.org/batik/architecture.html">modules</a>.</p>
<h2 id="apache-batik-modules">Apache™ Batik Modules<a class="headerlink" href="#apache-batik-modules" title="Permanent link">¶</a></h2>
<ul>
<li>the <a href="/batik/architecture.html#lowLevelComponents">SVG Parser</a></li>
<li>the <a href="/batik/svggen.html">SVG Generator</a></li>
<li>the <a href="/batik/domapi.html">SVG DOM</a></li>
</ul>
-<p>Another ambition for the Batik project is to make it highly <a href="/batik/extendingBatik.html">extensible</a> (for example, Batik allows the developer to handle custom SVG tags). Even though the goal of the project is to provide a set of core modules, one of the deliverables is a full fledged <a href="http://xmlgraphics.apache.org/batik/svgviewer.html">SVG Browser</a> implementation, which validates the various modules and their inter-operability.</p>
+<p>Another ambition for the Batik project is to make it highly <a href="/batik/extendingBatik.html">extensible</a> (for example, Batik allows the developer to handle custom SVG tags). Even though the goal of the project is to provide a set of core modules, one of the deliverables is a full fledged <a href="http://xmlgraphics.apache.org/batik/tools/browser.html">SVG Browser</a> implementation, which validates the various modules and their inter-operability.</p>
<p>Find out more about <a href="/batik/">Apache Batik</a>.</p>
<h1 id="apache-fop-a-java-based-xsl-fo-formatting-objects-processor">Apache FOP: a Java-based XSL-FO (Formatting Objects) processor<a class="headerlink" href="#apache-fop-a-java-based-xsl-fo-formatting-objects-processor" title="Permanent link">¶</a></h1>
<p>FOP (Formatting Objects Processor) is the world's first print formatter driven by <a href="http://www.w3.org/TR/xsl/">XSL formatting objects</a> (XSL-FO) and the world's first output independent formatter. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. The primary output target is PDF but there are other <a href="/fop/output.html">output formats</a> currently supported.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org