xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r813018 [3/24] - in /websites/staging/xmlgraphics/trunk/content: ./ fop/ fop/0.95/ fop/0.95/images/ fop/1.0/ fop/1.0/images/ fop/dev/ fop/dev/design/ fop/dev/fo/ fop/dev/svg/ fop/fo/ fop/trunk/ fop/trunk/images/
Date Sun, 15 Apr 2012 05:39:54 GMT
Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/hyphenation.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,181 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP: Hyphenation</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP: Hyphenation</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="support">Hyphenation Support</h1>
+<h2 id="intro">Introduction</h2>
+<p>Apache™ FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.</p>
+<p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a href="http://offo.sourceforge.net/hyphenation/index.html">Objects For Formatting Objects</a> project.
+If you have made improvements to an existing FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the <a href="../maillist.html#fop-user">FOP User mailing list</a> .</p>
+<h2 id="license-issues">License Issues</h2>
+<p>Many of the hyphenation files distributed with TeX and its offspring are licenced under the <a href="http://www.latex-project.org/lppl.html">LaTeX Project Public License (LPPL)</a> , which prevents them from being distributed with Apache software. The LPPL puts restrictions on file names in redistributed derived works which we feel can't guarantee. Some hyphenation pattern files have other or additional restrictions, for example against use for commercial purposes.</p>
+<p>Although Apache FOP cannot redistribute hyphenation pattern files that do not conform with its license scheme, that does not necessarily prevent users from using such hyphenation patterns with FOP. However, it does place on the user the responsibility for determining whether the user can rightly use such hyphenation patterns under the hyphenation pattern license.
+<warning>The user is responsible to settle license issues for hyphenation pattern files that are obtained from non-Apache sources.</warning></p>
+<h2 id="sources">Sources of Custom Hyphenation Pattern Files</h2>
+<p>The most important source of hyphenation pattern files is the <a href="http://www.ctan.org/tex-archive/language/hyphenation/">CTAN TeX Archive</a> .</p>
+<h2 id="install">Installing Custom Hyphenation Patterns</h2>
+<p>To install a custom hyphenation pattern for use with FOP:</p>
+<ol>
+<li>
+<p>Convert the TeX hyphenation pattern file to the FOP format. The FOP format is an xml file conforming to the DTD found at <code>{fop-dir}/hyph/hyphenation.dtd</code> .</p>
+</li>
+<li>
+<p>Name this new file following this schema: <code>languageCode_countryCode.xml</code> . The country code is optional, and should be used only if needed. For example:</p>
+</li>
+<li>
+<p><code>en_US.xml</code> would be the file name for American English hyphenation patterns.</p>
+</li>
+<li>
+<p><code>it.xml</code> would be the file name for Italian hyphenation patterns.
+The language and country codes must match the XSL-FO input, which follows <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt">ISO 639</a> (languages) and <a href="http://www.ics.uci.edu/pub/ietf/http/related/iso3166.txt">ISO 3166</a> (countries). NOTE: The ISO 639/ISO 3166 convention is that language names are written in lower case, while country codes are written in upper case. FOP does not check whether the language and country specified in the FO source are actually from the current standard, but it relies on it being two letter strings in a few places. So you can make up your own codes for custom hyphenation patterns, but they should be two letter strings too (patches for proper handling extensions are welcome)</p>
+</li>
+<li>
+<p>There are basically three ways to make the FOP-compatible hyphenation pattern file(s) accessible to FOP:</p>
+</li>
+<li>
+<p>Download the precompiled JAR from <a href="http://offo.sourceforge.net/hyphenation/index.html">OFFO</a> and place it either in the <code>{fop-dir}/lib</code> directory, or in a directory of your choice (and append the full path to the JAR to the environment variable <code>FOP_HYPHENATION_PATH</code> ).</p>
+</li>
+<li>
+<p>Download the desired FOP-compatible hyphenation pattern file(s) from <a href="http://offo.sourceforge.net/hyphenation/index.html">OFFO</a> , and/or take your self created hyphenation pattern file(s),</p>
+<ul>
+<li>
+<p>place them in the directory <code>{fop-dir}/hyph</code> ,</p>
+</li>
+<li>
+<p>or place them in a directory of your choice and set the Ant variable <code>user.hyph.dir</code> to point to that directory (in <code>build-local.properties</code> ),
+and run Ant with build target <code>jar-hyphenation</code> . This will create a JAR containing the compiled patterns in <code>{fop-dir}/build</code> that will be added to the classpath on the next run. (When FOP is built from scratch, and there are pattern source file(s) present in the directory pointed to by the <code>user.hyph.dir</code> variable, this JAR will automatically be created from the supplied pattern(s)).</p>
+</li>
+</ul>
+</li>
+<li>
+<p>Put the pattern source file(s) into a directory of your choice and configure FOP to look for custom patterns in this directory, by setting the <a href="configuration.html"><hyphenation-base></a> configuration option.</p>
+</li>
+</ol>
+<p><warning>Either of these three options will ensure hyphenation is working when using FOP from the command-line. If FOP is being embedded, remember to add the location(s) of the hyphenation JAR(s) to the CLASSPATH (option 1 and 2) or to set the <a href="configuration.html#hyphenation-dir"><hyphenation-dir></a> configuration option programmatically (option 3).</warning></p>
+<h1 id="patterns">Hyphenation Patterns</h1>
+<p>If you would like to build your own hyphenation pattern files, or modify existing ones, this section will help you understand how to do so. Even when creating a pattern file from scratch, it may be beneficial to start with an existing file and modify it. See <a href="http://offo.sourceforge.net/hyphenation/index.html">OFFO's Hyphenation page</a> for examples. Here is a brief explanation of the contents of FOP's hyphenation patterns:
+<warning>The remaining content of this section should be considered "draft" quality. It was drafted from theoretical literature, and has not been tested against actual FOP behavior. It may contain errors or omissions. Do not rely on these instructions without testing everything stated here. If you use these instructions, please provide feedback on the <a href="../maillist.html#fop-user">FOP User mailing list</a> , either confirming their accuracy, or raising specific problems that we can address.</warning></p>
+<ul>
+<li>
+<p>The root of the pattern file is the <hyphenation-info> element.</p>
+</li>
+<li>
+<p><hyphen-char>: its attribute "value" contains the character signalling a hyphen in the <exceptions> section. It has nothing to do with the hyphenation character used in FOP, use the XSLFO hyphenation-character property for defining the hyphenation character there. At some points a dash U+002D is hardwired in the code, so you'd better use this too (patches to rectify the situation are welcome). There is no default, if you declare exceptions with hyphenations, you must declare the hyphen-char too.</p>
+</li>
+<li>
+<p><hyphen-min> contains two attributes:</p>
+<ul>
+<li>
+<p>before: the minimum number of characters in a word allowed to exist on a line immediately preceding a hyphenated word-break.</p>
+</li>
+<li>
+<p>after: the minimum number of characters in a word allowed to exist on a line immediately after a hyphenated word-break.
+This element is unused and not even read. It should be considered a documentation for parameters used during pattern generation.</p>
+</li>
+</ul>
+</li>
+<li>
+<p><classes> contains whitespace-separated character sets. The members of each set should be treated as equivalent for purposes of hyphenation, usually upper and lower case of the same character. The first character of the set is the canonical character, the patterns and exceptions should only contain these canonical representation characters (except digits for weight, the period (.) as word delimiter in the patterns and the hyphen char in exceptions, of course).</p>
+</li>
+<li>
+<p><exceptions> contains whitespace-separated words, each of which has either explicit hyphen characters to denote acceptable breakage points, or no hyphen characters, to indicate that this word should never be hyphenated, or contain explicit <hyp> elements for specifying changes of spelling due to hyphenation (like backen -&gt; bak-ken or Stoffarbe -&gt; Stoff-farbe in the old german spelling). Exceptions override the patterns described below. Explicit <hyp> declarations don't work yet (patches welcome). Exceptions are generally a bit brittle, test carefully.</p>
+</li>
+<li>
+<p><patterns> includes whitespace-separated patterns, which are what drive most hyphenation decisions. The characters in these patterns are explained as follows:</p>
+<ul>
+<li>
+<p>non-numeric characters represent characters in a sub-word to be evaluated</p>
+</li>
+<li>
+<p>the period character (.) represents a word boundary, i.e. either the beginning or ending of a word</p>
+</li>
+<li>
+<p>numeric characters represent a scoring system for indicating the acceptability of a hyphen in this location. Odd numbers represent an acceptable location for a hyphen, with higher values overriding lower inhibiting values. Even numbers indicate an unacceptable location, with higher values overriding lower values indicating an acceptable position. A value of zero (inhibiting) is implied when there is no number present. Generally patterns are constructed so that valuse greater than 4 are rare. Due to a bug currently patterns with values of 8 and greater don't have an effect, so don't wonder.
+Here are some examples from the English patterns file:</p>
+</li>
+<li>
+<p>Knuth ( <em>The TeXBook</em> , Appendix H) uses the example <strong>hach4</strong> , which indicates that it is extremely undesirable to place a hyphen after the substring "hach", for example in the word "toothach-es".</p>
+</li>
+<li>
+<p><strong>.leg5e</strong> indicates that "leg-e", when it occurs at the beginning of a word, is a very good place to place a hyphen, if one is needed. Words like "leg-end" and "leg-er-de-main" fit this pattern.
+Note that the algorithm that uses this data searches for each of the word's substrings in the patterns, and chooses the <em>highest</em> value found for letter combination.</p>
+</li>
+</ul>
+</li>
+</ul>
+<p>If you want to convert a TeX hyphenation pattern file, you have to undo the TeX encoding for non-ASCII text. FOP uses Unicode, and the patterns must be proper Unicode too. You should be aware of the XML encoding issues, preferably use a good Unicode editor.</p>
+<p>Note that FOP does not do Unicode character normalization. If you use combining chars for accents and other character decorations, you must declare character classes for them, and use the same sequence of base character and combining marks in the XSLFO source, otherwise the pattern wouldn't match. Fortunately, Unicode provides precomposed characters for all important cases in common languages, until now nobody run seriously into this issue. Some dead languages and dialects, especially ancient ones, may pose a real problem though.</p>
+<p>If you want to generate your own patterns, an open-source utility called patgen is available on many Unix/Linux distributions and every TeX distribution which can be used to assist in creating pattern files from dictionaries. Pattern creation for languages like english or german is an art. If you can, read Frank Liang's original paper "Word Hy-phen-a-tion by Com-pu-ter" (yes, with hyphens). It is not available online. The original patgen.web source, included in the TeX source distributions, contains valuable comments, unfortunately technical details obscure often the high level issues. Another important source is <a href="http://www.ctan.org/tex-archive/systems/knuth/tex/texbook.tex">The TeX Book</a> , appendix H (either read the TeX source, or run it through TeX to typeset it). Secondary articles, for example the works by Petr Sojka, may also give some much needed insight into problems arising in automated hyphenation.</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleFO2PDF.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleFO2PDF.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleObj2PDF.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleObj2PDF.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleObj2XML.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleObj2XML.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleXML2FO.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleXML2FO.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleXML2PDF.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/0.95/images/EmbeddingExampleXML2PDF.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/index.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/index.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,84 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Version 0.95</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP Version 0.95</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="intro">Introduction</h1>
+<p>The Apache™ FOP team is proud to present to you this production quality release. We're still in the process of adding new features. We welcome any feedback you might have and even more, any other form of help to get the project forward.</p>
+<p>This sixth release contains many bug fix release and new features compared to 0.94. To see what has changed since the last release, please visit the <a href="changes_0.95.html">Changes Page</a> and the <a href="releaseNotes_0.95.html">Release Notes</a> .</p>
+<h1 id="upgrading">Upgrading from an earlier version</h1>
+<p>If you're upgrading to this version from an earlier version of FOP, please read the information contained on the <a href="upgrading.html">Upgrading page</a> !</p>
+<h1 id="download">Download</h1>
+<p>To download this version, please visit the <a href="../download.html">download page</a> .</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/intermediate.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,119 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP: Intermediate Format</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP: Intermediate Format</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version>
+Please note that the intermediate format is an <strong>advanced feature</strong> and can be ignored by most users of Apache™ FOP.</p>
+<h1 id="introduction">Introduction</h1>
+<p>The intermediate format (IF) is a proprietary XML format that represents the area tree generated by the layout engine. The area tree is conceptually defined in the <a href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting">XSL-FO specification in chapter 1.1.2</a> . The IF can be generated through the area tree XML Renderer (the XMLRenderer).</p>
+<p>The intermediate format can be used to generate intermediate documents that are modified before they are finally rendered to their ultimate output format. Modifications include adjusting and changing trait values, adding or modifying area objects, inserting prefabricated pages, overlays, imposition (n-up, rotation, scaling etc.). Multiple IF files can be combined to a single output file.</p>
+<h1 id="usage">Usage of the Intermediate Format</h1>
+<p>As already mentioned, the IF is generated by using the <strong>XMLRenderer</strong> (MIME type: <strong>application/X-fop-areatree</strong> ). So, you basically set the right MIME type for the output format and process your FO files as if you would create a PDF file. However, there is an important detail to consider: The various Renderers don't all use the same font sources. To be able to create the right area tree for the ultimate output file, you need to create the IF file using the right font setup. This is achieved by telling the XMLRenderer to mimic another renderer. This is done by calling the XMLRenderer's mimicRenderer() method with an instance of the ultimate target renderer as the single parameter. This has a consequence: An IF file rendered with the Java2DRenderer may not look as expected when it was actually generated for the PDF renderer. For renderers that use the same font setup, this restriction does not apply (PDF and PS, for example). Generating the inte
 rmediate format file is the first step.</p>
+<p>The second step is to reparse the IF file using the <strong>AreaTreeParser</strong> which is found in the org.apache.fop.area package. The pages retrieved from the IF file are added to an AreaTreeModel instance from where they are normally rendered using one of the available Renderer implementations. You can find examples for the IF processing in the <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/"></a> directory in the FOP distribution</p>
+<p>The basic pattern to parse the IF format looks like this:</p>
+<p>FopFactory fopFactory = FopFactory.newInstance();    <br />
+</p>
+<p>// Setup output
+OutputStream out = new java.io.FileOutputStream(pdffile);
+out = new java.io.BufferedOutputStream(out);
+try {
+    //Setup fonts and user agent
+    FontInfo fontInfo = new FontInfo();
+    FOUserAgent userAgent = fopFactory.newFOUserAgent();</p>
+<div class="codehilite"><pre><span class="sr">//</span><span class="n">Construct</span> <span class="n">the</span> <span class="n">AreaTreeModel</span> <span class="n">that</span> <span class="n">will</span> <span class="n">received</span> <span class="n">the</span> <span class="n">individual</span> <span class="n">pages</span>
+<span class="n">AreaTreeModel</span> <span class="n">treeModel</span> <span class="o">=</span> <span class="k">new</span> <span class="n">RenderPagesModel</span><span class="p">(</span><span class="n">userAgent</span><span class="p">,</span> 
+        <span class="n">MimeConstants</span><span class="o">.</span><span class="n">MIME_PDF</span><span class="p">,</span> <span class="n">fontInfo</span><span class="p">,</span> <span class="n">out</span><span class="p">);</span>
+
+<span class="sr">//</span><span class="n">Parse</span> <span class="n">the</span> <span class="n">IF</span> <span class="n">file</span> <span class="n">into</span> <span class="n">the</span> <span class="n">area</span> <span class="n">tree</span>
+<span class="n">AreaTreeParser</span> <span class="n">parser</span> <span class="o">=</span> <span class="k">new</span> <span class="n">AreaTreeParser</span><span class="p">();</span>
+<span class="n">Source</span> <span class="n">src</span> <span class="o">=</span> <span class="k">new</span> <span class="n">StreamSource</span><span class="p">(</span><span class="n">myIFFile</span><span class="p">);</span>
+<span class="n">parser</span><span class="o">.</span><span class="n">parse</span><span class="p">(</span><span class="n">src</span><span class="p">,</span> <span class="n">treeModel</span><span class="p">,</span> <span class="n">userAgent</span><span class="p">);</span>
+
+<span class="sr">//</span><span class="n">Signal</span> <span class="n">the</span> <span class="n">end</span> <span class="n">of</span> <span class="n">the</span> <span class="n">processing</span><span class="o">.</span> <span class="n">The</span> <span class="n">renderer</span> <span class="n">can</span> <span class="n">finalize</span> <span class="n">the</span> <span class="n">target</span> <span class="n">document</span><span class="o">.</span>
+<span class="n">treeModel</span><span class="o">.</span><span class="n">endDocument</span><span class="p">();</span>
+</pre></div>
+
+
+<p>} finally {
+    out.close();
+}
+This example simply reads an IF file and renders it to a PDF file. Please note, that in normal FOP operation you're shielded from having to instantiate the FontInfo object yourself. This is normally a task of the AreaTreeHandler which is not present in this scenario. The same applies to the AreaTreeModel instance, in this case an instance of a subclass called RenderPagesModel. RenderPagesModel is ideal in this case as it has very little overhead processing the individual pages. An important line in the example is the call to <code>endDocument()</code> on the AreaTreeModel. This lets the Renderer know that the processing is now finished.</p>
+<p>The intermediate format can also be used from the <a href="running.html#standalone-start">command-line</a> by using the "-atin" parameter for specifying the area tree XML as input file. You can also specify a "mimic renderer" by inserting a MIME type between "-at" and the output file.</p>
+<h2 id="concat">Concatenating Documents</h2>
+<p>This initial example is obviously not very useful. It would be faster to create the PDF file directly. As the <a href="http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/examples/embedding/java/embedding/intermediate/ExampleConcat.java">ExampleConcat.java</a> example shows you can easily parse multiple IF files in a row and add the parsed pages to the same AreaTreeModel instance which essentially concatenates all the input document to one single output document.</p>
+<h2 id="modifying">Modifying Documents</h2>
+<p>One of the most important use cases for the intermediate format is obviously modifying the area tree XML before finally rendering it to the target format. You can easily use XSLT to process the IF file according to your needs. Please note, that we will currently not formally describe the intermediate format. You need to have a good understanding its structure so you don't create any non-parseable files. We may add an XML Schema and more detailed documentation at a later time. You're invited to help us with that.</p>
+<h2 id="advanced">Advanced Use</h2>
+<p>The generation of the intermediate format as well as it parsing process has been designed to allow for maximum flexibility and optimization. Please note that you can call <code>setTransformerHandler()</code> on XMLRenderer to give the XMLRenderer your own TransformerHandler instance in case you would like to do custom serialization (to a W3C DOM, for example) and/or to directly modify the area tree using XSLT. The AreaTreeParser on the other side allows you to retrieve a ContentHandler instance where you can manually send SAX events to to start the parsing process (see <code>getContentHandler()</code> ).</p></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/knownissues_overview.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,179 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP: Known Issues</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP: Known Issues</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="known-issues-knownissues">Known issues # {#Known+issues}</h1>
+<p>This page lists currently known issues in the current release.</p>
+<p>For additional information on known issues in Apache™ FOP, please have a look at the following pages, too:</p>
+<ul>
+<li>
+<p><a href="../bugs.html">the bug list in Bugzilla</a> </p>
+</li>
+<li>
+<p><a href="http://wiki.apache.org/xmlgraphics-fop/FOPProjectTasks">the task list in the Wiki</a> </p>
+</li>
+</ul>
+<p>Apache FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.</p>
+<h2 id="fo-tree-fotree">FO Tree ## {#FO+Tree}</h2>
+<p>This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.</p>
+<p><strong>from-table-column_marker.fo</strong> (Markers and core function evaluation):<br></br>The code currently evaluates this function according to the column in which the marker appears in the source document, rather than the column it is retrieved in.</p>
+<h2 id="layout-engine-layoutengine">Layout Engine ## {#Layout+Engine}</h2>
+<p>This section lists disabled test cases in the test suite for the layout engine tests, at the time of the release.</p>
+<p><strong>basic-link_external-destination_2.xml</strong> (External link around an SVG not properly sized):<br></br>The bpd trait of the inlineparent area for the basic-link is not sized correctly if it wraps an image that is higher than the nominal line.</p>
+<p><strong>block-container_space-before_space-after_3.xml</strong> (Auto-height block-containers produce fences):<br></br>Block-containers with no height currently don't create a fence for spaces as they should (they behave like a normal block).</p>
+<p><strong>block_font-stretch.xml</strong> (font-stretch NYI):<br></br>Font-stretch is not implemented, yet.</p>
+<p><strong>block_hyphenation_linefeed_preserve.xml</strong> (Hyphenation with preserved linefeeds):<br></br>When hyphenation is enabled and linefeeds are preserved, the text is output multiple times.</p>
+<p><strong>block_linefeed-treatment.xml</strong> (linefeed-treatment):<br></br>Preserved linefeeds in a fo:character are not handled correctly.</p>
+<p><strong>block_white-space-treatment_3.xml</strong> (white-space-treatment):<br></br>White space handling incorrectly stops at fo:inline boundaries when it comes to formatter generated line breaks.</p>
+<p><strong>block_space-before_space-after_8.xml</strong> (Empty blocks produce fences):<br></br>An empty block currently produces a fence for stacking constraints which it shouldn't.</p>
+<p><strong>block_white-space_nbsp_2.xml</strong> (block white-space nbsp 2):<br></br>The nbsp given as an fo:character is not adjustable and therefore the justification does not work in this case.</p>
+<p><strong>block_word-spacing.xml</strong> (block word-spacing):<br></br>Word-spacing may not work as expected.</p>
+<p><strong>block_word-spacing_text-align_justify.xml</strong> (block word-spacing text-align justify):<br></br>Word-spacing may not work as expected.</p>
+<p><strong>external-graphic_oversized.xml</strong> (external-graphic don't shrink):<br></br>Images currently don't shrink so they fit on a page when they are too big and shrinking is allowed to happen (min/opt/max).</p>
+<p><strong>external-graphic_src_uri.xml</strong> (Test case with HTTP URL):<br></br>Doesn't work behind a proxy which requires authorization.</p>
+<p><strong>footnote_space-resolution.xml</strong> (Space Resolution in foot note area):<br></br>Space resolution does not work between footnote regions.</p>
+<p><strong>footnote_in_list.xml</strong> (Footnotes swallowed in lists):<br></br>Element lists for lists are created by combining the element lists from list-item-label and list-item-body. The footnotes contained in the KnuthBlockBoxes are not propagated to the combined element list.<br></br>See also: <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37579">http://issues.apache.org/bugzilla/show_bug.cgi?id=37579</a> </p>
+<p><strong>footnote_in_table.xml</strong> (Footnotes swallowed in tables):<br></br>Element lists for tables are created by combining the element lists from the individual table-cells. The footnotes contained in the KnuthBlockBoxes are not propagated to the combined element list.<br></br>See also: <a href="http://issues.apache.org/bugzilla/show_bug.cgi?id=37579">http://issues.apache.org/bugzilla/show_bug.cgi?id=37579</a> </p>
+<p><strong>inline_block_nested_3.xml</strong> (NPE for table inside an inline):<br></br>Placing a table as a child of an fo:inline produces a NullPointerException.</p>
+<p><strong>inline-container_block_nested.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed. The test case contains no checks.</p>
+<p><strong>inline-container_border_padding.xml</strong> (inline-container is not implemented, yet.):<br></br>inline-container is not implemented, yet. Content of an inline-container will get swallowed.</p>
+<p><strong>inline_letter-spacing.xml</strong> (inline letter-spacing):<br></br>Letter-spacing may not work as expected within fo:inline.</p>
+<p><strong>inline_word-spacing.xml</strong> (inline word-spacing):<br></br>Word-spacing may not work as expected within fo:inline.</p>
+<p><strong>inline_word-spacing_text-align_justify.xml</strong> (inline word-spacing text-align justify):<br></br> <em>TODO: Add missing description in disabled-testcases.xml!</em> </p>
+<p><strong>leader-alignment.xml</strong> (leader-alignment NYI):<br></br>Leader-alignment is not yet implemented.</p>
+<p><strong>leader_leader-pattern_use-content_bug.xml</strong> (leader-pattern="use-content": Problem with line height):<br></br>Line height is not correctly calculated for use-content leaders whose height is larger than the rest of the line.<br></br>See also: <a href="http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html">http://www.nabble.com/leaders-with-leader-pattern%3D%22use-content%22-t546244.html</a> </p>
+<p><strong>list-block_keep-with-previous.xml</strong> (keep-with-previous doesn't work in lists):<br></br>Keep-with-previous doesn't work inside tables and lists, yet.</p>
+<p><strong>list-item_block_keep-with-previous.xml</strong> (keep-with-previous doesn't work in lists):<br></br>Keep-with-previous doesn't work inside tables and lists, yet.</p>
+<p><strong>page-breaking_4.xml</strong> (Page breaking doesn't deal with IPD changes):<br></br>Page breaking currently doesn't support changing available IPD between pages of a single page-sequence. Element list generation has to be reset to redetermine line breaks in this case.</p>
+<p><strong>page-breaking_6.xml</strong> (Overflow handing is incomplete):<br></br>Line breaking is not 100% correct when there's too little space. Overflows are not detected and warned.</p>
+<p><strong>page-height_indefinite_simple.xml</strong> (Indefinite page height handling is imcomplete):<br></br>A RuntimeException is thrown for a page of indefinite height. Lots of warnings.</p>
+<p><strong>page-number-citation_background-image.xml</strong> (page-number-citation: Problem with background-image):<br></br>Background-images on page-number-citations are not placed correctly.</p>
+<p><strong>page-number-citation-last_basic.xml</strong> (page-number-citation-last: FOs spanning multiple pages are not properly handled.):<br></br>Resolution of forward references does not wait until an FO is fully finished when an FO spans multiple pages.</p>
+<p><strong>page-number-citation_complex_1.xml</strong> (IDs are not working on all FO elements):<br></br>The "id" attributes are not properly handled for all block-level FO elements.</p>
+<p><strong>page-number-citation_complex_2.xml</strong> (IDs are not working on all FO elements):<br></br>The "id" attributes are not properly handled for all inline-level FO elements.</p>
+<p><strong>region-body_column-count_footnote.xml</strong> (Footnotes in multi-column documents):<br></br>Footnotes may overlap with text of the region-body in multi-column documents.</p>
+<p><strong>region-body_column-count_balance_4col.xml</strong> (Column Balancing problems):<br></br>Situation in a 4-column document where the column balancing doesn't work and even causes some content to disappear.</p>
+<p><strong>region-body_column-count_bug36356.xml</strong> (Column Balancing problems):<br></br>Column balancing doesn't work as expected.</p>
+<p><strong>table-cell_empty_area_with_marker.xml</strong> (table-cell empty area with marker.xml):<br></br>A table-cell producing an empty area does currently not add any markers to a page. See TODO entry in AreaAdditionUtil.</p>
+<p><strong>table_border-width_conditionality.xml</strong> (Border conditionality on table):<br></br>The code should be ok, but the test case uses shorthands and therefore is probably not expressing the indended outcome according to the spec. The test case should be revisited.</p>
+<p><strong>wrapper_block_id.xml</strong> (fo:wrapper around block-level content (with id)):<br></br>"id" attributes on fo:wrapper around block-level content don't get added to the area tree.</p>
+<p><strong>block_shy_linebreaking_hyph.xml</strong> (Soft hyphen with normal hyphenation enabled):<br></br>A soft hyphen should be a preferred as break compared to a normal hyphenation point but is not.</p>
+<h2 id="other-known-issues-otherknownissues">Other known issues ## {#Other+known+issues}</h2>
+<p>This section lists other known issues.</p>
+<ul>
+<li>
+<p>MIF and SVG output support have not been restored, yet.</p>
+</li>
+<li>
+<p>Auto table layout is not implemented, yet.</p>
+</li>
+<li>
+<p>Footnotes may overlap with text of the region-body in multi-column documents.</p>
+</li>
+<li>
+<p>Space resolution does not work between footnote regions.</p>
+</li>
+<li>
+<p>There's a problem involving nested block-containers and reference-orientation 180/-180 (Bugzilla #36391)</p>
+</li>
+<li>
+<p>block-containers with no height currently don't create a fence for spaces as they should (they behave like a normal block).</p>
+</li>
+<li>
+<p>Preserved linefeeds in fo:character are not handled correctly.</p>
+</li>
+<li>
+<p>An empty block currently produces a fence for stacking constraints which it shouldn't.</p>
+</li>
+<li>
+<p>There are several small problems around white space handling.</p>
+</li>
+<li>
+<p>leaders with leader-pattern="use-content" may not work as expected.</p>
+</li>
+<li>
+<p>If two consecutive pages don't have the same available width, the content currently isn't properly fit into the available space on the new page.</p>
+</li>
+<li>
+<p>background-images on page-number-citations are not placed correctly.</p>
+</li>
+<li>
+<p>Not all FO elements can be referenced by their "id", most notably: table-body, table-header, table-footer and table-row.</p>
+</li>
+<li>
+<p>Column balancing in multi-column documents may not work as expected (Bugzilla #36356)</p>
+</li>
+</ul></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>

Added: websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/0.95/metadata.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,212 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP: Metadata</title>
+
+    <meta http-equiv="Content-Type" content="text/html;charset=UTF-8">
+    <meta property="og:image" content="http://www.apache.org/images/asf_logo.gif" />
+<!--
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/style.css">
+    <link rel="stylesheet" type="text/css" media="screen" href="http://www.apache.org/css/code.css">
+-->
+    <link href="/css/xmlgraphics.css" rel="stylesheet" type="text/css">
+
+    </style>
+
+    
+
+    
+    
+  </head>
+
+  <body>
+	  <div id="banner">&nbsp;
+	  </div>
+
+	  <div id="navigation">
+	  <h1 id="xml-graphics">XML Graphics</h1>
+<ul>
+<li><a href="/">Overview</a></li>
+<li><a href="/team.html">Who We Are</a></li>
+<li><a href="/legal.html">Legal Stuff</a></li>
+<li><a href="/charter.html">Project Charter</a></li>
+<li><a href="/mail.html">Mailing Lists</a></li>
+<li><a href="/repo.html">Code Repositories</a></li>
+<li><a href="http://www.apache.org/foundation/sponsorship.html">ASF Sponsorship Program</a></li>
+<li><a href="http://www.apache.org/foundation/thanks.html">ASF Thanks</a></li>
+</ul>
+<h1 id="subprojects">Subprojects</h1>
+<ul>
+<li><a href="/batik/">Batik</a></li>
+<li><a href="/fop/">FOP</a></li>
+<li><a href="/commons/">Commons</a></li>
+</ul>
+<form name="search" id="search" action="http://www.google.com/search" method="get">
+  <input value="xmlgraphics.apache.org" name="sitesearch" type="hidden"/>
+  <input type="text" name="q" id="query" /><br />
+  <input type="submit" id="submit" value="Search" />
+</form>
+	  </div>
+	
+	  <div id="bannertext">
+        <a href="/"><img src="/images/apache-xml-graphics.gif" alt="The Apache XML Graphics Project" width="220" heigh="51" /></a>
+        <h1>Apache™ FOP: Metadata</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/0.95/">0.95</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><h1 id="overview">Overview</h1>
+<p>Document metadata is an important tool for categorizing and finding documents. Various formats support different kinds of metadata representation and to different levels. One of the more popular and flexible means of representing document or object metadata is <a href="http://www.adobe.com/products/xmp/">XMP (eXtensible Metadata Platform, specified by Adobe)</a> . PDF 1.4 introduced the use of XMP. The XMP specification lists recommendation for embedding XMP metdata in other document and image formats. Given its flexibility it makes sense to make use this approach in the XSL-FO context. Unfortunately, unlike SVG which also refers to XMP, XSL-FO doesn't recommend a preferred way of specifying document and object metadata. Therefore, there's no portable way to represent metadata in XSL-FO documents. Each implementation does it differently.</p>
+<h1 id="xmp-in-fo">Embedding XMP in an XSL-FO document</h1>
+<p>As noted above, there's no officially recommended way to embed metadata in XSL-FO. Apache™ FOP supports embedding XMP in XSL-FO. Currently, only support for document-level metadata is implemented. Object-level metadata will be implemented when there's interest.</p>
+<p>Document-level metadata can be specified in the <code>fo:declarations</code> element. XMP specification recommends to use <code>x:xmpmeta</code> , <code>rdf:RDF</code> , and <code>rdf:Description</code> elements as shown in example below. Both <code>x:xmpmeta</code> and <code>rdf:RDF</code> elements are recognized as the top-level element introducing an XMP fragment (as per the XMP specification).</p>
+<h2 id="xmp-example">Example</h2>
+<p>[..]
+</fo:layout-master-set>
+<fo:declarations>
+  <x:xmpmeta xmlns:x="adobe:ns:meta/">
+    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
+      <rdf:Description rdf:about=""
+          xmlns:dc="http://purl.org/dc/elements/1.1/">
+        <!-- Dublin Core properties go here -->
+        <dc:title>Document title</dc:title>
+        <dc:creator>Document author</dc:creator>
+        <dc:description>Document subject</dc:description>
+      </rdf:Description>
+      <rdf:Description rdf:about=""
+          xmlns:xmp="http://ns.adobe.com/xap/1.0/">
+        <!-- XMP properties go here -->
+        <xmp:CreatorTool>Tool used to make the PDF</xmp:CreatorTool>
+      </rdf:Description>
+    </rdf:RDF>
+  </x:xmpmeta>
+</fo:declarations>
+&lt;fo:page-sequence ...
+[..] <code>fo:declarations</code>  <strong>must</strong> be declared after <code>fo:layout-master-set</code> and before the first <code>page-sequence</code> .</p>
+<h1 id="xmp-impl-in-fop">Implementation in Apache FOP</h1>
+<p>Currently, XMP support is only available for PDF output.</p>
+<p>Originally, you could set some metadata information through FOP's FOUserAgent by using its set*() methods (like setTitle(String) or setAuthor(String). These values are directly used to set value in the PDF Info object. Since PDF 1.4, adding metadata as an XMP document to a PDF is possible. That means that there are now two mechanisms in PDF that hold metadata.</p>
+<p>Apache FOP now synchronizes the Info and the Metadata object in PDF, i.e. when you set the title and the author through the FOUserAgent, the two values will end up in the (old) Info object and in the new Metadata object as XMP content. If instead of FOUserAgent, you embed XMP metadata in the XSL-FO document (as shown above), the XMP metadata will be used as-is in the PDF Metadata object and some values from the XMP metadata will be copied to the Info object to maintain backwards-compatibility for PDF readers that don't support XMP metadata.</p>
+<p>The mapping between the Info and the Metadata object used by Apache FOP comes from the <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=38920">PDF/A-1 specification</a> . For convenience, here's the mapping table:</p>
+<table>
+<thead>
+<tr>
+<th>Document information dictionary</th>
+<th>XMP</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Entry</td>
+<td>PDF type</td>
+</tr>
+<tr>
+<td>-------</td>
+<td>----------</td>
+</tr>
+<tr>
+<td>Title</td>
+<td>text string</td>
+</tr>
+<tr>
+<td>Author</td>
+<td>text string</td>
+</tr>
+<tr>
+<td>Subject</td>
+<td>text string</td>
+</tr>
+<tr>
+<td>Keywords</td>
+<td>text string</td>
+</tr>
+<tr>
+<td>Creator</td>
+<td>text string</td>
+</tr>
+<tr>
+<td>Producer</td>
+<td>text string</td>
+</tr>
+<tr>
+<td>CreationDate</td>
+<td>date</td>
+</tr>
+<tr>
+<td>ModDate</td>
+<td>date</td>
+</tr>
+<tr>
+<td>"Internal" in the Category column means that the user should not set this value. It is set by the application.The "Subject" used to be mapped to <code>dc:subject</code> in the initial publication of PDF/A-1 (ISO 19005-1). In the <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45613">Technical Corrigendum 1</a> this was changed to map to <code>dc:description["x-default"]</code> .</td>
+<td></td>
+</tr>
+<tr>
+<td id="namespaces">## Namespaces</td>
+<td></td>
+</tr>
+</tbody>
+</table>
+<p>Metadata is made of property sets where each property set uses a different namespace URI.</p>
+<p>The following is a listing of namespaces that Apache FOP recognizes and acts upon, mostly to synchronize the XMP metadata with the PDF Info dictionary:</p>
+<table>
+<thead>
+<tr>
+<th>Set/Schema</th>
+<th>Namespace Prefix</th>
+<th>Namespace URI</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Dublin Core</td>
+<td>dc</td>
+<td>http://purl.org/dc/elements/1.1/</td>
+</tr>
+<tr>
+<td>XMP Basic</td>
+<td>xmp</td>
+<td>http://ns.adobe.com/xap/1.0/</td>
+</tr>
+<tr>
+<td>Adobe PDF Schema</td>
+<td>pdf</td>
+<td>http://ns.adobe.com/pdf/1.3/</td>
+</tr>
+</tbody>
+</table>
+<p>Please refer to the <a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">XMP Specification</a> for information on other metadata namespaces.</p>
+<p>Property sets (Namespaces) not listed here are simply passed through to the final document (if supported). That is useful if you want to specify a custom metadata schema.</p>
+<h1 id="links">Links</h1>
+<ul>
+<li>
+<p><a href="http://www.adobe.com/products/xmp/">Adobe's Extensible Metadata Platform (XMP) website</a> </p>
+</li>
+<li>
+<p><a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">Adobe XMP Specification</a> </p>
+</li>
+<li>
+<p><a href="http://partners.adobe.com/public/developer/en/xmp/sdk/XMPspecification.pdf">Adobe XMP Specification</a> </p>
+</li>
+<li>
+<p><a href="http://dublincore.org/">http://dublincore.org/</a> </p>
+</li>
+</ul></div></div>
+      <div class="clear"></div>
+
+	  <div id="footer">
+		<a alt="Apache Software Foundation" href="http://www.apache.org">
+		  <img id="asf-logo" alt="Apache Software Foundation" src="/images/feather-small.gif"/ width="100">
+		</a>
+		<div class="copyright">
+		  <p>
+			Copyright &copy; 2011 The Apache Software Foundation, Licensed under
+			the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.
+			<br />
+			Apache, Apache XML Graphics, the Apache feather logo, and the Apache XML Graphics logos are
+			trademarks of <a href="http://www.apache.org">The Apache Software Foundation</a>. All other
+			marks mentioned may be trademarks or registered trademarks of their respective owners.
+			<br />
+		  </p>
+		</div> 
+	  </div>
+  </body>
+</html>



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


Mime
View raw message