xml-general-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From je...@apache.org
Subject cvs commit: xml-site/targets/fop/dev conventions.html conventions.pdf rtflib.html rtflib.pdf
Date Thu, 10 Jul 2003 18:47:18 GMT
jefft       2003/07/10 11:47:18

  Modified:    targets/fop anttask.html bugs.html changes.html
                        compiling.html compliance.html configuration.html
                        configuration.pdf download.html download.pdf
                        embedding.html examples.html extensions.html
                        faq.html fo.html fonts.html fonts.pdf gethelp.html
                        graphics.html graphics.pdf index.html license.html
                        logocontest.html maillist.html maillist.pdf
                        news.html news.pdf output.html pdfencryption.html
                        relnotes.html resources.html running.html
                        servlets.html status.html team.html todo.html
               targets/fop/design/alt.design FOPropertySets.html
                        FoXMLEvent.html SyncedFoXmlEventsBuffer.html
                        XMLNamespaces.html codedisplay.js
               targets/fop/design/alt.design/properties
                        AbstractPropertyValue.html FOAttributes.html
                        PropNames.html Property.html PropertyConsts.html
                        PropertyParser.html PropertySets.html
                        PropertyTokenizer.html PropertyValue.html
                        PropertyValueList.html ShorthandPropSets.html
                        codedisplay.js
               targets/fop/dev conventions.html conventions.pdf rtflib.html
                        rtflib.pdf
  Added:       targets/fop hyphenation.html hyphenation.pdf
  Log:
  Automatic publish at Thu Jul 10 20:47:15 CEST 2003 from http://forrestbot.cocoondev.org.
  
  Revision  Changes    Path
  1.10      +4 -0      xml-site/targets/fop/anttask.html
  
  Index: anttask.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/anttask.html,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- anttask.html	30 May 2003 18:37:30 -0000	1.9
  +++ anttask.html	10 Jul 2003 18:47:12 -0000	1.10
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.32      +4 -0      xml-site/targets/fop/bugs.html
  
  Index: bugs.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/bugs.html,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- bugs.html	30 May 2003 18:37:30 -0000	1.31
  +++ bugs.html	10 Jul 2003 18:47:12 -0000	1.32
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.20      +4 -0      xml-site/targets/fop/changes.html
  
  Index: changes.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/changes.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- changes.html	21 Jun 2003 14:47:42 -0000	1.19
  +++ changes.html	10 Jul 2003 18:47:12 -0000	1.20
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.38      +4 -0      xml-site/targets/fop/compiling.html
  
  Index: compiling.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/compiling.html,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- compiling.html	21 Jun 2003 14:47:42 -0000	1.37
  +++ compiling.html	10 Jul 2003 18:47:12 -0000	1.38
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.19      +4 -0      xml-site/targets/fop/compliance.html
  
  Index: compliance.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/compliance.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- compliance.html	7 Jul 2003 04:45:16 -0000	1.18
  +++ compliance.html	10 Jul 2003 18:47:12 -0000	1.19
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.16      +118 -84   xml-site/targets/fop/configuration.html
  
  Index: configuration.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/configuration.html,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- configuration.html	30 May 2003 18:37:33 -0000	1.15
  +++ configuration.html	10 Jul 2003 18:47:12 -0000	1.16
  @@ -2,7 +2,7 @@
   <html>
   <head>
   <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  -<title>Configuration</title>
  +<title>FOP: Configuration</title>
   <link type="text/css" href="skin/page.css" rel="stylesheet">
   </head>
   <body text="#000000" bgcolor="#FFFFFF">
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  @@ -297,7 +301,7 @@
   <table class="title" summary="">
   <tr>
   <td valign="middle">
  -<h1>Configuration</h1>
  +<h1>FOP: Configuration</h1>
   </td><td nowrap="nowrap" width="80" align="center"><a class="dida" href="configuration.pdf"><img alt="printer" src="skin/images/printer.gif" border="0"><br>
             print-friendly<br>
             PDF</a></td>
  @@ -305,114 +309,144 @@
   </table>
   <ul class="minitoc">
   <li>
  -<a href="#general">How to configure FOP</a>
  +<a href="#general">Configuration File Basics</a>
  +<ul class="minitoc">
  +<li>
  +<a href="#general-entries">Creating Entries</a>
  +</li>
  +<li>
  +<a href="#general-available">Making Configuration Available to FOP</a>
  +</li>
  +</ul>
  +</li>
  +<li>
  +<a href="#summary-key-value">Summary of Key-Value Configuration Options</a>
   </li>
   <li>
  -<a href="#hyphenation">Setting up hyphenation</a>
  +<a href="#detail-key-value">Detail for Key-Value Configuration Options</a>
   <ul class="minitoc">
   <li>
  -<a href="#hyphenation-sources">Places to find TeX hyphenation pattern files</a>
  +<a href="#hyphenation-dir">hyphenation-dir (URL, none)</a>
  +</li>
  +<li>
  +<a href="#strokeSVGText">strokeSVGText (boolean, True)</a>
   </li>
   </ul>
   </li>
  +<li>
  +<a href="#fonts">Fonts</a>
  +</li>
   </ul>
     
   <a name="N101BE"></a><a name="general"></a>
  -<h3>How to configure FOP</h3>
  +<h3>Configuration File Basics</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>The FOP configuration file is an XML file containing a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use.</p>
  +<p>The easiest way to get started using a FOP configuration file is to copy the sample found at <span class="codefrag">{fop-dir}/conf/userconfig.xml</span> to a location of your choice, and then to edit it according to your needs.
  +It contains templates for the various configuration options, most of which are commented out. Remove the comments and change the settings for entries that you wish to use.
  +Be sure to follow any instructions, including comments which specify the value range.
  +Also, since the configuration file is XML, be sure to keep it well-formed.</p>
  +<div class="frame note">
  +<div class="label">Note</div>
  +<div class="content">Do <strong>not</strong> change <span class="codefrag">{fop-dir}/conf/config.xml</span> or use it as the basis for your configuration file. It has an entirely different purpose.</div>
  +</div>
  +<a name="N101D6"></a><a name="general-entries"></a>
  +<h4>Creating Entries</h4>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>The general structure of the configuration file is a series of &lt;entry&gt; tags, each containing a &lt;key&gt; and a &lt;value&gt;. (Fonts use a different format). Here is an example:</p>
  +<pre class="code">&lt;entry&gt;
  +  &lt;key&gt;strokeSVGText&lt;/key&gt;
  +  &lt;value&gt;false&lt;/value&gt;
  +&lt;/entry&gt;</pre>
  +</div>
  +<a name="N101E4"></a><a name="general-available"></a>
  +<h4>Making Configuration Available to FOP</h4>
   <div style="margin-left: 0 ; border: 2px">
  -<p>In the directory {fop-dir}/conf you will find two configuration files. One of them,
  -       config.xml, is only intended for FOP developers, who want to add new default values
  -       to some FOP feature. Don't change this file. For user configuration there is a file called
  -       userconfig.xml. It contains templates for all settings a user can change. Most of them are
  -       commented out. Uncomment the entry you want to set and change the value according to
  -       your wishes. Please regard any comments which specify the value range. And, well, the
  -       configuration files are xml files, so keep them at least well-formed. ;-)
  -    </p>
  -<p>The file userconfig.xml is not read automatically, but the user must specify its use on
  -       the command line. See <a href="running.html">Running FOP</a>
  -       or <a href="embedding.html">Embedding FOP</a> for details.
  -    </p>
  +<p>After creating your configuration file, you must tell FOP how to find it:</p>
  +<ul>
  +        
  +<li>If running FOP from the command-line, see the "-c" command-line option in <a href="running.html">Running FOP</a>.</li>
  +        
  +<li>If running FOP as an embedded application, see <a href="embedding.html#config-external">FOP: Embedding, Using a Configuration File</a>.</li>
  +      
  +</ul>
  +<p>See <a href="embedding.html#config-internal">Setting the Configuration Programmatically</a> for instructions on how to do so in an embedded environment.</p>
  +</div>
   </div>
     
  -<a name="N101D3"></a><a name="hyphenation"></a>
  -<h3>Setting up hyphenation</h3>
  +<a name="N10207"></a><a name="summary-key-value"></a>
  +<h3>Summary of Key-Value Configuration Options</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<p>
  -      FOP comes already with some hyphenation patterns. If you need a hyphenation pattern
  -      which isn't included in the distribution, do the following:
  -    </p>
  -<ol>
  +<table class="ForrestTable" cellspacing="1" cellpadding="4">
         
  -<li>
  -Get the TeX hyphenation pattern file and turn it into an xml file which
  -conforms to the hyphenation.dtd in the subdirectory {fop-dir}/src/hyph.
  -      </li>
  +<tr>
  +        
  +<th colspan="1" rowspan="1">Option (key)</th>
  +        <th colspan="1" rowspan="1">Data Type (for the value)</th>
  +        <th colspan="1" rowspan="1">Default Value</th>
         
  -<li>
  -Name this new file following this schema: <span class="codefrag">languageCode_countryCode.xml</span>. If
  -you don't need a country code, leave it out, e.g. the file name for an American
  -english hyphenation pattern would look like this: <span class="codefrag">en_US.xml</span>. For an Italian 
  -file: <span class="codefrag">it.xml</span>. Language and country codes must be the same as in XSL-FO, that
  -is follow
  -<a href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt">ISO 639</a>
  -and
  -<a href="http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt">ISO 3166</a>
  -respectively. NOTE: The ISO 639/ISO 3166 convention is that language names are
  -written in lower case, while country codes are written in upper case.
  -      </li>
  +</tr>
         
  -<li>
  -If you have built your new hyphenation pattern file successfully there are
  -two ways to make it accessible to FOP.
  -        <ul>
  -          
  -<li>
  -Put this new file into the directory {fop-dir}/src/hyph and rebuild FOP. The file will
  -be picked up and added to fop.jar.
  -          </li>
  -          
  -<li>
  -Put the file into a directory of your choice and specify this directory
  -in the userconfig.xml in the entry &lt;hyphenation-dir&gt;.
  -          </li>
  +<tr>
           
  -</ul>
  +<td colspan="1" rowspan="1">baseDir</td>
  +        <td colspan="1" rowspan="1">URL</td>
  +        <td colspan="1" rowspan="1">directory containing the input FO file</td>
         
  -</li>
  -    
  -</ol>
  -<a name="N10202"></a><a name="hyphenation-sources"></a>
  -<h4>Places to find TeX hyphenation pattern files</h4>
  -<div style="margin-left: 0 ; border: 2px">
  -<p>
  -        The most important place to find hyphenation pattern file is the CTAN TeX Archive:
  -      </p>
  -<ul>
  +</tr>
  +      
  +<tr>
           
  -<li>
  -<a target="_blank" href="http://www.ctan.org/tex-archive/language/hyphenation/">CTAN TeX Archive</a>
  -</li>
  +<td colspan="1" rowspan="1">fontBaseDir</td>
  +        <td colspan="1" rowspan="1">URL</td>
  +        <td colspan="1" rowspan="1">value of baseDir</td>
         
  -</ul>
  +</tr>
  +      
  +<tr>
  +        
  +<td colspan="1" rowspan="1">hyphenation-dir</td>
  +        <td colspan="1" rowspan="1">URL</td>
  +        <td colspan="1" rowspan="1">None. This is for custom hyphenation patterns.</td>
  +      
  +</tr>
  +      
  +<tr>
  +        
  +<td colspan="1" rowspan="1"><a href="#svg-strokeSVGText">strokeSVGText</a></td>
  +        <td colspan="1" rowspan="1">Boolean</td>
  +        <td colspan="1" rowspan="1">True</td>
  +      
  +</tr>
  +    
  +</table>
   </div>
  -<div class="frame warning">
  -<div class="label">Warning</div>
  -<div class="content">
  -      You have to carefully check license issues when using hyphenation
  -      pattern files from other places. The licenses of the files found
  -      on the Internet are not always clear.
  -    </div>
  +  
  +<a name="N1026D"></a><a name="detail-key-value"></a>
  +<h3>Detail for Key-Value Configuration Options</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>The sections below provide detailed information for configuration options that are not self-explanatory. The parenthetical information after each key name indicates (Data Type, Default).</p>
  +<a name="N10276"></a><a name="hyphenation-dir"></a>
  +<h4>hyphenation-dir (URL, none)</h4>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>Use this entry to indicate a directory containing custom hyphenation files (if any).
  +See <a href="hyphenation.html">FOP: Hyphenation</a> for more information on creating and modifying hyphenation within FOP.</p>
   </div>
  +<a name="N10284"></a><a name="strokeSVGText"></a>
  +<h4>strokeSVGText (boolean, True)</h4>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>In some cases, some text in SVG documents is converted to graphical shapes instead of retaining its character as text. To force all text to be rendered as text, set strokeSVGText = false. For a discussion of this issue, see <a href="graphics.html#svg-pdf-text">FOP: Graphics, Placing SVG Text into PDF</a>.</p>
   <div class="frame note">
   <div class="label">Note</div>
  -<div class="content">
  -      Most of the files published in the CTAN Archive are licenced under the 
  -      <a target="_blank" href="http://www.latex-project.org/lppl.html">LaTeX Project Public License (LPPL)</a>.
  -      The Apache Foundation can't redistribute files under this license. If you want to use such
  -      a file you have to decide for yourself if you can use (and possibly distribute) the file under 
  -      these conditions.
  -    </div>
  +<div class="content">strokeSVGText is currently only effective in the PDF renderer.</div>
   </div>
  +</div>
  +</div>
  +  
  +<a name="N10296"></a><a name="fonts"></a>
  +<h3>Fonts</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>Font configuration information is included in the FOP configuration file, but is documented at <a href="fonts.html">FOP: Fonts</a>. Note especially the section entitled <a href="fonts.html#register">Register Fonts with FOP</a>.</p>
   </div>
     
   </div>
  
  
  
  1.7       +539 -127  xml-site/targets/fop/configuration.pdf
  
  	<<Binary file>>
  
  
  1.38      +13 -2     xml-site/targets/fop/download.html
  
  Index: download.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/download.html,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- download.html	30 May 2003 18:37:33 -0000	1.37
  +++ download.html	10 Jul 2003 18:47:12 -0000	1.38
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  @@ -335,10 +339,17 @@
   <h3>Binary Download</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Binary distributions include "-bin" in their names, and can be downloaded from the <a href="http://xml.apache.org/dist/fop/">FOP Distribution</a> directory.
  -</p>
  +    </p>
  +<div class="frame note">
  +<div class="label">Note</div>
  +<div class="content">We're in the process of moving the download location. Please download the
  +      latest release candidate from a
  +      <a href="http://www.apache.org/dyn/closer.cgi/xml/fop">mirror</a>.
  +    </div>
  +</div>
   </div>
     
  -<a name="N101E2"></a><a name="source"></a>
  +<a name="N101E9"></a><a name="source"></a>
   <h3>Source Download</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>You must first determine which of the two main development branches you wish to download, "maintenance" or "redesign".
  
  
  
  1.10      +207 -194  xml-site/targets/fop/download.pdf
  
  	<<Binary file>>
  
  
  1.41      +4 -0      xml-site/targets/fop/embedding.html
  
  Index: embedding.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/embedding.html,v
  retrieving revision 1.40
  retrieving revision 1.41
  diff -u -r1.40 -r1.41
  --- embedding.html	21 Jun 2003 14:47:42 -0000	1.40
  +++ embedding.html	10 Jul 2003 18:47:12 -0000	1.41
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.33      +4 -0      xml-site/targets/fop/examples.html
  
  Index: examples.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/examples.html,v
  retrieving revision 1.32
  retrieving revision 1.33
  diff -u -r1.32 -r1.33
  --- examples.html	21 Jun 2003 14:47:42 -0000	1.32
  +++ examples.html	10 Jul 2003 18:47:13 -0000	1.33
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.27      +4 -0      xml-site/targets/fop/extensions.html
  
  Index: extensions.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/extensions.html,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- extensions.html	30 May 2003 18:37:33 -0000	1.26
  +++ extensions.html	10 Jul 2003 18:47:13 -0000	1.27
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <span class="sel"><font color="#ffcc00">Extensions</font></span>
   </li>
           
  
  
  
  1.32      +4 -0      xml-site/targets/fop/faq.html
  
  Index: faq.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/faq.html,v
  retrieving revision 1.31
  retrieving revision 1.32
  diff -u -r1.31 -r1.32
  --- faq.html	21 Jun 2003 14:47:42 -0000	1.31
  +++ faq.html	10 Jul 2003 18:47:13 -0000	1.32
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.8       +4 -0      xml-site/targets/fop/fo.html
  
  Index: fo.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/fo.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- fo.html	21 Jun 2003 14:47:44 -0000	1.7
  +++ fo.html	10 Jul 2003 18:47:14 -0000	1.8
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.31      +230 -194  xml-site/targets/fop/fonts.html
  
  Index: fonts.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/fonts.html,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- fonts.html	21 Jun 2003 14:47:44 -0000	1.30
  +++ fonts.html	10 Jul 2003 18:47:14 -0000	1.31
  @@ -2,7 +2,7 @@
   <html>
   <head>
   <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  -<title>Fonts</title>
  +<title>FOP: Fonts</title>
   <link type="text/css" href="skin/page.css" rel="stylesheet">
   </head>
   <body text="#000000" bgcolor="#FFFFFF">
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  @@ -297,7 +301,7 @@
   <table class="title" summary="">
   <tr>
   <td valign="middle">
  -<h1>Fonts</h1>
  +<h1>FOP: Fonts</h1>
   </td><td nowrap="nowrap" width="80" align="center"><a class="dida" href="fonts.pdf"><img alt="printer" src="skin/images/printer.gif" border="0"><br>
             print-friendly<br>
             PDF</a></td>
  @@ -308,257 +312,289 @@
   </p>
   <ul class="minitoc">
   <li>
  -<a href="#intro">Important</a>
  +<a href="#intro">Summary</a>
  +</li>
  +<li>
  +<a href="#Base-14+Fonts">Base-14 Fonts</a>
   </li>
   <li>
  -<a href="#status">Status</a>
  +<a href="#awt">AWT/Operating System Fonts</a>
   </li>
   <li>
  -<a href="#type1">Adding Type 1 fonts</a>
  +<a href="#custom">Custom Fonts</a>
   <ul class="minitoc">
   <li>
  -<a href="#type1-metrics">Generating a font metrics file</a>
  +<a href="#type1-metrics">Type 1 Font Metrics</a>
   </li>
   <li>
  -<a href="#type1-register">Register the fonts within FOP</a>
  +<a href="#truetype-metrics">TrueType Font Metrics</a>
   </li>
  -</ul>
  -</li>
  -<li>
  -<a href="#truetype">Adding TrueType Fonts</a>
  -<ul class="minitoc">
   <li>
  -<a href="#truetype-metrics">Generating a font metrics file</a>
  +<a href="#truetype-collections-metrics">TrueType Collections Font Metrics</a>
   </li>
   <li>
  -<a href="#truetype-collections">TrueType collections</a>
  +<a href="#register">Register Fonts with FOP</a>
   </li>
   <li>
  -<a href="#truetype-register">Register the fonts within FOP</a>
  +<a href="#embedding">Embedding</a>
   </li>
   </ul>
   </li>
  -<li>
  -<a href="#embedding">Embedding fonts</a>
  -</li>
   </ul>
  -  
  +    
   <a name="N101C9"></a><a name="intro"></a>
  -<h3>Important</h3>
  +<h3>Summary</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<p>The information on this page applies primarily to the PDF renderer. The PostScript renderer
  -    also supports custom fonts but doesn't support font embedding, yet. This page does 
  -    <strong>not</strong> apply to the AWT, PCL, MIF and other renderers.</p>
  -<p>The AWT renderer relies upon AWT to provide the available fonts. And it's the printer 
  -    driver of your operating system that decides if a font is embedded when using the AWT 
  -    renderer.</p>
  +<p>The following table summarizes the font capabilites of the various FOP renderers:</p>
  +<table class="ForrestTable" cellspacing="1" cellpadding="4">
  +        
  +<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">no</td>
  +        
  +</tr>
  +        
  +<tr>
  +          
  +<td colspan="1" rowspan="1">PCL</td>
  +          <td colspan="1" rowspan="1">yes (modified)</td>
  +          <td colspan="1" rowspan="1">no</td>
  +          <td colspan="1" rowspan="1">no</td>
  +          <td colspan="1" rowspan="1">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">no</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">no</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>
   </div>
  -  
  -<a name="N101D9"></a><a name="status"></a>
  -<h3>Status</h3>
  +    
  +<a name="N1030A"></a><a name="Base-14+Fonts"></a>
  +<h3>Base-14 Fonts</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<p>FOP (building PDF files) normally supports only the base 14 font package defined in the Adobe PDF specification.
  -    That includes the following fonts: Helvetica, Times, Courier, Symbol and ZapfDingbats.
  -    </p>
  -<p>Font support in FOP can be extended by the addition of font metric files (written in XML) created from Adobe
  -    Type 1 fonts and TrueType fonts. No other font types (Type 3, etc.) are supported at this time.
  -    More information about font types can be found at
  -    the <a href="http://partners.adobe.com/asn/developer/type/ftypes.html">
  -    Adobe font types</a>. There is also lots more font information
  -    on this <a href="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</a>.
  -    </p>
  -<div class="frame note">
  -<div class="label">Note</div>
  -<div class="content">
  -        The font is simply embedded into the PDF file, it is not converted.
  -    </div>
  +<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>
   </div>
  +    
  +<a name="N10314"></a><a name="awt"></a>
  +<h3>AWT/Operating System Fonts</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<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>
   </div>
  -  
  -<a name="N101F1"></a><a name="type1"></a>
  -<h3>Adding Type 1 fonts</h3>
  +    
  +<a name="N1031E"></a><a name="custom"></a>
  +<h3>Custom Fonts</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<p>As mentioned above you need an XML file containing font metrics to be able to use an additional font. FOP
  -    contains a tool that can generate such a font metrics file from a PFM file, which normally comes with the font file.
  -    </p>
  -<a name="N101FA"></a><a name="type1-metrics"></a>
  -<h4>Generating a font metrics file</h4>
  +<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>
  +<a href="http://partners.adobe.com/asn/developer/type/ftypes.html">Adobe font types</a>
  +</li>
  +        
  +<li>
  +<a href="http://partners.adobe.com/asn/developer/technotes/fonts.html">Adobe Font Technote</a>
  +
  +</li>
  +      
  +</ul>
  +<a name="N10335"></a><a name="type1-metrics"></a>
  +<h4>Type 1 Font Metrics</h4>
   <div style="margin-left: 0 ; border: 2px">
  -<p> Run the class org.apache.fop.fonts.apps.PFMReader to generate the XML file.
  -      </p>
  +<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:</p>
  -<pre class="code">
  -java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar;
  +<pre class="code">java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar;
            lib\xercesImpl.jar;lib\xalan.jar
  -           org.apache.fop.fonts.apps.PFMReader pfm-file xml-file
  -</pre>
  +           org.apache.fop.fonts.apps.PFMReader pfm-file xml-file</pre>
   <p>Unix:</p>
  -<pre class="code">
  -java -cp build/fop.jar:lib/avalon-framework.jar:lib/xml-apis.jar:
  +<pre class="code">java -cp build/fop.jar:lib/avalon-framework.jar:lib/xml-apis.jar:
            lib/xercesImpl.jar:lib/xalan.jar
  -           org.apache.fop.fonts.apps.PFMReader pfm-file xml-file
  -</pre>
  +           org.apache.fop.fonts.apps.PFMReader pfm-file xml-file</pre>
   <div class="frame note">
   <div class="label">Note</div>
  -<div class="content">
  -        The classpath in the above example has been simplified for readibity. 
  -        You will have to adjust the classpath to the names of the actual JAR files in the lib directory.
  -        avalon-framework.jar is necessary only for versions 0.20.5 or later.
  -        xml-apis.jar, xercesImpl.jar and xalan.jar are not necessary for JDK version 1.4 or later.
  -      </div>
  +<div class="content">The classpath in the above example has been simplified for readibity.
  +You will have to adjust the classpath to the names of the actual JAR files in the lib directory.
  +avalon-framework.jar is necessary only for versions 0.20.5 or later.
  +xml-apis.jar, xercesImpl.jar and xalan.jar are not necessary for JDK version 1.4 or later.</div>
   </div>
   <div class="frame note">
   <div class="label">Note</div>
  -<div class="content">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.
  -      </div>
  +<div class="content">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.</div>
   </div>
   </div>
  -<a name="N10218"></a><a name="type1-register"></a>
  -<h4>Register the fonts within FOP</h4>
  +<a name="N10353"></a><a name="truetype-metrics"></a>
  +<h4>TrueType Font Metrics</h4>
   <div style="margin-left: 0 ; border: 2px">
  -<p>
  -        Edit conf/userconfig.xml and add entries for the font
  -        if the fonts section,
  -        ie:
  -      </p>
  +<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 metcis file in Windows from the TrueType font at c:\myfonts\cmr10.ttf:</p>
  +<pre class="code">java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar;
  +         lib\xercesImpl.jar;lib\xalan.jar
  +           org.apache.fop.fonts.apps.TTFReader
  +             C:\myfonts\cmr10.ttf ttfcm.xml</pre>
  +</div>
  +<a name="N10361"></a><a name="truetype-collections-metrics"></a>
  +<h4>TrueType Collections Font Metrics</h4>
  +<div style="margin-left: 0 ; border: 2px">
  +<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>
  +<pre class="code">java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar;
  +         lib\xercesImpl.jar;lib\xalan.jar
  +           org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho"
  +             msmincho.ttc msminch.xml</pre>
  +</div>
  +<a name="N10375"></a><a name="register"></a>
  +<h4>Register Fonts with FOP</h4>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>You must tell FOP how to find and use the font metrics files by registering them in the <a href="configuration.html">FOP Configuration</a>. Add entries for your custom fonts, regardless of font type, to the configuration file in a manner similar to the following:</p>
   <pre class="code">&lt;font metrics-file="FTL_____.xml" kerning="yes"
         embed-file="C:\myfonts\FTL_____.pfb"&gt;
     &lt;font-triplet name="FrutigerLight" style="normal" weight="normal"/&gt;
   &lt;/font&gt;</pre>
   <div class="frame note">
   <div class="label">Note</div>
  -<div class="content">
  -        Starting from FOP version 0.20.5 you can use URLs for the paths to the font files. Relative URLs are resolved 
  -        relative to the fontBaseDir property (or baseDir) if available.
  -      </div>
  +<div class="content">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.</div>
   </div>
  +<ul>
  +          
  +<li>Starting with FOP version 0.20.5 you can use URLs for the paths to the font files.
  +Relative URLs are resolved relative to the fontBaseDir property (or baseDir) if available. See <a href="configuration.html">FOP: Configuration</a> for more information.</li>
  +          
  +<li>The "kerning" and "embed-file" 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-file 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>
  +        
  +</ul>
   <div class="frame note">
   <div class="label">Note</div>
  -<div class="content">
  -        Make sure you specify the PFB file in the embed-file attribute 
  -        and not the PFM you used to generate the XML font metrics file.
  -      </div>
  +<div class="content">Cocoon users will need to setup the config, see FOPSerializer for more information.</div>
   </div>
  +</div>
  +<a name="N103A1"></a><a name="embedding"></a>
  +<h4>Embedding</h4>
  +<div style="margin-left: 0 ; border: 2px">
   <div class="frame note">
   <div class="label">Note</div>
  -<div class="content">
  -        If you do not want the font embedded in the PDF then remove the
  -        "embed-file" attribute. The PDF will then contain text using
  -        the font with the font metrics and to view it properly the
  -        font will need to be installed where it is being viewed.
  -      </div>
  +<div class="content">The PostScript renderer does not yet support font embedding.</div>
   </div>
   <div class="frame note">
   <div class="label">Note</div>
  -<div class="content">
  -        Cocoon users will need to setup the config, see FOPSerializer
  -        for more information.
  -      </div>
  +<div class="content">The font is simply embedded into the PDF file, it is not converted.</div>
   </div>
  -</div>
  -</div>
  -  
  -<a name="N10233"></a><a name="truetype"></a>
  -<h3>Adding TrueType Fonts</h3>
  -<div style="margin-left: 0 ; border: 2px">
  -<p>Adding TrueType fonts is almost identical to the process of
  -        adding Type 1 fonts. The main difference is in the first
  -        step.</p>
  -<a name="N1023C"></a><a name="truetype-metrics"></a>
  -<h4>Generating a font metrics file</h4>
  -<div style="margin-left: 0 ; border: 2px">
  -<p>As mentioned above you need an XML file containing font
  -            metrics to be able to use an additional font. FOP contains
  -            a tool that can generate such a font metrics file from
  -            your TrueType font file.
  -      </p>
  -<p>
  -      Create metrics for the fontfile (we assume the file has
  -            the name cmr10.ttf and exists in c:\myfonts\):
  -      </p>
  -<pre class="code">
  -java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar;
  -         lib\xercesImpl.jar;lib\xalan.jar
  -           org.apache.fop.fonts.apps.TTFReader
  -             C:\myfonts\cmr10.ttf ttfcm.xml
  -</pre>
  -</div>
  -<a name="N1024D"></a><a name="truetype-collections"></a>
  -<h4>TrueType collections</h4>
  -<div style="margin-left: 0 ; border: 2px">
  -<p>
  -      TrueType collections (.ttc files) contains more than one
  -      font. To create metrics for a ttc file you must specify
  -      the font in the collection with the -ttcname option to
  -      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 then display all the font
  -      names and exit with an Exception...
  -      </p>
  -<p>
  -      Example on generating metrics for a .ttc file:
  -      </p>
  -<pre class="code">
  -java -cp build\fop.jar;lib\avalon-framework.jar;lib\xml-apis.jar;
  -         lib\xercesImpl.jar;lib\xalan.jar
  -           org.apache.fop.fonts.apps.TTFReader -ttcname "MS Mincho"
  -             msmincho.ttc msminch.xml
  -</pre>
  -</div>
  -<a name="N10261"></a><a name="truetype-register"></a>
  -<h4>Register the fonts within FOP</h4>
  -<div style="margin-left: 0 ; border: 2px">
  -<p>
  -          Similiar to Type 1 fonts.
  -        </p>
  -<pre class="code">&lt;font metrics-file="cyberbit.xml" kerning="yes"
  -      embed-file="C:\WINNT\Fonts\Cyberbit.ttf"&gt;
  -  &lt;font-triplet name="Cyberbit" style="normal" weight="normal"/&gt;
  -&lt;/font&gt;</pre>
  -</div>
  -</div>
  -  
  -<a name="N10270"></a><a name="embedding"></a>
  -<h3>Embedding fonts</h3>
  -<div style="margin-left: 0 ; border: 2px">
  -<p>
  -      Font embedding is enabled in the userconfig.xml file and controlled by the embed-file attribute.
  -      If you don't specify the embed-file attribute the font will not be embedded, but will only be referenced.
  -    </p>
  -<p>
  -      When FOP embeds a font, it scrambles its fontname by inserting a prefix that ensures that the fontname 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 new font, containing only the glyphs used, is created from the original font and embedded in the pdf.
  +<p>Font embedding is enabled in the userconfig.xml file and controlled by the embed-file attribute.
  +If you don't specify the embed-file attribute the font will not be embedded, but will only be referenced.</p>
  +<p>When FOP embeds a font, it scrambles its fontname by inserting a prefix that ensures that the fontname 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 new font, containing only the glyphs used, is created from the original font and embedded in the pdf.
   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 -ansi option when generating metrics with TTFReader.
  +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 -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.
  -    </p>
  +Characters will be WinAnsi encoded (as specified in the PDF spec), so you lose the ability to use characters from other character sets.</p>
   </div>
  -  
  -<div class="frame note">
  -<div class="label">Note</div>
  -<div class="content">
  -    Be sure to start FOP with the option to find the config file ("-c conf/userconfig.xml" from the command line). Otherwise, it has no way of finding your custom font information.
  -  </div>
   </div>
  -
  +  
   </div>
   </td><td width="10"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td>
   </tr>
  
  
  
  1.11      +375 -262  xml-site/targets/fop/fonts.pdf
  
  	<<Binary file>>
  
  
  1.20      +4 -0      xml-site/targets/fop/gethelp.html
  
  Index: gethelp.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/gethelp.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- gethelp.html	30 May 2003 18:37:36 -0000	1.19
  +++ gethelp.html	10 Jul 2003 18:47:14 -0000	1.20
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.6       +61 -45    xml-site/targets/fop/graphics.html
  
  Index: graphics.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/graphics.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- graphics.html	30 May 2003 18:37:36 -0000	1.5
  +++ graphics.html	10 Jul 2003 18:47:14 -0000	1.6
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  @@ -325,12 +329,18 @@
   </ul>
   </li>
   <li>
  +<a href="#bmp">BMP</a>
  +</li>
  +<li>
   <a href="#eps">EPS</a>
   </li>
   <li>
   <a href="#jpeg">JPEG</a>
   </li>
   <li>
  +<a href="#png">PNG</a>
  +</li>
  +<li>
   <a href="#svg">SVG</a>
   <ul class="minitoc">
   <li>
  @@ -379,7 +389,7 @@
           
   <tr>
             
  -<td colspan="1" rowspan="1">BMP (Microsoft Windows Bitmap)</td>
  +<td colspan="1" rowspan="1"><a href="#bmp">BMP</a> (Microsoft Windows Bitmap)</td>
             <td colspan="1" rowspan="1">bitmap</td>
             <td colspan="1" rowspan="1"><a href="#native">FOP native</a></td>
           
  @@ -411,7 +421,7 @@
           
   <tr>
             
  -<td colspan="1" rowspan="1">PNG (Portable Network Graphic)</td>
  +<td colspan="1" rowspan="1"><a href="#png">PNG</a> (Portable Network Graphic)</td>
             <td colspan="1" rowspan="1">bitmap</td>
             <td colspan="1" rowspan="1"><a href="#jimi">JIMI</a> or <a href="#jai">JAI</a></td>
           
  @@ -436,17 +446,17 @@
   </table>
   </div>
       
  -<a name="N10289"></a><a name="packages"></a>
  +<a name="N1028F"></a><a name="packages"></a>
   <h3>Graphics Packages</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<a name="N1028F"></a><a name="native"></a>
  +<a name="N10295"></a><a name="native"></a>
   <h4>FOP Native</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>
             FOP has native ability to handle some graphic file formats.
           </p>
   </div>
  -<a name="N10299"></a><a name="jimi"></a>
  +<a name="N1029F"></a><a name="jimi"></a>
   <h4>JIMI</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -454,7 +464,7 @@
   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>
   </div>
  -<a name="N102A7"></a><a name="jai"></a>
  +<a name="N102AD"></a><a name="jai"></a>
   <h4>JAI (Java Advanced Imaging API)</h4>
   <div style="margin-left: 0 ; border: 2px">
   <div class="frame warning">
  @@ -467,7 +477,7 @@
   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.
           </p>
   </div>
  -<a name="N102BC"></a><a name="batik"></a>
  +<a name="N102C2"></a><a name="batik"></a>
   <h4>Batik</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>Current FOP distributions include a distribution of the Apache Software Foundation's <a target="_top" href="http://xml.apache.org/batik">Batik</a> version 1.5beta4.
  @@ -493,7 +503,13 @@
   </div>
   </div>
       
  -<a name="N102E7"></a><a name="eps"></a>
  +<a name="N102ED"></a><a name="bmp"></a>
  +<h3>BMP</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>FOP native support for BMP images is limited to the RGB color-space.</p>
  +</div>
  +    
  +<a name="N102F7"></a><a name="eps"></a>
   <h3>EPS</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>FOP provides support for two output targets:</p>
  @@ -516,25 +532,27 @@
         </p>
   </div>
       
  -<a name="N102FD"></a><a name="jpeg"></a>
  +<a name="N1030D"></a><a name="jpeg"></a>
   <h3>JPEG</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<p>
  -        Not all variants of JPEG are supported, 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.
  -      </p>
  -<p>
  -        For the PDF and PostScript renderers most JPEG images can be passed through without 
  -        decompression.
  +<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>
   </div>
       
  -<a name="N1030A"></a><a name="svg"></a>
  +<a name="N10317"></a><a name="png"></a>
  +<h3>PNG</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>If using JAI for PNG support, only RGB and RGBA color-spaces are supported for FOP rendering.</p>
  +</div>
  +    
  +<a name="N10321"></a><a name="svg"></a>
   <h3>SVG</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<a name="N10310"></a><a name="svg-intro"></a>
  +<a name="N10327"></a><a name="svg-intro"></a>
   <h4>Introduction</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>FOP uses <a href="#batik">Batik</a> for SVG support.
  @@ -550,7 +568,7 @@
         </div>
   </div>
   </div>
  -<a name="N1032B"></a><a name="svg-pdf-graphics"></a>
  +<a name="N10342"></a><a name="svg-pdf-graphics"></a>
   <h4>Placing SVG Graphics into PDF</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -570,7 +588,7 @@
   correctly.
           </p>
   </div>
  -<a name="N1033B"></a><a name="svg-pdf-text"></a>
  +<a name="N10352"></a><a name="svg-pdf-text"></a>
   <h4>Placing SVG Text into PDF</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>If possible, Batik will use normal PDF text when inserting text. It does
  @@ -590,29 +608,16 @@
   for PDF it will use a single character.
           </p>
   <p>
  -It is possible to make sure that all text is drawn into PDF using the
  -PDF text commands (instead of the graphical shapes), by adding the following to the user config:
  -        </p>
  -<pre class="code">&lt;entry&gt;
  -  &lt;key&gt;strokeSVGText&lt;/key&gt;
  -  &lt;value&gt;false&lt;/value&gt;
  -&lt;/entry&gt;</pre>
  -<p>In a servlet environment, you can set it directly:</p>
  -<pre class="code">org.apache.fop.configuration.Configuration.put("strokeSVGText", Boolean.FALSE);</pre>
  -<p>For information on using a configuration file in a servlet, see the <a href="faq.html#usercfg">FAQ</a> on that topic.</p>
  -<p>Note that this configuration setting works only for the PDF renderer.</p>
  -<p>
  -The drawback to forcing text to be rendered as text is that it will be confined to text that is
  -possible for PDF fonts (including embedded fonts) and implemented with
  -this workaround. The fonts available are the standard pdf fonts and any
  -fonts that you have embedded using FOP. The font sizes will be rounded
  -to an integer value. In future this will be improved.
  +For PDF output, there is a <a href="configuration.html#svg-strokeSVGText">configuration option to force SVG text to be rendered as text</a>.
  +The drawback to this approach is that it is effective only for available fonts (including embedded fonts).
  +Font sizes are rounded to the next integer point size.
  +This will be improved in the future.
           </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>
   </div>
  -<a name="N1036E"></a><a name="svg-scaling"></a>
  +<a name="N10371"></a><a name="svg-scaling"></a>
   <h4>Scaling</h4>
   <div style="margin-left: 0 ; border: 2px">
   <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.
  @@ -620,7 +625,7 @@
   The SVG standard leaves this issue as an implementation detail.
   FOP will probably implement a scaling mechanism in the future.</p>
   </div>
  -<a name="N1037B"></a><a name="svg-problems"></a>
  +<a name="N1037E"></a><a name="svg-problems"></a>
   <h4>Known Problems</h4>
   <div style="margin-left: 0 ; border: 2px">
   <ul>
  @@ -662,13 +667,24 @@
   </div>
   </div>
       
  -<a name="N10398"></a><a name="tiff"></a>
  +<a name="N1039B"></a><a name="tiff"></a>
   <h3>TIFF</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<p>TIFF images with JPEG or CCITT content are passed through by FOP natively (PDF and PostScript only). Other TIFF subformats are handled by JAI.</p>
  +<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>
   </div>
       
  -<a name="N103A2"></a><a name="resolution"></a>
  +<a name="N103B6"></a><a name="resolution"></a>
   <h3>Graphics Resolution</h3>
   <div style="margin-left: 0 ; border: 2px">
   <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>
  @@ -688,7 +704,7 @@
   </div>
   </div>
       
  -<a name="N103BE"></a><a name="caching"></a>
  +<a name="N103D2"></a><a name="caching"></a>
   <h3>Image caching</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  
  
  
  1.6       +855 -516  xml-site/targets/fop/graphics.pdf
  
  	<<Binary file>>
  
  
  1.51      +4 -0      xml-site/targets/fop/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/index.html,v
  retrieving revision 1.50
  retrieving revision 1.51
  diff -u -r1.50 -r1.51
  --- index.html	30 May 2003 18:37:36 -0000	1.50
  +++ index.html	10 Jul 2003 18:47:14 -0000	1.51
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.35      +4 -0      xml-site/targets/fop/license.html
  
  Index: license.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/license.html,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- license.html	30 May 2003 18:37:36 -0000	1.34
  +++ license.html	10 Jul 2003 18:47:14 -0000	1.35
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.13      +4 -0      xml-site/targets/fop/logocontest.html
  
  Index: logocontest.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/logocontest.html,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- logocontest.html	7 Jul 2003 04:45:16 -0000	1.12
  +++ logocontest.html	10 Jul 2003 18:47:14 -0000	1.13
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.2       +24 -10    xml-site/targets/fop/maillist.html
  
  Index: maillist.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/maillist.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- maillist.html	30 May 2003 18:37:36 -0000	1.1
  +++ maillist.html	10 Jul 2003 18:47:14 -0000	1.2
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  @@ -335,18 +339,28 @@
   <a name="N101BE"></a><a name="general"></a>
   <h3>General Information</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<p>Before posting questions to any list, review "<a target="_top" href="http://www.catb.org/~esr/faqs/smart-questions.html">How To Ask Questions The Smart Way</a>".</p>
  -<p>Be sure to set your email client to send plain text email messages to any mailing lists.
  +<p>Before posting questions to any list:</p>
  +<ul>
  +        
  +<li>Review the <a target="_top" href="http://jakarta.apache.org/site/mail.html">Jakarta Mailing Lists - Guidelines</a> for general principles about mailing lists.</li>
  +        
  +<li>Review "<a target="_top" href="http://www.catb.org/~esr/faqs/smart-questions.html">How To Ask Questions The Smart Way</a>".</li>
  +        
  +<li>Send only <em>plain text</em> email messages to any mailing lists.
   Please do <em>not</em> send html or rtf email, as they do not work well with the archive engines.
  -If you are using Microsoft Outlook, this setting can be found at the "Mail Format" tab of the Tools/Options menu.</p>
  +If you are using Microsoft Outlook, this setting can be found at the "Mail Format" tab of the Tools/Options menu.</li>
  +        
  +<li>Use a mail client that respects the <em>References</em> and/or <em>In-Reply-To</em> mail header entries. This is important for mail clients that can display threads as trees. <strong>Compliant mail clients</strong> include Microsoft Outlook, Becky!, KMail, Apple Mail, Ximian Evolution, Mozilla (version 1.2 or greater). Non-compliant mail clients include Microsoft Exchange, Lotus Notes, Internet Mail Service (MUA or MTA), and dtmail.</li>
  +      
  +</ul>
   <p>For help in understanding email acronyms, see the <a target="_top" href="http://www.lingo2word.com/lists/acronym_listA.html">Lingo2Word Acronym List</a>, or the <a target="_top" href="http://www.keno.org/web_design/acronyms.htm">Keno Internet Services Internet Glossary</a>.</p>
   </div>
       
  -<a name="N101DD"></a><a name="fop-user"></a>
  +<a name="N101F9"></a><a name="fop-user"></a>
   <h3>FOP User Mailing List</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Use this forum to discuss topics of interest to FOP users.</p>
  -<a name="N101E6"></a><a name="fop-user-archive"></a>
  +<a name="N10202"></a><a name="fop-user-archive"></a>
   <h4>Archives</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>To review the archives, you have several options:</p>
  @@ -360,7 +374,7 @@
           
   </ul>
   </div>
  -<a name="N10208"></a><a name="fop-user-subscribe"></a>
  +<a name="N10224"></a><a name="fop-user-subscribe"></a>
   <h4>Subscription Information</h4>
   <div style="margin-left: 0 ; border: 2px">
   <ul>
  @@ -377,7 +391,7 @@
           
   </ul>
   </div>
  -<a name="N10235"></a><a name="fop-user-policy"></a>
  +<a name="N10251"></a><a name="fop-user-policy"></a>
   <h4>Submitting a Question</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>FOP support is primarily <em>self-service</em>. The FOP User Mailing List serves as a backup to the self-service documentation for cases where either the documentation is deficient or where users have unusual circumstances. FOP developers and users are happy to help answer questions that are <em>appropriate to the forum</em> (i.e. FOP-specific), and that are <em>submitted after appropriate preparation</em>. To ensure that your question is not <strong>abusive</strong> of this policy, please use the following checklist:</p>
  @@ -425,7 +439,7 @@
   </div>
   </div>
       
  -<a name="N10291"></a><a name="w3c-xslfo"></a>
  +<a name="N102AD"></a><a name="w3c-xslfo"></a>
   <h3>XSL-FO Mailing List (at W3C)</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Use this forum to ask general XSL-FO questions.</p>
  @@ -441,7 +455,7 @@
   </ul>
   </div>
       
  -<a name="N102B7"></a><a name="yahoogroups-xslfo"></a>
  +<a name="N102D3"></a><a name="yahoogroups-xslfo"></a>
   <h3>XSL-FO Mailing List (at YahooGroups)</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Use this forum to ask general XSL-FO questions.</p>
  @@ -454,7 +468,7 @@
   </ul>
   </div>
       
  -<a name="N102D2"></a><a name="xslt-mulberry"></a>
  +<a name="N102EE"></a><a name="xslt-mulberry"></a>
   <h3>XSLT List (Mulberry Tech)</h3>
   <div style="margin-left: 0 ; border: 2px">
   <ul>
  
  
  
  1.2       +353 -289  xml-site/targets/fop/maillist.pdf
  
  	<<Binary file>>
  
  
  1.21      +27 -14    xml-site/targets/fop/news.html
  
  Index: news.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/news.html,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- news.html	21 Jun 2003 14:47:44 -0000	1.20
  +++ news.html	10 Jul 2003 18:47:14 -0000	1.21
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  @@ -305,6 +309,9 @@
   </table>
   <ul class="minitoc">
   <li>
  +<a href="#29+June+2003+-+New+Committer">29 June 2003 - New Committer</a>
  +</li>
  +<li>
   <a href="#23+May+2003+-+FOP+0.20.5+Release+Candidate+3+available">23 May 2003 - FOP 0.20.5 Release Candidate 3 available</a>
   </li>
   <li>
  @@ -345,7 +352,13 @@
   </li>
   </ul>
       
  -<a name="N101BE"></a><a name="23+May+2003+-+FOP+0.20.5+Release+Candidate+3+available"></a>
  +<a name="N101BE"></a><a name="29+June+2003+-+New+Committer"></a>
  +<h3>29 June 2003 - New Committer</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>Welcome Glen Mazza!</p>
  +</div>
  +    
  +<a name="N101C8"></a><a name="23+May+2003+-+FOP+0.20.5+Release+Candidate+3+available"></a>
   <h3>23 May 2003 - FOP 0.20.5 Release Candidate 3 available</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -353,7 +366,7 @@
         </p>
   </div>
       
  -<a name="N101CC"></a><a name="18+February+2003+-+FOP+0.20.5+Release+Candidate+2+available"></a>
  +<a name="N101D6"></a><a name="18+February+2003+-+FOP+0.20.5+Release+Candidate+2+available"></a>
   <h3>18 February 2003 - FOP 0.20.5 Release Candidate 2 available</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -361,7 +374,7 @@
         </p>
   </div>
       
  -<a name="N101DA"></a><a name="2+February+2003+-+New+XML+PMC"></a>
  +<a name="N101E4"></a><a name="2+February+2003+-+New+XML+PMC"></a>
   <h3>2 February 2003 - New XML PMC</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -369,14 +382,14 @@
         </p>
   </div>
       
  -<a name="N101E4"></a><a name="28+January+2003+-+FOP+logo+contest"></a>
  +<a name="N101EE"></a><a name="28+January+2003+-+FOP+logo+contest"></a>
   <h3>28 January 2003 - FOP logo contest</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>We are looking for a new logo. FOP <a href="logocontest.html">logo
  -           contest</a> is started!</p>
  +      contest</a> is started!</p>
   </div>
       
  -<a name="N101F2"></a><a name="23+December+2002+-+Official+FOP+Wiki"></a>
  +<a name="N101FC"></a><a name="23+December+2002+-+Official+FOP+Wiki"></a>
   <h3>23 December 2002 - Official FOP Wiki</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -384,7 +397,7 @@
         </p>
   </div>
       
  -<a name="N10200"></a><a name="10+December+2002+-+FOP+0.20.5+Release+Candidate+available"></a>
  +<a name="N1020A"></a><a name="10+December+2002+-+FOP+0.20.5+Release+Candidate+available"></a>
   <h3>10 December 2002 - FOP 0.20.5 Release Candidate available</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -392,7 +405,7 @@
         </p>
   </div>
       
  -<a name="N1020E"></a><a name="23+November+2002+-+EXLSFO+project+has+been+created"></a>
  +<a name="N10218"></a><a name="23+November+2002+-+EXLSFO+project+has+been+created"></a>
   <h3>23 November 2002 - EXLSFO project has been created</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -402,19 +415,19 @@
         </p>
   </div>
       
  -<a name="N1021C"></a><a name="22+November+2002+-+New+Committer"></a>
  +<a name="N10226"></a><a name="22+November+2002+-+New+Committer"></a>
   <h3>22 November 2002 - New Committer</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Welcome Victor Mote!</p>
   </div>
       
  -<a name="N10226"></a><a name="9+November+2002+-+New+Committer"></a>
  +<a name="N10230"></a><a name="9+November+2002+-+New+Committer"></a>
   <h3>9 November 2002 - New Committer</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Welcome Oleg Tkachenko!</p>
   </div>
       
  -<a name="N10230"></a><a name="7+July+2002+FOP+0.20.4+released"></a>
  +<a name="N1023A"></a><a name="7+July+2002+FOP+0.20.4+released"></a>
   <h3>7 July 2002 FOP 0.20.4 released</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -462,7 +475,7 @@
         </p>
   </div>
       
  -<a name="N10267"></a><a name="13+June+2002+FOP+0.20.4+Release+Candidate+available"></a>
  +<a name="N10271"></a><a name="13+June+2002+FOP+0.20.4+Release+Candidate+available"></a>
   <h3>13 June 2002 FOP 0.20.4 Release Candidate available</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>
  @@ -470,13 +483,13 @@
         </p>
   </div>
       
  -<a name="N10275"></a><a name="19+April+2002+-+New+Committers"></a>
  +<a name="N1027F"></a><a name="19+April+2002+-+New+Committers"></a>
   <h3>19 April 2002 - New Committers</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>Welcome Jeremias Maerki, Joerg Pietschmann and Peter B. West!</p>
   </div>
   
  -<a name="N1027F"></a><a name="11+March+2002+-+FOP+0.20.3+released"></a>
  +<a name="N10289"></a><a name="11+March+2002+-+FOP+0.20.3+released"></a>
   <h3>11 March 2002 - FOP 0.20.3 released</h3>
   <div style="margin-left: 0 ; border: 2px">
   <p>This is a maintenance release, the first version which supports the XSL-FO
  
  
  
  1.12      +182 -192  xml-site/targets/fop/news.pdf
  
  	<<Binary file>>
  
  
  1.23      +4 -0      xml-site/targets/fop/output.html
  
  Index: output.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/output.html,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- output.html	21 Jun 2003 14:47:44 -0000	1.22
  +++ output.html	10 Jul 2003 18:47:14 -0000	1.23
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.14      +4 -0      xml-site/targets/fop/pdfencryption.html
  
  Index: pdfencryption.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/pdfencryption.html,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- pdfencryption.html	7 Jul 2003 04:45:16 -0000	1.13
  +++ pdfencryption.html	10 Jul 2003 18:47:14 -0000	1.14
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.23      +4 -0      xml-site/targets/fop/relnotes.html
  
  Index: relnotes.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/relnotes.html,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- relnotes.html	21 Jun 2003 14:47:44 -0000	1.22
  +++ relnotes.html	10 Jul 2003 18:47:14 -0000	1.23
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.34      +4 -0      xml-site/targets/fop/resources.html
  
  Index: resources.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/resources.html,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -r1.33 -r1.34
  --- resources.html	7 Jul 2003 04:45:16 -0000	1.33
  +++ resources.html	10 Jul 2003 18:47:14 -0000	1.34
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.42      +4 -0      xml-site/targets/fop/running.html
  
  Index: running.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/running.html,v
  retrieving revision 1.41
  retrieving revision 1.42
  diff -u -r1.41 -r1.42
  --- running.html	30 May 2003 18:37:38 -0000	1.41
  +++ running.html	10 Jul 2003 18:47:15 -0000	1.42
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.2       +4 -0      xml-site/targets/fop/servlets.html
  
  Index: servlets.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/servlets.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- servlets.html	30 May 2003 18:37:38 -0000	1.1
  +++ servlets.html	10 Jul 2003 18:47:15 -0000	1.2
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.17      +4 -0      xml-site/targets/fop/status.html
  
  Index: status.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/status.html,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- status.html	30 May 2003 18:37:38 -0000	1.16
  +++ status.html	10 Jul 2003 18:47:15 -0000	1.17
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.4       +4 -0      xml-site/targets/fop/team.html
  
  Index: team.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/team.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- team.html	7 Jul 2003 04:45:16 -0000	1.3
  +++ team.html	10 Jul 2003 18:47:15 -0000	1.4
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.25      +4 -0      xml-site/targets/fop/todo.html
  
  Index: todo.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/todo.html,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- todo.html	30 May 2003 18:37:39 -0000	1.24
  +++ todo.html	10 Jul 2003 18:47:15 -0000	1.25
  @@ -186,6 +186,10 @@
   </li>
             
   <li>
  +<a href="hyphenation.html">Hyphenation</a>
  +</li>
  +          
  +<li>
   <a href="extensions.html">Extensions</a>
   </li>
           
  
  
  
  1.1                  xml-site/targets/fop/hyphenation.html
  
  Index: hyphenation.html
  ===================================================================
  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  <html>
  <head>
  <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  <title>FOP: Hyphenation</title>
  <link type="text/css" href="skin/page.css" rel="stylesheet">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
  <!--================= start Navigation Path ==================-->
  <table summary="navigation path" width="100%" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <td nowrap="nowrap" valign="middle" bgcolor="#CFDCED" height="20"><img height="1" width="5" alt="" border="0" src="skin/images/spacer.gif"><!--===== breadcrumb trail (javascript-generated) ====--><font size="2" face="Arial, Helvetica, Sans-serif"><script src="skin/breadcrumbs.js" language="JavaScript" type="text/javascript"></script></font></td>
  </tr>
  <tr>
  <td bgcolor="#4C6C8F" height="2"><img height="2" width="2" alt="" border="0" src="skin/images/spacer.gif"></td>
  </tr>
  </table>
  <!--================= end Navigation Path ==================-->
  <!--================= start Banner ==================-->
  <table summary="header with logos" width="100%" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <!--================= start Group Logo ==================-->
  <td bgcolor="#294563"><a href="http://xml.apache.org/"><img border="0" class="logoImage" alt="Apache XML" src="images/group-logo.gif"></a></td>
  <!--================= end Group Logo ==================-->
  <!--================= start Project Logo ==================--><td width="100%" align="center" bgcolor="#294563"><a href="http://xml.apache.org/fop/"><img border="0" class="logoImage" alt="FOP" src="images/logo.jpg"></a></td>
  <!--================= end Project Logo ==================-->
  <!--================= start Search ==================--><td valign="top" rowspan="2" bgcolor="#294563">
  <form target="_blank" action="http://www.google.com/search" method="get">
  <table summary="search" border="0" cellspacing="0" cellpadding="0" bgcolor="#4C6C8F">
  <tr>
  <td colspan="3"><img height="10" width="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <tr>
  <td><img height="1" width="1" alt="" src="skin/images/spacer.gif"></td><td nowrap="nowrap"><input value="xml.apache.org" name="sitesearch" type="hidden"><input size="15" name="q" id="query" type="text"><img height="1" width="5" alt="" src="skin/images/spacer.gif"><input name="Search" value="Search" type="submit">
  <br>
  <font face="Arial, Helvetica, Sans-serif" size="2" color="white">
                        the Apache XML site
                        
                        
                      </font></td><td><img height="1" width="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <tr>
  <td><img alt="" border="0" height="10" width="9" src="skin/images/search-left.gif"></td><td><img height="1" width="1" alt="" src="skin/images/spacer.gif"></td><td><img alt="" border="0" height="10" width="9" src="skin/images/search-right.gif"></td>
  </tr>
  </table>
  </form>
  </td>
  <!--================= start Search ==================--><td bgcolor="#294563"><img height="10" width="10" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <tr>
  <td valign="bottom" bgcolor="#294563" colspan="2">
  <!--================= start Tabs ==================-->
  <div class="tab">
  <table summary="tab bar" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <td width="8"><img alt="" height="8" width="8" src="skin/images/spacer.gif"></td><td valign="bottom">
  <table summary="selected tab" style="height: 1.7em" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <td valign="top" width="5" bgcolor="#4C6C8F"><img height="5" width="5" alt="" src="skin/images/tabSel-left.gif"></td><td valign="middle" bgcolor="#4C6C8F"><font color="#ffffff" size="2" face="Arial, Helvetica, Sans-serif"><b><a href="index.html"><font color="#000000">Home</font></a></b></font></td><td valign="top" width="5" bgcolor="#4C6C8F"><img height="5" width="5" alt="" src="skin/images/tabSel-right.gif"></td>
  </tr>
  </table>
  </td><td width="8"><img alt="" height="8" width="8" src="skin/images/spacer.gif"></td><td valign="bottom">
  <table summary="non selected tab" style="height: 1.6em" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <td valign="top" width="5" bgcolor="#B2C4E0"><img height="5" width="5" alt="" src="skin/images/tab-left.gif"></td><td valign="middle" bgcolor="#B2C4E0"><a href="dev/index.html"><font face="Arial, Helvetica, Sans-serif">Development</font></a></td><td valign="top" width="5" bgcolor="#B2C4E0"><img height="5" width="5" alt="" src="skin/images/tab-right.gif"></td>
  </tr>
  </table>
  </td><td width="8"><img alt="" height="8" width="8" src="skin/images/spacer.gif"></td><td valign="bottom">
  <table summary="non selected tab" style="height: 1.6em" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <td valign="top" width="5" bgcolor="#B2C4E0"><img height="5" width="5" alt="" src="skin/images/tab-left.gif"></td><td valign="middle" bgcolor="#B2C4E0"><a href="design/index.html"><font face="Arial, Helvetica, Sans-serif">Design</font></a></td><td valign="top" width="5" bgcolor="#B2C4E0"><img height="5" width="5" alt="" src="skin/images/tab-right.gif"></td>
  </tr>
  </table>
  </td><td width="8"><img alt="" height="8" width="8" src="skin/images/spacer.gif"></td><td valign="bottom">
  <table summary="non selected tab" style="height: 1.6em" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <td valign="top" width="5" bgcolor="#B2C4E0"><img height="5" width="5" alt="" src="skin/images/tab-left.gif"></td><td valign="middle" bgcolor="#B2C4E0"><a href="design/alt.design/index.html"><font face="Arial, Helvetica, Sans-serif">Alt Design</font></a></td><td valign="top" width="5" bgcolor="#B2C4E0"><img height="5" width="5" alt="" src="skin/images/tab-right.gif"></td>
  </tr>
  </table>
  </td>
  </tr>
  </table>
  </div>
  <!--================= end Tabs ==================-->
  </td><td bgcolor="#294563"><img alt="" width="1" height="1" src="skin/images/spacer.gif"></td>
  </tr>
  <tr>
  <td bgcolor="#4C6C8F" colspan="4"><img width="1" height="10" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  </table>
  <!--================= end Banner ==================-->
  <!--================= start Menu, NavBar, Content ==================-->
  <table summary="page content" bgcolor="#ffffff" width="100%" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <td valign="top">
  <table summary="menu" border="0" cellspacing="0" cellpadding="0">
  <tr>
  <!--================= start left top NavBar ==================-->
  <td rowspan="3" valign="top">
  <table summary="blue line" border="0" cellpadding="0" cellspacing="0">
  <tr>
  <td bgcolor="#294563"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <tr>
  <td bgcolor="#CFDCED"><font color="#4C6C8F" size="4" face="Arial, Helvetica, Sans-serif">&nbsp;</font></td>
  </tr>
  <tr>
  <td bgcolor="#294563"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  </table>
  </td>
  <!--================= end left top NavBar ==================--><td bgcolor="#294563"><img width="1" height="1" alt="" src="skin/images/spacer.gif"></td><td valign="bottom" bgcolor="#4C6C8F"><img width="10" height="10" alt="" src="skin/images/spacer.gif"></td><td nowrap="nowrap" valign="top" bgcolor="#4C6C8F">
  <!--================= start Menu items ==================-->
  <div class="menu">
  <ul>
  <li>
  <font color="#CFDCED">Home</font>
  <ul>
            
  <li>
  <a href="index.html">Introduction</a>
  </li>
          
  </ul>
  </li>
  <li>
  <font color="#CFDCED">Using FOP</font>
  <ul>
            
  <li>
  <a href="relnotes.html">Release Notes</a>
  </li>
            
  <li>
  <a href="download.html">Download</a>
  </li>
            
  <li>
  <a href="compiling.html">Build</a>
  </li>
            
  <li>
  <a href="configuration.html">Configure</a>
  </li>
            
  <li>
  <a href="running.html">Run</a>
  </li>
            
  <li>
  <a href="embedding.html">Embed</a>
  </li>
            
  <li>
  <a href="servlets.html">Servlets</a>
  </li>
            
  <li>
  <a href="anttask.html">Ant task</a>
  </li>
          
  </ul>
  </li>
  <li>
  <font color="#CFDCED">Features</font>
  <ul>
            
  <li>
  <a href="compliance.html">Compliance</a>
  </li>
            
  <li>
  <a href="output.html">Output Targets</a>
  </li>
            
  <li>
  <a href="pdfencryption.html">PDF encryption</a>
  </li>
            
  <li>
  <a href="graphics.html">Graphics</a>
  </li>
            
  <li>
  <a href="fonts.html">Fonts</a>
  </li>
            
  <li>
  <span class="sel"><font color="#ffcc00">Hyphenation</font></span>
  </li>
            
  <li>
  <a href="extensions.html">Extensions</a>
  </li>
          
  </ul>
  </li>
  <li>
  <font color="#CFDCED">Resources</font>
  <ul>
            
  <li>
  <a href="gethelp.html">Getting Help</a>
  </li>
            
  <li>
  <a href="faq.html">FAQs</a>
  </li>
            
  <li>
  <a href="fo.html">XSL-FO</a>
  </li>
            
  <li>
  <a href="examples.html">Examples</a>
  </li>
            
  <li>
  <a href="maillist.html">Mailing Lists</a>
  </li>
            
  <li>
  <a href="bugs.html">Bugs</a>
  </li>
            
  <li>
  <a href="license.html">License</a>
  </li>
            
  <li>
  <a href="resources.html">Other</a>
  </li>
          
  </ul>
  </li>
  <li>
  <font color="#CFDCED">Project</font>
  <ul>
            
  <li>
  <a href="news.html">News</a>
  </li>
            
  <li>
  <a href="logocontest.html">Logo contest</a>
  </li>
            
  <li>
  <a href="status.html">Status</a>
  </li>
            
  <li>
  <a href="changes.html">Changes</a>
  </li>
            
  <li>
  <a href="todo.html">Todo</a>
  </li>
            
  <li>
  <a href="team.html">Team</a>
  </li>
          
  </ul>
  </li>
  </ul>
  </div>
  <!--================= end Menu items ==================-->
  </td><td valign="bottom" bgcolor="#4C6C8F"><img width="10" height="10" alt="" src="skin/images/spacer.gif"></td><td bgcolor="#294563"><img width="1" height="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <tr>
  <td valign="bottom" align="left" colspan="2" rowspan="2" bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="skin/images/menu-left.gif"></td><td bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="skin/images/spacer.gif"></td><td valign="bottom" align="right" colspan="2" rowspan="2" bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="skin/images/menu-right.gif"></td>
  </tr>
  <tr>
  <td height="1" bgcolor="#294563"><img width="1" height="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  </table>
  </td><td valign="top" width="100%">
  <table summary="content" width="100%" border="0" cellpadding="0" cellspacing="0">
  <!--================= start middle NavBar ==================-->
  <tr>
  <td colspan="4" bgcolor="#294563"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <tr>
  <td align="left" width="10" bgcolor="#CFDCED"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td><td align="left" width="50%" bgcolor="#CFDCED"><font color="#4C6C8F" size="3" face="Arial, Helvetica, Sans-serif">
                  &nbsp;
                  
                  </font><img width="10" height="8" alt="" src="skin/images/spacer.gif"></td><td align="right" width="50%" bgcolor="#CFDCED"><font color="#4C6C8F" size="3" face="Arial, Helvetica, Sans-serif">
                  &nbsp;
                  
                  </font><img width="10" height="8" alt="" src="skin/images/spacer.gif"></td><td width="10" bgcolor="#CFDCED"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <tr>
  <td colspan="4" bgcolor="#294563"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <!--================= end middle NavBar ==================-->
  <!--================= start Content==================-->
  <tr>
  <td align="left" width="10"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td><td align="left" width="100%">
  <div class="content">
  <table class="title" summary="">
  <tr>
  <td valign="middle">
  <h1>FOP: Hyphenation</h1>
  </td><td nowrap="nowrap" width="80" align="center"><a class="dida" href="hyphenation.pdf"><img alt="printer" src="skin/images/printer.gif" border="0"><br>
            print-friendly<br>
            PDF</a></td>
  </tr>
  </table>
  <ul class="minitoc">
  <li>
  <a href="#hyphenation">Setting up hyphenation</a>
  <ul class="minitoc">
  <li>
  <a href="#hyphenation-sources">Places to find TeX hyphenation pattern files</a>
  </li>
  </ul>
  </li>
  </ul>
      
  <a name="N101BE"></a><a name="hyphenation"></a>
  <h3>Setting up hyphenation</h3>
  <div style="margin-left: 0 ; border: 2px">
  <p>FOP comes already with some hyphenation patterns.
  If you need a hyphenation pattern which isn't included in the distribution, do the following:</p>
  <ol>
          
  <li>Get the TeX hyphenation pattern file and turn it into an xml file which
  conforms to the hyphenation.dtd in the subdirectory {fop-dir}/src/hyph.</li>
          
  <li>Name this new file following this schema: <span class="codefrag">languageCode_countryCode.xml</span>.
  If you don't need a country code, leave it out, e.g. the file name for an American
  english hyphenation pattern would look like this: <span class="codefrag">en_US.xml</span>.
  For an Italian file: <span class="codefrag">it.xml</span>.
  Language and country codes must be the same as in XSL-FO, that is follow <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt">ISO 639</a> and
  <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt">ISO 3166</a>
  respectively.
  NOTE: The ISO 639/ISO 3166 convention is that language names are
  written in lower case, while country codes are written in upper case.</li>
          
  <li>If you have built your new hyphenation pattern file successfully there are
  two ways to make it accessible to FOP.
            <ul>
              
  <li>Put this new file into the directory {fop-dir}/src/hyph and rebuild FOP. The file will be picked up and added to fop.jar.</li>
              
  <li>Put the file into a directory of your choice and specify this directory
  in the userconfig.xml in the entry &lt;hyphenation-dir&gt;.</li>
            
  </ul>
          
  </li>
        
  </ol>
  <a name="N101ED"></a><a name="hyphenation-sources"></a>
  <h4>Places to find TeX hyphenation pattern files</h4>
  <div style="margin-left: 0 ; border: 2px">
  <p>The most important place to find hyphenation pattern file is the <a target="_blank" href="http://www.ctan.org/tex-archive/language/hyphenation/">CTAN TeX Archive</a>.</p>
  </div>
  <div class="frame warning">
  <div class="label">Warning</div>
  <div class="content">You have to carefully check license issues when using hyphenation pattern files from other places.
  The licenses of the files found on the Internet are not always clear.</div>
  </div>
  <div class="frame note">
  <div class="label">Note</div>
  <div class="content">Most of the files published in the CTAN Archive are licenced under the <a target="_blank" href="http://www.latex-project.org/lppl.html">LaTeX Project Public License (LPPL)</a>.
  The Apache Foundation can't redistribute files under this license. If you want to use such a file you have to decide for yourself if you can use (and possibly distribute) the file under these conditions.</div>
  </div>
  </div>
    
  </div>
  </td><td width="10"><img width="10" height="1" alt="" src="skin/images/spacer.gif"></td>
  </tr>
  <!--================= end Content==================-->
  </table>
  </td>
  </tr>
  </table>
  <!--================= end Menu, NavBar, Content ==================-->
  <!--================= start Footer ==================-->
  <table summary="footer" cellspacing="0" cellpadding="0" width="100%" border="0">
  <tr>
  <td colspan="2" height="1" bgcolor="#4C6C8F"><img height="1" width="1" alt="" src="skin/images/spacer.gif"><a href="skin/images/label.gif"></a><a href="skin/images/page.gif"></a><a href="skin/images/chapter.gif"></a><a href="skin/images/chapter_open.gif"></a><a href="skin/images/current.gif"></a><a href="/favicon.ico"></a></td>
  </tr>
  <tr>
  <td colspan="2" bgcolor="#CFDCED" class="copyright" align="center"><font size="2" face="Arial, Helvetica, Sans-Serif">Copyright &copy;
            1999-2003&nbsp;The Apache Software Foundation. All rights reserved.<script type="text/javascript" language="JavaScript"><!--
                document.write(" - "+"Last Published: " + document.lastModified);
              //  --></script></font></td>
  </tr>
  <tr>
  <td colspan="2" align="left" bgcolor="#CFDCED" class="logos"></td>
  </tr>
  </table>
  <!--================= end Footer ==================-->
  </body>
  </html>
  
  
  
  1.1                  xml-site/targets/fop/hyphenation.pdf
  
  	<<Binary file>>
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/FOPropertySets.html
  
  Index: FOPropertySets.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/FOPropertySets.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.19      +0 -0      xml-site/targets/fop/design/alt.design/FoXMLEvent.html
  
  Index: FoXMLEvent.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/FoXMLEvent.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  
  
  
  1.19      +0 -0      xml-site/targets/fop/design/alt.design/SyncedFoXmlEventsBuffer.html
  
  Index: SyncedFoXmlEventsBuffer.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/SyncedFoXmlEventsBuffer.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  
  
  
  1.19      +0 -0      xml-site/targets/fop/design/alt.design/XMLNamespaces.html
  
  Index: XMLNamespaces.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/XMLNamespaces.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  
  
  
  1.18      +0 -0      xml-site/targets/fop/design/alt.design/codedisplay.js
  
  Index: codedisplay.js
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/codedisplay.js,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/AbstractPropertyValue.html
  
  Index: AbstractPropertyValue.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/AbstractPropertyValue.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/FOAttributes.html
  
  Index: FOAttributes.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/FOAttributes.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/PropNames.html
  
  Index: PropNames.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/PropNames.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/Property.html
  
  Index: Property.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/Property.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/PropertyConsts.html
  
  Index: PropertyConsts.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/PropertyConsts.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/PropertyParser.html
  
  Index: PropertyParser.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/PropertyParser.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/PropertySets.html
  
  Index: PropertySets.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/PropertySets.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/PropertyTokenizer.html
  
  Index: PropertyTokenizer.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/PropertyTokenizer.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/PropertyValue.html
  
  Index: PropertyValue.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/PropertyValue.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/PropertyValueList.html
  
  Index: PropertyValueList.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/PropertyValueList.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.28      +0 -0      xml-site/targets/fop/design/alt.design/properties/ShorthandPropSets.html
  
  Index: ShorthandPropSets.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/ShorthandPropSets.html,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  
  
  
  1.18      +0 -0      xml-site/targets/fop/design/alt.design/properties/codedisplay.js
  
  Index: codedisplay.js
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/design/alt.design/properties/codedisplay.js,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  
  
  
  1.2       +109 -5    xml-site/targets/fop/dev/conventions.html
  
  Index: conventions.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/dev/conventions.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- conventions.html	7 Jul 2003 04:45:19 -0000	1.1
  +++ conventions.html	10 Jul 2003 18:47:18 -0000	1.2
  @@ -273,6 +273,9 @@
   </table>
   <ul class="minitoc">
   <li>
  +<a href="#cvs">CVS Repository</a>
  +</li>
  +<li>
   <a href="#java">Java</a>
   <ul class="minitoc">
   <li>
  @@ -284,14 +287,38 @@
   <li>
   <a href="#java-best-practices">Java Best Practices</a>
   </li>
  +<li>
  +<a href="#java-resources">Resources</a>
  +</li>
  +<li>
  +<a href="#java-links">Related Links</a>
  +</li>
   </ul>
   </li>
  +<li>
  +<a href="#xml">XML</a>
  +</li>
   </ul>
       
  -<a name="N101BE"></a><a name="java"></a>
  +<p>Acknowledgement: Some content in this guide was adapted from other Apache projects such as Avalon, Cactus, Turbine and Velocity.</p>
  +    
  +<a name="N101C1"></a><a name="cvs"></a>
  +<h3>CVS Repository</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>Conventions in this section apply to Repository content, regardless of type:</p>
  +<ul>
  +        
  +<li>Files checked in must conform to the code conventions for that type of file (java files must conform to java requirements, xml to xml requirements, etc.). If a submitted patch does not conform, it is the responsibility of the committer to bring it into conformance before checking it in. Developers submitting patches are encouraged to follow the code conventions to reduce the work load on the the committers.</li>
  +        
  +<li>To reduce the amount of spurious deltas, all text (non-binary) files checked into CVS must have Unix-style line endings (LF only). Many IDEs and editors (even on non-Unix platforms) have settings that can facilitate this convention.</li>
  +      
  +</ul>
  +</div>
  +    
  +<a name="N101D4"></a><a name="java"></a>
   <h3>Java</h3>
   <div style="margin-left: 0 ; border: 2px">
  -<a name="N101C4"></a><a name="java-style"></a>
  +<a name="N101DA"></a><a name="java-style"></a>
   <h4>Java Style</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>In order to facilitate the human reading of FOP source code, the FOP developers have agreed on a set of coding conventions.
  @@ -362,11 +389,19 @@
               <td colspan="1" rowspan="1">checkstyle</td>
             
   </tr>
  +          
  +<tr>
  +            
  +<td colspan="1" rowspan="1">Write appropriate javadoc entries for all public and protected classes, methods, and variables.</td>
  +            <td colspan="1" rowspan="1">Basic API documentation is needed.</td>
  +            <td colspan="1" rowspan="1">checkstyle</td>
  +          
  +</tr>
           
   </table>
   <p>For developers that dislike these conventions, one workaround is to develop using their own style, then use a formatting tool like <a href="http://astyle.sourceforge.net/">astyle</a> (Artistic Style) before committing.</p>
   </div>
  -<a name="N10273"></a><a name="java-checkstyle"></a>
  +<a name="N1029B"></a><a name="java-checkstyle"></a>
   <h4>Checkstyle</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The java syntax checker "<a target="_top" href="http://checkstyle.sourceforge.net">Checkstyle</a>" is used to enforce many of the FOP coding standards.
  @@ -377,7 +412,7 @@
   <p>To use the "checkstyle" target in FOP's build process, download the source from the <a target="_top" href="http://checkstyle.sourceforge.net">Checkstyle web site</a>, place checkstyle-all-*.jar in the lib directory and call "build checkstyle". Output (in the build directory) includes checkstyle_report.txt and checkstyle_report.xml. If you copy the file contrib/checkstyle-noframes.xsl from Checkstyle into FOP's root directory, you will also get an HTML report.</p>
   <p>Checkstyle is probably most useful when integrated into your IDE. See the Checkstyle web site for more information about IDE plugins.</p>
   </div>
  -<a name="N1028E"></a><a name="java-best-practices"></a>
  +<a name="N102B6"></a><a name="java-best-practices"></a>
   <h4>Java Best Practices</h4>
   <div style="margin-left: 0 ; border: 2px">
   <p>The following general principles are a distillation of best practice expectations on the FOP project.</p>
  @@ -401,7 +436,7 @@
   <li>Try to catch exceptions as much as possible and rethrow higher level exceptions (meaning hiding the low level detailed and putting a message that is more related to the function of your code).</li> 
             
   <li>It is important not to lose the stack trace which contains important information.
  -Use chained exception for that. Avalon Framework provides [CascadingException] (and similar) for this.
  +Use chained exception for that. Avalon Framework provides <a target="_top" href="http://jakarta.apache.org/avalon/api/org/apache/avalon/framework/CascadingException.htm">CascadingException</a> (and similar) for this.
   Exception class names and stack traces must be treated like gold.
   Do whatever is required so that this information is not lost.
   Printing error messages to System.err or System.out is useless in a server-side environment where this info is usually lost.</li>
  @@ -412,6 +447,75 @@
           
   </ul>
   </div>
  +<a name="N102E5"></a><a name="java-resources"></a>
  +<h4>Resources</h4>
  +<div style="margin-left: 0 ; border: 2px">
  +<ul>
  +          
  +<li>[book on code style] Code Complete by Steve McConnell.</li>
  +          
  +<li>[code formatting software] <a target="_top" href="http://jrefactory.sourceforge.net">JRefactory</a>.</li>
  +        
  +</ul>
  +</div>
  +<a name="N102F9"></a><a name="java-links"></a>
  +<h4>Related Links</h4>
  +<div style="margin-left: 0 ; border: 2px">
  +<ul>
  +          
  +<li>
  +<a target="_top" href="http://xml.apache.org/source.html">Apache Source Repositories</a>
  +</li>
  +          
  +<li>
  +<a target="_top" href="http://jakarta.apache.org/site/faqs.html#Coding%20Conventions%20and%20Standards">Jakarta Code Conventions and Standards</a> (see Coding Conventions and Standards section)</li>
  +          
  +<li>
  +<a target="_top" href="http://jakarta.apache.org/avalon/code-standards.html">Avalon Project - Coding Standards</a>
  +</li>
  +        
  +</ul>
  +</div>
  +</div>
  +    
  +<a name="N10314"></a><a name="xml"></a>
  +<h3>XML</h3>
  +<div style="margin-left: 0 ; border: 2px">
  +<table class="ForrestTable" cellspacing="1" cellpadding="4">
  +        
  +<tr>
  +          
  +<th colspan="1" rowspan="1">Convention</th>
  +          <th colspan="1" rowspan="1">Rationale</th>
  +          <th colspan="1" rowspan="1">Enforced By</th>
  +        
  +</tr>
  +        
  +<tr>
  +          
  +<td colspan="1" rowspan="1">XML files must always be well-formed. Validation is optional.</td>
  +          <td colspan="1" rowspan="1">Document integrity</td>
  +          <td colspan="1" rowspan="1">Not enforced</td>
  +        
  +</tr>
  +        
  +<tr>
  +          
  +<td colspan="1" rowspan="1">No tabs in content.</td>
  +          <td colspan="1" rowspan="1">Users should not have to adjust tab settings in their editor to be able to read the content.</td>
  +          <td colspan="1" rowspan="1">Not enforced</td>
  +        
  +</tr>
  +        
  +<tr>
  +          
  +<td colspan="1" rowspan="1">Indentation of 2 spaces per level</td>
  +          <td colspan="1" rowspan="1">Maximize readability</td>
  +          <td colspan="1" rowspan="1">Not enforced</td>
  +        
  +</tr>
  +      
  +</table>
   </div>
     
   </div>
  
  
  
  1.2       +356 -165  xml-site/targets/fop/dev/conventions.pdf
  
  	<<Binary file>>
  
  
  1.2       +339 -9    xml-site/targets/fop/dev/rtflib.html
  
  Index: rtflib.html
  ===================================================================
  RCS file: /home/cvs/xml-site/targets/fop/dev/rtflib.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- rtflib.html	7 Jul 2003 04:45:19 -0000	1.1
  +++ rtflib.html	10 Jul 2003 18:47:18 -0000	1.2
  @@ -315,7 +315,8 @@
   <li>Although it is used by FOP to generate FOP's RTF output, it is not dependent on FOP for any of its functionality.</li>
             
   <li>It does not require FOP as a front-end, nor does it even require XSL-FO for input.
  -It can be used anywhere RTF output is required and java is available.</li>
  +It essentially exposes an API of relatively high-level RTF construction routines to a host program.
  +This means it can be used anywhere RTF output is required and java is available.</li>
           
   </ul>
   <p>The FOP development team intends to keep the RTFLib package independent so that it can be used for other purposes.</p>
  @@ -344,7 +345,7 @@
   <div style="margin-left: 0 ; border: 2px">
   <p>Perhaps the easiest way to see how to use RTFLib is by looking at an example. A set of test documents is part of the package, and can be <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/">viewed online</a>.
   A quick look at the Abstract <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/TestDocument.java?rev=HEAD&content-type=text/vnd.viewcvs-markup">TestDocument</a> class, and one of the Concrete subclasses, <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/SimpleDocument.java?rev=HEAD&content-type=text/vnd.viewcvs-markup">SimpleDocument</a> will provide the basics of how to use the package.</p>
  -<p>There are two basic concepts you will need to understand to use RTFLib:</p>
  +<p>There are two basic concepts you will need to understand in order to use RTFLib:</p>
   <ul>
             
   <li>Documents are created by filling bigger containers with successively smaller containers, and eventually with content.</li>
  @@ -361,6 +362,7 @@
   <div class="label">Warning</div>
   <div class="content">This section is very incomplete.</div>
   </div>
  +<p>The documentation in this section is intended to provide a high-level view of the process of building an RTF document. For more detailed API documentation of the various methods, be sure to consult the Javadocs for RTFLib.</p>
   <p>The following table summarizes the various containers that can be created:</p>
   <table class="ForrestTable" cellspacing="1" cellpadding="4">
             
  @@ -377,7 +379,7 @@
               
   <td colspan="1" rowspan="1">Document Area</td>
               <td colspan="1" rowspan="1">RtfFile.startDocumentArea()</td>
  -            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">Information Group, Document Formatting</td>
               <td colspan="1" rowspan="1">Section</td>
             
   </tr>
  @@ -386,8 +388,8 @@
               
   <td colspan="1" rowspan="1">Section</td>
               <td colspan="1" rowspan="1">RtfDocumentArea.newSection()</td>
  -            <td colspan="1" rowspan="1">.</td>
  -            <td colspan="1" rowspan="1">Paragraph</td>
  +            <td colspan="1" rowspan="1">Section Formatting</td>
  +            <td colspan="1" rowspan="1">Paragraph, ParagraphKeepTogether, Image, List, Before (Page Heading), After (Page Footer), JforCmd</td>
             
   </tr>
             
  @@ -395,30 +397,358 @@
               
   <td colspan="1" rowspan="1">Paragraph</td>
               <td colspan="1" rowspan="1">RtfSection.newParagraph()</td>
  -            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">Paragraph Formatting, Character Formatting</td>
               <td colspan="1" rowspan="1">Text</td>
             
   </tr>
             
   <tr>
               
  +<td colspan="1" rowspan="1">ParagraphKeepTogether</td>
  +            <td colspan="1" rowspan="1">RtfSection.newParagraphKeepTogether</td>
  +            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">.</td>
  +          
  +</tr>
  +          
  +<tr>
  +            
  +<td colspan="1" rowspan="1">Image</td>
  +            <td colspan="1" rowspan="1">RtfSection.newImage</td>
  +            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">.</td>
  +          
  +</tr>
  +          
  +<tr>
  +            
  +<td colspan="1" rowspan="1">Table</td>
  +            <td colspan="1" rowspan="1">RtfSection.newTable</td>
  +            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">.</td>
  +          
  +</tr>
  +          
  +<tr>
  +            
  +<td colspan="1" rowspan="1">List</td>
  +            <td colspan="1" rowspan="1">RtfSection.newList</td>
  +            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">.</td>
  +          
  +</tr>
  +          
  +<tr>
  +            
  +<td colspan="1" rowspan="1">Before (Page Heading)</td>
  +            <td colspan="1" rowspan="1">RtfSection.newBefore</td>
  +            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">.</td>
  +          
  +</tr>
  +          
  +<tr>
  +            
  +<td colspan="1" rowspan="1">After (Page Footer)</td>
  +            <td colspan="1" rowspan="1">RtfSection.newAfter</td>
  +            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">.</td>
  +          
  +</tr>
  +          
  +<tr>
  +            
  +<td colspan="1" rowspan="1">JforCmd</td>
  +            <td colspan="1" rowspan="1">RtfSection.newJforCmd</td>
  +            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">.</td>
  +          
  +</tr>
  +          
  +<tr>
  +            
   <td colspan="1" rowspan="1">Text</td>
               <td colspan="1" rowspan="1">RtfParagraph.newText()</td>
  -            <td colspan="1" rowspan="1">.</td>
  +            <td colspan="1" rowspan="1">Character Formatting</td>
               <td colspan="1" rowspan="1">N/A</td>
             
   </tr>
           
   </table>
   </div>
  -<a name="N102B6"></a><a name="userdoc-attributes"></a>
  +<a name="N1035A"></a><a name="userdoc-attributes"></a>
   <h4>Attributes</h4>
   <div style="margin-left: 0 ; border: 2px">
   <div class="frame warning">
   <div class="label">Warning</div>
   <div class="content">This section is very incomplete.</div>
   </div>
  -<p>Attributes can be set for each container and piece of content in the document. The general approach is to build an RtfAttributes object containing the various attributes, then pass that RtfAttributes object to the method that creates the new container or content. The following information lists the various attributes that can be set for each type of container.</p>
  +<p>Attributes can be set for each container and piece of content in the document. The general approach is to build an RtfAttributes object containing the various attributes, then pass that RtfAttributes object to the method that creates the new container or content. See the Javadoc API documentation for RtfAttributes for details on the syntax for creating an RtfAttributes object. The following information lists the various attributes that can be set for each type of container.</p>
  +<a name="N10366"></a><a name="userdoc-attr-ig"></a>
  +<h5>Information Group</h5>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>These attributes are set when creating a Document.</p>
  +</div>
  +<a name="N10370"></a><a name="userdoc-attr-df"></a>
  +<h5>Document Formatting</h5>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>These attributes are set when creating a Document.</p>
  +</div>
  +<a name="N1037A"></a><a name="userdoc-attr-sf"></a>
  +<h5>Section Formatting</h5>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>These attributes are set when creating a Section.</p>
  +</div>
  +<a name="N10384"></a><a name="userdoc-attr-pf"></a>
  +<h5>Paragraph Formatting</h5>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>These attributes are set when creating a Paragraph.</p>
  +<table class="ForrestTable" cellspacing="1" cellpadding="4">
  +            
  +<tr>
  +              
  +<th colspan="1" rowspan="1">Description</th>
  +              <th colspan="1" rowspan="1">Attribute Name</th>
  +              <th colspan="1" rowspan="1">Attribute Value</th>
  +              <th colspan="1" rowspan="1">RTF Control Word</th>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="4" rowspan="1">.</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<th colspan="1" rowspan="1">Alignment</th>
  +              <th colspan="3" rowspan="1">.</th>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Align Left</td>
  +              <td colspan="1" rowspan="1">RtfText.ALIGN_LEFT</td>
  +              <td colspan="1" rowspan="1">N/A (boolean)</td>
  +              <td colspan="1" rowspan="1">\ql</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Align Right</td>
  +              <td colspan="1" rowspan="1">RtfText.ALIGN_RIGHT</td>
  +              <td colspan="1" rowspan="1">N/A (boolean)</td>
  +              <td colspan="1" rowspan="1">\qr</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Align Centered</td>
  +              <td colspan="1" rowspan="1">RtfText.ALIGN_CENTER</td>
  +              <td colspan="1" rowspan="1">N/A (boolean)</td>
  +              <td colspan="1" rowspan="1">\qc</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Align Justified</td>
  +              <td colspan="1" rowspan="1">RtfText.ALIGN_JUSTIFIED</td>
  +              <td colspan="1" rowspan="1">N/A (boolean)</td>
  +              <td colspan="1" rowspan="1">\qj</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Align Distributed</td>
  +              <td colspan="1" rowspan="1">RtfText.ALIGN_DISTRIBUTED</td>
  +              <td colspan="1" rowspan="1">N/A (boolean)</td>
  +              <td colspan="1" rowspan="1">\qd</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Kashida justification</td>
  +              <td colspan="1" rowspan="1">not implemented</td>
  +              <td colspan="1" rowspan="1">0-20 (integer)</td>
  +              <td colspan="1" rowspan="1">\qkN</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Thai Distributed justification</td>
  +              <td colspan="1" rowspan="1">not implemented</td>
  +              <td colspan="1" rowspan="1">N/A (boolean)</td>
  +              <td colspan="1" rowspan="1">\qt</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<th colspan="1" rowspan="1">Indentation</th>
  +              <th colspan="3" rowspan="1">.</th>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Left indent body</td>
  +              <td colspan="1" rowspan="1">RtfText.LEFT_INDENT_BODY</td>
  +              <td colspan="1" rowspan="1">(int) "hundredths of a character unit" (?)</td>
  +              <td colspan="1" rowspan="1">\li</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Left indent first</td>
  +              <td colspan="1" rowspan="1">RtfText.LEFT_INDENT_FIRST</td>
  +              <td colspan="1" rowspan="1">(int) "hundredths of a character unit" (?)</td>
  +              <td colspan="1" rowspan="1">\fi</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<th colspan="1" rowspan="1">Borders</th>
  +              <th colspan="3" rowspan="1">.</th>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Bottom single border</td>
  +              <td colspan="1" rowspan="1">RtfText.BDR_BOTTOM_SINGLE</td>
  +              <td colspan="1" rowspan="1">Boolean?</td>
  +              <td colspan="1" rowspan="1">brdrb\\brsp40\\brdrs</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Bottom double border</td>
  +              <td colspan="1" rowspan="1">RtfText.BDR_BOTTOM_DOUBLE</td>
  +              <td colspan="1" rowspan="1">Boolean?</td>
  +              <td colspan="1" rowspan="1">brdrb\\brsp40\\brdrdb</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Bottom embossed border</td>
  +              <td colspan="1" rowspan="1">RtfText.BDR_BOTTOM_EMBOSS</td>
  +              <td colspan="1" rowspan="1">Boolean?</td>
  +              <td colspan="1" rowspan="1">brdrb\\brsp40\\brdremboss</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">bottom dotted border</td>
  +              <td colspan="1" rowspan="1">RtfText.BDR_BOTTOM_DOTTED</td>
  +              <td colspan="1" rowspan="1">Boolean?</td>
  +              <td colspan="1" rowspan="1">brdrb\\brsp40\\brdrdot</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">bottom dashed border</td>
  +              <td colspan="1" rowspan="1">RtfText.BDR_BOTTOM_DASH</td>
  +              <td colspan="1" rowspan="1">Boolean?</td>
  +              <td colspan="1" rowspan="1">brdrb\\brsp40\\brdrdash</td>
  +            
  +</tr>
  +          
  +</table>
  +</div>
  +<a name="N10519"></a><a name="userdoc-attr-cf"></a>
  +<h5>Character Formatting</h5>
  +<div style="margin-left: 0 ; border: 2px">
  +<p>These attributes are set when creating a Paragraph, or Text.</p>
  +<table class="ForrestTable" cellspacing="1" cellpadding="4">
  +            
  +<tr>
  +              
  +<th colspan="1" rowspan="1">Description</th>
  +              <th colspan="1" rowspan="1">Attribute Name</th>
  +              <th colspan="1" rowspan="1">Attribute Value</th>
  +              <th colspan="1" rowspan="1">RTF Control Word</th>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Bold</td>
  +              <td colspan="1" rowspan="1">RtfText.ATTR_BOLD</td>
  +              <td colspan="1" rowspan="1">N/A (boolean)</td>
  +              <td colspan="1" rowspan="1">\b</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Italic</td>
  +              <td colspan="1" rowspan="1">RtfText.ATTR_ITALIC</td>
  +              <td colspan="1" rowspan="1">N/A (boolean)</td>
  +              <td colspan="1" rowspan="1">\i</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Underline</td>
  +              <td colspan="1" rowspan="1">RtfText.ATTR_UNDERLINE</td>
  +              <td colspan="1" rowspan="1">N/A (boolean), or (int) 0 to turn underlining off</td>
  +              <td colspan="1" rowspan="1">\ul</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Font Size</td>
  +              <td colspan="1" rowspan="1">RtfText.ATTR_FONT_SIZE</td>
  +              <td colspan="1" rowspan="1">(int) font size in half-points</td>
  +              <td colspan="1" rowspan="1">\fs</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Font Family</td>
  +              <td colspan="1" rowspan="1">RtfText.ATTR_FONT_FAMILY</td>
  +              <td colspan="1" rowspan="1">(int) entry in document font-table</td>
  +              <td colspan="1" rowspan="1">\f</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Font Color</td>
  +              <td colspan="1" rowspan="1">RtfText.ATTR_FONT_COLOR</td>
  +              <td colspan="1" rowspan="1">(int) entry in document color-table</td>
  +              <td colspan="1" rowspan="1">\cf</td>
  +            
  +</tr>
  +            
  +<tr>
  +              
  +<td colspan="1" rowspan="1">Background Color</td>
  +              <td colspan="1" rowspan="1">RtfText.ATTR_BACKGROUND_COLOR</td>
  +              <td colspan="1" rowspan="1">(int) entry in document color-table</td>
  +              <td colspan="1" rowspan="1">\chcbpat</td>
  +            
  +</tr>
  +          
  +</table>
  +</div>
   </div>
   </div>
     
  
  
  
  1.2       +524 -215  xml-site/targets/fop/dev/rtflib.pdf
  
  	<<Binary file>>
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: general-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: general-cvs-help@xml.apache.org


Mime
View raw message