xmlgraphics-fop-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vhenneb...@apache.org
Subject svn commit: r562903 - in /xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs: ./ 0.93/ 0.94/ dev/ dev/design/ trunk/
Date Sun, 05 Aug 2007 16:24:01 GMT
Author: vhennebert
Date: Sun Aug  5 09:23:59 2007
New Revision: 562903

URL: http://svn.apache.org/viewvc?view=rev&rev=562903
Log:
Style only: remove tab characters

Modified:
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/configuration.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/running.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/upgrading.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/configuration.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/fonts.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/running.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/upgrading.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/design/configuration.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/faq.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/release.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/examples.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/faq.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/news.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/configuration.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/fonts.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/running.xml
    xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/upgrading.xml

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/configuration.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/configuration.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/configuration.xml Sun Aug  5 09:23:59 2007
@@ -290,10 +290,10 @@
     </section>
   </section>
 
-	<section>
-	  <title>When it does not work</title>
+  <section>
+    <title>When it does not work</title>
 
-	  <p>FOP searches the configuration file for the information it
+    <p>FOP searches the configuration file for the information it
 expects, at the position it expects. When that information is not
 present, FOP will not complain, it will just continue. When there is
 other information in the file, FOP will not complain, it will just
@@ -301,14 +301,14 @@
 the file but in a different XML element, or in a different XML path,
 than FOP expects, it will be silently ignored.</p>
 
-	  <p>Check the following possibilities:</p>
+    <p>Check the following possibilities:</p>
 
-	  <ul>
-		<li>The format of the configuration file has changed
+    <ul>
+    <li>The format of the configuration file has changed
 considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did
 you convert your file to the new format?</li>
 
-		<li>The FOP distribution contains a schema for configuration
+    <li>The FOP distribution contains a schema for configuration
 files, at src/foschema/fop-configuration.xsd. Did you validate your
 configuration file against it? Add the following schema location to
 the <code>schema</code> element:
@@ -323,13 +323,13 @@
 parser. Note that the schema cannot detect all errors, and that it is
 stricter about the order of some elements than FOP itself is.</li>
 
-		<li>Run FOP in debug mode (command line option
+    <li>Run FOP in debug mode (command line option
 <code>-d</code>). This makes FOP report which configuration
 information it finds. Check if FOP finds what you expect.</li>
 
-	  </ul>
+    </ul>
 
-	</section>
+  </section>
   </body>
 </document>
 

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/running.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/running.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/running.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/running.xml Sun Aug  5 09:23:59 2007
@@ -212,35 +212,35 @@
       directory in a single directory. If you use hyphenation, you
       must also put <code>fop-hyph.jar</code> in that directory.</p>
 
-		<p>In both cases the arguments consist of the options and
+    <p>In both cases the arguments consist of the options and
         infile and outfile specifications as shown above for the
         standard scripts.</p>
       </section>
       <section id="dynamical-classpath">
-		<title>FOP's dynamical classpath construction</title>
+        <title>FOP's dynamical classpath construction</title>
 
-		<p>If FOP is started without a proper classpath, it tries to
-		add its dependencies dynamically. FOP uses the current working
-		directory as the base directory for its search. If the base
-		directory is called <code>build</code>, then its parent
-		directory becomes the base directory.</p>
+        <p>If FOP is started without a proper classpath, it tries to
+        add its dependencies dynamically. FOP uses the current working
+        directory as the base directory for its search. If the base
+        directory is called <code>build</code>, then its parent
+        directory becomes the base directory.</p>
 
         <p>FOP expects to find <code>fop.jar</code> in the
-		<code>build</code> subdirectory of the base directory, and
-		adds it to the classpath. Subsequently FOP adds all
-		<code>jar</code> files in the lib directory to the
-		classpath. The lib directory is either the <code>lib</code>
-		subdirectory of the base directory, or, if that does not
-		exist, the base directory itself.</p>
+        <code>build</code> subdirectory of the base directory, and
+        adds it to the classpath. Subsequently FOP adds all
+        <code>jar</code> files in the lib directory to the
+        classpath. The lib directory is either the <code>lib</code>
+        subdirectory of the base directory, or, if that does not
+        exist, the base directory itself.</p>
 
         <p>If the system property <code>fop.optional.lib</code>
-		contains the name of a directory, then all <code>jar</code>
-		files in that directory are also added to the classpath. See
-		the methods <code>getJARList</code> and
-		<code>checkDependencies</code> in
-		<code>org.apache.fop.cli.Main</code>.</p>
+        contains the name of a directory, then all <code>jar</code>
+        files in that directory are also added to the classpath. See
+        the methods <code>getJARList</code> and
+        <code>checkDependencies</code> in
+        <code>org.apache.fop.cli.Main</code>.</p>
 
-	  </section>
+      </section>
     </section>
     <section id="check-input">
       <title>Using Xalan to Check XSL-FO Input</title>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/upgrading.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/upgrading.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/upgrading.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.93/upgrading.xml Sun Aug  5 09:23:59 2007
@@ -51,7 +51,7 @@
           an example configuration file. A XML Schema file can be found under
           src/foschema/fop-configuration.xsd.
         </li>
-		<li>
+        <li>
           If you are using font metrics files for version 0.20.5 or
           0.92 or earlier, you have to regenerate them in the new
           format. The new format is characterized by a version

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/configuration.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/configuration.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/configuration.xml Sun Aug  5 09:23:59 2007
@@ -78,7 +78,7 @@
         <td>URL or directory</td>
         <td>Specifies the base URL based on which relative font URLs will be resolved.
         </td>
-	<td>base URL/directory (above)</td>
+        <td>base URL/directory (above)</td>
       </tr>
       <tr>
         <td>hyphenation-base</td>
@@ -112,10 +112,10 @@
         <td>strict-configuration</td>
         <td>Boolean (true, false)</td>
         <td>
-	  Setting this option to 'true' will cause FOP to strictly verify the contents of the
-	  FOP configuration file to ensure that defined resources (such as fonts and base
-	  URLs/directories) are valid and available to FOP.  Any errors found will cause FOP to
-	  immediately raise an exception.</td>
+          Setting this option to 'true' will cause FOP to strictly verify the contents of the
+          FOP configuration file to ensure that defined resources (such as fonts and base
+          URLs/directories) are valid and available to FOP.  Any errors found will cause FOP to
+          immediately raise an exception.</td>
         <td>false</td>
       </tr>
       <tr>
@@ -125,7 +125,7 @@
           Setting this option to 'false' causes FOP to be more forgiving about XSL-FO validity, 
           for example, you're allowed to specify a border on a region-body which is supported 
           by some FO implementations but is non-standard. Note that such a border would 
-	  currently have no effect in Apache FOP.</td>
+          currently have no effect in Apache FOP.</td>
         <td>true</td>
       </tr>
       <tr>
@@ -173,7 +173,7 @@
         <td>renderers</td>
         <td>(see text below)</td>
         <td>Contains the configuration for each renderer. See below.</td>
-	<td>N/A</td>
+        <td>N/A</td>
       </tr>
     </table>
     <p>
@@ -332,18 +332,18 @@
       </p>
     </section>
   </section>
-	<section id="fonts">
-		<title>Apache FOP Font Config</title>
-		<p>
-			Apache FOP has special Font configuration considerations, which are explained
-			in detail on the <a href="fonts.html">Fonts</a> page.
-		</p>
-	</section>
+  <section id="fonts">
+    <title>Apache FOP Font Config</title>
+    <p>
+      Apache FOP has special Font configuration considerations, which are explained
+      in detail on the <a href="fonts.html">Fonts</a> page.
+    </p>
+  </section>
 
-	<section>
-	  <title>When it does not work</title>
+  <section>
+    <title>When it does not work</title>
 
-	  <p>FOP searches the configuration file for the information it
+    <p>FOP searches the configuration file for the information it
 expects, at the position it expects. When that information is not
 present, FOP will not complain, it will just continue. When there is
 other information in the file, FOP will not complain, it will just
@@ -351,14 +351,14 @@
 the file but in a different XML element, or in a different XML path,
 than FOP expects, it will be silently ignored.</p>
 
-	  <p>Check the following possibilities:</p>
+      <p>Check the following possibilities:</p>
 
-	  <ul>
-		<li>The format of the configuration file has changed
+      <ul>
+        <li>The format of the configuration file has changed
 considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did
 you convert your file to the new format?</li>
 
-		<li>The FOP distribution contains a schema for configuration
+        <li>The FOP distribution contains a schema for configuration
 files, at src/foschema/fop-configuration.xsd. Did you validate your
 configuration file against it? Add the following schema location to
 the <code>schema</code> element:
@@ -373,13 +373,13 @@
 parser. Note that the schema cannot detect all errors, and that it is
 stricter about the order of some elements than FOP itself is.</li>
 
-		<li>Run FOP in debug mode (command line option
+        <li>Run FOP in debug mode (command line option
 <code>-d</code>). This makes FOP report which configuration
 information it finds. Check if FOP finds what you expect.</li>
 
-	  </ul>
+      </ul>
 
-	</section>
+    </section>
   </body>
 </document>
 

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/fonts.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/fonts.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/fonts.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/fonts.xml Sun Aug  5 09:23:59 2007
@@ -255,16 +255,16 @@
   <auto-detect/>  
 </fonts>]]></source>
         <note>
-        	Review the documentation for <a href="configuration.html">FOP Configuration</a> for
-        	instructions on making the FOP configuration available to FOP when it runs. Otherwise,
-        	FOP has no way of finding your custom font information.
+          Review the documentation for <a href="configuration.html">FOP Configuration</a> for
+          instructions on making the FOP configuration available to FOP when it runs. Otherwise,
+          FOP has no way of finding your custom font information.
         </note>
         The Unix autodetect feature looks in the following locations for fonts it can use:
         <ul>
-					<li><code>java user.home + "/.fonts"</code></li>
-					<li><code>"/usr/local/fonts"</code></li>
-					<li><code>"/usr/share/fonts"</code></li>
-					<li><code>"/usr/X11R6/lib/X11/fonts"</code></li>
+          <li><code>java user.home + "/.fonts"</code></li>
+          <li><code>"/usr/local/fonts"</code></li>
+          <li><code>"/usr/share/fonts"</code></li>
+          <li><code>"/usr/X11R6/lib/X11/fonts"</code></li>
         </ul>
         <ul>
           <li>
@@ -274,7 +274,7 @@
           </li>
           <li>Either an "embed-url" or a "metrics-url" must be specified for font tag configurations.</li>
           <li>The font "kerning" attribute is optional.</li>
-	      <li>If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
+          <li>If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
           <li>When setting the "embed-url" attribute for Type 1 fonts, be sure to specify the PFB (actual font data), not PFM (font metrics) file that you used to generate the XML font metrics file.</li>
           <li>The fonts "directory" tag can be used to register fonts contained within a single or list of directory paths.  The "recursive" attribute can be specified to recursively add fonts from all sub directories.</li>
           <li>The fonts "auto-detect" tag can be used to automatically register fonts that are found to be installed on the native operating system.</li>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/running.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/running.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/running.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/running.xml Sun Aug  5 09:23:59 2007
@@ -214,37 +214,37 @@
       directory in a single directory. If you use hyphenation, you
       must also put <code>fop-hyph.jar</code> in that directory.</p>
 
-		<p>In both cases the arguments consist of the options and
+      <p>In both cases the arguments consist of the options and
         infile and outfile specifications as shown above for the
         standard scripts.</p>
       </section>
       <section id="dynamical-classpath">
-		<title>FOP's dynamical classpath construction</title>
+        <title>FOP's dynamical classpath construction</title>
 
-		<p>If FOP is started without a proper classpath, it tries to
-		add its dependencies dynamically. If the system property
-		<code>fop.home</code> contains the name of a directory, then
-		FOP uses that directory as the base directory for its
-		search. Otherwise the current working directory is the base
-		directory. If the base directory is called <code>build</code>,
-		then its parent directory becomes the base directory.</p>
+        <p>If FOP is started without a proper classpath, it tries to
+        add its dependencies dynamically. If the system property
+        <code>fop.home</code> contains the name of a directory, then
+        FOP uses that directory as the base directory for its
+        search. Otherwise the current working directory is the base
+        directory. If the base directory is called <code>build</code>,
+        then its parent directory becomes the base directory.</p>
 
         <p>FOP expects to find <code>fop.jar</code> in the
-		<code>build</code> subdirectory of the base directory, and
-		adds it to the classpath. Subsequently FOP adds all
-		<code>jar</code> files in the lib directory to the
-		classpath. The lib directory is either the <code>lib</code>
-		subdirectory of the base directory, or, if that does not
-		exist, the base directory itself.</p>
+        <code>build</code> subdirectory of the base directory, and
+        adds it to the classpath. Subsequently FOP adds all
+        <code>jar</code> files in the lib directory to the
+        classpath. The lib directory is either the <code>lib</code>
+        subdirectory of the base directory, or, if that does not
+        exist, the base directory itself.</p>
 
         <p>If the system property <code>fop.optional.lib</code>
-		contains the name of a directory, then all <code>jar</code>
-		files in that directory are also added to the classpath. See
-		the methods <code>getJARList</code> and
-		<code>checkDependencies</code> in
-		<code>org.apache.fop.cli.Main</code>.</p>
+        contains the name of a directory, then all <code>jar</code>
+        files in that directory are also added to the classpath. See
+        the methods <code>getJARList</code> and
+        <code>checkDependencies</code> in
+        <code>org.apache.fop.cli.Main</code>.</p>
 
-	  </section>
+      </section>
     </section>
     <section id="check-input">
       <title>Using Xalan to Check XSL-FO Input</title>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/upgrading.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/upgrading.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/upgrading.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/0.94/upgrading.xml Sun Aug  5 09:23:59 2007
@@ -52,7 +52,7 @@
           an example configuration file. A XML Schema file can be found under
           src/foschema/fop-configuration.xsd.
         </li>
-		<li>
+        <li>
           If you are using font metrics files for version 0.20.5 or
           0.92 or earlier, you have to regenerate them in the new
           format. The new format is characterized by a version

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/design/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/design/configuration.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/design/configuration.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/design/configuration.xml Sun Aug  5 09:23:59 2007
@@ -47,30 +47,30 @@
 instructions, including comments which specify the value range.  Also,
 since the configuration file is XML, be sure to keep it
 well-formed.</p>
-	</section>
+    </section>
 
-	<section id="general-available">
-	  <title>Making Configuration Available to FOP</title>
-	  <p>After creating your configuration file, you must tell FOP how
+    <section id="general-available">
+      <title>Making Configuration Available to FOP</title>
+      <p>After creating your configuration file, you must tell FOP how
 to find it.</p> 
 
-	  <section id="command-line">
-		<title>From the Command Line</title>
-		<p>When you run FOP from the command-line, use the
+      <section id="command-line">
+        <title>From the Command Line</title>
+        <p>When you run FOP from the command-line, use the
 &ldquo;<code>-c</code>&rdquo; command-line option with the path to the
 configuration file as the option value.</p>
-	  </section>
+      </section>
 
-	  <section id="embedded-file">
-		<title>A Configuration File in an Embedded Application</title>
-		<p>FOP uses the Avalon framework configuration package
+      <section id="embedded-file">
+        <title>A Configuration File in an Embedded Application</title>
+        <p>FOP uses the Avalon framework configuration package
 <code>org.apache.avalon.framework.configuration</code>. For detailed
 information, see the documentation of the package.</p>
-		<p>If you want to use a user configuration file with your
+        <p>If you want to use a user configuration file with your
 embedded program, you need to build an Avalon configuration 
 object from it, and register that with the user agent:</p>
 
-		<source>FOUserAgent foUserAgent;
+        <source>FOUserAgent foUserAgent;
 XMLReader parser;
 DefaultConfigurationBuilder configBuilder;
 File userConfigFile;
@@ -81,81 +81,81 @@
 userConfig = configBuilder.buildFromFile(userConfigFile);
 foUserAgent.setUserConfig(userConfig);
 </source>
-		<p>You can find example code in FOP's
+        <p>You can find example code in FOP's
 <code>apps.CommandLine</code> class, method
 <code>createUserConfig</code>.</p>
-	  </section>
+      </section>
 
-	  <section id="embedded-build">
-		<title>Programmatically Building the Configuration</title>
-		<p>You can also build the configuration object programmatically,
+      <section id="embedded-build">
+        <title>Programmatically Building the Configuration</title>
+        <p>You can also build the configuration object programmatically,
 instead of building it from an external file. Make sure that the
 configuration object is equivalent to a configuration object that
 would be obtained from a correct configuration file. Register the
 configuration object with the user agent as described above.</p>
-	  </section>
+      </section>
 
-	</section>
+    </section>
 
-	<section id="config-overview">
-	  <title>The Configuration File</title>
-	  <p>The top-level element is arbitrary. You may give it any name
+    <section id="config-overview">
+      <title>The Configuration File</title>
+      <p>The top-level element is arbitrary. You may give it any name
 that is useful for you, e.g. <code>&lt;fop-configuration
 version="2"></code>.</p>
-	  <p>Inside the top-level element the configuration may contain
+      <p>Inside the top-level element the configuration may contain
 three sections: <code>userAgent</code>, <code>renderers</code>,
 and <code>hyphenation</code>. At the moment of this writing the
 <code>userAgent</code> and <code>hyphenation</code> sections are
 not used by FOP.</p>
-	  <p>The <code>renderers</code> section has subsections called
+      <p>The <code>renderers</code> section has subsections called
 <code>renderer</code>. There may be one subsection for each type
 of renderer. The renderers are identified by their MIME type,
 which is given in the <code>mime</code> attribute. For example:
 <code>&lt;renderer mime="application/pdf"></code>. The content
 of each <code>renderer</code> subsection depends on the type of
 renderer.</p>
-	  <p>The PDF renderer (MIME type <code>application/pdf</code>) has
+      <p>The PDF renderer (MIME type <code>application/pdf</code>) has
 several options:</p>
-	  <dl>
-		<dt><code>filterList</code></dt>
-		<dd>Contains a number of <code>value</code> elements, whose
+      <dl>
+        <dt><code>filterList</code></dt>
+        <dd>Contains a number of <code>value</code> elements, whose
 content specify a filter which should be applied. Possible
 filters are: <code>flate</code>, <code>ascii-85</code>,
 <code>ascii-hex</code>. The <code>flate</code> filter is on by
 default.</dd>
-		<dt><code>fonts</code></dt>
-		<dd>Contains a number of <code>font</code> elements. Each
+        <dt><code>fonts</code></dt>
+        <dd>Contains a number of <code>font</code> elements. Each
 <code>font</code> element represents a font file,
 e.g. <code>arial.ttf</code>. It contains a number of
 <code>font-triplet</code> elements, defining the font triplets
 which are provided by this font file. See the example
 configuration file for details.</dd>
-	  </dl>
-	  <p>The example configuration file provides for details about the
+      </dl>
+      <p>The example configuration file provides for details about the
 other renderers.</p> 
-	</section>
+    </section>
 
     <section id="hyphenation-dir">
       <title>Hyphenation</title>
-	  <p>When FOP needs to load a hyphenation file for a certain
+      <p>When FOP needs to load a hyphenation file for a certain
 language and country combination, it follows these steps.</p> 
-	  <ol>
-		<li>FOP searches for the compiled hyphenation file (extension
+      <ol>
+        <li>FOP searches for the compiled hyphenation file (extension
 <code>hyp</code> in the directory <code>hyph</code> in the
 class path.</li> 
-		<li>FOP searches for the compiled or the XML hyphenation file
+        <li>FOP searches for the compiled or the XML hyphenation file
 in a user directory. At the time of this writing FOP does not
 read the configuration file for the user directory. It always
 uses the directory <code>/hyph</code>.</li>
-	  </ol>
-	  <p>It is possible to add user hyphenation files to FOP's
+      </ol>
+      <p>It is possible to add user hyphenation files to FOP's
 hyphenation directory when FOP is built. The directory
 containing user hyphenation files must be specified in the
 variable <code>user.hyph.dir</code> in the local build
 properties file. All hyphenation files in the directory are
 compiled, and the compiled files are added to the hyphenation
 directory in the build directory.</p>
-	  <p>See <link href="../hyphenation.html">FOP: Hyphenation</link> for
+      <p>See <link href="../hyphenation.html">FOP: Hyphenation</link> for
 more information on creating and modifying hyphenation within FOP.</p>
     </section>
 
@@ -168,24 +168,24 @@
 href="../fonts.html#register">Register Fonts with FOP</link>.</p>
     </section>
 
-	<section id="logging">
-	  <title>Logging</title>
-	  <p>FOP uses the Jakarta Commons logging package
+    <section id="logging">
+      <title>Logging</title>
+      <p>FOP uses the Jakarta Commons logging package
 <code>org.apache.commons.logging</code>. For detailed information, see
 the documentation of the package.</p>
-	  <p>Commons logging is entirely configured by the user, using
+      <p>Commons logging is entirely configured by the user, using
 Java system properties. Configuration happens in two stages.</p>
-		<p>First you configure which logging implementation you want
+        <p>First you configure which logging implementation you want
 to use. For example:</p>
-	  <source>org.apache.commons.logging.Log
+      <source>org.apache.commons.logging.Log
     =org.apache.commons.logging.impl.SimpleLog</source>
-	  <p><code>SimpleLog is the default logging package on most Java
+      <p><code>SimpleLog is the default logging package on most Java
 systems. On Java 1.4 systems JDK 1.4 is the default.</code></p>
-	  <p>Secondly, you configure the selected logging package. How
+      <p>Secondly, you configure the selected logging package. How
 this is done depends on the logging package. The most important
 feature is the log level. The default is level &ldquo;info&rdquo;. An
 example configuration file for SimpleLog is:</p>
-	  <source>
+      <source>
 # logging level for all loggers, default info
 org.apache.commons.logging.simplelog.defaultlog=info
 
@@ -193,7 +193,7 @@
 org.apache.commons.logging.simplelog.log.xxxxx=debug
 org.apache.commons.logging.simplelog.log.org.apache.fop.pdf=trace
 </source>
-	  <p>FOP uses several named loggers. When you set the logging level
+      <p>FOP uses several named loggers. When you set the logging level
 for all loggers to &ldquo;info&rdquo;, you get a decent small amount
 of information 
 about application progress. The debugging and especially the trace
@@ -201,7 +201,7 @@
 it is wise to switch them on for one or several specific loggers. The
 names of the loggers can be found in the source files. Many loggers
 bear the name of their package, their class or of a superclass.</p>
-	</section>
+    </section>
 
   </body>
 </document>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/faq.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/faq.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/faq.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/faq.xml Sun Aug  5 09:23:59 2007
@@ -48,9 +48,9 @@
     <faq id="doc-mgt">
       <question>Where can I learn how the FOP docs and web site are built?</question>
       <answer>
-      	<p>
-      		See FOP <link href="doc.html">Doc Management</link>. ;-)
-      	</p>
+        <p>
+            See FOP <link href="doc.html">Doc Management</link>. ;-)
+        </p>
       </answer>
     </faq>
   </part>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/release.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/release.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/release.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/dev/release.xml Sun Aug  5 09:23:59 2007
@@ -37,7 +37,7 @@
         <li>Determine whether this is a Release Candidate or a Release.</li>
         <li>Determine whether further testing is required.</li>
         <li>Commit any outstanding changes</li>
-		<li>Create a branch called <code>branches/fop-v_vv</code></li>
+        <li>Create a branch called <code>branches/fop-v_vv</code></li>
         <li>Edit release notes (<code>README</code> and <code>status.xml</code> in the root).</li>
         <li>Update the <code>index.xml</code> and <code>site.xml</code> for the new version.</li>
         <li>Update the version numbers in the release column on the
@@ -48,7 +48,7 @@
         <li>Copy trunk documentation directory to a new directory with
         the version number, and update any links and the .htaccess
         file for redirections.</li>
-		<li>Copy <code>test/fotree/disabled-testcases.xml</code> and
+        <li>Copy <code>test/fotree/disabled-testcases.xml</code> and
         <code>test/layoutengine/disabled-testcases.xml</code> to the
         new version directory
         <code>&lt;version>/fotree/disabled-testcases.xml</code> and
@@ -56,11 +56,11 @@
         Copy <code>known-issues.xml</code> to the new version
         directory. Copy <code>knownissues-overview.xml</code> from the
         previous to the new version directory.</li>
-		<li>Delete the previous version directory.</li>
-		<li>Build the dist files (<code>build[.sh] dist</code>)
+        <li>Delete the previous version directory.</li>
+        <li>Build the dist files (<code>build[.sh] dist</code>)
         and upload them to your web directory on
         <code>people.apache.org</code></li>
-		<li>Ask on fop-dev to check the branch and the generated dist
+        <li>Ask on fop-dev to check the branch and the generated dist
         files for errors.</li>
         <li>Tag the source tree with the release ID. For example, if the release is 0.94:
           <code>svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_94 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-0_94</code></li>
@@ -69,7 +69,7 @@
         <li>Copy jimi and jai to lib/ (jimi-1.0.jar, jai_core.jar, jai_codec.jar)</li>
         <li>Copy jce-jdk13-119.jar from <link href="http://www.bouncycastle.org/latest_releases.html">
           from http://www.bouncycastle.org/latest_releases.html</link> to lib/</li>
-		<li>Copy the hyphenation patterns jar file
+        <li>Copy the hyphenation patterns jar file
         <code>fop-hyph.jar</code> to lib/ (e.g. from
         <code>http://sourceforge.net/projects/offo</code></li>
         <li>Alternatively, create a build-local.properties file that points to the above libs.</li>
@@ -85,11 +85,11 @@
         <li>Add MD5 sums: <code>md5 fop-0.94-src.tar.gz &gt;
           fop-0.94-src.tar.gz.md5</code> etc.</li>
         <li>Make a test download.</li>
-		<li>Start a vote for the release on
+        <li>Start a vote for the release on
         <code>general@xmlgraphics.a.o</code>. The message should point
         to the release files and list the MD5 sums (<code>cat
         *.md5</code>). The vote is open for 72hrs.</li>
-		<li>When the release is accepted, copy the release files,
+        <li>When the release is accepted, copy the release files,
         their md5 sum files and the signature files to
         /www/www.apache.org/dist/xmlgraphics/fop/ in the
         subdirectories <code>source</code> and
@@ -98,10 +98,10 @@
         the previous version.</li>
         <li>Update HEADER.html and README.html in people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/</li>
         <li>Wait 24 hours (for the mirrors to catch up).</li>
-		<li>Merge the changes of the subversion release branch back
+        <li>Merge the changes of the subversion release branch back
         into trunk (not the version number in the build file) and
         delete the branch.</li>
-		<li>Deploy the updated documentation to the FOP website.</li>
+        <li>Deploy the updated documentation to the FOP website.</li>
         <li>Post announcements on fop-dev and fop-user and other related mailing lists.</li>
         <li>Ask a Bugzilla admin (Christian Geisert) to add a bugzilla
         entry for the new release id, or create an issue at
@@ -131,7 +131,7 @@
         <li>general@xmlgraphics.apache.org</li>
         <li>general@xml.apache.org</li>
         <li>announce@apache.org (from your apache.org address)</li>
-		<li>xsl-list@lists.mulberrytech.com (subscriber-only)</li>
+        <li>xsl-list@lists.mulberrytech.com (subscriber-only)</li>
         <li>XSL-FO@yahoogroups.com (subscriber-only)</li>
         <li>www-xsl-fo@w3.org</li>
         <li>docbook-apps@lists.oasis-open.org (subscriber-only)</li>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/examples.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/examples.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/examples.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/examples.xml Sun Aug  5 09:23:59 2007
@@ -85,7 +85,7 @@
 Developers will find the first steps to a test suite for all implemented
 formatting objects and properties in xml-fop/test/xml/.
       </p>
-	</section>
+    </section>
           <section>
             <title>Images Examples</title>
             <p>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/faq.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/faq.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/faq.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/faq.xml Sun Aug  5 09:23:59 2007
@@ -140,8 +140,8 @@
           the time-consuming process of creating a release. We
           released version 0.94 on XX August 2007, and intend to
           release version 1.0 later in late 2007 or early 2008. If you
-        	want to speed up the process, consider
-        	<link href="dev/index.html#involved">contributing</link> to FOP.</p>
+          want to speed up the process, consider
+          <link href="dev/index.html#involved">contributing</link> to FOP.</p>
       </answer>
     </faq>
     <faq id="redesign">
@@ -1109,21 +1109,21 @@
       <question>Can I use FOP to convert XHTML or HTML files to PDF?</question>
       <answer>
         <p>
-        	You will get better results if you transform your source
-			XML directly into XSLFO. It is tempting to use the
-			XML-&gt;XHTML-&gt;XSLFO approach, because this apparently means
-			there's only one transformation to maintain, but XHTML
-			and publishing grade PDF are dissimilar enough that an
-			"generic" XHTML-&gt;XSLFO(PDF) usually wont cut it, because
-			the XHTML already lacks information from the original XML.
-			It may be worthwhile to go from the source XML to an
-			intermediate custom XML which on one hand is close enough
-			to representation to allow simple transformation to either
-			XHTML or XSLFO for most of the structure, but on the other
-			hand retains enough semantic from the original XML that
-			elements which must be handled differently in the two
-			representations can be handled differently. Setting this
-			up requires experience and most likely extensive prototyping.
+          You will get better results if you transform your source
+          XML directly into XSLFO. It is tempting to use the
+          XML-&gt;XHTML-&gt;XSLFO approach, because this apparently means
+          there's only one transformation to maintain, but XHTML
+          and publishing grade PDF are dissimilar enough that an
+          "generic" XHTML-&gt;XSLFO(PDF) usually wont cut it, because
+          the XHTML already lacks information from the original XML.
+          It may be worthwhile to go from the source XML to an
+          intermediate custom XML which on one hand is close enough
+          to representation to allow simple transformation to either
+          XHTML or XSLFO for most of the structure, but on the other
+          hand retains enough semantic from the original XML that
+          elements which must be handled differently in the two
+          representations can be handled differently. Setting this
+          up requires experience and most likely extensive prototyping.
         </p>
       </answer>
     </faq>
@@ -1131,11 +1131,11 @@
       <question>I know it may be a bad idea to use FOP to convert XHTML or HTML files to PDF, but I want to do it anyway. Are there any tools available to help me?</question>
       <answer>
         <p>
-        	The <link href="resources.html">FOP Resources page</link> has links
-        	to a tool called <link href="http://html2fo.sourceforge.net/">html2fo</link>
-        	which can be used to make such a transformation. In addition, there
-        	are tools on the Antenna House <link href="http://www.antennahouse.com/XSLsample/XSLsample.htm">XSL-FO Tutorial and Sample</link>
-			page.
+          The <link href="resources.html">FOP Resources page</link> has links
+          to a tool called <link href="http://html2fo.sourceforge.net/">html2fo</link>
+          which can be used to make such a transformation. In addition, there
+          are tools on the Antenna House <link href="http://www.antennahouse.com/XSLsample/XSLsample.htm">XSL-FO Tutorial and Sample</link>
+          page.
         </p>
       </answer>
     </faq>
@@ -1145,9 +1145,9 @@
     <faq id="doc-mgt">
       <question>Where can I learn how the FOP docs and web site are built?</question>
       <answer>
-      	<p>
-      		See FOP <link href="dev/doc.html">Doc Management</link>. ;-)
-      	</p>
+        <p>
+          See FOP <link href="dev/doc.html">Doc Management</link>. ;-)
+        </p>
       </answer>
     </faq>
   </part>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/news.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/news.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/news.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/news.xml Sun Aug  5 09:23:59 2007
@@ -35,15 +35,15 @@
       <title>26 January 2007 - New Committer</title>
       <p>Welcome Jay Bryant!</p>
     </section>
-	<section>
-	  <title>9 January 2007 - Apache FOP 0.93 released</title>
+    <section>
+      <title>9 January 2007 - Apache FOP 0.93 released</title>
       <p>
         The Apache FOP team is proud to present to you the first
         production grade release of the new FOP codebase. This release
         has the new API first introduced in release 0.92 beta. It
         contains again many bug fixes and new features.
       </p>
-	</section>
+    </section>
     <section>
       <title>16 October 2006 - New Committer</title>
       <p>Welcome Vincent Hennebert!</p>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/configuration.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/configuration.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/configuration.xml Sun Aug  5 09:23:59 2007
@@ -78,7 +78,7 @@
         <td>URL or directory</td>
         <td>Specifies the base URL based on which relative font URLs will be resolved.
         </td>
-	<td>base URL/directory (above)</td>
+        <td>base URL/directory (above)</td>
       </tr>
       <tr>
         <td>hyphenation-base</td>
@@ -112,10 +112,10 @@
         <td>strict-configuration</td>
         <td>Boolean (true, false)</td>
         <td>
-	  Setting this option to 'true' will cause FOP to strictly verify the contents of the
-	  FOP configuration file to ensure that defined resources (such as fonts and base
-	  URLs/directories) are valid and available to FOP.  Any errors found will cause FOP to
-	  immediately raise an exception.</td>
+          Setting this option to 'true' will cause FOP to strictly verify the contents of the
+          FOP configuration file to ensure that defined resources (such as fonts and base
+          URLs/directories) are valid and available to FOP.  Any errors found will cause FOP to
+          immediately raise an exception.</td>
         <td>false</td>
       </tr>
       <tr>
@@ -125,7 +125,7 @@
           Setting this option to 'false' causes FOP to be more forgiving about XSL-FO validity, 
           for example, you're allowed to specify a border on a region-body which is supported 
           by some FO implementations but is non-standard. Note that such a border would 
-	  currently have no effect in Apache FOP.</td>
+          currently have no effect in Apache FOP.</td>
         <td>true</td>
       </tr>
       <tr>
@@ -173,7 +173,7 @@
         <td>renderers</td>
         <td>(see text below)</td>
         <td>Contains the configuration for each renderer. See below.</td>
-	<td>N/A</td>
+        <td>N/A</td>
       </tr>
     </table>
     <p>
@@ -333,10 +333,10 @@
     </section>
   </section>
 
-	<section>
-	  <title>When it does not work</title>
+        <section>
+          <title>When it does not work</title>
 
-	  <p>FOP searches the configuration file for the information it
+          <p>FOP searches the configuration file for the information it
 expects, at the position it expects. When that information is not
 present, FOP will not complain, it will just continue. When there is
 other information in the file, FOP will not complain, it will just
@@ -344,14 +344,14 @@
 the file but in a different XML element, or in a different XML path,
 than FOP expects, it will be silently ignored.</p>
 
-	  <p>Check the following possibilities:</p>
+          <p>Check the following possibilities:</p>
 
-	  <ul>
-		<li>The format of the configuration file has changed
+          <ul>
+            <li>The format of the configuration file has changed
 considerably between FOP 0.20.5 and FOP 1.0 and its beta versions. Did
 you convert your file to the new format?</li>
 
-		<li>The FOP distribution contains a schema for configuration
+            <li>The FOP distribution contains a schema for configuration
 files, at src/foschema/fop-configuration.xsd. Did you validate your
 configuration file against it? Add the following schema location to
 the <code>schema</code> element:
@@ -366,13 +366,13 @@
 parser. Note that the schema cannot detect all errors, and that it is
 stricter about the order of some elements than FOP itself is.</li>
 
-		<li>Run FOP in debug mode (command line option
+            <li>Run FOP in debug mode (command line option
 <code>-d</code>). This makes FOP report which configuration
 information it finds. Check if FOP finds what you expect.</li>
 
-	  </ul>
+          </ul>
 
-	</section>
+        </section>
   </body>
 </document>
 

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/fonts.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/fonts.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/fonts.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/fonts.xml Sun Aug  5 09:23:59 2007
@@ -263,7 +263,7 @@
           </li>
           <li>Either an "embed-url" or a "metrics-url" must be specified for font tag configurations.</li>
           <li>The font "kerning" attribute is optional.</li>
-	      <li>If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
+          <li>If embedding is off, the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
           <li>When setting the "embed-url" attribute for Type 1 fonts, be sure to specify the PFB (actual font data), not PFM (font metrics) file that you used to generate the XML font metrics file.</li>
           <li>The fonts "directory" tag can be used to register fonts contained within a single or list of directory paths.  The "recursive" attribute can be specified to recursively add fonts from all sub directories.</li>
           <li>The fonts "auto-detect" tag can be used to automatically register fonts that are found to be installed on the native operating system.</li>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/running.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/running.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/running.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/running.xml Sun Aug  5 09:23:59 2007
@@ -214,37 +214,37 @@
       directory in a single directory. If you use hyphenation, you
       must also put <code>fop-hyph.jar</code> in that directory.</p>
 
-		<p>In both cases the arguments consist of the options and
+    <p>In both cases the arguments consist of the options and
         infile and outfile specifications as shown above for the
         standard scripts.</p>
       </section>
       <section id="dynamical-classpath">
-		<title>FOP's dynamical classpath construction</title>
+        <title>FOP's dynamical classpath construction</title>
 
-		<p>If FOP is started without a proper classpath, it tries to
-		add its dependencies dynamically. If the system property
-		<code>fop.home</code> contains the name of a directory, then
-		FOP uses that directory as the base directory for its
-		search. Otherwise the current working directory is the base
-		directory. If the base directory is called <code>build</code>,
-		then its parent directory becomes the base directory.</p>
+        <p>If FOP is started without a proper classpath, it tries to
+          add its dependencies dynamically. If the system property
+          <code>fop.home</code> contains the name of a directory, then
+          FOP uses that directory as the base directory for its
+          search. Otherwise the current working directory is the base
+          directory. If the base directory is called <code>build</code>,
+          then its parent directory becomes the base directory.</p>
 
         <p>FOP expects to find <code>fop.jar</code> in the
-		<code>build</code> subdirectory of the base directory, and
-		adds it to the classpath. Subsequently FOP adds all
-		<code>jar</code> files in the lib directory to the
-		classpath. The lib directory is either the <code>lib</code>
-		subdirectory of the base directory, or, if that does not
-		exist, the base directory itself.</p>
+          <code>build</code> subdirectory of the base directory, and
+          adds it to the classpath. Subsequently FOP adds all
+          <code>jar</code> files in the lib directory to the
+          classpath. The lib directory is either the <code>lib</code>
+          subdirectory of the base directory, or, if that does not
+          exist, the base directory itself.</p>
 
         <p>If the system property <code>fop.optional.lib</code>
-		contains the name of a directory, then all <code>jar</code>
-		files in that directory are also added to the classpath. See
-		the methods <code>getJARList</code> and
-		<code>checkDependencies</code> in
-		<code>org.apache.fop.cli.Main</code>.</p>
+          contains the name of a directory, then all <code>jar</code>
+          files in that directory are also added to the classpath. See
+          the methods <code>getJARList</code> and
+          <code>checkDependencies</code> in
+          <code>org.apache.fop.cli.Main</code>.</p>
 
-	  </section>
+      </section>
     </section>
     <section id="check-input">
       <title>Using Xalan to Check XSL-FO Input</title>

Modified: xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/upgrading.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/upgrading.xml?view=diff&rev=562903&r1=562902&r2=562903
==============================================================================
--- xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/upgrading.xml (original)
+++ xmlgraphics/fop/branches/fop-0_94/src/documentation/content/xdocs/trunk/upgrading.xml Sun Aug  5 09:23:59 2007
@@ -54,7 +54,7 @@
           an example configuration file. A XML Schema file can be found under
           src/foschema/fop-configuration.xsd.
         </li>
-		<li>
+        <li>
           If you are using font metrics files for version 0.20.5 or
           0.92 or earlier, you have to regenerate them in the new
           format. The new format is characterized by a version



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


Mime
View raw message