xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1006883 [1/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/
Date Thu, 16 Feb 2017 13:05:57 GMT
Author: buildbot
Date: Thu Feb 16 13:05:56 2017
New Revision: 1006883

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/batik/contributors.html
    websites/staging/xmlgraphics/trunk/content/batik/dev/svg12.html
    websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html
    websites/staging/xmlgraphics/trunk/content/batik/uses.html
    websites/staging/xmlgraphics/trunk/content/batik/using/extending.html
    websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html
    websites/staging/xmlgraphics/trunk/content/commons/image-loader.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html
    websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/events.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/output.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/events.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html
    websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html
    websites/staging/xmlgraphics/trunk/content/fop/2.0/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/2.0/events.html
    websites/staging/xmlgraphics/trunk/content/fop/2.0/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/2.0/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/2.0/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/2.0/output.html
    websites/staging/xmlgraphics/trunk/content/fop/2.0/running.html
    websites/staging/xmlgraphics/trunk/content/fop/2.1/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/2.1/events.html
    websites/staging/xmlgraphics/trunk/content/fop/2.1/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/2.1/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/2.1/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/2.1/output.html
    websites/staging/xmlgraphics/trunk/content/fop/2.1/running.html
    websites/staging/xmlgraphics/trunk/content/fop/changes.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html
    websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html
    websites/staging/xmlgraphics/trunk/content/fop/faq.html
    websites/staging/xmlgraphics/trunk/content/fop/resources.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/anttask.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/events.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/fonts.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/graphics.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/hyphenation.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/output.html
    websites/staging/xmlgraphics/trunk/content/fop/trunk/running.html
    websites/staging/xmlgraphics/trunk/content/index.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb 16 13:05:56 2017
@@ -1 +1 @@
-1782960
+1783200

Modified: websites/staging/xmlgraphics/trunk/content/batik/contributors.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/contributors.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/contributors.html Thu Feb 16 13:05:56 2017
@@ -230,7 +230,7 @@ worked on.</p>
 <p>The following people are some of the Batik project founders and helped define and implement the initial Batik architecture:</p>
 <ul>
 <li>
-<p><a href="mailto:bill.haneman@ireland.sun.com">Bill Haneman</a> works for Sun Microsystems’ Desktop Enabling Middleware group in Dublin, Ireland, and implemented much of the Batik’s text support (though not SVG Fonts, thanks Bella, Dean, and David!). He is also technical lead for the <a href="http://developer.gnome.org/projects/gap">GNOME Accessibility Project</a>, an open project to provide an accessibility framework for Linux and Solaris(TM) desktops. A twenty-year veteran of scientific programming and application development, he is a US expatriate who plays traditional Irish music on the uilleann pipes.</p>
+<p><a href="mailto:bill.haneman@ireland.sun.com">Bill Haneman</a> works for Sun Microsystems’ Desktop Enabling Middleware group in Dublin, Ireland, and implemented much of the Batik’s text support (though not SVG Fonts, thanks Bella, Dean, and David!). He is also technical lead for the <a href="https://wiki.gnome.org/Accessibility">GNOME Accessibility Project</a>, an open project to provide an accessibility framework for Linux and Solaris(TM) desktops. A twenty-year veteran of scientific programming and application development, he is a US expatriate who plays traditional Irish music on the uilleann pipes.</p>
 </li>
 <li>
 <p><a href="mailto:vincent.hardy@eng.sun.com">Vincent Hardy</a> is one of the founders of the SVG Batik project at Apache. He is a Senior Staff Engineer at Sun Microsystems Inc., where he is part of the XML technology center. Vincent represented Sun in the W3C’s SVG Working Group and is currently a W3C fellow in the W3C office in Sophia Antipolis, France. Vincent is the author of papers and a book on the Java 2D API.</p>

Modified: websites/staging/xmlgraphics/trunk/content/batik/dev/svg12.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/dev/svg12.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/dev/svg12.html Thu Feb 16 13:05:56 2017
@@ -223,7 +223,7 @@ h2:hover > .headerlink, h3:hover > .head
 </ol>
 <h3 id="dom3java">Using DOM Level 3 functionality from Java<a class="headerlink" href="#dom3java" title="Permanent link">&para;</a></h3>
 <p>JREs before 1.5 include the DOM Level 2 interfaces and this can cause problems when trying to use the DOM Level 3 versions of these same interface files (<code>org.w3c.dom.*</code>). Though the concrete Batik DOM classes implement the DOM Level 3 functionality, you won’t be able to access those methods through the <code>org.w3c.dom</code> interfaces on these earlier JREs.</p>
-<p>There are two ways to overcome this problem. The first is to install the DOM Level 3 interfaces using the <a href="http://java.sun.com/j2se/1.4.2/docs/guide/standards/">Endorsed Standards Override Mechanism</a>. Copy the file <code>lib/xml-apis-ext.jar</code> into the endorsed standards override directory and the DOM Level 3 interfaces will be visible. You can then write code against them (for example, call <code>Document.renameNode</code> directly). However, this will mean that other people cannot run or compile your code unless they have JRE 1.5 or later, or they have also installed the <code>xml-apis-ext.jar</code> in the same way.</p>
+<p>There are two ways to overcome this problem. The first is to install the DOM Level 3 interfaces using the <a href="https://docs.oracle.com/javase/6/docs/technotes/guides/standards/">Endorsed Standards Override Mechanism</a>. Copy the file <code>lib/xml-apis-ext.jar</code> into the endorsed standards override directory and the DOM Level 3 interfaces will be visible. You can then write code against them (for example, call <code>Document.renameNode</code> directly). However, this will mean that other people cannot run or compile your code unless they have JRE 1.5 or later, or they have also installed the <code>xml-apis-ext.jar</code> in the same way.</p>
 <p>The second method, which requires less messing about with the JRE, is to cast your DOM objects to the concrete Batik DOM objects and call your DOM Level 3 methods directly on them. The Batik DOM classes are in the <code>org.apache.batik.dom</code> package. The classes named <code>Abstract*</code> implement the DOM interfaces, and also contain the DOM Level 3 methods. The advantage of this method is that for your code to compile and run in others’ environments, they need not install any jars with the endorsed standards overrides.</p>
 <p>Here is an example of using the second method to get access to DOM Level 3 specific methods:</p>
 <div class="codehilite"><pre><span class="kn">import</span> <span class="nn">org.apache.batik.dom.AbstractDocument</span><span class="o">;</span>

Modified: websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/tools/rasterizer.html Thu Feb 16 13:05:56 2017
@@ -443,7 +443,7 @@ For windows, type the following at the c
 </tr>
 </tbody>
 </table>
-<p>You can use <code>fileset</code> elements to select input files and directories. See the <a href="http://ant.apache.org/">Ant</a> documentation to learn how to use <a href="http://ant.apache.org/manual/CoreTypes/fileset.html">filesets</a>.</p>
+<p>You can use <code>fileset</code> elements to select input files and directories. See the <a href="http://ant.apache.org/">Ant</a> documentation to learn how to use <a href="https://ant.apache.org/manual/Types/fileset.html">filesets</a>.</p>
 <h3 id="taskExamples">Examples of using the rasterizer task<a class="headerlink" href="#taskExamples" title="Permanent link">&para;</a></h3>
 <p>The following example is the complete Ant project that converts an SVG image (called <code>input.svg</code>) to a PNG image (called <code>output.png</code>):</p>
 <div class="codehilite"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot;?&gt;</span>

Modified: websites/staging/xmlgraphics/trunk/content/batik/uses.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/uses.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/uses.html Thu Feb 16 13:05:56 2017
@@ -224,7 +224,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p><a href="http://www.exurbi.com/">eDoc Studio</a>, a page layout package, uses the Batik SVG generator to export pages to SVG.</p>
 </li>
 <li>
-<p><a href="http://www.elixirtech.com/ElixirReport">ElixirTech’s ElixirReport</a> uses Batik for charting and for its SVG component.</p>
+<p><a href="http://www.elixirtech.com/products/Reporting.html">ElixirTech’s ElixirReport</a> uses Batik for charting and for its SVG component.</p>
 </li>
 <li>
 <p><a href="http://glipssvgeditor.sourceforge.net/">GLIPS Graffiti</a> is an Open Source Extensible Full Feature Native SVG Editor.</p>
@@ -251,7 +251,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p><a href="http://www.optimalj.com">OptimalJ</a>, a UML Class Diagram Editor for NetBeans, uses Batik to export SVG.</p>
 </li>
 <li>
-<p><a href="http://otn.oracle.com/products/jdev/content.html">Oracle Corp.’s JDeveloper10i</a> uses Batik to export class diagrams in SVG. It uses the SVG export module.</p>
+<p><a href="http://www.oracle.com/technetwork/developer-tools/jdev/overview/index-094652.html">Oracle Corp.’s JDeveloper10i</a> uses Batik to export class diagrams in SVG. It uses the SVG export module.</p>
 </li>
 <li>
 <p><a href="http://www.kiyut.com/">Sketsa</a> is a vector drawing application based on Batik. With Sketsa, you can create vector graphics that can be scaled and printed at any resolution, without losing detail or clarity.</p>

Modified: websites/staging/xmlgraphics/trunk/content/batik/using/extending.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/extending.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/extending.html Thu Feb 16 13:05:56 2017
@@ -204,7 +204,7 @@ $(document).ready(function () {
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1 id="extending-batik">Extending Batik<a class="headerlink" href="#extending-batik" title="Permanent link">&para;</a></h1>
 <p>This page provides an overview of the built in extension mechanisms of Batik. As an open source project, people can of course make any extension they feel is interesting, however Batik has been designed with several forms of extension in mind.</p>
-<p>In general, extensions are added through the Service Provider Interface mechanism as described in the <a href="http://java.sun.com/j2se/1.4/docs/guide/jar/jar.html#Service Provider">jar file documentation</a>. This allows for the extension of Batik simply by adding a new jar file(s) to the class path, and thus no modification of the Batik source is required!
+<p>In general, extensions are added through the Service Provider Interface mechanism as described in the <a href="http://docs.oracle.com/javase/1.5.0/docs/guide/jar/jar.html#Service%20Provider">jar file documentation</a>. This allows for the extension of Batik simply by adding a new jar file(s) to the class path, and thus no modification of the Batik source is required!
 If you feel that the Batik team has overlooked an important area for extension please let your feelings be known on the mailing lists.</p>
 <h1 id="customXMLTags">Custom XML elements<a class="headerlink" href="#customXMLTags" title="Permanent link">&para;</a></h1>
 <p>First one must ask what it means to support custom XML elements? There are three basic options Batik considers:</p>

Modified: websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html (original)
+++ websites/staging/xmlgraphics/trunk/content/batik/using/svg-generator.html Thu Feb 16 13:05:56 2017
@@ -462,7 +462,7 @@ h2:hover > .headerlink, h3:hover > .head
 
 
 <h2 id="Extending-Paint-object-to-SVG-element-translation">Extending Paint object to SVG element translation<a class="headerlink" href="#Extending-Paint-object-to-SVG-element-translation" title="Permanent link">&para;</a></h2>
-<p>The <code>SVGGraphics2D</code> is able to generate SVG elements for generic Java 2D objects, but you sometimes have your own classes such as implementations of the Java 2D <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/awt/Paint.html">Paint</a> interface. In this case, you will need to write an <a href="../javadoc/org/apache/batik/svggen/ExtensionHandler.html">ExtensionHandler</a> that you will set on your <code>SVGGeneratorContext</code>.</p>
+<p>The <code>SVGGraphics2D</code> is able to generate SVG elements for generic Java 2D objects, but you sometimes have your own classes such as implementations of the Java 2D <a href="https://docs.oracle.com/javase/7/docs/api/java/awt/Paint.html">Paint</a> interface. In this case, you will need to write an <a href="../javadoc/org/apache/batik/svggen/ExtensionHandler.html">ExtensionHandler</a> that you will set on your <code>SVGGeneratorContext</code>.</p>
 <p>In the following example we define the first draft of an <code>ExtensionHandler</code> allowing to translate a Batik implementation of the <code>Paint</code> interface named <a href="../javadoc/org/apache/batik/ext/awt/LinearGradientPaint.html">LinearGradientPaint</a>.</p>
 <div class="codehilite"><pre><span class="kd">class</span> <span class="nc">MyExtensionHandler</span> <span class="kd">extends</span> <span class="n">DefaultExtensionHandler</span> <span class="o">{</span>
 

Modified: websites/staging/xmlgraphics/trunk/content/commons/image-loader.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/commons/image-loader.html (original)
+++ websites/staging/xmlgraphics/trunk/content/commons/image-loader.html Thu Feb 16 13:05:56 2017
@@ -297,7 +297,7 @@ h2:hover > .headerlink, h3:hover > .head
 </blockquote>
 <h1 id="tipsntricks">Tips &amp; Tricks<a class="headerlink" href="#tipsntricks" title="Permanent link">&para;</a></h1>
 <p>If you are loading bitmap images and you get an error like <code>"Cannot load image (no suitable loader/converter combination available) for
-        myimage.tif (image/tiff)</code>, you maybe be missing the necessary ImageIO codec to decode the image. A number of well-written codecs can be found in <a href="https://jai-imageio.dev.java.net/">JAI Image I/O Tools Project</a>. Just download the distribution and add the JAR to the classpath. ImageIO will automatically pick up the new codecs and they will subsequently be available to the image framework.</p>
+        myimage.tif (image/tiff)</code>, you maybe be missing the necessary ImageIO codec to decode the image. A number of well-written codecs can be found in <a href="https://github.com/jai-imageio/jai-imageio-core/releases">JAI Image I/O Tools Project</a>. Just download the distribution and add the JAR to the classpath. ImageIO will automatically pick up the new codecs and they will subsequently be available to the image framework.</p>
 <h2 id="spi">Service Provider Interface (SPI, Plug-ins)<a class="headerlink" href="#spi" title="Permanent link">&para;</a></h2>
 <p>The whole image framework is designed to be highly extensible. There are various extension points where new functionality can be added. The three main SPI interfaces are:</p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/anttask.html Thu Feb 16 13:05:56 2017
@@ -564,7 +564,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/0.95/graphics.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/graphics.html Thu Feb 16 13:05:56 2017
@@ -562,8 +562,8 @@ 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.
- <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&nbsp;I/O API but does not include all the image manipulation functionality.</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.
+ <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&nbsp;I/O API but does not include all the image manipulation functionality.</p>
 </li>
 </ul>
 <h3 id="format-map">Map of supported image formats by output format<a class="headerlink" href="#format-map" title="Permanent link">&para;</a></h3>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/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">&para;</a></h2>
 <h3 id="intro">Introduction<a class="headerlink" href="#intro" title="Permanent link">&para;</a></h3>
 <p>Apache&trade; 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>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.
 If you have made improvements to an existing 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>.</p>
 <h3 id="license-issues">License Issues<a class="headerlink" href="#license-issues" title="Permanent link">&para;</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.html">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>
@@ -515,7 +515,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">&para;</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/0.95/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/output.html Thu Feb 16 13:05:56 2017
@@ -610,7 +610,7 @@ Here is some sample code that uses iText
 <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">&para;</a></h3>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/pdfencryption.html Thu Feb 16 13:05:56 2017
@@ -591,7 +591,7 @@ h2:hover > .headerlink, h3:hover > .head
 </li>
 </ol>
 <h2 id="Environment">Environment<a class="headerlink" href="#Environment" title="Permanent link">&para;</a></h2>
-<p>In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html">JCE</a> is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.</p>
+<p>In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only <a href="https://docs.oracle.com/javase/1.5.0/docs/guide/security/jce/JCERefGuide.html">JCE</a> is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.</p>
 <p>Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does <strong>not</strong> provide RC4. If you get a message saying
 "Cannot find any provider supporting RC4"
 then you don't have the needed infrastructure.</p>
@@ -605,7 +605,7 @@ then you don't have the needed infrastru
 <li>
 <p>Open the <code>java.security</code> file and add</p>
 <p><code>security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider</code>,</p>
-<p>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a>.</p>
+<p>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="https://docs.oracle.com/javase/1.5.0/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a>.</p>
 </li>
 </ol>
 <p>If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/releaseNotes_0.95.html Thu Feb 16 13:05:56 2017
@@ -484,7 +484,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>-
 If an fo:table element contains explicit fo:table-column children, then those elements set the total number of columns in the table. This means that a validation error will now occur if a row contains more cells than available columns. This change allows to improve performance, since the rendering of the table may start as soon as the table-column elements have been parsed.</p>
 <p>If more flexibility is needed, then the fo:table-column elements may be just omitted. The final number of columns will then be set by the row that has the most cells.</p>
-<p>The image libraries Jimi and JAI are no longer needed (and used) for image loading. Instead we rely completely on the Image I/O API that has been introduced with Java 1.4. If you still need support for bitmap image formats that do not work out-of-the-box, we recommend adding <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> (an Image I/O compatible image codec package) to the classpath. JAI is still required for building the FOP distribution but it is optional for normal builds and at run-time.</p>
+<p>The image libraries Jimi and JAI are no longer needed (and used) for image loading. Instead we rely completely on the Image I/O API that has been introduced with Java 1.4. If you still need support for bitmap image formats that do not work out-of-the-box, we recommend adding <a href="https://github.com/jai-imageio/jai-imageio-core">JAI Image I/O Tools</a> (an Image I/O compatible image codec package) to the classpath. JAI is still required for building the FOP distribution but it is optional for normal builds and at run-time.</p>
 <p>This final 0.95 release also includes all of the <a href="changes_0.95beta.html">changes made for Apache FOP 0.95beta</a>.</section></notes></p>
 <h1 id="version_0.95">Major Changes in Version 0.95<a class="headerlink" href="#version_0.95" title="Permanent link">&para;</a></h1>
 <p>This is not a complete list of changes, just some of the more important ones. A full list of changes in this release <a href="changes_0.95.html">is available</a>.</p>

Modified: websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/running.html Thu Feb 16 13:05:56 2017
@@ -514,7 +514,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">&para;</a></h2>
 <h3 id="fop-script">Using the fop script or batch file<a class="headerlink" href="#fop-script" title="Permanent link">&para;</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">&lt;</span><span class="n">outfile</span><span class="o">&gt;</span>
  <span class="p">[</span><span class="n">OPTIONS</span><span class="p">]</span>
@@ -617,7 +617,7 @@ The -foout option works the same way as
 <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/1.0/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/anttask.html 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/1.0/events.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.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">&para;</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">&para;</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/1.0/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/fonts.html Thu Feb 16 13:05:56 2017
@@ -808,7 +808,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>
 <p>Various notes related to embedded fonts:</p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/graphics.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.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&nbsp;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&nbsp;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">&para;</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/1.0/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/hyphenation.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.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">&para;</a></h2>
 <h3 id="intro">Introduction<a class="headerlink" href="#intro" title="Permanent link">&para;</a></h3>
 <p>Apache&trade; 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&trade; 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">&para;</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.html">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">&para;</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/1.0/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/output.html Thu Feb 16 13:05:56 2017
@@ -620,7 +620,7 @@ Here is some sample code that uses iText
 <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">&para;</a></h3>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html Thu Feb 16 13:05:56 2017
@@ -581,7 +581,7 @@ h2:hover > .headerlink, h3:hover > .head
 </li>
 </ol>
 <h2 id="Environment">Environment<a class="headerlink" href="#Environment" title="Permanent link">&para;</a></h2>
-<p>In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html">JCE</a> is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.</p>
+<p>In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only <a href="https://docs.oracle.com/javase/1.5.0/docs/guide/security/jce/JCERefGuide.html">JCE</a> is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.</p>
 <p>Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does <strong>not</strong> provide RC4. If you get a message saying
 "Cannot find any provider supporting RC4"
 then you don't have the needed infrastructure.</p>
@@ -598,7 +598,7 @@ then you don't have the needed infrastru
 <li>
 <p>Open the <code>java.security</code> file and add</p>
 <p><code>security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider</code>,</p>
-<p>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a>.</p>
+<p>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="https://docs.oracle.com/javase/1.5.0/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a>.</p>
 </li>
 </ol>
 <p>If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html Thu Feb 16 13:05:56 2017
@@ -514,7 +514,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">&para;</a></h2>
 <h3 id="fop-script">Using the fop script or batch file<a class="headerlink" href="#fop-script" title="Permanent link">&para;</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">&lt;</span><span class="n">outfile</span><span class="o">&gt;</span>
  <span class="p">[</span><span class="n">OPTIONS</span><span class="p">]</span>
@@ -628,7 +628,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/1.1/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.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/1.1/events.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/events.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.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">&para;</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">&para;</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/1.1/fonts.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/fonts.html Thu Feb 16 13:05:56 2017
@@ -802,7 +802,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>
 <p>Various notes related to embedded fonts:</p>
 <ul>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/graphics.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/graphics.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.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&nbsp;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&nbsp;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">&para;</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/1.1/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/hyphenation.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.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">&para;</a></h2>
 <h3 id="intro">Introduction<a class="headerlink" href="#intro" title="Permanent link">&para;</a></h3>
 <p>Apache&trade; 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&trade; 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">&para;</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.html">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">&para;</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/1.1/output.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/output.html Thu Feb 16 13:05:56 2017
@@ -645,7 +645,7 @@ Here is some sample code that uses iText
 <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">&para;</a></h3>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.1/pdfencryption.html Thu Feb 16 13:05:56 2017
@@ -677,7 +677,7 @@ h2:hover > .headerlink, h3:hover > .head
 </li>
 </ol>
 <h2 id="Environment">Environment<a class="headerlink" href="#Environment" title="Permanent link">&para;</a></h2>
-<p>In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html">JCE</a> is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.</p>
+<p>In order to use PDF encryption, FOP has to be compiled with cryptography support. Currently, only <a href="https://docs.oracle.com/javase/1.5.0/docs/guide/security/jce/JCERefGuide.html">JCE</a> is supported. JCE is part of JDK 1.4. For earlier JDKs, it can be installed separately. The build process automatically detects JCE presence and installs PDF encryption support if possible, otherwise a stub is compiled in.</p>
 <p>Cryptography support must also be present at run time. In particular, a provider for the RC4 cipher is needed. Unfortunately, the sample JCE provider in Sun's JDK 1.4 does <strong>not</strong> provide RC4. If you get a message saying
 "Cannot find any provider supporting RC4"
 then you don't have the needed infrastructure.</p>
@@ -694,7 +694,7 @@ then you don't have the needed infrastru
 <li>
 <p>Open the <code>java.security</code> file and add</p>
 <p><code>security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider</code>,</p>
-<p>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="http://java.sun.com/j2se/1.4/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a>.</p>
+<p>preferably at the end of the block defining the other crypto providers. For JDK 1.4 this is detailed on <a href="https://docs.oracle.com/javase/1.5.0/docs/guide/security/jce/JCERefGuide.html#InstallProvider">Sun's web site</a>.</p>
 </li>
 </ol>
 <p>If you have any experience with Mozilla JSS or any other cryptography provider, please post it to the fop-user list.</p></div>

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/1.1/running.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/1.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">&para;</a></h2>
 <h3 id="fop-script">Using the fop script or batch file<a class="headerlink" href="#fop-script" title="Permanent link">&para;</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">&lt;</span><span class="n">outfile</span><span class="o">&gt;</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.0/anttask.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/2.0/anttask.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/2.0/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>



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


Mime
View raw message