xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vhenneb...@apache.org
Subject svn commit: r569118 [3/49] - in /xmlgraphics/site/deploy/fop: ./ 0.93/ 0.94/ 0.94/images/ dev/ dev/design/ skin/ trunk/
Date Thu, 23 Aug 2007 19:00:51 GMT
Added: xmlgraphics/site/deploy/fop/0.93/fonts.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/fonts.xml?rev=569118&view=auto
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/fonts.xml (added)
+++ xmlgraphics/site/deploy/fop/0.93/fonts.xml Thu Aug 23 12:00:37 2007
@@ -0,0 +1,306 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
+<document>
+  <header>
+    <title>Apache FOP: Fonts</title>
+    <version>$Revision: 520886 $</version>
+    <authors>
+      <person name="Jeremias Märki" email=""/>
+      <person name="Tore Engvig" email=""/>
+    </authors>
+  </header>
+  <body>
+    <section id="intro">
+      <title>Summary</title>
+      <note>The FOP Font subsystem is currently undergoing a significant change.
+        The details provided here especially related to the generation of FOP Font
+        Metrics files and the FOP Font configuration are likely to change substantially
+        in the future.
+      </note>
+      <p>The following table summarizes the font capabilities of the various FOP renderers:</p>
+      <table>
+        <tr>
+          <th colspan="1" rowspan="1">Renderer</th>
+          <th colspan="1" rowspan="1">Base-14</th>
+          <th colspan="1" rowspan="1">AWT/OS</th>
+          <th colspan="1" rowspan="1">Custom</th>
+          <th colspan="1" rowspan="1">Custom Embedding</th>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">PDF</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">no</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">yes</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">PostScript</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">no</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">yes</td>
+        </tr>
+        <!--tr> NOT AVAILABLE YET!!!
+          <td>PCL</td>
+          <td>yes (modified)</td>
+          <td>no</td>
+          <td>no</td>
+          <td>no</td>
+        </tr-->
+        <tr>
+          <td colspan="1" rowspan="1">TXT</td>
+          <td colspan="1" rowspan="1">yes (used for layout but not for output)</td>
+          <td colspan="1" rowspan="1">no</td>
+          <td colspan="1" rowspan="1">yes (used for layout but not for output)</td>
+          <td colspan="1" rowspan="1">no</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">AWT</td>
+          <td colspan="1" rowspan="1">if available from OS</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">n/a (display only)</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">Print</td>
+          <td colspan="1" rowspan="1">if available from OS</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">controlled by OS printer driver</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">RTF</td>
+          <td colspan="1" rowspan="1">n/a (font metrics not needed)</td>
+          <td colspan="1" rowspan="1">n/a</td>
+          <td colspan="1" rowspan="1">n/a</td>
+          <td colspan="1" rowspan="1">n/a</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">MIF</td>
+          <td colspan="1" rowspan="1">n/a (font metrics not needed)</td>
+          <td colspan="1" rowspan="1">n/a</td>
+          <td colspan="1" rowspan="1">n/a</td>
+          <td colspan="1" rowspan="1">n/a</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">SVG</td>
+          <td colspan="1" rowspan="1">if available from OS</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">no</td>
+          <td colspan="1" rowspan="1">no</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">XML</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">no</td>
+          <td colspan="1" rowspan="1">yes</td>
+          <td colspan="1" rowspan="1">n/a</td>
+        </tr>
+      </table>
+    </section>
+    <section>
+      <title>Base-14 Fonts</title>
+      <p>The Adobe PDF Specification specifies a set of 14 fonts that must be available to every PDF reader: Helvetica (normal, bold, italic, bold italic), Times (normal, bold, italic, bold italic), Courier (normal, bold, italic, bold italic), Symbol and ZapfDingbats.</p>
+    </section>
+    <section id="awt">
+      <title>AWT/Operating System Fonts</title>
+      <p>The AWT family of renderers (AWT, Print, SVG), use the Java AWT libraries for font metric information. Through operating system registration, the AWT libraries know what fonts are available on the system, and the font metrics for each one.</p>
+    </section>
+    <section id="custom">
+      <title>Custom Fonts</title>
+      <p>Support for custom fonts is added by creating font metric files (written in XML) from the actual font files, and registering them with FOP. Currently only Type 1 and TrueType fonts can be added.
+More information about fonts can be found at:</p>
+      <ul>
+        <li><link href="http://partners.adobe.com/asn/developer/type/ftypes.html">Adobe font types</link></li>
+        <li><link href="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</link>
+</li>
+      </ul>
+      <section id="type1-metrics">
+        <title>Type 1 Font Metrics</title>
+        <p>FOP includes PFMReader, which reads the PFM file that normally comes with a Type 1 font, and generates an appropriate font metrics file for it.
+To use it, run the class org.apache.fop.fonts.apps.PFMReader:</p>
+        <p>Windows (on JDK 1.4 and later):</p>
+        <source xml:space="preserve"><![CDATA[java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
+           org.apache.fop.fonts.apps.PFMReader [options] pfm-file xml-file]]></source>
+        <p>Windows (on JDK 1.3.x):</p>
+        <source xml:space="preserve"><![CDATA[java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar;lib\xml-apis.jar;
+         lib\xercesImpl.jar;lib\xalan.jar;lib\serializer.jar
+           org.apache.fop.fonts.apps.PFMReader [options] pfm-file xml-file]]></source>
+        <p>Unix (on JDK 1.4 and later):</p>
+        <source xml:space="preserve"><![CDATA[java -cp build/fop.jar:lib/avalon-framework.jar:lib/commons-logging.jar:lib/commons-io.jar
+           org.apache.fop.fonts.apps.PFMReader [options] pfm-file xml-file]]></source>
+        <p>Unix (on JDK 1.3.1):</p>
+        <source xml:space="preserve"><![CDATA[java -cp build/fop.jar:lib/avalon-framework.jar:lib/commons-logging.jar:lib/commons-io.jar:lib/xml-apis.jar:
+         lib/xercesImpl.jar:lib/xalan.jar:lib/serializer.jar
+           org.apache.fop.fonts.apps.PFMReader [options] pfm-file xml-file]]></source>
+        <p>PFMReader [options]:</p>
+        <ul>
+          <li><strong>-fn &lt;fontname&gt;</strong> By default, FOP uses the fontname from the
+.pfm file when embedding the font. Use the "-fn" option to override this name with one you have
+chosen. This may be useful in some cases to ensure that applications using the output document
+(Acrobat Reader for example) use the embedded font instead of a local font with the same
+name.</li>
+        </ul>
+        <note>The classpath in the above example has been simplified for readability.
+You will have to adjust the classpath to the names of the actual JAR files in the lib directory.
+xml-apis.jar, xercesImpl.jar, xalan.jar and serializer.jar are not necessary for JDK version 1.4 or later.</note>
+        <note>The tool will construct some values (FontBBox, StemV and ItalicAngle) based on assumptions and calculations which are only an approximation to the real values.
+FontBBox and Italic Angle can be found in the human-readable part of the PFB file or in the AFM file.
+The PFMReader tool does not yet interpret PFB or AFM files, so if you want to be correct, you may have to adjust the values in the XML file manually.
+The constructed values however appear to have no visible influence.</note>
+      </section>
+      <section id="truetype-metrics">
+        <title>TrueType Font Metrics</title>
+        <p>FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it.
+Use it in a similar manner to PFMReader.
+For example, to create such a metrics file in Windows from the TrueType font at c:\myfonts\cmr10.ttf:</p>
+        <source xml:space="preserve"><![CDATA[java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
+           org.apache.fop.fonts.apps.TTFReader [options]
+             C:\myfonts\cmr10.ttf ttfcm.xml]]></source>
+        <p>TTFReader [options]:</p>
+        <ul>
+          <li><strong>-d &lt;DEBUG | INFO &gt;</strong> Sets the debug level (default is
+INFO).</li>
+          <li><strong>-fn &lt;fontname&gt;</strong> Same as for PFMReader.</li>
+          <li><strong>-ttcname &lt;fontname&gt;</strong> If you're reading data from a
+TrueType Collection (.ttc file) you must specify which font from the collection you will read
+metrics from.
+If you read from a .ttc file without this option, the fontnames will be listed for you.</li>
+          <li><strong>-enc ansi</strong> Creates a WinAnsi-encoded font metrics file.
+Without this option, a CID-keyed font metrics file is created.
+The table below summarizes the differences between these two encoding options as currently
+used within FOP.
+Please note that this information only applies to TrueType fonts and TrueType collections:</li>
+        </ul>
+        <table id="ttf-encoding">
+          <tr>
+            <th colspan="1" rowspan="1">Issue</th>
+            <th colspan="1" rowspan="1">WinAnsi</th>
+            <th colspan="1" rowspan="1">CID-keyed</th>
+          </tr>
+          <tr>
+            <td colspan="1" rowspan="1">Usable Character Set</td>
+            <td colspan="1" rowspan="1">Limited to WinAnsi character set, which is roughly equivalent to iso-8889-1.</td>
+            <td colspan="1" rowspan="1">Limited only by the characters in the font itself.</td>
+          </tr>
+          <tr>
+            <td colspan="1" rowspan="1">Character Encoding in the Output Document.</td>
+            <td colspan="1" rowspan="1">Correct.</td>
+            <td colspan="1" rowspan="1">Never correct. Search, index, and cut-and-paste operations in the output document
+will produce incorrect results.</td>
+          </tr>
+          <tr>
+            <td colspan="1" rowspan="1">Character Display</td>
+            <td colspan="1" rowspan="1">Correct.</td>
+            <td colspan="1" rowspan="1">Correct, but copy/paste won't work in Acrobat Reader. (FOP currently doesn't emit the /ToUnicode table which is necessary for copy/paste to work.)</td>
+          </tr>
+          <tr>
+            <td colspan="1" rowspan="1">Embedding the Font</td>
+            <td colspan="1" rowspan="1">Optional.</td>
+            <td colspan="1" rowspan="1">Mandatory. Not embedding the font produces invalid PDF documents.</td>
+          </tr>
+        </table>
+        <warning>
+          You may experience failures with certain TrueType fonts, especially if they don't contain 
+          the so-called "cmap" table. TTFReader can currently not deal with font like this.
+        </warning>
+      </section>
+      <section id="truetype-collections-metrics">
+        <title>TrueType Collections Font Metrics</title>
+        <p>TrueType collections (.ttc files) contain more than one font.
+To create metrics files for these fonts, you must specify which font in the collection should be generated, by using the "-ttcname" option with the TTFReader.</p>
+        <p>To get a list of the fonts in a collection, just start the TTFReader as if it were a normal TrueType file (without the -ttcname option).
+It will display all of the font names and exit with an Exception.</p>
+        <p>Here is an example of generating a metrics file for a .ttc file:</p>
+        <source xml:space="preserve"><![CDATA[java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
+           org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho"
+             msmincho.ttc msminch.xml]]></source>
+      </section>
+      <section id="register">
+        <title>Register Fonts with FOP</title>
+        <p>You must tell FOP how to find and use the font metrics files by registering them in the <link href="configuration.html">FOP Configuration</link>. Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:</p>
+        <source xml:space="preserve"><![CDATA[<font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes"
+      embed-url="file:///C:/myfonts/FTL_____.pfb">
+  <font-triplet name="FrutigerLight" style="normal" weight="normal"/>
+</font>]]></source>
+        <note>Review the documentation for <link href="configuration.html">FOP Configuration</link> 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>
+        <ul>
+          <li>
+            URLs are used to access the font metric and font files.
+            Relative URLs are resolved relative to the font-base property (or base) if available.
+            See <link href="configuration.html">FOP: Configuration</link> for more information.
+          </li>
+          <li>The "kerning" and "embed-url" attributes are optional. Kerning is currently not used at all. 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>
+            If relative URLs are specified, they are evaluated relative to the value of the 
+            "font-base" setting. If there is no "font-base" setting, the fonts are evaluated 
+            relative to the base directory.
+          </li>
+        </ul>
+        <!--note>Cocoon users will need to setup the config, see FOPSerializer for more information.</note-->
+      </section>
+      <section id="embedding">
+        <title>Embedding</title>
+        <note>The PostScript renderer does not yet support TrueType fonts, but can embed Type 1 fonts.</note>
+        <note>The font is simply embedded into the PDF file, it is not converted.</note>
+        <p>Font embedding is enabled in the userconfig.xml file and controlled by the embed-url attribute.
+If you don't specify the embed-url attribute the font will not be embedded, but will only be referenced.</p>
+        <warning>
+          Omitting the embed-url attribute for CID-encoded TrueType fonts will currently produce invalid 
+          PDF files! If you create the XML font metric file using the "-enc ansi" option, you can omit 
+          the embed-url attribute for TrueType fonts but you're restricted to the WinAnsi character set.
+        </warning>
+        <p>When FOP embeds a font, it adds a prefix to the fontname to ensure that the name will not match the fontname of an installed font.
+This is helpful with older versions of Acrobat Reader that preferred installed fonts over embedded fonts.</p>
+        <p>When embedding PostScript fonts, the entire font is always embedded.</p>
+        <p>When embedding TrueType fonts (ttf) or TrueType Collections (ttc), a subset of the original font, containing only the glyphs used, is embedded in the output document.
+Currently, this embedded font contains only the minimum data needed to be embedded in a pdf document, and does not contain any codepage information.
+The PDF document contains indexes to the glyphs in the font instead of to encoded characters.
+While the document will be displayed correctly, the net effect of this is that searching, indexing, and cut-and-paste will not work properly.</p>
+        <p>One workaround for this behavior is to use the "-enc ansi" option when generating metrics with TTFReader.
+This will cause the whole font to be embedded in the pdf document.
+Characters will be WinAnsi encoded (as specified in the PDF spec), so you lose the ability to use characters from other character sets.
+See <link href="#ttf-encoding">Table of TTF Encoding Options</link> for more details.</p>
+      </section>
+      <section id="embedding-base14">
+        <title>Explicitely embedding the base 14 fonts</title>
+        <p>
+          There are cases where you might want to force the embedding of one or more of the base 14 fonts that
+          can normally be considered available on the target platform (viewer, printer). One of these cases is
+          PDF/A which mandates the embedding of even the base 14 fonts. Embedding a font such as Helvetica or
+          Courier is straight-forward. The "Symbol" and "ZapfDingbats" fonts, however, currently present a 
+          problem because FOP cannot correctly determine the encoding of these two single-byte fonts through
+          the PFM file. FOP now correctly interprets the "encoding" value in the XML font metrics file, but the
+          PFMReader application writes "UnknownEncoding" to the generated XML file. In order to embed "Symbol"
+          and "ZapfDingbats" you have to manually change the XML font metrics file and specify "SymbolEncoding"
+          or "ZapfdingbatsEncoding" encoding respectively as the value for the "encoding" element.
+        </p>
+        <p>Example:</p>
+        <source xml:space="preserve"><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<font-metrics type="TYPE1">
+  <font-name>Symbol</font-name>
+  <embed/>
+  <encoding>SymbolEncoding</encoding>
+  <cap-height>673</cap-height>
+  <x-height>766</x-height>
+  [..]]]></source>
+      </section>
+    </section>
+  </body>
+</document>
\ No newline at end of file

Propchange: xmlgraphics/site/deploy/fop/0.93/fonts.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: xmlgraphics/site/deploy/fop/0.93/fonts.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Modified: xmlgraphics/site/deploy/fop/0.93/graphics.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/graphics.html?rev=569118&r1=569117&r2=569118&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/graphics.html (original)
+++ xmlgraphics/site/deploy/fop/0.93/graphics.html Thu Aug 23 12:00:37 2007
@@ -57,13 +57,13 @@
 <li>
 <a class="base-not-selected" href="../index.html">Home</a>
 </li>
-<li>
-<a class="base-not-selected" href="../0.20.5/index.html">Version 0.20.5</a>
-</li>
 <li class="current">
 <a class="base-selected" href="../0.93/index.html">Version 0.93</a>
 </li>
 <li>
+<a class="base-not-selected" href="../0.94/index.html">Version 0.94</a>
+</li>
+<li>
 <a class="base-not-selected" href="../trunk/index.html">FOP Trunk</a>
 </li>
 <li>
@@ -187,10 +187,20 @@
     |start content
     +-->
 <div id="content">
+<div title="raw XML" class="xmllink">
+<a class="dida" href="graphics.xml"><img alt="XML - icon" src="../skin/images/xmldoc.gif" class="skin"><br>
+        XML</a>
+</div>
 <div title="Portable Document Format" class="pdflink">
 <a class="dida" href="graphics.pdf"><img alt="PDF -icon" src="../skin/images/pdfdoc.gif" class="skin"><br>
         PDF</a>
 </div>
+<div class="trail">
+<text>Font size:</text> 
+	          &nbsp;<input value="Reset" class="resetfont" title="Reset text" onclick="ndeSetTextSize('reset'); return false;" type="button">      
+	          &nbsp;<input value="-a" class="smallerfont" title="Shrink text" onclick="ndeSetTextSize('decr'); return false;" type="button">
+	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
+</div>
 <h1>Apache FOP: Graphics Formats</h1>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -401,14 +411,14 @@
 <h3 class="underlined_5">Image I/O (JDK 1.4 or higher)</h3>
 <p>
           For JDKs 1.4 or higher, FOP provides a wrapper to load images through the 
-          <a target="_blank" class="fork" href="http://java.sun.com/j2se/1.4.2/docs/guide/imageio/index.html">JDK's Image I/O API</a> (JSR 015).
+          <a class="external" href="http://java.sun.com/j2se/1.4.2/docs/guide/imageio/index.html">JDK's Image I/O API</a> (JSR 015).
           Image I/O allows to dynamically add additional image codecs. An example of such an add-on library are the
-          <a target="_blank" class="fork" href="http://java.sun.com/products/java-media/jai/">JAI Image I/O Tools</a> available from Sun.
+          <a class="external" href="http://java.sun.com/products/java-media/jai/">JAI Image I/O Tools</a> available from Sun.
         </p>
 <a name="N101AF"></a><a name="jimi"></a>
 <h3 class="underlined_5">JIMI</h3>
 <p>
-          Because of licensing issues, the JIMI image library is not included in the FOP distribution. First, <a target="_blank" class="fork" href="http://java.sun.com/products/jimi">download</a> and install it.
+          Because of licensing issues, the JIMI image library is not included in the FOP distribution. First, <a class="external" href="http://java.sun.com/products/jimi">download</a> and install it.
 Then, copy the file "JimiProClasses.zip" from the archive to {fop-install-dir}/lib/jimi-1.0.jar. Please note that FOP binary distributions are compiled with JIMI support, so there is no need for you to build FOP to add the support. If jimi-1.0.jar is installed in the right place, it will automatically be used by FOP, otherwise it will not.
         </p>
 <a name="N101BE"></a><a name="jai"></a>
@@ -419,8 +429,8 @@
 </div>
 <p>
           FOP has been compiled with JAI support, but JAI is not included in the FOP distribution.
-To use it, install <a href="http://java.sun.com/products/java-media/jai">JAI</a>, then copy the jai_core.jar and the jai_codec.jar files to {fop-install-dir}/lib.
-JAI is much faster than JIMI, but is not available for all platforms. See <a href="http://java.sun.com/products/java-media/jai/forDevelopers/jaifaq.html#platforms">What platforms are supported?</a> on the JAI FAQ page for more details.
+To use it, install <a class="external" href="http://java.sun.com/products/java-media/jai">JAI</a>, then copy the jai_core.jar and the jai_codec.jar files to {fop-install-dir}/lib.
+JAI is much faster than JIMI, but is not available for all platforms. See <a class="external" href="http://java.sun.com/products/java-media/jai/forDevelopers/jaifaq.html#platforms">What platforms are supported?</a> on the JAI FAQ page for more details.
         </p>
 <a name="N101D3"></a><a name="batik"></a>
 <h3 class="underlined_5">Batik</h3>
@@ -441,7 +451,7 @@
           
 <li>Install an X server which provides an in-memory framebuffer without actually using a screen device or any display hardware. One example is Xvfb.</li>
           
-<li>Install a toolkit which emulates AWT without the need for an underlying X server. One example is the <a href="http://www.eteks.com/pja/en">PJA toolkit</a>, which is free and comes with detailed installation instructions.</li>
+<li>Install a toolkit which emulates AWT without the need for an underlying X server. One example is the <a class="external" href="http://www.eteks.com/pja/en">PJA toolkit</a>, which is free and comes with detailed installation instructions.</li>
         
 </ul>
 </div>
@@ -506,7 +516,7 @@
 <div class="content">   
 Batik's SVG Rasterizer utility may also be used to convert standalone SVG
 documents into PDF.  For more information please see the
-<a href="http://xml.apache.org/batik/svgrasterizer.html">SVG Rasterizer documentation</a>
+<a class="external" href="http://xml.apache.org/batik/svgrasterizer.html">SVG Rasterizer documentation</a>
 on the Batik site.
       </div>
 </div>

Modified: xmlgraphics/site/deploy/fop/0.93/graphics.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/graphics.pdf?rev=569118&r1=569117&r2=569118&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/graphics.pdf (original)
+++ xmlgraphics/site/deploy/fop/0.93/graphics.pdf Thu Aug 23 12:00:37 2007
@@ -1054,8 +1054,8 @@
 135 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F3
-/BaseFont /Helvetica-Bold
+/Name /F1
+/BaseFont /Helvetica
 /Encoding /WinAnsiEncoding >>
 endobj
 136 0 obj
@@ -1068,15 +1068,15 @@
 137 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F6
-/BaseFont /Times-Italic
+/Name /F3
+/BaseFont /Helvetica-Bold
 /Encoding /WinAnsiEncoding >>
 endobj
 138 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F1
-/BaseFont /Helvetica
+/Name /F2
+/BaseFont /Helvetica-Oblique
 /Encoding /WinAnsiEncoding >>
 endobj
 139 0 obj
@@ -1089,8 +1089,8 @@
 140 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F2
-/BaseFont /Helvetica-Oblique
+/Name /F6
+/BaseFont /Times-Italic
 /Encoding /WinAnsiEncoding >>
 endobj
 141 0 obj
@@ -1114,7 +1114,7 @@
 endobj
 3 0 obj
 << 
-/Font << /F3 135 0 R /F5 136 0 R /F1 138 0 R /F6 137 0 R /F9 139 0 R /F2 140 0 R /F7 141 0 R >> 
+/Font << /F1 135 0 R /F5 136 0 R /F3 137 0 R /F2 138 0 R /F9 139 0 R /F6 140 0 R /F7 141 0 R >> 
 /ProcSet [ /PDF /ImageC /Text ] >> 
 endobj
 9 0 obj
@@ -1386,11 +1386,11 @@
 0000035205 00000 n 
 0000035428 00000 n 
 0000035605 00000 n 
-0000035719 00000 n 
-0000035830 00000 n 
-0000035942 00000 n 
-0000036051 00000 n 
-0000036158 00000 n 
+0000035714 00000 n 
+0000035825 00000 n 
+0000035939 00000 n 
+0000036056 00000 n 
+0000036163 00000 n 
 0000036275 00000 n 
 trailer
 <<

Added: xmlgraphics/site/deploy/fop/0.93/graphics.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/graphics.xml?rev=569118&view=auto
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/graphics.xml (added)
+++ xmlgraphics/site/deploy/fop/0.93/graphics.xml Thu Aug 23 12:00:37 2007
@@ -0,0 +1,335 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
+<document>
+  <header>
+    <title>Apache FOP: Graphics Formats</title>
+    <version>$Revision: 493717 $</version>
+  </header>
+  <body>
+    <section id="support-overview">
+      <title>Overview of Graphics Support</title>
+      <p>
+        The table below summarizes the <em>theoretical</em> support for graphical formats within FOP. In other words, within the constraints of the limitations listed here, these formats <em>should</em> work. However, many of them have not been tested, and there may be limitations that have not yet been discovered or documented. The packages needed to support some formats are not included in the FOP distribution and must be installed separately. Follow the links in the "Support Thru" column for more details.
+      </p>
+      <table>
+        <tr>
+          <th colspan="1" rowspan="1">Format</th>
+          <th colspan="1" rowspan="1">Type</th>
+          <th colspan="1" rowspan="1"><link href="#native">FOP native support</link></th>
+          <th colspan="1" rowspan="1"><link href="#batik">Batik SVG</link></th>
+          <th colspan="1" rowspan="1"><link href="#batik-codecs">Batik codecs</link></th>
+          <th colspan="1" rowspan="1"><link href="#imageio">Image I/O</link></th>
+          <th colspan="1" rowspan="1"><link href="#jai">JAI</link></th>
+          <th colspan="1" rowspan="1"><link href="#jimi">JIMI</link></th>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><link href="#bmp">BMP</link> (Microsoft Windows Bitmap)</td>
+          <td colspan="1" rowspan="1">bitmap</td>
+          <td colspan="1" rowspan="1">X</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><link href="#eps">EPS</link> (Encapsulated PostScript)</td>
+          <td colspan="1" rowspan="1">metafile (both bitmap and vector), probably most frequently used for vector drawings</td>
+          <td colspan="1" rowspan="1">(X)</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">GIF (Graphics Interchange Format)</td>
+          <td colspan="1" rowspan="1">bitmap</td>
+          <td colspan="1" rowspan="1">X</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1">X</td>
+          <td colspan="1" rowspan="1">X</td>
+          <td colspan="1" rowspan="1">X</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><link href="#jpeg">JPEG</link> (Joint Photographic Experts Group)</td>
+          <td colspan="1" rowspan="1">bitmap</td>
+          <td colspan="1" rowspan="1">(X)</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><link href="#png">PNG</link> (Portable Network Graphic)</td>
+          <td colspan="1" rowspan="1">bitmap</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1">X</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><link href="#svg">SVG</link> (Scalable Vector Graphics)</td>
+          <td colspan="1" rowspan="1">vector (with embedded bitmaps)</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1">X</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1"/>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1"><link href="#tiff">TIFF</link> (Tag Image Format File)</td>
+          <td colspan="1" rowspan="1">bitmap</td>
+          <td colspan="1" rowspan="1">(X)</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1">X</td>
+          <td colspan="1" rowspan="1"/>
+          <td colspan="1" rowspan="1">X</td>
+          <td colspan="1" rowspan="1"/>
+          <!--td><a href="#native">FOP native</a> or <a href="#jai">JAI</a>, depending on the subformat. See <a href="#tiff">TIFF</a> for more details.(JIMI also supports TIFF, but this has not been implemented within FOP).</td-->
+        </tr>
+      </table>
+      <note>"(X)" means restricted support. Please see the details below.</note>
+    </section>
+    <section id="packages">
+      <title>Graphics Packages</title>
+      <section id="native">
+        <title>FOP Native</title>
+        <p>
+          FOP has native ability to handle some graphic file formats.
+        </p>
+      </section>
+      <section id="batik-codecs">
+        <title>Batik codecs</title>
+        <p>
+          Apache Batik contains codecs for PNG and TIFF access. FOP can use these.
+        </p>
+      </section>
+      <section id="imageio">
+        <title>Image I/O (JDK 1.4 or higher)</title>
+        <p>
+          For JDKs 1.4 or higher, FOP provides a wrapper to load images through the 
+          <link class="fork" href="http://java.sun.com/j2se/1.4.2/docs/guide/imageio/index.html">JDK's Image I/O API</link> (JSR 015).
+          Image I/O allows to dynamically add additional image codecs. An example of such an add-on library are the
+          <link class="fork" href="http://java.sun.com/products/java-media/jai/">JAI Image I/O Tools</link> available from Sun.
+        </p>
+      </section>
+      <section id="jimi">
+        <title>JIMI</title>
+        <p>
+          Because of licensing issues, the JIMI image library is not included in the FOP distribution. First, <link class="fork" href="http://java.sun.com/products/jimi">download</link> and install it.
+Then, copy the file "JimiProClasses.zip" from the archive to {fop-install-dir}/lib/jimi-1.0.jar. Please note that FOP binary distributions are compiled with JIMI support, so there is no need for you to build FOP to add the support. If jimi-1.0.jar is installed in the right place, it will automatically be used by FOP, otherwise it will not.
+        </p>
+      </section>
+      <section id="jai">
+        <title>JAI (Java Advanced Imaging API)</title>
+        <warning>JAI support is available for Release 0.20.5 and later. The comments in this section do not apply to releases earlier than 0.20.5.</warning>
+        <p>
+          FOP has been compiled with JAI support, but JAI is not included in the FOP distribution.
+To use it, install <link href="http://java.sun.com/products/java-media/jai">JAI</link>, then copy the jai_core.jar and the jai_codec.jar files to {fop-install-dir}/lib.
+JAI is much faster than JIMI, but is not available for all platforms. See <link href="http://java.sun.com/products/java-media/jai/forDevelopers/jaifaq.html#platforms">What platforms are supported?</link> on the JAI FAQ page for more details.
+        </p>
+      </section>
+      <section id="batik">
+        <title>Batik</title>
+        <p>Current FOP distributions include a distribution of the Apache <link class="fork" href="ext:batik">Batik</link> version 1.6.
+It is automatically installed with FOP.
+Because Batik's API changes frequently, it is highly recommended that you use the version that ships with FOP, at least when running FOP.</p>
+        <warning>Batik must be run in a graphical environment.</warning>
+        <p>Batik must be run in a graphical environment.
+It uses AWT classes for rendering SVG, which in turn require an X server on Unixish systems.
+If you run a server without X, or if you can't connect to the X server due to security restrictions or policies (a so-called "headless" environment), SVG rendering will fail.</p>
+        <p>Here are some workarounds:</p>
+        <ul>
+          <li>If you are using JDK 1.4, start it with the <code>-Djava.awt.headless=true</code> command line option.</li>
+          <li>Install an X server which provides an in-memory framebuffer without actually using a screen device or any display hardware. One example is Xvfb.</li>
+          <li>Install a toolkit which emulates AWT without the need for an underlying X server. One example is the <link href="http://www.eteks.com/pja/en">PJA toolkit</link>, which is free and comes with detailed installation instructions.</li>
+        </ul>
+      </section>
+    </section>
+    <section id="bmp">
+      <title>BMP</title>
+      <p>FOP native support for BMP images is limited to the RGB color-space.</p>
+    </section>
+    <section id="eps">
+      <title>EPS</title>
+      <p>FOP provides support for two output targets:</p>
+      <ul>
+        <li>PostScript (full support).</li>
+        <li>
+          PDF (partial support). Due to the lack of a built-in PostScript interpreter, FOP 
+          can only embed the EPS file into the PDF. Acrobat Reader will not currently display 
+          the EPS (it doesn't have a PostScript interpreter, either) but it will be shown 
+          correctly when you print the PDF on a PostScript-capable printer. PostScript devices 
+          (including GhostScript) will render the EPS correctly.
+        </li>
+      </ul>
+      <p>
+        Other output targets can't be supported at the moment because
+        FOP lacks a PostScript interpreter. Furthermore, FOP is not able
+        to parse the preview bitmaps sometimes contained in EPS files.
+      </p>
+    </section>
+    <section id="jpeg">
+      <title>JPEG</title>
+      <p>FOP native support of JPEG does not include all variants, especially those containing unusual color lookup tables and color profiles.
+If you have trouble with a JPEG image in FOP, try opening it with an image processing program (such as Photoshop or Gimp) and then saving it.
+Specifying 24-bit color output may also help.
+For the PDF and PostScript renderers most JPEG images can be passed through without decompression.
+User reports indicate that grayscale, RGB, and CMYK color-spaces are all rendered properly.
+      </p>
+    </section>
+    <section id="png">
+      <title>PNG</title>
+      <p>If using JAI for PNG support, only RGB and RGBA color-spaces are supported for FOP rendering.</p>
+    </section>
+    <section id="svg">
+      <title>SVG</title>
+      <section id="svg-intro">
+        <title>Introduction</title>
+        <p>FOP uses <link href="#batik">Batik</link> for SVG support.
+This format can be handled as an <code>fo:instream-foreign-object</code> or in a separate
+file referenced with <code>fo:external-graphic</code>.</p>
+      <note>   
+Batik's SVG Rasterizer utility may also be used to convert standalone SVG
+documents into PDF.  For more information please see the
+<link href="http://xml.apache.org/batik/svgrasterizer.html">SVG Rasterizer documentation</link>
+on the Batik site.
+      </note>
+      </section>
+      <section id="svg-pdf-graphics">
+        <title>Placing SVG Graphics into PDF</title>
+        <p>
+The SVG is rendered into PDF by using PDF commands to draw and fill
+lines and curves. This means that the graphical objects created with
+this remain as vector graphics.
+        </p>
+        <p>
+There are a number of SVG things that cannot be converted directly into
+PDF. Parts of the graphic such as effects, patterns and images are inserted
+into the PDF as a raster graphic. The resolution of this graphic may not
+be ideal depending on the FOP dpi (72dpi) and the scaling for that graphic.
+We hope to improve this in the future.</p>
+        <p>
+Currently transparency is not supported in PDF so many svg images that
+contain effects or graphics with transparent areas will not be displayed
+correctly.
+        </p>
+      </section>
+      <section id="svg-pdf-text">
+        <title>Placing SVG Text into PDF</title>
+        <p>If possible, Batik will use normal PDF text when inserting text. It does
+this by checking if the text can be drawn normally and the font is
+supported. This example svg <link href="../dev/svg/text.svg">text.svg</link> /
+<!--link href="../dev/svg/text.pdf"-->text.pdf<!--/link-->
+shows how various types and effects with text are handled.
+Note that tspan and outlined text are not yet implemented.</p>
+        <p>
+Otherwise, text is converted and drawn as a set of shapes by batik, using the stroking text painter.
+This means that a typical character will
+have about 10 curves (each curve consists of at least 20 characters).
+This can make the pdf files large and when the pdf is viewed the
+viewer does not normally draw those fine curves very well (turning on
+Smooth Line Art in the Acrobat preferences will fix this).
+If the text is inserted into the PDF using the inbuilt text commands
+for PDF it will use a single character.
+        </p>
+        <p>Note that because SVG text can be rendered as either text or a vector graphic, you may need to consider settings in your viewer for both.
+The Acrobat viewer has both "smooth line art" and "smooth text" settings that may need to be set for SVG images to be displayed nicely on your screen (see Edit / Preferences / Display).
+This setting will not affect the printing of your document, which should be OK in any case, but will only affect the quality of the screen display.</p>
+      </section>
+      <section id="svg-scaling">
+        <title>Scaling</title>
+        <p>Currently, SVG images are rendered with the dimensions specified <em>in the SVG file</em>, within the viewport specified in the fo:external-graphic element.
+For everything to work properly, the two should be equal.
+The SVG standard leaves this issue as an implementation detail.
+FOP will probably implement a scaling mechanism in the future.</p>
+      </section>
+      <section id="svg-problems">
+        <title>Known Problems</title>
+        <ul>
+          <li>
+soft mask transparency is combined with white so that it looks better
+on pdf 1.3 viewers but this causes the soft mask to be slightly lighter
+or darker on pdf 1.4 viewers
+          </li>
+          <li>
+there is some problem with a gradient inside a pattern causing a pdf
+error when viewed in acrobat 5
+          </li>
+          <li>
+text is not always handled correctly, it may select the wrong font
+especially if characters have multiple fonts in the font list
+          </li>
+          <li>
+more pdf text handling could be implemented
+It could draw the string using the attributed character iterator
+to handle tspans and other simple changes of text.
+          </li>
+          <li>
+JPEG images are not inserted directly into the pdf document
+This area has not been implemented yet since the appropriate
+method in batik is static
+          </li>
+          <li>
+Uniform transparency for images and other svg elements that are converted
+into a raster graphic are not drawn properly in PDF. The image is opaque.
+          </li>
+        </ul>
+      </section>
+    </section>
+    <section id="tiff">
+      <title>TIFF</title>
+      <p>FOP-native TIFF support is limited to PDF and PostScript output only. Also, according to user reports, FOP's native support for TIFF is limited to images with the following characteristics (all must be true for successful rendering):</p>
+      <ul>
+        <li>single channel images (i.e., bi-level and grayscale only)</li>
+        <li>uncompressed images, or images using CCITT T.4, CCITT T.6, or JPEG compression</li>
+        <li>images using white-is-zero encoding in the TIFF PhotometricInterpretation tag</li>
+      </ul>
+      <p><em>JAI:</em> Supports RGB and RGBA only for FOP rendering.</p>
+    </section>
+    <section id="resolution">
+      <title>Graphics Resolution</title>
+      <p>Some bitmapped image file formats store a dots-per-inch (dpi) or other resolution value. Since PDF and most output formats do not have a concept of resolution, but only of absolute image units (i.e. pixels) FOP ignores the resolution values as well. Instead, FOP uses the dimensions of the image as specified in the fo:external-graphic element to render the image:</p>
+      <ul>
+        <li>If no dimensions are given, FOP uses a default value of 72 dpi to compute the graphic's dimensions. For example, suppose a graphic 300 pixels wide and 400 pixels high. FOP will render the graphic at 4.167 inches wide, 5.555 inches high, with an apparent resolution of 72 dpi.</li>
+        <li>If only one dimension is given, FOP by default uses the same aspect ratio to compute the other dimension (to avoid the appearance of stretching). For example, suppose a graphic 300 pixels wide and 400 pixels high, for which content-width = ".5in". FOP will compute the content-height = .667 inches, and will render the graphic at that size, with an apparent resolution of 600 dpi.</li>
+        <li>If both dimensions are given, FOP simply renders the image in that space. For example, suppose a graphic 300 pixels wide and 400 pixels high, for which content-width = "3in" and content-height = "4in". FOP will render the graphic at that size, with an apparent resolution of 100 dpi.</li>
+      </ul>
+      <p>If you need a higher apparent output resolution for bitmapped images, first make sure that at least one dimension of the image is defined in your XSL-FO input. Apart from that, resolution problems are in the image file itself, and must be corrected there: use or create a higher-resolution image file.</p>
+      <note>The explanation above describes only the basic default behavior. There are other attributes of the fo:external-graphic element that can affect the behavior described above.</note>
+    </section>
+    <section id="caching">
+      <title>Image caching</title>
+      <p>
+        FOP caches images between runs. The URL is used as a key to identify images which means that when
+        a particular URL appears again, the image is taken from the cache. If you have a servlet that
+        generates a different image each time it is called with the same URL you need to use a constantly 
+        changing dummy parameter on the URL to avoid caching.
+      </p>
+      <p>
+        The image cache has been improved considerably in the redesigned code. Therefore, a resetCache() method
+        has become unnecessary. If you still experience OutOfMemoryErrors, please notify us.
+      </p>
+    </section>
+  </body>
+</document>
\ No newline at end of file

Propchange: xmlgraphics/site/deploy/fop/0.93/graphics.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: xmlgraphics/site/deploy/fop/0.93/graphics.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Modified: xmlgraphics/site/deploy/fop/0.93/hyphenation.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/hyphenation.html?rev=569118&r1=569117&r2=569118&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/hyphenation.html (original)
+++ xmlgraphics/site/deploy/fop/0.93/hyphenation.html Thu Aug 23 12:00:37 2007
@@ -57,13 +57,13 @@
 <li>
 <a class="base-not-selected" href="../index.html">Home</a>
 </li>
-<li>
-<a class="base-not-selected" href="../0.20.5/index.html">Version 0.20.5</a>
-</li>
 <li class="current">
 <a class="base-selected" href="../0.93/index.html">Version 0.93</a>
 </li>
 <li>
+<a class="base-not-selected" href="../0.94/index.html">Version 0.94</a>
+</li>
+<li>
 <a class="base-not-selected" href="../trunk/index.html">FOP Trunk</a>
 </li>
 <li>
@@ -187,10 +187,20 @@
     |start content
     +-->
 <div id="content">
+<div title="raw XML" class="xmllink">
+<a class="dida" href="hyphenation.xml"><img alt="XML - icon" src="../skin/images/xmldoc.gif" class="skin"><br>
+        XML</a>
+</div>
 <div title="Portable Document Format" class="pdflink">
 <a class="dida" href="hyphenation.pdf"><img alt="PDF -icon" src="../skin/images/pdfdoc.gif" class="skin"><br>
         PDF</a>
 </div>
+<div class="trail">
+<text>Font size:</text> 
+	          &nbsp;<input value="Reset" class="resetfont" title="Reset text" onclick="ndeSetTextSize('reset'); return false;" type="button">      
+	          &nbsp;<input value="-a" class="smallerfont" title="Shrink text" onclick="ndeSetTextSize('decr'); return false;" type="button">
+	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
+</div>
 <h1>Apache FOP: Hyphenation</h1>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -226,7 +236,7 @@
        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 target="_blank" class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">Objects For 
+       the <a class="external" href="http://offo.sourceforge.net/hyphenation/index.html">Objects For 
        Formatting Objects</a> project.</p>
 <div class="note">
 <div class="label">Note</div>
@@ -239,7 +249,7 @@
 <a name="N10034"></a><a name="license-issues"></a>
 <h3 class="underlined_5">License Issues</h3>
 <p>Many of the hyphenation files distributed with TeX and its offspring are
-       licenced under the <a target="_blank" class="fork" href="http://www.latex-project.org/lppl.html">LaTeX
+       licenced under the <a class="external" 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
@@ -258,7 +268,7 @@
 <a name="N10049"></a><a name="sources"></a>
 <h3 class="underlined_5">Sources of Custom Hyphenation Pattern Files</h3>
 <p>The most important source of hyphenation pattern files is the
-       <a target="_blank" class="fork" href="http://www.ctan.org/tex-archive/language/hyphenation/">CTAN TeX
+       <a class="external" href="http://www.ctan.org/tex-archive/language/hyphenation/">CTAN TeX
         Archive</a>.</p>
 <a name="N10058"></a><a name="install"></a>
 <h3 class="underlined_5">Installing Custom Hyphenation Patterns</h3>
@@ -284,8 +294,8 @@
           
 </ul>
           The language and country codes must match the XSL-FO input, which
-          follows <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt">ISO
-          639</a> (languages) and <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt">ISO
+          follows <a class="external" href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt">ISO
+          639</a> (languages) and <a class="external" href="http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt">ISO
           3166</a> (countries). NOTE: The ISO 639/ISO 3166 convention is that
           language names are written in lower case, while country codes are written
           in upper case. FOP does not check whether the language and country specified
@@ -298,13 +308,13 @@
           file(s) accessible to FOP:
           <ul>
             
-<li>Download the precompiled JAR from <a target="_blank" class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">OFFO
+<li>Download the precompiled JAR from <a class="external" href="http://offo.sourceforge.net/hyphenation/index.html">OFFO
             </a> and place it either in the <span class="codefrag">{fop-dir}/lib</span> directory, or 
              in a directory of your choice (and append the full path to the JAR to 
              the environment variable <span class="codefrag">FOP_HYPHENATION_PATH</span>).</li>
             
 <li>Download the desired FOP-compatible hyphenation pattern file(s) from 
-             <a target="_blank" class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">OFFO</a>,
+             <a class="external" href="http://offo.sourceforge.net/hyphenation/index.html">OFFO</a>,
              and/or take your self created hyphenation pattern file(s), 
              <ul>
                 
@@ -352,7 +362,7 @@
 <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 target="_blank" class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">
+     with an existing file and modify it. See <a class="external" 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>
 <div class="warning">
@@ -467,7 +477,7 @@
      online. The original patgen.web source, included in the TeX source distributions,
      contains valuable comments, unfortunately technical details obscure often the
      high level issues. Another important source is
-     <a target="_blank" class="fork" href="http://www.ctan.org/tex-archive/systems/knuth/tex/texbook.tex">The
+     <a class="external" href="http://www.ctan.org/tex-archive/systems/knuth/tex/texbook.tex">The
      TeX Book</a>, appendix H (either read the TeX source, or run it through
      TeX to typeset it). Secondary articles, for example the works by Petr Sojka,
      may also give some much needed insight into problems arising in automated

Modified: xmlgraphics/site/deploy/fop/0.93/hyphenation.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/hyphenation.pdf?rev=569118&r1=569117&r2=569118&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/hyphenation.pdf (original)
+++ xmlgraphics/site/deploy/fop/0.93/hyphenation.pdf Thu Aug 23 12:00:37 2007
@@ -507,8 +507,8 @@
 63 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F3
-/BaseFont /Helvetica-Bold
+/Name /F1
+/BaseFont /Helvetica
 /Encoding /WinAnsiEncoding >>
 endobj
 64 0 obj
@@ -521,15 +521,15 @@
 65 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F6
-/BaseFont /Times-Italic
+/Name /F3
+/BaseFont /Helvetica-Bold
 /Encoding /WinAnsiEncoding >>
 endobj
 66 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F1
-/BaseFont /Helvetica
+/Name /F2
+/BaseFont /Helvetica-Oblique
 /Encoding /WinAnsiEncoding >>
 endobj
 67 0 obj
@@ -542,8 +542,8 @@
 68 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F2
-/BaseFont /Helvetica-Oblique
+/Name /F6
+/BaseFont /Times-Italic
 /Encoding /WinAnsiEncoding >>
 endobj
 69 0 obj
@@ -567,7 +567,7 @@
 endobj
 3 0 obj
 << 
-/Font << /F3 63 0 R /F5 64 0 R /F1 66 0 R /F6 65 0 R /F9 67 0 R /F2 68 0 R /F7 69 0 R >> 
+/Font << /F1 63 0 R /F5 64 0 R /F3 65 0 R /F2 66 0 R /F9 67 0 R /F6 68 0 R /F7 69 0 R >> 
 /ProcSet [ /PDF /ImageC /Text ] >> 
 endobj
 9 0 obj
@@ -677,11 +677,11 @@
 0000020543 00000 n 
 0000020870 00000 n 
 0000021081 00000 n 
-0000021194 00000 n 
-0000021304 00000 n 
-0000021415 00000 n 
-0000021523 00000 n 
-0000021629 00000 n 
+0000021189 00000 n 
+0000021299 00000 n 
+0000021412 00000 n 
+0000021528 00000 n 
+0000021634 00000 n 
 0000021745 00000 n 
 trailer
 <<

Added: xmlgraphics/site/deploy/fop/0.93/hyphenation.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/hyphenation.xml?rev=569118&view=auto
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/hyphenation.xml (added)
+++ xmlgraphics/site/deploy/fop/0.93/hyphenation.xml Thu Aug 23 12:00:37 2007
@@ -0,0 +1,234 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
+<document>
+  <header>
+    <title>Apache FOP: Hyphenation</title>
+    <version>$Revision: 493717 $</version>
+  </header>
+  <body>
+    <section id="support">
+    <title>Hyphenation Support</title>
+    <section id="intro">
+      <title>Introduction</title>
+      <p>FOP uses Liang's hyphenation algorithm, well known from TeX. It needs
+       language specific pattern and other data for operation.</p>
+      <p>Because of <link href="#license-issues">licensing issues</link> (and for 
+       convenience), all hyphenation patterns for FOP are made available through 
+       the <link class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">Objects For 
+       Formatting Objects</link> project.</p>
+      <note>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 <link href="../maillist.html#fop-user">FOP User
+       mailing list</link>.</note>
+    </section>
+    <section id="license-issues">
+      <title>License Issues</title>
+      <p>Many of the hyphenation files distributed with TeX and its offspring are
+       licenced under the <link class="fork" href="http://www.latex-project.org/lppl.html">LaTeX
+       Project Public License (LPPL)</link>, 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>
+      <p>Although Apache FOP cannot redistribute hyphenation pattern files that do
+       not conform with its license scheme, that does not necessarily prevent users
+       from using such hyphenation patterns with FOP. However, it does place on
+       the user the responsibility for determining whether the user can rightly use
+       such hyphenation patterns under the hyphenation pattern license.</p>
+      <warning>The user is responsible to settle license issues for hyphenation
+       pattern files that are obtained from non-Apache sources.</warning>
+    </section>
+    <section id="sources">
+      <title>Sources of Custom Hyphenation Pattern Files</title>
+      <p>The most important source of hyphenation pattern files is the
+       <link class="fork" href="http://www.ctan.org/tex-archive/language/hyphenation/">CTAN TeX
+        Archive</link>.</p>
+    </section>
+    <section id="install">
+      <title>Installing Custom Hyphenation Patterns</title>
+      <p>To install a custom hyphenation pattern for use with FOP:</p>
+      <ol>
+        <li>Convert the TeX hyphenation pattern file to the FOP format. The FOP
+         format is an xml file conforming to the DTD found at
+         <code>{fop-dir}/hyph/hyphenation.dtd</code>.</li>
+        <li>Name this new file following this schema:
+         <code>languageCode_countryCode.xml</code>. The country code is
+          optional, and should be used only if needed. For example:
+          <ul>
+            <li><code>en_US.xml</code> would be the file name for American
+             English hyphenation patterns.</li>
+            <li><code>it.xml</code> would be the file name for Italian
+             hyphenation patterns.</li>
+          </ul>
+          The language and country codes must match the XSL-FO input, which
+          follows <link href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt">ISO
+          639</link> (languages) and <link href="http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt">ISO
+          3166</link> (countries). NOTE: The ISO 639/ISO 3166 convention is that
+          language names are written in lower case, while country codes are written
+          in upper case. FOP does not check whether the language and country specified
+          in the FO source are actually from the current standard, but it relies
+          on it being two letter strings in a few places. So you can make up your
+          own codes for custom hyphenation patterns, but they should be two
+          letter strings too (patches for proper handling extensions are welcome)</li>
+        <li>There are basically three ways to make the FOP-compatible hyphenation pattern 
+          file(s) accessible to FOP:
+          <ul>
+            <li>Download the precompiled JAR from <link class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">OFFO
+            </link> and place it either in the <code>{fop-dir}/lib</code> directory, or 
+             in a directory of your choice (and append the full path to the JAR to 
+             the environment variable <code>FOP_HYPHENATION_PATH</code>).</li>
+            <li>Download the desired FOP-compatible hyphenation pattern file(s) from 
+             <link class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">OFFO</link>,
+             and/or take your self created hyphenation pattern file(s), 
+             <ul>
+                <li>place them in the directory <code>{fop-dir}/hyph</code>, </li>
+                <li>or place them in a directory of your choice and set the Ant variable
+                <code>user.hyph.dir</code> to point to that directory (in
+                <code>build-local.properties</code>),</li>
+             </ul>
+             and run Ant with build target
+             <code>jar-hyphenation</code>. This will create a JAR containing the 
+             compiled patterns in <code>{fop-dir}/build</code> that will be added to the 
+             classpath on the next run.
+             (When FOP is built from scratch, and there are pattern source file(s) 
+             present in the directory pointed to by the
+             <code>user.hyph.dir</code> variable, this JAR will automatically 
+             be created from the supplied pattern(s)).</li>
+            <li>Put the pattern source file(s) into a directory of your choice and 
+             configure FOP to look for custom patterns in this directory, by setting the
+             <link href="configuration.html">&lt;hyphenation-base&gt;</link> 
+             configuration option.</li>
+          </ul>
+        </li>
+      </ol>
+      <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 
+        <link href="configuration.html#hyphenation-dir">&lt;hyphenation-dir&gt;</link> 
+        configuration option programmatically (option 3).
+      </warning>
+    </section>
+  </section>
+  <section id="patterns">
+    <title>Hyphenation Patterns</title>
+    <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 <link class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">
+     OFFO's Hyphenation page</link> for examples. 
+     Here is a brief explanation of the contents of FOP's hyphenation patterns:</p>
+    <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
+     <link href="../maillist.html#fop-user">FOP User mailing list</link>, either
+     confirming their accuracy, or raising specific problems that we can
+     address.</warning>
+    <ul>
+      <li>The root of the pattern file is the &lt;hyphenation-info&gt; element.</li>
+      <li>&lt;hyphen-char&gt;: its attribute "value" contains the character signalling
+       a hyphen in the &lt;exceptions&gt; section. It has nothing to do with the
+       hyphenation character used in FOP, use the XSLFO hyphenation-character
+       property for defining the hyphenation character there. At some points
+       a dash U+002D is hardwired in the code, so you'd better use this too
+       (patches to rectify the situation are welcome). There is no default,
+       if you declare exceptions with hyphenations, you must declare the
+       hyphen-char too.</li>
+      <li>&lt;hyphen-min&gt; contains two attributes:
+        <ul>
+          <li>before: the minimum number of characters in a word allowed to exist
+           on a line immediately preceding a hyphenated word-break.</li>
+          <li>after: the minimum number of characters in a word allowed to exist
+           on a line immediately after a hyphenated word-break.</li>
+        </ul>
+        This element is unused and not even read. It should be considered a
+        documentation for parameters used during pattern generation.
+      </li>
+      <li>&lt;classes&gt; contains whitespace-separated character sets. The members
+       of each set should be treated as equivalent for purposes of hyphenation,
+       usually upper and lower case of the same character. The first character
+       of the set is the canonical character, the patterns and exceptions
+       should only contain these canonical representation characters (except
+       digits for weight, the period (.) as word delimiter in the patterns and
+       the hyphen char in exceptions, of course).</li>
+      <li>&lt;exceptions&gt; contains whitespace-separated words, each of which
+       has either explicit hyphen characters to denote acceptable breakage
+       points, or no hyphen characters, to indicate that this word should
+       never be hyphenated, or contain explicit &lt;hyp&gt; elements for specifying
+       changes of spelling due to hyphenation (like backen -&gt; bak-ken or
+       Stoffarbe -&gt; Stoff-farbe in the old german spelling). Exceptions override
+       the patterns described below. Explicit &lt;hyp&gt; declarations don't work
+       yet (patches welcome). Exceptions are generally a bit brittle, test
+       carefully.</li>
+      <li>&lt;patterns&gt; includes whitespace-separated patterns, which are what
+       drive most hyphenation decisions. The characters in these patterns are
+       explained as follows:
+        <ul>
+          <li>non-numeric characters represent characters in a sub-word to be
+           evaluated</li>
+          <li>the period character (.) represents a word boundary, i.e. either
+           the beginning or ending of a word</li>
+          <li>numeric characters represent a scoring system for indicating the
+           acceptability of a hyphen in this location. Odd numbers represent an
+           acceptable location for a hyphen, with higher values overriding lower
+           inhibiting values. Even numbers indicate an unacceptable location, with
+           higher values overriding lower values indicating an acceptable position.
+           A value of zero (inhibiting) is implied when there is no number present.
+           Generally patterns are constructed so that valuse greater than 4 are rare.
+           Due to a bug currently patterns with values of 8 and greater don't
+           have an effect, so don't wonder.</li>
+        </ul>
+        Here are some examples from the English patterns file:
+        <ul>
+          <li>Knuth (<em>The TeXBook</em>, Appendix H) uses the example <strong>hach4</strong>, which indicates that it is extremely undesirable to place a hyphen after the substring "hach", for example in the word "toothach-es".</li>
+          <li><strong>.leg5e</strong> indicates that "leg-e", when it occurs at the beginning of a word, is a very good place to place a hyphen, if one is needed. Words like "leg-end" and "leg-er-de-main" fit this pattern.</li>
+        </ul>
+        Note that the algorithm that uses this data searches for each of the word's substrings in the patterns, and chooses the <em>highest</em> value found for letter combination.
+      </li>
+    </ul>
+    <p>If you want to convert a TeX hyphenation pattern file, you have to undo
+     the TeX encoding for non-ASCII text. FOP uses Unicode, and the patterns
+     must be proper Unicode too. You should be aware of the XML encoding issues,
+     preferably use a good Unicode editor.</p>
+    <p>Note that FOP does not do Unicode character normalization. If you use
+     combining chars for accents and other character decorations, you must
+     declare character classes for them, and use the same sequence of base character
+     and combining marks in the XSLFO source, otherwise the pattern wouldn't match.
+     Fortunately, Unicode provides precomposed characters for all important cases
+     in common languages, until now nobody run seriously into this issue. Some dead
+     languages and dialects, especially ancient ones, may pose a real problem
+     though.</p>
+    <p>If you want to generate your own patterns, an open-source utility called
+     patgen is available on many Unix/Linux distributions and every TeX
+     distribution which can be used to assist in
+     creating pattern files from dictionaries. Pattern creation for languages like
+     english or german is an art. If you can, read Frank Liang's original paper
+     "Word Hy-phen-a-tion by Com-pu-ter" (yes, with hyphens). It is not available
+     online. The original patgen.web source, included in the TeX source distributions,
+     contains valuable comments, unfortunately technical details obscure often the
+     high level issues. Another important source is
+     <link class="fork" href="http://www.ctan.org/tex-archive/systems/knuth/tex/texbook.tex">The
+     TeX Book</link>, appendix H (either read the TeX source, or run it through
+     TeX to typeset it). Secondary articles, for example the works by Petr Sojka,
+     may also give some much needed insight into problems arising in automated
+     hyphenation.</p>
+  </section>
+  </body>
+</document>
\ No newline at end of file

Propchange: xmlgraphics/site/deploy/fop/0.93/hyphenation.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: xmlgraphics/site/deploy/fop/0.93/hyphenation.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Modified: xmlgraphics/site/deploy/fop/0.93/index.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/index.html?rev=569118&r1=569117&r2=569118&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/index.html (original)
+++ xmlgraphics/site/deploy/fop/0.93/index.html Thu Aug 23 12:00:37 2007
@@ -57,13 +57,13 @@
 <li>
 <a class="base-not-selected" href="../index.html">Home</a>
 </li>
-<li>
-<a class="base-not-selected" href="../0.20.5/index.html">Version 0.20.5</a>
-</li>
 <li class="current">
 <a class="base-selected" href="../0.93/index.html">Version 0.93</a>
 </li>
 <li>
+<a class="base-not-selected" href="../0.94/index.html">Version 0.94</a>
+</li>
+<li>
 <a class="base-not-selected" href="../trunk/index.html">FOP Trunk</a>
 </li>
 <li>
@@ -190,9 +190,19 @@
     |start content
     +-->
 <div id="content">
+<div title="raw XML" class="xmllink">
+<a class="dida" href="index.xml"><img alt="XML - icon" src="../skin/images/xmldoc.gif" class="skin"><br>
+        XML</a>
+</div>
 <div title="Portable Document Format" class="pdflink">
 <a class="dida" href="index.pdf"><img alt="PDF -icon" src="../skin/images/pdfdoc.gif" class="skin"><br>
         PDF</a>
+</div>
+<div class="trail">
+<text>Font size:</text> 
+	          &nbsp;<input value="Reset" class="resetfont" title="Reset text" onclick="ndeSetTextSize('reset'); return false;" type="button">      
+	          &nbsp;<input value="-a" class="smallerfont" title="Shrink text" onclick="ndeSetTextSize('decr'); return false;" type="button">
+	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
 </div>
 <h1>Apache FOP Version 0.93</h1>
 <div id="minitoc-area">

Modified: xmlgraphics/site/deploy/fop/0.93/index.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/index.pdf?rev=569118&r1=569117&r2=569118&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/index.pdf (original)
+++ xmlgraphics/site/deploy/fop/0.93/index.pdf Thu Aug 23 12:00:37 2007
@@ -198,8 +198,8 @@
 29 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F3
-/BaseFont /Helvetica-Bold
+/Name /F1
+/BaseFont /Helvetica
 /Encoding /WinAnsiEncoding >>
 endobj
 30 0 obj
@@ -212,8 +212,8 @@
 31 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F1
-/BaseFont /Helvetica
+/Name /F3
+/BaseFont /Helvetica-Bold
 /Encoding /WinAnsiEncoding >>
 endobj
 32 0 obj
@@ -244,7 +244,7 @@
 endobj
 3 0 obj
 << 
-/Font << /F3 29 0 R /F5 30 0 R /F1 31 0 R /F2 32 0 R /F7 33 0 R >> 
+/Font << /F1 29 0 R /F5 30 0 R /F3 31 0 R /F2 32 0 R /F7 33 0 R >> 
 /ProcSet [ /PDF /ImageC /Text ] >> 
 endobj
 9 0 obj
@@ -302,8 +302,8 @@
 0000004559 00000 n 
 0000004859 00000 n 
 0000004999 00000 n 
-0000005112 00000 n 
-0000005222 00000 n 
+0000005107 00000 n 
+0000005217 00000 n 
 0000005330 00000 n 
 0000005446 00000 n 
 trailer

Added: xmlgraphics/site/deploy/fop/0.93/index.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/index.xml?rev=569118&view=auto
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/index.xml (added)
+++ xmlgraphics/site/deploy/fop/0.93/index.xml Thu Aug 23 12:00:37 2007
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="ISO-8859-1"?><!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+--><!-- $Id$ --><!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "document-v13.dtd">
+<document>
+  <header>
+    <title>Apache FOP Version 0.93</title>
+    <version>$Revision: 201586 $</version>
+  </header>
+  <body>
+    <section id="intro">
+      <title>Introduction</title>
+      <p>
+        The Apache FOP team is proud to present to you this production quality release. It has taken
+        over three years to get this far and over two years without a new release from the FOP
+        project. We're still in the process of adding new features. We welcome any feedback you
+        might have and even more, any other form of help to get the project forward.
+      </p>
+      <p>
+        This fourth release contains many bug fix release and new features compared
+        to 0.92beta. To see what has changed since the last release, please visit the 
+        <link href="changes_0.93.html">Changes Page</link> and the <link href="releaseNotes_0.93.html">Release Notes</link>.
+      </p>
+    </section>
+    <section id="upgrading">
+      <title>Upgrading from an earlier version</title>
+      <p>
+        If you're upgrading to this version from an earlier version of FOP, please read the 
+        information contained on the <link href="upgrading.html">Upgrading page</link>!
+      </p>
+    </section>
+    <section id="download">
+      <title>Download</title>
+      <p>
+        To download this version, please visit the <link href="../download.html">download page</link>.
+      </p>
+    </section>
+  </body>
+</document>
\ No newline at end of file

Propchange: xmlgraphics/site/deploy/fop/0.93/index.xml
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: xmlgraphics/site/deploy/fop/0.93/index.xml
------------------------------------------------------------------------------
    svn:keywords = Id

Modified: xmlgraphics/site/deploy/fop/0.93/intermediate.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/intermediate.html?rev=569118&r1=569117&r2=569118&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/intermediate.html (original)
+++ xmlgraphics/site/deploy/fop/0.93/intermediate.html Thu Aug 23 12:00:37 2007
@@ -57,13 +57,13 @@
 <li>
 <a class="base-not-selected" href="../index.html">Home</a>
 </li>
-<li>
-<a class="base-not-selected" href="../0.20.5/index.html">Version 0.20.5</a>
-</li>
 <li class="current">
 <a class="base-selected" href="../0.93/index.html">Version 0.93</a>
 </li>
 <li>
+<a class="base-not-selected" href="../0.94/index.html">Version 0.94</a>
+</li>
+<li>
 <a class="base-not-selected" href="../trunk/index.html">FOP Trunk</a>
 </li>
 <li>
@@ -187,10 +187,20 @@
     |start content
     +-->
 <div id="content">
+<div title="raw XML" class="xmllink">
+<a class="dida" href="intermediate.xml"><img alt="XML - icon" src="../skin/images/xmldoc.gif" class="skin"><br>
+        XML</a>
+</div>
 <div title="Portable Document Format" class="pdflink">
 <a class="dida" href="intermediate.pdf"><img alt="PDF -icon" src="../skin/images/pdfdoc.gif" class="skin"><br>
         PDF</a>
 </div>
+<div class="trail">
+<text>Font size:</text> 
+	          &nbsp;<input value="Reset" class="resetfont" title="Reset text" onclick="ndeSetTextSize('reset'); return false;" type="button">      
+	          &nbsp;<input value="-a" class="smallerfont" title="Shrink text" onclick="ndeSetTextSize('decr'); return false;" type="button">
+	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr'); return false;" type="button">
+</div>
 <h1>Intermediate Format</h1>
 <div id="minitoc-area">
 <ul class="minitoc">
@@ -228,7 +238,7 @@
 <p>
         The intermediate format (IF) is a proprietary XML format that represents the area tree 
         generated by the layout engine. The area tree is conceptually defined in the 
-        <a href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting">XSL-FO specification in chapter 1.1.2</a>.
+        <a class="external" href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting">XSL-FO specification in chapter 1.1.2</a>.
         The IF can be generated through the area tree XML Renderer (the XMLRenderer).
       </p>
 <p>
@@ -261,7 +271,7 @@
         found in the org.apache.fop.area package. The pages retrieved from the IF file are added to an
         AreaTreeModel instance from where they are normally rendered using one of the available Renderer
         implementations. You can find examples for the IF processing in the 
-        <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/"><span class="codefrag">examples/embedding</span></a>
+        <a class="external" href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/"><span class="codefrag">examples/embedding</span></a>
         directory in the FOP distribution
       </p>
 <p>
@@ -311,7 +321,7 @@
 <h3 class="underlined_5">Concatenating Documents</h3>
 <p>
           This initial example is obviously not very useful. It would be faster to create the PDF file 
-          directly. As the <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/ExampleConcat.java">ExampleConcat.java</a>
+          directly. As the <a class="external" href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/ExampleConcat.java">ExampleConcat.java</a>
           example shows you can easily parse multiple IF files in a row and add the parsed pages to the
           same AreaTreeModel instance which essentially concatenates all the input document to one single
           output document.

Modified: xmlgraphics/site/deploy/fop/0.93/intermediate.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/0.93/intermediate.pdf?rev=569118&r1=569117&r2=569118&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/0.93/intermediate.pdf (original)
+++ xmlgraphics/site/deploy/fop/0.93/intermediate.pdf Thu Aug 23 12:00:37 2007
@@ -337,8 +337,8 @@
 46 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F3
-/BaseFont /Helvetica-Bold
+/Name /F1
+/BaseFont /Helvetica
 /Encoding /WinAnsiEncoding >>
 endobj
 47 0 obj
@@ -351,22 +351,22 @@
 48 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F1
-/BaseFont /Helvetica
+/Name /F3
+/BaseFont /Helvetica-Bold
 /Encoding /WinAnsiEncoding >>
 endobj
 49 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F9
-/BaseFont /Courier
+/Name /F2
+/BaseFont /Helvetica-Oblique
 /Encoding /WinAnsiEncoding >>
 endobj
 50 0 obj
 << /Type /Font
 /Subtype /Type1
-/Name /F2
-/BaseFont /Helvetica-Oblique
+/Name /F9
+/BaseFont /Courier
 /Encoding /WinAnsiEncoding >>
 endobj
 51 0 obj
@@ -390,7 +390,7 @@
 endobj
 3 0 obj
 << 
-/Font << /F3 46 0 R /F5 47 0 R /F1 48 0 R /F9 49 0 R /F2 50 0 R /F7 51 0 R >> 
+/Font << /F1 46 0 R /F5 47 0 R /F3 48 0 R /F2 49 0 R /F9 50 0 R /F7 51 0 R >> 
 /ProcSet [ /PDF /ImageC /Text ] >> 
 endobj
 9 0 obj
@@ -477,10 +477,10 @@
 0000012313 00000 n 
 0000012542 00000 n 
 0000012715 00000 n 
-0000012828 00000 n 
-0000012938 00000 n 
+0000012823 00000 n 
+0000012933 00000 n 
 0000013046 00000 n 
-0000013152 00000 n 
+0000013162 00000 n 
 0000013268 00000 n 
 trailer
 <<



---------------------------------------------------------------------
Apache XML Graphics Project URL: http://xmlgraphics.apache.org/
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message