xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jerem...@apache.org
Subject svn commit: r735455 [3/3] - in /xmlgraphics/site/deploy/fop: ./ 0.94/ 0.95/ dev/ dev/design/ dev/svg/ trunk/
Date Sun, 18 Jan 2009 13:37:49 GMT
Modified: xmlgraphics/site/deploy/fop/resources.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/resources.xml?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/resources.xml (original)
+++ xmlgraphics/site/deploy/fop/resources.xml Sun Jan 18 05:37:46 2009
@@ -18,7 +18,7 @@
   <header>
     <title>FOP: Other Resources</title>
     <subtitle>Resources useful for developing and using FOP</subtitle>
-    <version>$Revision: 627324 $</version>
+    <version>$Revision: 735448 $</version>
   </header>
   <body>
     <section id="specs">
@@ -190,33 +190,33 @@
         <title>FOP add-ons</title>
         <ul>
           <li>[software] TIFFRenderer is a renderer for outputting multi-page TIFF: <jump href="http://www.tkachenko.com/fop/tiffrenderer.html">http://www.tkachenko.com/fop/tiffrenderer.html</jump> (MPL)</li>
-          <li>[software] AFP Renderer / Batch Assembler for FOP: <jump href="http://mypage.bluewin.ch/huanderegg/">http://mypage.bluewin.ch/huanderegg/</jump> (open source, license unclear)</li>
           <li>[software] The <jump href="http://mogwai.sourceforge.net">Mogwai Project</jump> includes a renderer for FOP that generates output for Okidata dot matrix printers (GPL).</li>
           <li>[software] <jump href="http://barcode4j.sourceforge.net">Barcode4J</jump> (formerly Krysalis Barcode) is a barcode generator which can be used with FOP (Apache license v2.0).</li>
           <li>[software] <jump href="http://jeuclid.sourceforge.net">JEuclid</jump> is a MathML implementation which can be used with FOP (Apache license v2.0).</li>
-          <li>[software] <jump href="http://afp-renderer.sourceforge.net/">AFP Renderer</jump> renders formatted objects to AFP or (MO:DCA).</li>
+          <li>[software] <jump href="http://afp-renderer.sourceforge.net/">AFP Renderer</jump> renders formatted objects to AFP or (MO:DCA). (Has been integrated in FOP)</li>
           <li>[software &amp; tools] <jump href="http://offo.sourceforge.net/">Objects For Formatting Objects</jump> hosts hyphenation patterns and (eventually) files other accessory data files &amp; scripts.</li>
         </ul>        
       </section>
       <section id="products-pdf">
         <title>PDF post-processors</title>
         <ul>
+          <li>[software] <jump href="http://incubator.apache.org/pdfbox">Apache PDFBox</jump> (Incubating, Apache License V2.0)</li>
           <li>[software] <jump href="http://www.lowagie.com/iText">iText</jump> (MPL and LGPL)</li>
           <li>[software] <jump href="http://www.etymon.com/pjc">PJ Classic</jump> by Etymon (GPL)</li>
           <li>[software] <jump href="http://www.etymon.com/pjx">PJ Professional</jump> by Etymon (commercial)</li>
           <li>[software] <jump href="http://www.accesspdf.com/pdftk/">pdftk</jump> the pdf toolkit</li>
-          <li>[software] <jump href="http://www.pdfbox.org">PDFBox</jump> (BSD)</li>
         </ul>
       </section>
       <section id="products-editors">
         <title>XSL-FO editors</title>
         <ul>
           <li>[software] <jump href="http://foa.sourceforge.net/">FOA (Formatting Objects Authoring)</jump> (MPL)</li>
-          <li>[software] <jump href="http://www.scruffyware.com/products/foeditor/">FOEditor</jump> by Scruffy Software (Shareware)</li>
+          <!--infected website
+            <li>[software] <jump href="http://www.scruffyware.com/products/foeditor/">FOEditor</jump> by Scruffy Software (Shareware)</li>
+          -->
           <li>[software] <jump href="http://www.scriptura-xsl.com">Scriptura</jump> by Inventive Designers (commercial)</li>
           <li>[software] <jump href="http://www.xslfast.com">XSLfast</jump> by jCatalog Software AG (commercial)</li>
           <li>[software] <jump href="http://www.digiforms.com/">DIGIFORMS Document Designer</jump> by Metafocus (commercial)</li>
-          <li>[software] <jump href="http://web.assentis.com/products/products.php?navi=Products&amp;product_id=7">Assentis:DocDesign</jump> by Assentis Technologies (commercial)</li>
         </ul>
       </section>
       <section id="products-other">
@@ -224,6 +224,7 @@
         <ul>
           <li>[software] <jump href="http://foray.sourceforge.net/">FOray</jump> a renderer for converting XML files to PDF via XSL Formatting Object elements (FOP fork)</li>
           <li>[software] <jump href="http://defoe.sourceforge.net/folio">Folio</jump> a renderer for XML files containing Formatting Object elements (aka FOP Alt.Design)</li>
+          <li>[software] <jump href="http://xmlroff.org/">xmlroff</jump> an open source XSL-FO implementation written in C (BSD-style license)</li>
 
           <li>[commercial software developer] <jump href="http://antennahouse.com/product.htm">Antenna House</jump> - XSL Formatter, WordMLToFo, XML Editor...</li>
           <li>[commercial software developer] <jump href="http://www.renderx.net/">RenderX</jump> XEP, EnMasse, Docbench...</li>
@@ -238,10 +239,6 @@
           is the most obvious language it would be used for. The tool has a number of
           page-related extensions. It also comes with an API in the form of an XML
           filter (OSI-Approved Open Source - Public Domain).</li>
-          <li> [software] <jump href="http://www.vbxml.com/xpathvisualizer">The XPath Visualizer</jump>.
-Web site says: "This is a full blown Visual XPath Interpreter for the evaluation of any XPath expression and visual presentation of the resulting nodeset or scalar value."
-Requires Internet Explorer 5+.
-(freeware)</li>
           <li>
             [software] <jump href="http://www.ahmadsoft.org/fopbridge.html">FOP Bridge</jump> is an Eclipse plug-in
             that allows to convert FO documents using Apache FOP directly inside the Eclipse workbench (LGPL).

Modified: xmlgraphics/site/deploy/fop/status.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/status.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/status.pdf (original) and xmlgraphics/site/deploy/fop/status.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/team.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/team.html?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/team.html (original)
+++ xmlgraphics/site/deploy/fop/team.html Sun Jan 18 05:37:46 2009
@@ -459,7 +459,7 @@
 </div>
   
 <span class="version">
-          version 682625</span>
+          version 735451</span>
 </div>
 <!--+
     |end content

Modified: xmlgraphics/site/deploy/fop/team.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/team.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/team.pdf (original) and xmlgraphics/site/deploy/fop/team.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/team.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/team.xml?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/team.xml (original)
+++ xmlgraphics/site/deploy/fop/team.xml Sun Jan 18 05:37:46 2009
@@ -17,7 +17,7 @@
 <document>
   <header>
     <title>FOP: Development Team</title>
-    <version>$Revision: 682625 $</version>
+    <version>$Revision: 735451 $</version>
   </header>
   <body>
     <p>

Modified: xmlgraphics/site/deploy/fop/trunk/anttask.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/anttask.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/anttask.pdf (original) and xmlgraphics/site/deploy/fop/trunk/anttask.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/compiling.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/compiling.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/compiling.pdf (original) and xmlgraphics/site/deploy/fop/trunk/compiling.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/configuration.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/configuration.html?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/configuration.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/configuration.html Sun Jan 18 05:37:46 2009
@@ -224,6 +224,9 @@
 <li>
 <a href="#pcl-renderer">Special Settings for the PCL Renderer</a>
 </li>
+<li>
+<a href="#afp-renderer">Special Settings for the AFP Renderer</a>
+</li>
 </ul>
 </li>
 <li>
@@ -619,10 +622,35 @@
         If the mix of painting methods results in unwelcome output, you can set this
         to "bitmap" which causes all text to be rendered as bitmaps.
       </p>
+<a name="N101E6"></a><a name="afp-renderer"></a>
+<h3 class="underlined_5">Special Settings for the AFP Renderer</h3>
+<p>
+      
+</p>
+<p>
+        Additionally, there are certain settings that control how the renderer handles various elements.
+      </p>
+<pre class="code">&lt;renderer mime="application/x-afp"&gt;
+  &lt;images mode="b+w" bits-per-pixel="8" native="true"/&gt;
+  &lt;renderer-resolution&gt;240&lt;/renderer-resolution&gt;
+  
+  &lt;!-- a default external resource group file --&gt;
+  &lt;resource-group-file&gt;resources.afp&lt;/resource-group-file&gt;
+&lt;/renderer&gt;</pre>
+<p>
+        The default value for the images "mode" setting is "b+w" (black and white).  When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process.  With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. 
+        When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form.  When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.
+      </p>
+<p>
+        The default value for the "renderer-resolution" is 240 dpi. 
+      </p>
+<p>
+        By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp. 
+      </p>
 </div>
 
         
-<a name="N101E7"></a><a name="When+it+does+not+work"></a>
+<a name="N10203"></a><a name="When+it+does+not+work"></a>
 <h2 class="underlined_10">When it does not work</h2>
 <div class="section">
 <p>FOP searches the configuration file for the information it
@@ -665,7 +693,7 @@
 </div>
   
 <span class="version">
-          version 674471</span>
+          version 721430</span>
 </div>
 <!--+
     |end content

Modified: xmlgraphics/site/deploy/fop/trunk/configuration.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/configuration.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/configuration.pdf (original) and xmlgraphics/site/deploy/fop/trunk/configuration.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/configuration.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/configuration.xml?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/configuration.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/configuration.xml Sun Jan 18 05:37:46 2009
@@ -17,7 +17,7 @@
 <document>
   <header>
     <title>Apache FOP: Configuration</title>
-    <version>$Revision: 674471 $</version>
+    <version>$Revision: 721430 $</version>
   </header>
 
   <body>
@@ -365,6 +365,36 @@
         to "bitmap" which causes all text to be rendered as bitmaps.
       </p>
     </section>
+    <section id="afp-renderer">
+      <title>Special Settings for the AFP Renderer</title>
+      <p>
+      </p>
+      <p>
+        Additionally, there are certain settings that control how the renderer handles various elements.
+      </p>
+<source xml:space="preserve"><![CDATA[<renderer mime="application/x-afp">
+  <images mode="b+w" bits-per-pixel="8" native="true"/>
+  <renderer-resolution>240</renderer-resolution>
+  
+  <!-- a default external resource group file -->
+  <resource-group-file>resources.afp</resource-group-file>
+</renderer>]]></source>
+      <p>
+        The default value for the images "mode" setting is "b+w" (black and white).  When the images "mode" setting is "b+w" a "bits-per-pixel" setting can be provided to aid the grayscale conversion process.  With this setting all images referenced in your source document are converted to an IOCA FS45 grayscale bitmap image form. 
+        When the setting is "color" all images are converted to an IOCA FS45 color bitmap image form.  When "native" setting is "true", all images encountered (TIFF, GIF, JPEG and Encapsulated Postscript etc.) will be embedded directly in the datastream in their native form using a MO:DCA Object Container.
+      </p>
+      <p>
+        The default value for the "renderer-resolution" is 240 dpi. 
+      </p>
+ <!--
+      <p>
+        The default value for the MO:DCA "interchange-set" is "MO:DCA-L". Other compliance settings include presentation interchange sets "MO:DCA-P IS/1" and "MO:DCA-P IS/2" (Resource Groups). 
+      </p>
+ -->
+      <p>
+        By default if there is no configuration definition for "resource-group-file", external resources will be placed in a file called resources.afp. 
+      </p>
+    </section>
   </section>
 
         <section>

Modified: xmlgraphics/site/deploy/fop/trunk/embedding.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/embedding.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/embedding.pdf (original) and xmlgraphics/site/deploy/fop/trunk/embedding.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/events.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/events.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Binary files - no diff available.

Modified: xmlgraphics/site/deploy/fop/trunk/extensions.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/extensions.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/extensions.pdf (original) and xmlgraphics/site/deploy/fop/trunk/extensions.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/fonts.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/fonts.html?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/fonts.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/fonts.html Sun Jan 18 05:37:46 2009
@@ -208,7 +208,10 @@
 <a href="#Base-14+Fonts">Base-14 Fonts</a>
 </li>
 <li>
-<a href="#Missing+Fonts">Missing Fonts</a>
+<a href="#missing-fonts">Missing Fonts</a>
+</li>
+<li>
+<a href="#missing-glyphs">Missing Glyphs</a>
 </li>
 <li>
 <a href="#awt">Java2D/AWT/Operating System Fonts</a>
@@ -387,6 +390,54 @@
         Symbol and ZapfDingbats.
       </p>
 <p>
+        The following font family names are hard-coded into FOP for the Base-14 font set:
+      </p>
+<table class="ForrestTable" cellspacing="1" cellpadding="4">
+        
+<tr>
+          
+<th colspan="1" rowspan="1">Base-14 font</th>
+          <th colspan="1" rowspan="1">font families</th>
+        
+</tr>
+        
+<tr>
+          
+<td colspan="1" rowspan="1">Helvetica</td>
+          <td colspan="1" rowspan="1">Helvetica, sans-serif, SansSerif</td>
+        
+</tr>
+        
+<tr>
+          
+<td colspan="1" rowspan="1">Times</td>
+          <td colspan="1" rowspan="1">Times, Times Roman, Times-Roman, serif, any</td>
+        
+</tr>
+        
+<tr>
+          
+<td colspan="1" rowspan="1">Courier</td>
+          <td colspan="1" rowspan="1">Courier, monospace, Monospaced</td>
+        
+</tr>
+        
+<tr>
+          
+<td colspan="1" rowspan="1">Symbol</td>
+          <td colspan="1" rowspan="1">Symbol</td>
+        
+</tr>
+        
+<tr>
+          
+<td colspan="1" rowspan="1">ZapfDingbats</td>
+          <td colspan="1" rowspan="1">ZapfDingbats</td>
+        
+</tr>
+      
+</table>
+<p>
         Please note that recent versions of Adobe Acrobat Reader replace
         "Helvetica" with "Arial" and "Times" with "Times New Roman" internally.
         GhostScript replaces "Helvetica" with "Nimbus Sans L" and "Times" with 
@@ -397,7 +448,7 @@
       </p>
 </div>
     
-<a name="N1015A"></a><a name="Missing+Fonts"></a>
+<a name="N101AE"></a><a name="missing-fonts"></a>
 <h2 class="underlined_10">Missing Fonts</h2>
 <div class="section">
 <p>
@@ -408,7 +459,23 @@
       </p>
 </div>
     
-<a name="N10164"></a><a name="awt"></a>
+<a name="N101B8"></a><a name="missing-glyphs"></a>
+<h2 class="underlined_10">Missing Glyphs</h2>
+<div class="section">
+<p>
+        Every font contains a particular set of
+        <a class="external" href="http://en.wikipedia.org/wiki/Glyph">glyphs</a>. If no glyph can be found for
+        a given character, FOP will issue a warning and use the glpyh for "#" (if available)
+        instead. Before it does that, it consults a (currently hard-coded) registry of
+        glyph substitution groups (see Glyphs.java in Apache XML Graphics Commons).
+        This registry can supply alternative glyphs in some cases (like using space when a no-break
+        space is requested). But there's no guarantee that the result will be as expected (for
+        example, in the case of hyphens and similar glyphs). A better way is to use a font that
+        has all the necessary glyphs. This glyph substitution is only a last resort.
+      </p>
+</div>
+    
+<a name="N101C6"></a><a name="awt"></a>
 <h2 class="underlined_10">Java2D/AWT/Operating System Fonts</h2>
 <div class="section">
 <p>
@@ -425,7 +492,7 @@
       </p>
 </div>
     
-<a name="N10171"></a><a name="custom"></a>
+<a name="N101D3"></a><a name="custom"></a>
 <h2 class="underlined_10">Custom Fonts</h2>
 <div class="section">
 <p>
@@ -462,7 +529,7 @@
 </ul>
 </div>
     
-<a name="N10196"></a><a name="basics"></a>
+<a name="N101F8"></a><a name="basics"></a>
 <h2 class="underlined_10">Basic font configuration</h2>
 <div class="section">
 <p>
@@ -498,7 +565,7 @@
 </div>
 </div>
     
-<a name="N101AB"></a><a name="advanced"></a>
+<a name="N1020D"></a><a name="advanced"></a>
 <h2 class="underlined_10">Advanced font configuration</h2>
 <div class="section">
 <p>
@@ -506,7 +573,7 @@
         additional instructions in case the basic font configuration doesn't lead to
         the desired results.
       </p>
-<a name="N101B4"></a><a name="type1-metrics"></a>
+<a name="N10216"></a><a name="type1-metrics"></a>
 <h3 class="underlined_5">Type 1 Font Metrics</h3>
 <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>
@@ -540,7 +607,7 @@
           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>
-<a name="N101DD"></a><a name="truetype-metrics"></a>
+<a name="N1023F"></a><a name="truetype-metrics"></a>
 <h3 class="underlined_5">TrueType Font Metrics</h3>
 <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.
@@ -607,7 +674,7 @@
           the so-called Unicode "cmap" table. TTFReader can currently not deal with font like this.
         </div>
 </div>
-<a name="N10242"></a><a name="truetype-collections-metrics"></a>
+<a name="N102A4"></a><a name="truetype-collections-metrics"></a>
 <h3 class="underlined_5">TrueType Collections Font Metrics</h3>
 <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>
@@ -622,7 +689,7 @@
           using the "sub-font" attribute on the "font" element. That means that generating
           an XML font metrics file for TrueType collections is not necessary anymore.
         </p>
-<a name="N10259"></a><a name="register"></a>
+<a name="N102BB"></a><a name="register"></a>
 <h3 class="underlined_5">Register Fonts with FOP</h3>
 <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">
@@ -630,7 +697,9 @@
    &lt;renderer mime="application/pdf"&gt;
       &lt;fonts&gt;
          &lt;!-- register a particular font --&gt;
-         &lt;font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes" embed-url="file:///C:/myfonts/FTL_____.pfb"&gt;
+         &lt;font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes"
+           embed-url="file:///C:/myfonts/FTL_____.pfb"
+           encoding-mode="single-byte"&gt;
             &lt;font-triplet name="FrutigerLight" style="normal" weight="normal"/&gt;
          &lt;/font&gt;
   
@@ -663,6 +732,19 @@
           
 <li>When setting the "embed-url" attribute for Type 1 fonts, be sure to specify the PFB (actual font data), not PFM (font metrics) file that you used to generate the XML font metrics file.</li>
           
+<li>The attribute "encoding-mode" is optional an may have the following values:
+            <ul>
+              
+<li>auto: default font encoding mode ("cid" for Truetype, "single-byte" for Type 1)</li>
+              
+<li>single-byte: use single-byte encodings in the target format (if applicable)</li>
+              
+<li>cid: encode as CID-keyed font (currently only supported for PDF output with TrueType fonts)</li>
+            
+</ul>
+          
+</li>
+          
 <li>The fonts "directory" tag can be used to register fonts contained within a single or list of directory paths.  The "recursive" attribute can be specified to recursively add fonts from all sub directories.</li>
           
 <li>The fonts "auto-detect" tag can be used to automatically register fonts that are found to be installed on the native operating system.</li>
@@ -678,7 +760,7 @@
           </li>
         
 </ul>
-<a name="N10295"></a><a name="autodetect"></a>
+<a name="N10306"></a><a name="autodetect"></a>
 <h3 class="underlined_5">Auto-Detect and auto-embed feature</h3>
 <p>When the "auto-detect" flag is set in the configuration, FOP will automatically search for fonts in the default paths for your operating system.</p>
 <p>FOP will also auto-detect fonts which are available in the classpath, if they are described as "application/x-font" in the MANIFEST.MF file. For example, if your .jar file contains font/myfont.ttf:</p>
@@ -687,7 +769,7 @@
           Name: font/myfont.ttf
           Content-Type: application/x-font</pre>
 <p>This feature allows you to create JAR files containing fonts. The JAR files can be added to fop by providem them in the classpath, e.g. copying them into the lib/ directory.</p>
-<a name="N102A9"></a><a name="embedding"></a>
+<a name="N1031A"></a><a name="embedding"></a>
 <h3 class="underlined_5">Embedding</h3>
 <p>
           By default, all fonts are embedded if an output format supports font embedding. In some
@@ -748,7 +830,7 @@
           original font, containing only the glyphs used, is embedded in the output document.</li>
         
 </ul>
-<a name="N102E4"></a><a name="substitution"></a>
+<a name="N10355"></a><a name="substitution"></a>
 <h3 class="underlined_5">Substitution</h3>
 <p>When a &lt;substitutions/&gt; section is defined in the configuration, FOP will re-map any font-family references found in your FO input to a given substitution font.</p>
 <ul>
@@ -776,7 +858,7 @@
 &lt;/fop&gt;</pre>
 </div>
     
-<a name="N10301"></a><a name="selection"></a>
+<a name="N10372"></a><a name="selection"></a>
 <h2 class="underlined_10">Font Selection Strategies</h2>
 <div class="section">
 <p>
@@ -800,7 +882,7 @@
 <font size="-2">by&nbsp;Jeremias M&auml;rki,&nbsp;Tore Engvig,&nbsp;Adrian Cumiskey,&nbsp;Max Berger</font>
 </p>
 <span class="version">
-          version 661310</span>
+          version 731248</span>
 </div>
 <!--+
     |end content

Modified: xmlgraphics/site/deploy/fop/trunk/fonts.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/fonts.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/fonts.pdf (original) and xmlgraphics/site/deploy/fop/trunk/fonts.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/fonts.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/fonts.xml?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/fonts.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/fonts.xml Sun Jan 18 05:37:46 2009
@@ -17,7 +17,7 @@
 <document>
   <header>
     <title>Apache FOP: Fonts</title>
-    <version>$Revision: 661310 $</version>
+    <version>$Revision: 731248 $</version>
     <authors>
       <person name="Jeremias Märki" email=""/>
       <person name="Tore Engvig" email=""/>
@@ -127,6 +127,35 @@
         Symbol and ZapfDingbats.
       </p>
       <p>
+        The following font family names are hard-coded into FOP for the Base-14 font set:
+      </p>
+      <table>
+        <tr>
+          <th colspan="1" rowspan="1">Base-14 font</th>
+          <th colspan="1" rowspan="1">font families</th>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">Helvetica</td>
+          <td colspan="1" rowspan="1">Helvetica, sans-serif, SansSerif</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">Times</td>
+          <td colspan="1" rowspan="1">Times, Times Roman, Times-Roman, serif, any</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">Courier</td>
+          <td colspan="1" rowspan="1">Courier, monospace, Monospaced</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">Symbol</td>
+          <td colspan="1" rowspan="1">Symbol</td>
+        </tr>
+        <tr>
+          <td colspan="1" rowspan="1">ZapfDingbats</td>
+          <td colspan="1" rowspan="1">ZapfDingbats</td>
+        </tr>
+      </table>
+      <p>
         Please note that recent versions of Adobe Acrobat Reader replace
         "Helvetica" with "Arial" and "Times" with "Times New Roman" internally.
         GhostScript replaces "Helvetica" with "Nimbus Sans L" and "Times" with 
@@ -136,7 +165,7 @@
         the target document.
       </p>
     </section>
-    <section>
+    <section id="missing-fonts">
       <title>Missing Fonts</title>
       <p>
         When FOP does not have a specific font at its disposal (because it's 
@@ -145,6 +174,20 @@
         Base-14 font "Times" (see above).
       </p>
     </section>
+    <section id="missing-glyphs">
+      <title>Missing Glyphs</title>
+      <p>
+        Every font contains a particular set of
+        <link href="http://en.wikipedia.org/wiki/Glyph">glyphs</link>. If no glyph can be found for
+        a given character, FOP will issue a warning and use the glpyh for "#" (if available)
+        instead. Before it does that, it consults a (currently hard-coded) registry of
+        glyph substitution groups (see Glyphs.java in Apache XML Graphics Commons).
+        This registry can supply alternative glyphs in some cases (like using space when a no-break
+        space is requested). But there's no guarantee that the result will be as expected (for
+        example, in the case of hyphens and similar glyphs). A better way is to use a font that
+        has all the necessary glyphs. This glyph substitution is only a last resort.
+      </p>
+    </section>
     <section id="awt">
       <title>Java2D/AWT/Operating System Fonts</title>
       <p>
@@ -321,7 +364,9 @@
    <renderer mime="application/pdf">
       <fonts>
          <!-- register a particular font -->
-         <font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes" embed-url="file:///C:/myfonts/FTL_____.pfb">
+         <font metrics-url="file:///C:/myfonts/FTL_____.xml" kerning="yes"
+           embed-url="file:///C:/myfonts/FTL_____.pfb"
+           encoding-mode="single-byte">
             <font-triplet name="FrutigerLight" style="normal" weight="normal"/>
          </font>
   
@@ -347,6 +392,13 @@
           <li>The font "kerning" attribute is optional. Default is "true".</li>
           <li>If embedding is off (i.e. embed-url is not set), the output will position the text correctly (from the metrics file), but it will not be displayed or printed correctly unless the viewer has the applicable font available to their local system.</li>
           <li>When setting the "embed-url" attribute for Type 1 fonts, be sure to specify the PFB (actual font data), not PFM (font metrics) file that you used to generate the XML font metrics file.</li>
+          <li>The attribute "encoding-mode" is optional an may have the following values:
+            <ul>
+              <li>auto: default font encoding mode ("cid" for Truetype, "single-byte" for Type 1)</li>
+              <li>single-byte: use single-byte encodings in the target format (if applicable)</li>
+              <li>cid: encode as CID-keyed font (currently only supported for PDF output with TrueType fonts)</li>
+            </ul>
+          </li>
           <li>The fonts "directory" tag can be used to register fonts contained within a single or list of directory paths.  The "recursive" attribute can be specified to recursively add fonts from all sub directories.</li>
           <li>The fonts "auto-detect" tag can be used to automatically register fonts that are found to be installed on the native operating system.</li>
           <li>Fonts registered with "font" tag configurations override fonts found by means of "directory" tag definitions.</li>

Modified: xmlgraphics/site/deploy/fop/trunk/graphics.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/graphics.html?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/graphics.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/graphics.html Sun Jan 18 05:37:46 2009
@@ -263,6 +263,9 @@
 <a href="#svg-pdf-text">Placing SVG Text into PDF and PostScript</a>
 </li>
 <li>
+<a href="#svg-font-selection">Font selection notes</a>
+</li>
+<li>
 <a href="#svg-scaling">Scaling</a>
 </li>
 <li>
@@ -775,7 +778,7 @@
             be controlled through the "target resolution" setting in the 
             <a href="configuration.html">configuration</a>.</p>
 <p>
-            Currently transparency is limited in PDF so many SVG images that
+            Currently transparency is limited in PDF so some SVG images that
             contain effects or graphics with transparent areas may not be displayed
             correctly.
           </p>
@@ -784,11 +787,15 @@
 <p>If possible, Batik will use normal PDF or PostScript text when inserting text. It does
             this by checking if the text can be drawn normally and the font is
             supported. This example svg <a href="../dev/svg/text.svg">text.svg</a> /
-            <!--link href="../dev/svg/text.pdf"-->text.pdf<!--/link-->
+            <a href="../dev/svg/text.pdf">text.pdf</a> / <a href="../dev/svg/text.png">text.png</a>
             shows how various types and effects with text are handled.
-            Note that tspan and outlined text are not yet implemented.</p>
+            Note that SVG font support is not yet implemented. Furthermore, text handling in
+            PostScript output is inferior to PDF output - more text will be painted as shapes in
+            PS than in PDF.
+          </p>
 <p>
-            Otherwise, text is converted and drawn as a set of shapes by Batik, using the
+            When there's no support to paint text using native text operations,
+            text is converted and drawn as a set of shapes by Batik, using the
             stroking text painter. This means that a typical character will
             have about 10 curves (each curve consists of at least 20 characters).
             This can make the output files large and when it is viewed the
@@ -804,8 +811,30 @@
             "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>
-<a name="N10430"></a><a name="svg-scaling"></a>
+            any case, but will only affect the quality of the screen display.
+          </p>
+<a name="N10434"></a><a name="svg-font-selection"></a>
+<h4>Font selection notes</h4>
+<p>
+            Apache Batik uses the AWT/Java2D subsystem as font source while FOP has its on font
+            subsystem. Great care has been taken that font selection does the best possible choices.
+            But it must be noted when creating PDF or PostScript that a font used in SVG graphics
+            needs to be registered with the operating system as well as in FOP's configuration.
+            By using FOP's font auto-detection, you simply have to install the font in the operating
+            system and not care about anything else. This is less of an issue if you create
+            formats like TIFFs, PNGs or PCL because in these cases SVG graphics are usually rendered
+            to bitmaps which means that on both sides (Batik and FOP), AWT/Java2D is used as the
+            single font source.
+          </p>
+<p>
+            Whenever an SVG is converted into a PDF or PostScript file, the font that has been used
+            inside Batik has to be mapped to a font used by the actual output format. Features like
+            font substitution in FOP may need to be taken into account but can also be an advantage
+            when working around font mapping issues. Like for XSL-FO content, you'll get a warning
+            if a particular font could not be found and had to be substituted, or if a particular
+            glyph is missing in a font.
+          </p>
+<a name="N10441"></a><a name="svg-scaling"></a>
 <h4>Scaling</h4>
 <p>
             Currently, SVG images are rendered with the dimensions specified <em>in the SVG 
@@ -820,7 +849,7 @@
             size of a pixel. The use of pixels to specify sizes is discouraged as they may
             be interpreted differently in different environments.
           </p>
-<a name="N10444"></a><a name="svg-problems"></a>
+<a name="N10455"></a><a name="svg-problems"></a>
 <h4>Known Problems</h4>
 <ul>
             
@@ -846,7 +875,7 @@
             </li>
           
 </ul>
-<a name="N1045B"></a><a name="tiff"></a>
+<a name="N1046C"></a><a name="tiff"></a>
 <h3 class="underlined_5">TIFF</h3>
 <p>
           FOP can embed TIFF images without decompression into PDF, PostScript and AFP if they
@@ -856,7 +885,7 @@
 <p>
           There may be some limitation concerning images in the CMYK color space.
         </p>
-<a name="N10468"></a><a name="wmf"></a>
+<a name="N10479"></a><a name="wmf"></a>
 <h3 class="underlined_5">WMF</h3>
 <p>
           Windows Metafiles (WMF) are supported through classes in 
@@ -865,7 +894,7 @@
         </p>
 </div>
     
-<a name="N10477"></a><a name="resolution"></a>
+<a name="N10488"></a><a name="resolution"></a>
 <h2 class="underlined_10">Graphics Resolution</h2>
 <div class="section">
 <p>
@@ -890,7 +919,7 @@
       </p>
 </div>
     
-<a name="N1048B"></a><a name="page-selection"></a>
+<a name="N1049C"></a><a name="page-selection"></a>
 <h2 class="underlined_10">Page selection for multi-page formats</h2>
 <div class="section">
 <p>
@@ -901,7 +930,7 @@
       </p>
 </div>
     
-<a name="N10498"></a><a name="caching"></a>
+<a name="N104A9"></a><a name="caching"></a>
 <h2 class="underlined_10">Image caching</h2>
 <div class="section">
 <p>
@@ -912,14 +941,19 @@
         changing dummy parameter on the URI to avoid caching.
       </p>
 <p>
-        The image cache has been improved considerably in the redesigned code. Therefore, a 
-        resetCache() method like in earlier versions of FOP has become unnecessary. If you 
+        The image cache has been improved considerably in the redesigned code. Therefore,
+        resetting the image cache should be a thing of the past. If you 
         still experience OutOfMemoryErrors, please notify us.
       </p>
+<p>
+        If all else fails, the image cache can be cleared like this:
+        <span class="codefrag">fopFactory.getImageManager().getCache().clearCache();</span>
+      
+</p>
 </div>
   
 <span class="version">
-          version 652581</span>
+          version 722132</span>
 </div>
 <!--+
     |end content

Modified: xmlgraphics/site/deploy/fop/trunk/graphics.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/graphics.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/graphics.pdf (original) and xmlgraphics/site/deploy/fop/trunk/graphics.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/graphics.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/graphics.xml?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/graphics.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/graphics.xml Sun Jan 18 05:37:46 2009
@@ -17,7 +17,7 @@
 <document>
   <header>
     <title>Apache FOP: Graphics Formats</title>
-    <version>$Revision: 652581 $</version>
+    <version>$Revision: 722132 $</version>
   </header>
   <body>
     <section id="introduction">
@@ -418,7 +418,7 @@
             be controlled through the "target resolution" setting in the 
             <link href="configuration.html">configuration</link>.</p>
           <p>
-            Currently transparency is limited in PDF so many SVG images that
+            Currently transparency is limited in PDF so some SVG images that
             contain effects or graphics with transparent areas may not be displayed
             correctly.
           </p>
@@ -428,11 +428,15 @@
           <p>If possible, Batik will use normal PDF or PostScript text when inserting text. It does
             this by checking if the text can be drawn normally and the font is
             supported. This example svg <link href="../dev/svg/text.svg">text.svg</link> /
-            <!--link href="../dev/svg/text.pdf"-->text.pdf<!--/link-->
+            <link href="../dev/svg/text.pdf">text.pdf</link> / <link href="../dev/svg/text.png">text.png</link>
             shows how various types and effects with text are handled.
-            Note that tspan and outlined text are not yet implemented.</p>
+            Note that SVG font support is not yet implemented. Furthermore, text handling in
+            PostScript output is inferior to PDF output - more text will be painted as shapes in
+            PS than in PDF.
+          </p>
           <p>
-            Otherwise, text is converted and drawn as a set of shapes by Batik, using the
+            When there's no support to paint text using native text operations,
+            text is converted and drawn as a set of shapes by Batik, using the
             stroking text painter. This means that a typical character will
             have about 10 curves (each curve consists of at least 20 characters).
             This can make the output files large and when it is viewed the
@@ -448,7 +452,30 @@
             "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>
+            any case, but will only affect the quality of the screen display.
+          </p>
+        </section>
+        <section id="svg-font-selection">
+          <title>Font selection notes</title>
+          <p>
+            Apache Batik uses the AWT/Java2D subsystem as font source while FOP has its on font
+            subsystem. Great care has been taken that font selection does the best possible choices.
+            But it must be noted when creating PDF or PostScript that a font used in SVG graphics
+            needs to be registered with the operating system as well as in FOP's configuration.
+            By using FOP's font auto-detection, you simply have to install the font in the operating
+            system and not care about anything else. This is less of an issue if you create
+            formats like TIFFs, PNGs or PCL because in these cases SVG graphics are usually rendered
+            to bitmaps which means that on both sides (Batik and FOP), AWT/Java2D is used as the
+            single font source.
+          </p>
+          <p>
+            Whenever an SVG is converted into a PDF or PostScript file, the font that has been used
+            inside Batik has to be mapped to a font used by the actual output format. Features like
+            font substitution in FOP may need to be taken into account but can also be an advantage
+            when working around font mapping issues. Like for XSL-FO content, you'll get a warning
+            if a particular font could not be found and had to be substituted, or if a particular
+            glyph is missing in a font.
+          </p> 
         </section>
         <section id="svg-scaling">
           <title>Scaling</title>
@@ -551,10 +578,14 @@
         changing dummy parameter on the URI to avoid caching.
       </p>
       <p>
-        The image cache has been improved considerably in the redesigned code. Therefore, a 
-        resetCache() method like in earlier versions of FOP has become unnecessary. If you 
+        The image cache has been improved considerably in the redesigned code. Therefore,
+        resetting the image cache should be a thing of the past. If you 
         still experience OutOfMemoryErrors, please notify us.
       </p>
+      <p>
+        If all else fails, the image cache can be cleared like this:
+        <code>fopFactory.getImageManager().getCache().clearCache();</code>
+      </p>
     </section>
   </body>
 </document>

Modified: xmlgraphics/site/deploy/fop/trunk/hyphenation.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/hyphenation.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/hyphenation.pdf (original) and xmlgraphics/site/deploy/fop/trunk/hyphenation.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/index.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/index.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/index.pdf (original) and xmlgraphics/site/deploy/fop/trunk/index.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/intermediate.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/intermediate.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/intermediate.pdf (original) and xmlgraphics/site/deploy/fop/trunk/intermediate.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/metadata.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/metadata.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Binary files - no diff available.

Modified: xmlgraphics/site/deploy/fop/trunk/output.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/output.html?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/output.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/output.html Sun Jan 18 05:37:46 2009
@@ -283,6 +283,9 @@
 <li>
 <a href="#afp-image-config">Images</a>
 </li>
+<li>
+<a href="#afp-resource-group-file">Resource Group File</a>
+</li>
 </ul>
 </li>
 <li>
@@ -302,6 +305,14 @@
 </li>
 </ul>
 </li>
+<li>
+<a href="#afp-foreign-attributes">Foreign Attributes</a>
+<ul class="minitoc">
+<li>
+<a href="#afp-foreign-attributes-resource">Resource</a>
+</li>
+</ul>
+</li>
 </ul>
 </li>
 <li>
@@ -993,17 +1004,36 @@
 <a name="N10221"></a><a name="afp-image-config"></a>
 <h4>Images</h4>
 <p>By default the AFP Renderer converts all images to 8 bit grey level.
-        This can be overridden by the &lt;images&gt; configuration element. Example:</p>
+        This can be overridden by the &lt;images/&gt; configuration element. Example:</p>
 <pre class="code">
       &lt;images mode="color" /&gt;
 </pre>
 <p>This will put images as RGB images into the AFP output stream. The default setting is:</p>
 <pre class="code">
-      &lt;images mode="b+w" bits-per-pixel="8" /&gt;
+      &lt;images mode="b+w" bits-per-pixel="8" native="true"/&gt;
+</pre>
+<p>Only the values "color" and "b+w" are allowed for the mode attribute.</p>
+<p>The bits-per-pixel attribute is ignored if mode is "color". For "b+w" mode is must be 1, 4, or 8.</p>
+<pre class="code">
+      &lt;images native="true"/&gt;
 </pre>
-<p>Only the values "color" and "b+w" are allowed for the mode attribute. The bits-per-pixel
-      attribute is ignored if mode is "color". For "b+w" mode is must be 1, 4, or 8.</p>
-<a name="N1023A"></a><a name="afp-extensions"></a>
+<p>When the native attribute is specified and set to "true", all image resources will be natively injected
+      into the datastream using an object container rather than being converted into an IOCA FS45 image.
+      Support for native image formats (e.g. JPEG, GIF) is not always available on printer implementations
+      so by default this configuration option is set to "false".</p>
+<a name="N10243"></a><a name="afp-resource-group-file"></a>
+<h4>Resource Group File</h4>
+<p>By default the AFP Renderer will place all data resource objects such as images within
+      the document of the main output datastream.  An external resource group file where document resources
+      may be specified with the &lt;resource-group-file/&gt; configuration element.  Example:</p>
+<pre class="code">
+      &lt;resource-group-file&gt;external_resources.afp&lt;/resource-group-file&gt;
+</pre>
+<div class="note">
+<div class="label">Note</div>
+<div class="content">Be careful when using this option not to overwrite existing resource files from previous rendering runs.</div>
+</div>
+<a name="N10255"></a><a name="afp-extensions"></a>
 <h3 class="underlined_5">Extensions</h3>
 <p>The AFP Renderer supports some AFP specific extensions which can be embedded into the input 
       fo document. To use the extensions the appropriate namespace must be declared in the fo:root element like this:</p>
@@ -1011,7 +1041,7 @@
       &lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
                xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp"&gt;
 </pre>
-<a name="N10247"></a><a name="afp-page-overlay"></a>
+<a name="N10262"></a><a name="afp-page-overlay"></a>
 <h4>Page Overlay Extension</h4>
 <p>The include-page-overlay extension element allows to define on a per simple-page-master basis a page overlay resource. Example:</p>
 <pre class="code">
@@ -1024,7 +1054,7 @@
 </pre>
 <p>The mandatory name attribute must refer to an 8 character (space padded) resource name that
         must be known in the AFP processing environment.</p>
-<a name="N10258"></a><a name="afp-page-segment"></a>
+<a name="N10273"></a><a name="afp-page-segment"></a>
 <h4>Page Segment Extension</h4>
 <p>The include-page-segment extension element allows to define resource substitution for fo:external-graphics elements. 
           Example:</p>
@@ -1046,7 +1076,7 @@
         fo:external-graphic elements and if it is identical (string matching is used) in the generated
         AFP the external graphic is replaced by a reference to the given resource.
         </p>
-<a name="N10269"></a><a name="afp-tag-logical-element"></a>
+<a name="N10284"></a><a name="afp-tag-logical-element"></a>
 <h4>Tag Logical Element Extension</h4>
 <p>The tag-logical-element extension element allows to injects TLEs into the AFP output stream. Example:</p>
 <pre class="code">
@@ -1063,7 +1093,7 @@
         Multiple tag-logical-element extension elements within a simple-page-master are allowed.
         The name and value attributes are mandatory.
         </p>
-<a name="N1027A"></a><a name="afp-no-operation"></a>
+<a name="N10295"></a><a name="afp-no-operation"></a>
 <h4>No Operation Extension</h4>
 <p>The no-operation extension provides the ability to carry up to 32K of comments or any other type
         of unarchitected data into the AFP output stream. Example:</p>
@@ -1080,9 +1110,44 @@
         Multiple no-operation extension elements within a simple-page-master are allowed.
         The name attribute is mandatory.
         </p>
+<a name="N102A7"></a><a name="afp-foreign-attributes"></a>
+<h3 class="underlined_5">Foreign Attributes</h3>
+<a name="N102AD"></a><a name="afp-foreign-attributes-resource"></a>
+<h4>Resource</h4>
+<p>The resource foreign attributes provides the ability to name and control where data object resources
+        (e.g. images/scalable vector graphics) will reside in the AFP output.
+        The afp foreign attributes are only used in conjuntion with &lt;fo:external-graphic/&gt; and &lt;instream-foreign-object/&gt;.
+        Example:</p>
+<pre class="code">
+    &lt;fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
+     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp"&gt;
+     ...
+     &lt;fo:block&gt;
+      &lt;fo:external-graphic width="2.0cm" content-width="2.0cm" height="1.8cm" content-height="1.8cm"
+        src="examples/fo/graphics/xml_feather.gif"
+        afp:resource-name="feather" afp:resource-level="external" afp:resource-group-file="resources.afp"/&gt;
+     &lt;/fo:block&gt;
+     &lt;fo:block&gt;
+      &lt;fo:instream-foreign-object height="758.047pt" content-height="758.047pt" width="576.96pt" content-width="576.96pt"
+      afp:resource-name"circles" afp:resource-level="inline"&gt;
+       &lt;svg xmlns="http://www.w3.org/2000/svg" width="12cm" height="12cm"&gt;
+        &lt;g style="fill-opacity:0.7; stroke:black; stroke-width:0.1cm;"&gt;
+         &lt;circle cx="6cm" cy="2cm" r="100" style="fill:red;" transform="translate(0,50)" /&gt;
+         &lt;circle cx="6cm" cy="2cm" r="100" style="fill:blue;" transform="translate(70,150)" /&gt;
+         &lt;circle cx="6cm" cy="2cm" r="100" style="fill:green;" transform="translate(-70,150)"/&gt;
+        &lt;/g&gt;
+       &lt;/svg&gt;
+      &lt;/fo:instream-foreign-object&gt;
+     &lt;/fo:block&gt;
+</pre>
+<p>The resource-level attribute where the resource object will reside in the AFP output datastream.
+        The possible values for this are "inline", "print-file" and "external".
+        When no resource-level attribute is provided, resources are by default placed at "print-file" level.
+        When "external" is used a resource-group-file attribute must also be specified.</p>
+<p></p>
 </div>
 
-<a name="N1028D"></a><a name="rtf"></a>
+<a name="N102C2"></a><a name="rtf"></a>
 <h2 class="underlined_10">RTF</h2>
 <div class="section">
 <p>
@@ -1136,7 +1201,7 @@
 </ul>
 </div>
 
-<a name="N102C1"></a><a name="xml"></a>
+<a name="N102F6"></a><a name="xml"></a>
 <h2 class="underlined_10">XML (Area Tree XML)</h2>
 <div class="section">
 <p>
@@ -1150,7 +1215,7 @@
   </p>
 </div>
 
-<a name="N102D2"></a><a name="awt"></a>
+<a name="N10307"></a><a name="awt"></a>
 <h2 class="underlined_10">Java2D/AWT</h2>
 <div class="section">
 <p>
@@ -1165,14 +1230,14 @@
     </p>
 </div>
 
-<a name="N102DF"></a><a name="print"></a>
+<a name="N10314"></a><a name="print"></a>
 <h2 class="underlined_10">Print</h2>
 <div class="section">
 <p>
     It is possible to directly print the document from the command line.
     This is done with the same code that renders to the Java2D/AWT renderer.
   </p>
-<a name="N102E8"></a><a name="print-issues"></a>
+<a name="N1031D"></a><a name="print-issues"></a>
 <h3 class="underlined_5">Known issues</h3>
 <p>
       If you run into the problem that the printed output is incomplete on Windows:
@@ -1183,7 +1248,7 @@
     </p>
 </div>
 
-<a name="N102F3"></a><a name="bitmap"></a>
+<a name="N10328"></a><a name="bitmap"></a>
 <h2 class="underlined_10">Bitmap (TIFF/PNG)</h2>
 <div class="section">
 <p>
@@ -1197,7 +1262,7 @@
     page. The quality of the bitmap depends on the target resolution setting 
     on the FOUserAgent.
   </p>
-<a name="N102FF"></a><a name="bitmap-configuration"></a>
+<a name="N10334"></a><a name="bitmap-configuration"></a>
 <h3 class="underlined_5">Configuration</h3>
 <p>
         The TIFF and PNG renderer configuration currently allows the following settings:
@@ -1212,7 +1277,7 @@
         no such background will be painted and you will get a transparent image if
         an alpha channel is available in the output format.
       </p>
-<a name="N10310"></a><a name="tiff-configuration"></a>
+<a name="N10345"></a><a name="tiff-configuration"></a>
 <h3 class="underlined_5">TIFF-specific Configuration</h3>
 <p>
         In addition to the above values the TIFF renderer configuration allows some additional
@@ -1263,7 +1328,7 @@
 </div>
 </div>
 
-<a name="N10344"></a><a name="txt"></a>
+<a name="N10379"></a><a name="txt"></a>
 <h2 class="underlined_10">TXT</h2>
 <div class="section">
 <p>
@@ -1301,7 +1366,7 @@
 </ul>
 </div>
 
-<a name="N10360"></a><a name="sandbox"></a>
+<a name="N10395"></a><a name="sandbox"></a>
 <h2 class="underlined_10">Output Formats in the Sandbox</h2>
 <div class="section">
 <p>
@@ -1310,7 +1375,7 @@
     can be found under src/sandbox and are compiled into build/fop-sandbox.jar during the
     main build. The output formats in the sandbox are marked as such below.
   </p>
-<a name="N10369"></a><a name="mif"></a>
+<a name="N1039E"></a><a name="mif"></a>
 <h3 class="underlined_5">MIF</h3>
 <div class="warning">
 <div class="label">Warning</div>
@@ -1320,7 +1385,7 @@
       This format is the Maker Interchange Format which is used by
       Adobe Framemaker.
     </p>
-<a name="N10376"></a><a name="svg"></a>
+<a name="N103AB"></a><a name="svg"></a>
 <h3 class="underlined_5">SVG</h3>
 <div class="warning">
 <div class="label">Warning</div>
@@ -1339,7 +1404,7 @@
      </p>
 </div>
 
-<a name="N10384"></a><a name="wishlist"></a>
+<a name="N103B9"></a><a name="wishlist"></a>
 <h2 class="underlined_10">Wish list</h2>
 <div class="section">
 <p>
@@ -1362,7 +1427,7 @@
 <font size="-2">by&nbsp;Keiron Liddle,&nbsp;Art Welch</font>
 </p>
 <span class="version">
-          version 681307</span>
+          version 721430</span>
 </div>
 <!--+
     |end content

Modified: xmlgraphics/site/deploy/fop/trunk/output.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/output.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/output.pdf (original) and xmlgraphics/site/deploy/fop/trunk/output.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/output.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/output.xml?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/output.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/output.xml Sun Jan 18 05:37:46 2009
@@ -17,7 +17,7 @@
 <document>
   <header>
     <title>Apache FOP Output Formats</title>
-    <version>$Revision: 681307 $</version>
+    <version>$Revision: 721430 $</version>
     <authors>
       <person name="Keiron Liddle" email="keiron@aftexsw.com"/>
       <person name="Art Welch" email=""/>
@@ -474,7 +474,7 @@
     <section id="afp-configuration">
       <title>Configuration</title>
       <section id="afp-font-config">
-        <title>Fonts</title>
+      <title>Fonts</title>
       <p>The AFP Renderer requires special configuration particularly related to fonts.
       AFP Render configuration is done through the normal FOP configuration file. The MIME type
       for the AFP Renderer is application/x-afp which means the AFP Renderer section in the FOP configuration file
@@ -610,16 +610,33 @@
       <section id="afp-image-config">
         <title>Images</title>
         <p>By default the AFP Renderer converts all images to 8 bit grey level.
-        This can be overridden by the &lt;images&gt; configuration element. Example:</p>
+        This can be overridden by the &lt;images/&gt; configuration element. Example:</p>
       <source xml:space="preserve"><![CDATA[
       <images mode="color" />
 ]]></source>
       <p>This will put images as RGB images into the AFP output stream. The default setting is:</p>
       <source xml:space="preserve"><![CDATA[
-      <images mode="b+w" bits-per-pixel="8" />
+      <images mode="b+w" bits-per-pixel="8" native="true"/>
+]]></source>
+      <p>Only the values "color" and "b+w" are allowed for the mode attribute.</p>
+      <p>The bits-per-pixel attribute is ignored if mode is "color". For "b+w" mode is must be 1, 4, or 8.</p>
+      <source xml:space="preserve"><![CDATA[
+      <images native="true"/>
+]]></source>
+      <p>When the native attribute is specified and set to "true", all image resources will be natively injected
+      into the datastream using an object container rather than being converted into an IOCA FS45 image.
+      Support for native image formats (e.g. JPEG, GIF) is not always available on printer implementations
+      so by default this configuration option is set to "false".</p>
+      </section>
+      <section id="afp-resource-group-file">
+      <title>Resource Group File</title>
+      <p>By default the AFP Renderer will place all data resource objects such as images within
+      the document of the main output datastream.  An external resource group file where document resources
+      may be specified with the &lt;resource-group-file/&gt; configuration element.  Example:</p>
+      <source xml:space="preserve"><![CDATA[
+      <resource-group-file>external_resources.afp</resource-group-file>
 ]]></source>
-      <p>Only the values "color" and "b+w" are allowed for the mode attribute. The bits-per-pixel
-      attribute is ignored if mode is "color". For "b+w" mode is must be 1, 4, or 8.</p>
+      <note>Be careful when using this option not to overwrite existing resource files from previous rendering runs.</note>
       </section>
     </section>
     <section id="afp-extensions">
@@ -704,6 +721,43 @@
         </p>
       </section>
     </section>
+    <section id="afp-foreign-attributes">
+      <title>Foreign Attributes</title>
+        <section id="afp-foreign-attributes-resource">
+        <title>Resource</title>
+        <p>The resource foreign attributes provides the ability to name and control where data object resources
+        (e.g. images/scalable vector graphics) will reside in the AFP output.
+        The afp foreign attributes are only used in conjuntion with &lt;fo:external-graphic/&gt; and &lt;instream-foreign-object/&gt;.
+        Example:</p>
+      <source xml:space="preserve"><![CDATA[
+    <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
+     xmlns:afp="http://xmlgraphics.apache.org/fop/extensions/afp">
+     ...
+     <fo:block>
+      <fo:external-graphic width="2.0cm" content-width="2.0cm" height="1.8cm" content-height="1.8cm"
+        src="examples/fo/graphics/xml_feather.gif"
+        afp:resource-name="feather" afp:resource-level="external" afp:resource-group-file="resources.afp"/>
+     </fo:block>
+     <fo:block>
+      <fo:instream-foreign-object height="758.047pt" content-height="758.047pt" width="576.96pt" content-width="576.96pt"
+      afp:resource-name"circles" afp:resource-level="inline">
+       <svg xmlns="http://www.w3.org/2000/svg" width="12cm" height="12cm">
+        <g style="fill-opacity:0.7; stroke:black; stroke-width:0.1cm;">
+         <circle cx="6cm" cy="2cm" r="100" style="fill:red;" transform="translate(0,50)" />
+         <circle cx="6cm" cy="2cm" r="100" style="fill:blue;" transform="translate(70,150)" />
+         <circle cx="6cm" cy="2cm" r="100" style="fill:green;" transform="translate(-70,150)"/>
+        </g>
+       </svg>
+      </fo:instream-foreign-object>
+     </fo:block>
+]]></source>
+        <p>The resource-level attribute where the resource object will reside in the AFP output datastream.
+        The possible values for this are "inline", "print-file" and "external".
+        When no resource-level attribute is provided, resources are by default placed at "print-file" level.
+        When "external" is used a resource-group-file attribute must also be specified.</p>
+        <p/>
+      </section>
+    </section>
   </section>
 <section id="rtf">
   <title>RTF</title>

Modified: xmlgraphics/site/deploy/fop/trunk/pdfa.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfa.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/pdfa.pdf (original) and xmlgraphics/site/deploy/fop/trunk/pdfa.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf (original) and xmlgraphics/site/deploy/fop/trunk/pdfencryption.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/pdfx.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/pdfx.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/pdfx.pdf (original) and xmlgraphics/site/deploy/fop/trunk/pdfx.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/running.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/running.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/running.pdf (original) and xmlgraphics/site/deploy/fop/trunk/running.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/servlets.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/servlets.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/servlets.pdf (original) and xmlgraphics/site/deploy/fop/trunk/servlets.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.html
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.html?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/upgrading.html (original)
+++ xmlgraphics/site/deploy/fop/trunk/upgrading.html Sun Jan 18 05:37:46 2009
@@ -249,13 +249,12 @@
         </li>
         
 <li>
-          If you are using font metrics files for version 0.20.5 or
-          0.92 or earlier, you have to regenerate them in the new
-          format. The new format is characterized by a version
-          attribute on the top-level font-metrics element, whose value
-          is 2.0. The absence of a version attribute will be
-          interpreted as version 1.0, and such metrics files will no
-          longer be parsed.
+          Beginning with version 0.94 you can skip the generation of
+          font metric files and remove the "font-metrics" attribute
+          in the font configuration. In the unlikely case that due to
+          a bug you still need to use font metrics files you will need
+          to regenerate the font metrics file if yours are from a FOP
+          version before 0.93.
         </li>
         
 <li>
@@ -334,18 +333,12 @@
           The <span class="codefrag">fox:outline</span> extension is not implemented in this version anymore. 
           It has been superseded by the new bookmark elements from XSL-FO 1.1.
         </li>
-        
-<li>
-          The <span class="codefrag">fox:destination</span> extension is also not implemented in this version
-          although it may be added in the future. See also
-          <a class="external" href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37157">Bug 37157</a>.
-        </li>
       
 </ul>
 </div>
   
 <span class="version">
-          version 645104</span>
+          version 733034</span>
 </div>
 <!--+
     |end content

Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.pdf
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.pdf?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
Files xmlgraphics/site/deploy/fop/trunk/upgrading.pdf (original) and xmlgraphics/site/deploy/fop/trunk/upgrading.pdf Sun Jan 18 05:37:46 2009 differ

Modified: xmlgraphics/site/deploy/fop/trunk/upgrading.xml
URL: http://svn.apache.org/viewvc/xmlgraphics/site/deploy/fop/trunk/upgrading.xml?rev=735455&r1=735454&r2=735455&view=diff
==============================================================================
--- xmlgraphics/site/deploy/fop/trunk/upgrading.xml (original)
+++ xmlgraphics/site/deploy/fop/trunk/upgrading.xml Sun Jan 18 05:37:46 2009
@@ -17,7 +17,7 @@
 <document>
   <header>
     <title>Upgrading from an Earlier Version of Apache FOP</title>
-    <version>$Revision: 645104 $</version>
+    <version>$Revision: 733034 $</version>
   </header>
   <body>
     <section id="important">
@@ -52,13 +52,12 @@
           src/foschema/fop-configuration.xsd.
         </li>
         <li>
-          If you are using font metrics files for version 0.20.5 or
-          0.92 or earlier, you have to regenerate them in the new
-          format. The new format is characterized by a version
-          attribute on the top-level font-metrics element, whose value
-          is 2.0. The absence of a version attribute will be
-          interpreted as version 1.0, and such metrics files will no
-          longer be parsed.
+          Beginning with version 0.94 you can skip the generation of
+          font metric files and remove the "font-metrics" attribute
+          in the font configuration. In the unlikely case that due to
+          a bug you still need to use font metrics files you will need
+          to regenerate the font metrics file if yours are from a FOP
+          version before 0.93.
         </li>
         <li>
           <p>
@@ -120,11 +119,6 @@
           The <code>fox:outline</code> extension is not implemented in this version anymore. 
           It has been superseded by the new bookmark elements from XSL-FO 1.1.
         </li>
-        <li>
-          The <code>fox:destination</code> extension is also not implemented in this version
-          although it may be added in the future. See also
-          <link href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37157">Bug 37157</link>.
-        </li>
       </ul>
     </section>
   </body>



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


Mime
View raw message