Index: pst/ps/fop.xml
===================================================================
--- pst/ps/fop.xml	(revision 67f7d7f8852b0199c08562b11ec13981f73fda35)
+++ pst/ps/fop.xml	(revision ac38e9dcc56be5d8809db3492da7b3380a64b944)
@@ -5,5 +5,5 @@
   %general-entities;
 
-  <!ENTITY fop-download-http "http://archive.apache.org/dist/xmlgraphics/fop/source/fop-&fop-version;-src.tar.gz">
+  <!ENTITY fop-download-http "https://archive.apache.org/dist/xmlgraphics/fop/source/fop-&fop-version;-src.tar.gz">
   <!ENTITY fop-download-ftp  " ">
   <!ENTITY fop-md5sum        "7b63af514b28c06fe710a794cbf4d68e">
@@ -44,13 +44,15 @@
     <title>Introduction to fop</title>
 
-    <para>The <application>FOP</application> (Formatting Objects Processor)
-    package contains a print formatter driven by XSL formatting objects
-    (XSL-FO). It is a <application>Java</application> application that reads
-    a formatting object tree and renders the resulting pages to a specified
-    output. Output formats currently supported include PDF, PCL, PostScript,
-    SVG, XML (area tree representation), print, AWT, MIF and ASCII text. The
-    primary output target is PDF.</para>
-
-    &lfs76_checked;
+    <para>
+      The <application>FOP</application> (Formatting Objects Processor)
+      package contains a print formatter driven by XSL formatting objects
+      (XSL-FO). It is a <application>Java</application> application that reads
+      a formatting object tree and renders the resulting pages to a specified
+      output. Output formats currently supported include PDF, PCL, PostScript,
+      SVG, XML (area tree representation), print, AWT, MIF and ASCII text. The
+      primary output target is PDF.
+    </para>
+
+    &lfs77_checked;
 
     <bridgehead renderas="sect3">Package Information</bridgehead>
@@ -137,18 +139,22 @@
     <title>Installation of fop</title>
 
-    <para>Ensure <envar>$JAVA_HOME</envar> is set correctly before beginning
-    the build. To build the <application>JIMI SDK</application> and/or
-    <application>XMLUnit</application> extension classes, ensure the
-    corresponding <filename class='extension'>.jar</filename> files can be
-    found via the <envar>CLASSPATH</envar> environment variable.</para>
+    <para>
+      Ensure <envar>$JAVA_HOME</envar> is set correctly before beginning
+      the build. To build the <application>JIMI SDK</application> and/or
+      <application>XMLUnit</application> extension classes, ensure the
+      corresponding <filename class='extension'>.jar</filename> files can be
+      found via the <envar>CLASSPATH</envar> environment variable.
+    </para>
 <!--
     <sect3>
       <title>Installing OFFO Hyphenation Patterns</title>
 
-      <para>First, unpack the <application>fop</application> source tarball and
-      the hyphenation zipfile from the same directory, then change directories
-      into the root of the <application>fop</application> source tree. Copy the
-      XML hyphenation patterns into the <application>fop</application> source
-      tree by running the following commands:</para>
+      <para>
+        First, unpack the <application>fop</application> source tarball and
+        the hyphenation zipfile from the same directory, then change directories
+        into the root of the <application>fop</application> source tree. Copy
+        the XML hyphenation patterns into the <application>fop</application>
+        source tree by running the following commands:
+      </para>
 
 <screen><userinput>cp ../offo-hyphenation/hyph/* hyph &amp;&amp;
@@ -160,8 +166,10 @@
       <title>Installing Java Advanced Imaging (JAI) API components</title>
 
-      <para>Next install the JAI API components. As the <systemitem
-      class="username">root</systemitem> user:</para>
-
-<screen><userinput>case `uname -m` in
+      <para>
+        Install the JAI API components. As the <systemitem
+        class="username">root</systemitem> user:
+      </para>
+
+<screen role="root"><userinput>case `uname -m` in
   i?86)
     tar -xf ../jai-&jai-version;-lib-linux-i586.tar.gz
@@ -181,6 +189,18 @@
       <title>Installing fop Components</title>
 
-      <para>Compile <application>fop</application> by running the
-      following commands:</para>
+      <para>
+        The <command>javadoc</command> command coming with OpenJDK 8 has
+        become much stricter than before regarding the conformance of the
+        Javadoc comments in source code to HTML. The FOP documentation does
+        not meet those standard, so the conformance checks have to be
+        disabled. This can be done with the following command:
+      </para>
+
+<screen><userinput>sed -i '\@&lt;/javad@i&lt;arg value="-Xdoclint:none"/&gt;' build.xml</userinput></screen>
+
+      <para>
+        Then, compile <application>fop</application> by running the
+        following commands:
+      </para>
 
 <screen><userinput>ant compile &amp;&amp;
@@ -189,17 +209,22 @@
 mv build/javadocs .</userinput></screen>
 
-      <para>If <application>Forrest</application> is installed,
-      build the full set of documentation:</para>
+      <para>
+        If <application>Forrest</application> is installed,
+        build the full set of documentation:
+      </para>
 
 <screen><userinput>ant docs</userinput></screen>
 
-      <para>To test the application, run <command>ant junit-all</command>. The
-      hyphenation tests will fail.  To see a list of other test targets, use
-      <command>ant -p</command>. You must run the tests from an X-window using
-      a GL-aware <application>Xorg</application> server or some of the
-      <application>JUnit</application> tests will hang.</para>
-
-      <para>Now, as the <systemitem class="username">root</systemitem>
-      user:</para>
+      <para>
+        To test the application, run <command>ant junit-all</command>. The
+        hyphenation tests will fail.  To see a list of other test targets, use
+        <command>ant -p</command>. You must run the tests from an X-window using
+        a GL-aware <application>Xorg</application> server or some of the
+        <application>JUnit</application> tests will hang.
+      </para>
+
+      <para>
+        Now, as the <systemitem class="username">root</systemitem> user:
+      </para>
 
 <screen role="root"><userinput>install -v -d -m755                                     /opt/fop-&fop-version; &amp;&amp;
@@ -216,10 +241,15 @@
     <title>Command Explanations</title>
 
-    <para><command>ant <option>target</option></command>: This reads the file
-    <filename>build.xml</filename> and builds the target files.</para>
-
-    <para><command>ln -v -sf fop-&fop-version; /opt/fop</command>: This is
-    optional and creates a convenience symlink so that <envar>$FOP_HOME</envar>
-    doesn't have to be changed each time there's a package version change.</para>
+    <para>
+      <command>ant <option>target</option></command>: This reads the file
+      <filename>build.xml</filename> and builds the target files.
+    </para>
+
+    <para>
+      <command>ln -v -sf fop-&fop-version; /opt/fop</command>: This is
+      optional and creates a convenience symlink so that
+      <envar>$FOP_HOME</envar> doesn't have to be changed each time there's a
+      package version change.
+    </para>
 
   </sect2>
@@ -231,5 +261,7 @@
       <title>Config Files</title>
 
-      <para><filename>~/.foprc</filename></para>
+      <para>
+        <filename>~/.foprc</filename>
+      </para>
 
       <indexterm zone="fop fop-config">
@@ -242,25 +274,35 @@
       <title>Configuration Information</title>
 
-      <para>Using <application>fop</application> to process some large FO's
-      (including the FO derived from the BLFS XML sources), can lead to memory
-      errors. Unless you add a parameter to the <command>java</command> command
-      used in the <command>fop</command> script you may receive messages
-      similar to the one shown below:</para>
-
-      <para><computeroutput>Exception in thread "main" java.lang.OutOfMemoryError:
-      Java heap space</computeroutput></para>
-
-      <para>To avoid errors like this, you need to pass an extra parameter to
-      the <command>java</command> command used in the <command>fop</command>
-      script. This can be accomplished by creating a
-      <filename>~/.foprc</filename> (which is sourced by the
-      <command>fop</command> script) and adding the parameter to the
-      <envar>FOP_OPTS</envar> environment variable.</para>
-
-      <para>The <command>fop</command> script looks for a
-      <envar>FOP_HOME</envar> environment variable to locate the
-      <application>fop</application> class libraries. You can create this
-      variable using the <filename>~/.foprc</filename> file as well. Create
-      a <filename>~/.foprc</filename> file using the following commands:</para>
+      <para>
+        Using <application>fop</application> to process some large FO's
+        (including the FO derived from the BLFS XML sources), can lead to
+        memory errors. Unless you add a parameter to the
+        <command>java</command> command used in the <command>fop</command>
+        script you may receive messages similar to the one shown below:
+      </para>
+
+      <para>
+        <computeroutput>
+          Exception in thread "main" java.lang.OutOfMemoryError: Java heap
+          space
+        </computeroutput>
+      </para>
+
+      <para>
+        To avoid errors like this, you need to pass an extra parameter to
+        the <command>java</command> command used in the <command>fop</command>
+        script. This can be accomplished by creating a
+        <filename>~/.foprc</filename> (which is sourced by the
+        <command>fop</command> script) and adding the parameter to the
+        <envar>FOP_OPTS</envar> environment variable.
+      </para>
+
+      <para>
+        The <command>fop</command> script looks for a
+        <envar>FOP_HOME</envar> environment variable to locate the
+        <application>fop</application> class libraries. You can create this
+        variable using the <filename>~/.foprc</filename> file as well. Create
+        a <filename>~/.foprc</filename> file using the following commands:
+      </para>
 
 <screen><userinput>cat &gt; ~/.foprc &lt;&lt; "EOF"
@@ -269,28 +311,35 @@
 EOF</userinput></screen>
 
-      <para>Replace <replaceable>&lt;RAM_Installed&gt;</replaceable> with a
-      number representing the amount of RAM installed in your computer (in
-      megabytes). An example would be
-      <userinput>FOP_OPTS="-Xmx768m"</userinput>.
-      <!--  the URL is broken 
-      For more information about
-      memory issues running <application>fop</application>, see
-      <ulink url="http://xml.apache.org/fop/running.html#memory"/>.
-      -->
-      </para>
-
-      <para>To include the <command>fop</command> script in your path,
-      update your personal or system-wide profile with the following:</para>
+      <para>
+        Replace <replaceable>&lt;RAM_Installed&gt;</replaceable> with a
+        number representing the amount of RAM installed in your computer (in
+        megabytes). An example would be
+        <userinput>FOP_OPTS="-Xmx768m"</userinput>.
+        <!--  the URL is broken
+        For more information about
+        memory issues running <application>fop</application>, see
+        <ulink url="http://xml.apache.org/fop/running.html#memory"/>.
+        -->
+      </para>
+
+      <para>
+        To include the <command>fop</command> script in your path,
+        update your personal or system-wide profile with the following:
+      </para>
 
 <screen><literal>PATH=$PATH:/opt/fop</literal></screen>
 
-       <note><para>Running <command>fop</command> can be somewhat verbose.
-       The default logging level can be changed from INFO to any of
-       FINEST, FINER, FINE, CONFIG, INFO, WARNING, SEVERE, ALL, or OFF.
-       To do this, edit
-       <filename>$JAVA_HOME/jre/lib/logging.properties</filename> and change
-       the entries for <option>.leval</option> and
-       <option>java.util.logging.ConsoleHandler.level</option> to
-       the desired value.</para></note>
+      <note>
+        <para>
+          Running <command>fop</command> can be somewhat verbose.
+          The default logging level can be changed from INFO to any of
+          FINEST, FINER, FINE, CONFIG, INFO, WARNING, SEVERE, ALL, or OFF.
+          To do this, edit
+          <filename>$JAVA_HOME/jre/lib/logging.properties</filename> and change
+          the entries for <option>.leval</option> and
+          <option>java.util.logging.ConsoleHandler.level</option> to
+          the desired value.
+        </para>
+      </note>
 
     </sect3>
