xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r813018 [16/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/dev/design/useragent.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/design/useragent.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/useragent.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,209 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Design: User Agent</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 Design: User Agent</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/design/">Design</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version><authors><person email="keiron@aftexsw.com" name="Keiron Liddle"></person></authors></p>
+<h1 id="intro">Introduction</h1>
+<p>Technically the user agent is Apache™ FOP in the role of determining the output format and when resolving various attributes. The user agent is represented by a class that is available to others to specify how FOP should behave.</p>
+<p>The user agent is used by the formatting process to determine certain user definable values.</p>
+<p>It will enable the customisation of values for generating and rendering the document.</p>
+<p>The user agent must be available to the layout processor and the renderer. Users can supply their own user agent or use the default one for a particular renderer.</p>
+<p>The user agent needs to be made available to the property resolution layout process and the renderer.</p>
+<p>Standard Features:</p>
+<ul>
+<li>
+<p>error handling, what to do if fo markup is invalid</p>
+</li>
+<li>
+<p>auto overflow value and handling error-if-overflow</p>
+</li>
+<li>
+<p>adjusting length values (eg. for borders) to renderable values</p>
+</li>
+<li>
+<p>available fonts</p>
+</li>
+<li>
+<p>converting cm/in to pt (dpi)</p>
+</li>
+<li>
+<p>active state for multi properties</p>
+</li>
+<li>
+<p>title, used to identify a set of pages (in a page sequence)</p>
+</li>
+<li>
+<p>the width (in inline-progression-dimension) of a character with treat-word-as-space true</p>
+</li>
+<li>
+<p>maximum space used by conditional areas from region-reference-area</p>
+</li>
+<li>
+<p>if there should be "hot links" to before floats or footnotes</p>
+</li>
+<li>
+<p>when to clear side floats if space in inline-progression-dimension is not enough</p>
+</li>
+<li>
+<p>placement of left over footnotes on a page with a region-body</p>
+</li>
+<li>
+<p>using color property as border colour</p>
+</li>
+<li>
+<p>interpretting all border styles (except outset) as solid</p>
+</li>
+<li>
+<p>thin, medium and thick values for border width</p>
+</li>
+<li>
+<p>initial font-family value</p>
+</li>
+<li>
+<p>absolute font sizes (eg, xx-small, x-small etc.)</p>
+</li>
+<li>
+<p>relative font sizes (eg. larger, smaller)</p>
+</li>
+<li>
+<p>small caps simulation</p>
+</li>
+<li>
+<p>font weight mapping</p>
+</li>
+<li>
+<p>baseline info for a font if not available</p>
+</li>
+<li>
+<p>determining sub/superscript when another baseline is dominant</p>
+</li>
+<li>
+<p>scaling method for external-graphic and instream-foreign-object</p>
+</li>
+<li>
+<p>the width of a replaced element</p>
+</li>
+<li>
+<p>"normal" line height value</p>
+</li>
+<li>
+<p>text alignment (stretching the line with letter and word spacing)</p>
+</li>
+<li>
+<p>text transform</p>
+</li>
+<li>
+<p>initial color</p>
+</li>
+<li>
+<p>rendering intent of auto</p>
+</li>
+<li>
+<p>dot character for leader</p>
+</li>
+<li>
+<p>line breaking with leaders, use optimum length when breaking the line</p>
+</li>
+<li>
+<p>page height/width of auto</p>
+</li>
+<li>
+<p>left and right caption widths</p>
+</li>
+<li>
+<p>glyph orientation vertical of auto</p>
+</li>
+<li>
+<p>rendering processor of content-type (mime type)</p>
+</li>
+</ul>
+<p>Interactive Features:</p>
+<ul>
+<li>
+<p>inline and block scroll amount</p>
+</li>
+<li>
+<p>dynamic effects, links and property sets</p>
+</li>
+<li>
+<p>initial "pause-after", "pause-before" and "voice-family" value</p>
+</li>
+<li>
+<p>treating fixed as scroll on background attachement</p>
+</li>
+<li>
+<p>media usage of auto</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/dev/doc.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,187 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: Managing Documentation</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 Development: Managing Documentation</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="general">General Information</h1>
+<p>All raw documentation content is managed in the Apache™ FOP SVN repository. Updates should be committed to the repository, then the repository files are used to generate usable output. The remaining discussions on this page assume that the SVN repository is the starting place for processing. The path to the documentation is src/documentation/content/xdocs.
+All documentation is maintained on the trunk.
+Basic documents are stored in XML files, and use DTDs provided by Apache Forrest.</p>
+<h1 id="design">Design Principles</h1>
+<p>These principles are not written in stone, but reflect the current philosophy, and are documented here primarily to help achieve consistency. These principles should be changed if better or more practical ones are found, but they should probably be discussed and changed by common consent.</p>
+<h2 id="where">Where</h2>
+<ul>
+<li>
+<p>To the extent possible, keep user content separate from developer content, primarily so the user doesn't have to filter out technical information.</p>
+</li>
+<li>
+<p>To the extent possible, try to document a topic exactly once, in the place the user is most likely to look for it, then link to that from other locations as appropriate. This is somewhat contrary to the principle above, which should be applied as a higher priority.</p>
+</li>
+</ul>
+<h2 id="design-when">When</h2>
+<p>The documentation and the product are in a constant state of change, and there is some difficulty in deciding what product state the website content should reflect. The current thinking is that the website should reflect the current state of the repository code branch from which releases are made. Features or other documentation that applies to unreleased code should be marked in such a way within the content that the user can determine whether and how it applies to the version they are using. For example, "Feature xyz is first available in Release n.nn.n".</p>
+<p>Other approaches were considered, but all seemed to have significantly higher costs both to the users and the developers. From the user's standpoint, the choice is either that they potentially have to look multiple places to get the information they need (which was rejected), or they have to filter out an occasional feature that is in code available subsequent to their release (which was accepted).</p>
+<h1 id="web">Website</h1>
+<h2 id="web-background">Background</h2>
+<p>The FOP web site and documentation are generated using <a href="http://forrest.apache.org">Apache Forrest</a> .</p>
+<p>The following table summarizes the flow of data to the FOP website in chronological order:</p>
+<table>
+<thead>
+<tr>
+<th>Process</th>
+<th>Output</th>
+<th>State</th>
+<th>View(s)</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Developer commits code to FOP repository.</td>
+<td>FOP repository (SVN)</td>
+<td>Raw XML and other content</td>
+<td><a href="http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/">in SVN</a></td>
+</tr>
+<tr>
+<td>Developer builds and uploads documentation using ForrestBot.</td>
+<td>/www/xmlgraphics.apache.org/fop on people.apache.org</td>
+<td>sync-ready</td>
+<td>n/a</td>
+</tr>
+<tr>
+<td>Cron job runs rsync to synchronize the website with the real web server (runs every few hours).</td>
+<td>Infrastructure knows. :-)</td>
+<td>web-ready</td>
+<td><a href="http://xmlgraphics.apache.org/fop">FOP Web Site</a></td>
+</tr>
+<tr>
+<td>Server-side ForrestBot is currently not available for website publishing. We use it locally and with manual invocation.</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td id="web-forrestbot-publish">## ForrestBot "publish" Step-by-Step</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+</tbody>
+</table>
+<p>We're using ForrestBot for build and deploy the FOP website. ForrestBot comes with Apache Forrest 0.8. The root directory of your FOP checkout contains the file "publish.xml" which is an Ant build file that manages the build and the deployment of the FOP website. Please look into this file for further instructions to set up ForrestBot on your machine. Basically, we're simply running ForrestBot manually by typing "ant -f publish.xml" once we're happy with our changes to the site. Step-by-step instructions for the deployment process again:
+Please make sure you use Forrest from the Trunk (revision 632959 or later) for the time being. You will need to download it directly from SVN: <a href="http://svn.apache.org/repos/asf/forrest/trunk">http://svn.apache.org/repos/asf/forrest/trunk</a> </p>
+<ul>
+<li>
+<p>Modify the sources of the website and check locally with Forrest (run "forrest run" or just "forrest").</p>
+</li>
+<li>
+<p>Once you're satisfied, run "ant -f publish.xml" to do a clean build of the website. If the build runs without problems, the website will be uploaded as a whole using SVN to the <a href="https://svn.apache.org/repos/asf/xmlgraphics/site/deploy/fop/">website staging directory in SVN</a> .</p>
+</li>
+<li>
+<p>Then log into people.apache.org using SSH, go to the /www/xmlgraphics.apache.org directory and run "svn up".</p>
+</li>
+<li>
+<p>Wait for the next rsync cycle and check your changes in the live site. (Sorry, no manual rsync available ATM)</p>
+</li>
+</ul>
+<p>The reason for putting the generated website in the SVN repository: The infrastructure people want to be able to restore the websites themselves in case of a crash.</p>
+<h2 id="web-local-forrest">Using a Local Forrest</h2>
+<p>To use a local Forrest (during website development, not for deployment):</p>
+<ul>
+<li>
+<p><a href="http://forrest.apache.org/mirrors.cgi#closest">download</a> latest the Forrest release (currently Forrest 0.8)</p>
+</li>
+<li>
+<p>set environment variable FORREST_HOME=~/apache-forrest-0.8 where ~ is the directory where Forrest is installed (see <a href="http://forrest.apache.org/docs/your-project.html">http://forrest.apache.org/docs/your-project.html</a> for details)</p>
+</li>
+<li>
+<p>set environment variable PATH=$PATH:$FORREST_HOME/bin</p>
+</li>
+<li>
+<p>cd to your local FOP checkout</p>
+</li>
+<li>
+<p>update your local FOP checkout (svn update)</p>
+</li>
+<li>
+<p>run forrest(.bat), which will build the web-site documents in xml-fop/build/site.
+You can use "forrest run" to start a local web server. That improves development speed as you can simply refresh in the browser after a change.</p>
+</li>
+</ul>
+<h2 id="distribution">Updating Distribution Files</h2>
+<p>The Apache distribution system mirrors distributions around the world. Since it uses <a href="http://httpd.apache.org/">Apache httpd</a> Module <a href="http://httpd.apache.org/docs/2.2/mod/mod_autoindex.html#headername">mod_autoindex</a> you also need to manually update the HEADER.html &amp; READER.html files on <code>people.apache.org</code> in <code>/www/www.apache.org/dist/xmlgraphics/fop/</code> .</p>
+<p>Please be careful when doing stuff like that.</p>
+<h2 id="delete">Deleting Documentation Files</h2>
+<p>ForrestBot simply uploads the whole generated site. It doesn't delete obsolete files. You can do that manually in the /www/xmlgraphics.apache.org/fop folder on cvs.apache.org. Be careful when doing stuff like that.
+Please make sure you always have <strong>group rw permissions on all files</strong> under the /www directory!</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/dev/extensions.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/extensions.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/extensions.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,117 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: Adding an Extension</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 Development: Adding an Extension</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="overview">Overview</h1>
+<p>For documentation of standard Apache™ FOP extensions, see the <a href="../trunk/extensions.html">User FOP Extensions</a> document.</p>
+<p>If the default funtionality of FOP needs to be extended for some reason then you can write an extension.</p>
+<p>There are three types of extensions possible:</p>
+<ul>
+<li>
+<p>An output document extension such as the PDF bookmarks</p>
+</li>
+<li>
+<p>an instream-foreign-object extensions such as SVG</p>
+</li>
+<li>
+<p>an fo extension that creates an area in the area tree where normal xsl:fo is not possible</p>
+</li>
+</ul>
+<h1 id="adding">Adding Your Own</h1>
+<p>To add your own extension you need to do the following things.</p>
+<ol>
+<li>
+<p>Write code that implements your extension functionality. The easiest place to start is by looking at the code in org.apache.fop.fo.extensions, and by looking at the examples in the <code>examples</code> directory.</p>
+</li>
+<li>
+<p>Create a class that extends the abstract org.apache.fop.fo.ElementMapping class. ElementMapping is a hashmap of all of the elements in a particular namespace, which makes it easier for FOP to create a different object for each element. ElementMapping objects are static to save on memory. They are loaded by FOP when parsing starts to validate input.</p>
+</li>
+<li>
+<p>Create the following file: "/META-INF/services/org.apache.fop.fo.ElementMapping", which should contain the fully qualified classname of your ElementMapping implementation class.</p>
+</li>
+<li>
+<p>Create a jar file containing all of the above files.</p>
+</li>
+<li>
+<p>Create your XSL-FO file with the extra XML data embedded in the file with the correct name space. The examples for SVG and pdfoutline.fo show how this can be done. The pdf documents on the FOP site use this extension. See also <a href="../examples.html">Examples</a> for more examples.</p>
+</li>
+<li>
+<p>Put your jar file in the classpath</p>
+</li>
+<li>
+<p>Run FOP using your XSL-FO file as input.</p>
+</li>
+</ol></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/dev/faq.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/faq.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/faq.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,102 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: FAQ</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 Development: FAQ</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><h1 id="Questions">Questions</h1>
+<h2 id="part_general">1. General Questions</h2>
+<h3 id="faq-N1000D">1.1. How can I contribute?</h3>
+<p>There are many ways that you can help:</p>
+<ul>
+<li>
+<p>You can help us implement missing features that are needed in order to comply with the standard. See the <a href="../compliance.html">Standards Compliance</a> for more details.</p>
+</li>
+<li>
+<p>You can help us address bug reports. See <a href="../bugs.html#issues_existing">bugzilla</a> for more information.</p>
+</li>
+<li>
+<p>You can help support our user base by answering questions on the fop-user mailing list.</p>
+</li>
+<li>
+<p>You can help us document FOP better.</p>
+</li>
+</ul>
+<h2 id="part_documentation">2. Documentation</h2>
+<h3 id="javadoc_location">2.1. How do I get the javadocs for FOP?</h3>
+<p>Currently, the only way to get FOP javadocs is to <a href="../download.html">Download the source code</a> and then <a href="../trunk/compiling.html">Build FOP</a> using the ant build task "javadocs".</p>
+<h3 id="doc-mgt">2.2. Where can I learn how the FOP docs and web site are built?</h3>
+<p>See FOP <a href="doc.html">Doc Management</a> . ;-)</p>
+<h2 id="part_further_help">3. Further Help</h2>
+<h3 id="other_faqs">3.1. I don't see my question addressed here. Are there other FAQs?</h3>
+<p>Yes. See also the <a href="../faq.html">FOP General FAQs</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/dev/fo/embedding.fo
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/fo/embedding.fo
------------------------------------------------------------------------------
    svn:mime-type = application/xml

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/fo/embedding.fo.pdf
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/fo/embedding.fo.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/implement.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/implement.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/implement.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,131 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: Implementation Overview</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 Development: Implementation Overview</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><subtitle>Following a Document Through Apache� FOP</subtitle><version>$Revision: 1298724 $</version><authors><person email="" name="Arved Sandstrom"></person></authors></p>
+<p>The purpose of this document is to tie together the Apache™ FOP design (interface) with some of the key points where control is passed within FOP (implementation), so that developers can quickly find the section of code that is relevant to their needs. The process described is for a "typical" command-line document. All classes are in org.apache.fop unless otherwise designated.</p>
+<h1 id="Overview">Overview</h1>
+<p>The input FO document is sent to the FO tree builder via SAX events. Fragments of an FO Tree are built from this process. As each page-sequence element is completed, it is passed to a layout processor, which in turn converts it into an Area Tree. The Area Tree is then given to the Renderer, which converts it into a stream of data containing the output document. The sections below will provide additional details. Where needed differences between the trunk and maintenance branches are shown in tabular format.</p>
+<h1 id="Startup">Startup</h1>
+<ul>
+<li>
+<p>The job starts in <em>apps.Fop.main()</em> .</p>
+</li>
+<li>
+<p>Control is passed to <em>apps.CommandLineStarter.run()</em> .</p>
+</li>
+<li>
+<p>Control is passed to <em>apps.Driver.render()</em> . This class fires up a SAX parser, the events from which indirectly control the remaining processing, including building the FO Tree, building the Area Tree, rendering, output and logging.</p>
+</li>
+</ul>
+<h1 id="formatting-object-tree-formattingobjecttree">Formatting Object Tree # {#Formatting+Object+Tree}</h1>
+<table>
+<thead>
+<tr>
+<th>Trunk</th>
+<th>Maintenance</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>The SAX events that the parser creates are handled by <em>fo.FOTreeBuilder</em> , which uses <code>startElement()</code> , <code>endElement()</code> , and <code>characters()</code> methods to build the FO Tree.</td>
+<td></td>
+</tr>
+<tr>
+<td><code>fo.FOTreeBuilder.endElement()</code> runs the <code>end()</code> method for each node as it is created. The <em>fo.pagination.PageSequence</em> class overrides this <code>end()</code> method to run <code>apps.LayoutHandler.endPageSequence()</code> , which in turn runs <code>fo.pagination.PageSequence.format()</code> .</td>
+<td>the end of a PageSequence element causes the PageSequence object to be passed to <code>apps.StreamRenderer.render()</code> , which in turn runs <code>fo.pagination.PageSequence.format()</code> .</td>
+</tr>
+<tr>
+<td><code>fo.pagination.PageSequence.format()</code> creates a <em>layoutmgr.PageLayoutManager</em> , passing the AreaTree and PageSequence objects to it, then calls its <code>run()</code> method.</td>
+<td><code>fo.pagination.PageSequence.addFlow()</code> programatically adds a Flow object to the page sequence.</td>
+</tr>
+<tr>
+<td>.</td>
+<td><code>fo.pagination.PageSequence.makePage()</code> creates a BodyArea and passes it to <em>fo.Flow.layout</em></td>
+</tr>
+<tr>
+<td>.</td>
+<td>the layout process is then driven from <code>fo.pagination.PageSequence.format()</code> .</td>
+</tr>
+</tbody>
+</table>
+<h1 id="Layout">Layout</h1>
+<p>There are layout managers for each type of layout decision. They take an FO Tree as input and build a laid-out Area Tree from it. The layout process involves finding out where line breaks and page breaks should be made, then creating the areas on the page. Static areas can then be added for any static regions. As pages are completed, they are added to the Area Tree.</p>
+<h1 id="area-tree-areatree">Area Tree # {#Area+Tree}</h1>
+<p>The area tree is a data structure designed to hold the page areas. These pages are then filled with the page regions and various areas. The area tree is used primarily as a minimal structure that can be rendered by the renderers.</p>
+<p>The area tree is supported by an area tree model. This model handles the adding of pages to the area tree. It also handles page sequence starts, document level extensions, id references and unresolved id areas. This model allows the pages to be handled directly by a renderer or to store the pages for later use.</p>
+<h1 id="Rendering">Rendering</h1>
+<p>The renderer receives pages from the area tree and renders those pages. If a renderer supports out of order rendering then it will either render or prepare a page in the correct order. Otherwise the pages are rendered in order. The task of the renderer is to take the pages and output them to the requested type. In the case of the AWTRenderer it needs to be able to view any page.</p>
+<p>When rendering a page it takes the page and renders each page region. The main work for a renderer implementation is to handle the viewports and inline areas. The inline areas need to be drawn on the page in the correct place.</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/dev/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/index.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/index.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,227 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: General Information</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 Development: General Information</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</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>These pages contain information that should be helpful for those developing Apache™ FOP. This certainly includes programmers, but may also include those contributing to the project in other ways.</p>
+<p>For basic and user information on FOP, please visit the <a href="http://xml.apache.org/fop">Apache™ FOP homepage</a> .</p>
+<h1 id="lines">Development</h1>
+<p>The main development happens on "FOP Trunk".
+The SVN repository URL for the trunk is:<br></br> <code>http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/</code> </p>
+<h1 id="involved">Getting Involved</h1>
+<h2 id="apache-roles">Understand Apache Roles</h2>
+<p>Review the <a href="http://xml.apache.org/roles.html">Apache Project Roles and Responsibilities</a> document for an understanding of the various roles of contributors within the community.</p>
+<h2 id="fop-tasks">How you can help</h2>
+<p>There are many different ways that you can help with FOP development. The following is a non-exhaustive list of ways that <em>non-programmers</em> can help. Remember that an hour spent on the tasks below is an hour that a programmer can devote to fixing bugs or adding features instead:</p>
+<ul>
+<li>
+<p>Answer questions on the fop-user mailing list.</p>
+</li>
+<li>
+<p>Contribute examples that are useful to other users.</p>
+</li>
+<li>
+<p>Contribute test cases.</p>
+</li>
+<li>
+<p>Submit well-written feature requests.</p>
+</li>
+<li>
+<p>Submit well-written bug reports.</p>
+</li>
+<li>
+<p>Review open issues to see if you have any insight into them that might help a programmer solve the problem faster. Add comments and test cases as appropriate.</p>
+</li>
+<li>
+<p>Test newly-closed issues to make sure they are truly closed.</p>
+</li>
+<li>
+<p>Submit patches to the documentation.</p>
+</li>
+</ul>
+<p>Of course, we're glad to have programmers help as well. Here are some additional tasks that would require programming ability:</p>
+<ul>
+<li>
+<p>Fixing bugs.</p>
+</li>
+<li>
+<p>Implementing new features.</p>
+</li>
+</ul>
+<h2 id="fop-standards">Understand FOP-related standards</h2>
+<p>At the moment FOP is mainly a tool to render XSL-FO files to pdf. Therefore if you want to contribute to FOP you should become familiar with these standards. You can find links at <a href="../resources.html#specs">Specifications</a> .</p>
+<h2 id="doc">Review the Developer Documentation</h2>
+<h2 id="design">Understand FOP's Design</h2>
+<p>The design for FOP is specified under the <a href="design/index.html">Design</a> section. This is where the information on how FOP is developed and designed internally will be kept.</p>
+<p>Another place where we write design documentation is the <a href="http://wiki.apache.org/xmlgraphics-fop/DeveloperPages">FOP Wiki</a> .
+Our design documentation may not always be up to date!</p>
+<h2 id="mail-fop-dev">Subscribe to the fop-dev Mailing List</h2>
+<p>Use this forum to discuss topics related to FOP development, including patch submissions, bug reports, and design issues. Please <em>do not</em> use it for XML support, XSLT support, XSL-FO support, or even FOP support. Appropriate mailing lists for these topics can be found on the <a href="../maillist.html">FOP Mailing List</a> page.</p>
+<ul>
+<li>
+<p>To review the archives, you have several options:</p>
+<ul>
+<li>
+<p>The <a href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-dev/">Apache Mailing List archive (mod_mbox)</a> .</p>
+</li>
+<li>
+<p>The <a href="http://xmlgraphics.apache.org/mail/fop-dev/">Apache Mailing List archive (gzipped mbox files)</a> .</p>
+</li>
+<li>
+<p>The <a href="http://marc.theaimsgroup.com/?l=fop-dev&amp;r=1&amp;w=2">Mailing list ARChives</a> (MARC) at the AIMS group (search).</p>
+</li>
+<li>
+<p><a href="http://www.mail-archive.com/fop-dev%40xmlgraphics.apache.org/">The Mail Archive</a> .</p>
+</li>
+<li>
+<p>The <a href="http://dir.gmane.org/gmane.text.xml.fop.devel">GMANE</a> archive.</p>
+</li>
+<li>
+<p>The <a href="http://www.nabble.com/FOP---Dev-f352.html">Nabble</a> archive.</p>
+</li>
+<li>
+<p>The <a href="http://fop-dev.markmail.org">MarkMail</a> archive.</p>
+</li>
+</ul>
+</li>
+<li>
+<p>Before posting questions to any list, see " <a href="../maillist.html#general">General Information</a> ".</p>
+</li>
+<li>
+<p>See <a href="http://xmlgraphics.apache.org/mail.html">Apache XML Graphics Mailing Lists</a> for detailed subscription information.</p>
+</li>
+<li>
+<p>To subscribe (digest only): Send email to <a href="mailto:fop-dev-digest-subscribe@xmlgraphics.apache.org">fop-dev-digest-subscribe@xmlgraphics.apache.org</a> .</p>
+</li>
+<li>
+<p>To subscribe fully: Send email to <a href="mailto:fop-dev-subscribe@xmlgraphics.apache.org">fop-dev-subscribe@xmlgraphics.apache.org</a> .</p>
+</li>
+<li>
+<p>For standard help: Send email to <a href="mailto:fop-dev-help@xmlgraphics.apache.org">fop-dev-help@xmlgraphics.apache.org</a> .</p>
+</li>
+<li>
+<p>To unsubscribe: Send email to <a href="mailto:fop-dev-unsubscribe@xmlgraphics.apache.org">fop-dev-unsubscribe@xmlgraphics.apache.org</a> .</p>
+</li>
+</ul>
+<h2 id="mail-fop-cvs">Subscribe to the fop-commits Mailing List</h2>
+<p>When changes are committed to the code repository, a record of the diffs is emailed to the fop-cvs mailing list. FOP developers are encouraged to subscribe to this list because it helps in following the progress of the project.</p>
+<ul>
+<li>
+<p>To review the archives, you have several options:</p>
+<ul>
+<li>
+<p>The <a href="http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-commits/">Apache Mailing List archive (mod_mbox)</a> .</p>
+</li>
+<li>
+<p>The <a href="http://xmlgraphics.apache.org/mail/fop-commits/">Apache Mailing List archive (gzipped mbox files)</a> .</p>
+</li>
+<li>
+<p>The <a href="http://marc.theaimsgroup.com/?l=fop-cvs&amp;r=1&amp;w=2">Mailing list ARChives</a> (MARC) at the AIMS group (search).</p>
+</li>
+<li>
+<p><a href="http://www.mail-archive.com/fop-commits%40xmlgraphics.apache.org/">The Mail Archive</a> .</p>
+</li>
+<li>
+<p>The <a href="http://dir.gmane.org/gmane.text.xml.fop.cvs">GMANE</a> archive.</p>
+</li>
+<li>
+<p>The <a href="http://fop-commits.markmail.org">MarkMail</a> archive.</p>
+</li>
+</ul>
+</li>
+<li>
+<p>Subscribe by sending an email to <a href="mailto:fop-commits-subscribe@xmlgraphics.apache.org">fop-commits-subscribe@xmlgraphics.apache.org</a> .</p>
+</li>
+</ul>
+<h2 id="dev-code">Download and Use the Developers' Code Using Subversion</h2>
+<p>Between releases the newest code can be accessed via SVN. To do this you need to install a SVN client on your computer, if it is not already there. An explanation how to connect to the FOP source repository can be found at <a href="http://xmlgraphics.apache.org/repo.html">http://xmlgraphics.apache.org/repo.html</a> . More information can be found on the <a href="tools.html">Tools page</a> .</p>
+<h2 id="patches">Submitting Patches</h2>
+<p>If you have useful changes to source code (bugfixes or enhancements), test files, or documentation that you would like to contribute to the project, please do the following:</p>
+<ul>
+<li>
+<p>If your changes include source code, make sure that it does not break FOP (i.e. make sure that FOP still compiles with your changes).</p>
+</li>
+<li>
+<p>If your changes include test files, review the <a href="testing.html">Testing page</a> .</p>
+</li>
+<li>
+<p><a href="tools.html#patches">Create a patch file</a> for the differences to be applied to the existing code.</p>
+</li>
+<li>
+<p><a href="../bugs.html#issues_new">Create a new bugzilla issue</a> for the patch. Include the text "[PATCH]" at the beginning of the description. Attach the patch file to the issue.</p>
+</li>
+</ul>
+<p>One of the committers will test your patch and consider its implications for the project. They will then either commit it to the repository or explain on the issue why they did not. Depending on the work load and skill-sets of the various committers, it may take some time before a a submitted patch is addressed.</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/dev/release.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/release.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/release.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,265 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: Release Mechanics</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 Development: Release Mechanics</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1310603 $</version></p>
+<h1 id="intro">Introduction</h1>
+<p>This page documents the process of creating a Apache™ FOP release. FOP releases are coordinated by some designated member of the team. The purpose of documenting it here is to facilitate consistency, ensure that the process is captured, and to allow others to comment on the process.</p>
+<p>The checklist below is based on a combination of input from from Christian Geisert and Simon Pepping.</p>
+<h1 id="checklist">Checklist</h1>
+<ul>
+<li>
+<p>Determine which open bugs must be solved before a release can take place (release critical bugs). Make this bug depend on each release critical bug and write a short argument why the bug is release critical.</p>
+</li>
+<li>
+<p>Determine whether this is a Release Candidate or a Release.</p>
+</li>
+<li>
+<p>Determine whether further testing is required.</p>
+</li>
+<li>
+<p>Commit any outstanding changes</p>
+</li>
+<li>
+<p>Create a branch called <code>branches/fop-v_vv</code> </p>
+</li>
+<li>
+<p>Edit release notes ( <code>README</code> and <code>status.xml</code> in the root).</p>
+</li>
+<li>
+<p>Add the release to <code>news-data.xml</code> ; remove links to release notes of older versions from this file.</p>
+</li>
+<li>
+<p>Update the FAQ ( <code>faq.xml</code> ) to the new release, e.g., update the answer for "When is the next release planned?".</p>
+</li>
+<li>
+<p>Check and update the copyright year in NOTICE and build.xml.</p>
+</li>
+<li>
+<p>Update the file <code>doap.rdf</code> , and the files <code>index.xml</code> , <code>site.xml</code> , <code>download.xml</code> , <code>fo.xml</code> , <code>maillist.xml</code> , and <code>quickstartguide.xml</code> in directory <code>xdocs</code> for the new version.</p>
+</li>
+<li>
+<p>Update the version numbers in the release column on the compliance page ( <code>compliance.xml</code> ); update the compliance in the release column to the current state (development column).</p>
+</li>
+<li>
+<p>Update version number in <code>build.xml</code> (not to be merged back into trunk).</p>
+</li>
+<li>
+<p>Copy trunk documentation directory to a new directory with the new version number, and update the <code>.htaccess</code> file for redirections.</p>
+</li>
+<li>
+<p>Copy <code>test/fotree/disabled-testcases.xml</code> and <code>test/layoutengine/disabled-testcases.xml</code> to the new version directory <code>&lt;version&gt;/fotree/disabled-testcases.xml</code> and <code>&lt;version&gt;/layoutengine/disabled-testcases.xml</code> . Copy <code>known-issues.xml</code> to the new version directory. Copy <code>knownissues-overview.xml</code> from the current to the new version directory, and update the <code>xi:include</code> links in it.</p>
+</li>
+<li>
+<p>Update the tab names and directories in <code>tabs.xml</code> </p>
+</li>
+<li>
+<p>Delete the previous version directory.</p>
+</li>
+<li>
+<p>Update <code>index.xml</code> in the new version directory.</p>
+</li>
+<li>
+<p>Update <code>compiling.xml</code> in the new version directory: change the introduction for trunk to that for a release.</p>
+</li>
+<li>
+<p>Build the dist files ( <code>build[.sh] dist</code> ) and upload them to your web directory on <code>people.apache.org</code> </p>
+</li>
+<li>
+<p>Ask on <code>fop-dev</code> ML to check the branch and the generated dist files for errors.</p>
+</li>
+<li>
+<p>Tag the source tree with the release ID. For example, if the release is 1.0: <code>svn copy https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-1_0 https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0</code> </p>
+</li>
+<li>
+<p>Make a fresh checkout with the just created tag: <code>svn co https://svn.apache.org/repos/asf/xmlgraphics/fop/tags/fop-1_0</code> </p>
+</li>
+<li>
+<p>Copy the hyphenation patterns jar file <code>fop-hyph.jar</code> to <code>lib</code> (e.g. from <code>http://sourceforge.net/projects/offo</code> </p>
+</li>
+<li>
+<p>Alternatively, create a <code>build-local.properties</code> file that points to the above libraries.</p>
+</li>
+<li>
+<p>Run <code>build[.sh] dist</code> . Do this using Sun JDK 1.5 or later. A Forrest installation is needed.</p>
+</li>
+<li>
+<p>Create signatures. Don't forget to upload your KEY: <code>gpg -a -b --force-v3-sigs fop-1.0-src.tar.gz</code> etc.</p>
+</li>
+<li>
+<p>Upload the dist and signature files to your web directory on people.apache.org (An account on minotaur is needed): <code>scp fop-1.0*.tar.gz* chrisg@people.apache.org:public_html/</code> </p>
+</li>
+<li>
+<p>Check permissions: <code>chmod 664 ... ; chgrp xmlgraphics ...</code> </p>
+</li>
+<li>
+<p>Add MD5 sums: <code>md5 fop-1.0-src.tar.gz &gt; fop-1.0-src.tar.gz.md5</code> etc.</p>
+</li>
+<li>
+<p>Make a test download.</p>
+</li>
+<li>
+<p>Start a vote for the release on <code>general@xmlgraphics.apache.org</code> . The message should point to the release files and list the MD5 sums ( <code>cat *.md5</code> ). The vote should remain open for 72hrs.</p>
+</li>
+<li>
+<p>When the release is accepted, copy the release files, their md5 sum files and the signature files to <code>/www/www.apache.org/dist/xmlgraphics/fop/</code> in the subdirectories <code>source</code> and <code>binaries</code> . Create links to all files in the <code>fop</code> directory. Remove the links to the files of the previous version.</p>
+</li>
+<li>
+<p>Update <code>HEADER.html</code> and <code>README.html</code> in <code>people.apache.org:/www/www.apache.org/dist/xmlgraphics/fop/</code> .</p>
+</li>
+<li>
+<p>Wait 24 hours (for the mirrors to catch up).</p>
+</li>
+<li>
+<p>Merge the changes of the subversion release branch back into trunk (not the version number in the build file) and delete the branch.</p>
+</li>
+<li>
+<p>Deploy the updated documentation to the FOP website.</p>
+</li>
+<li>
+<p>Post announcements on <code>fop-dev</code> and <code>fop-user</code> and other related mailing lists.</p>
+</li>
+<li>
+<p>Ask an FOP bugzilla admin to add a bugzilla entry for the new release id, or create an issue at <code>https://issues.apache.org/jira/browse/INFRA</code> .</p>
+</li>
+<li>
+<p>Deploy the maven bundle.</p>
+</li>
+</ul>
+<h1 id="other-checklists">Resources</h1>
+<p>The following is a sample of some other project release checklists, which might be consulted for ideas:</p>
+<ul>
+<li>
+<p><jump href="http://svn.apache.org/repos/asf/xmlgraphics/batik/trunk/MAINTAIN">Apache Batik</jump></p>
+</li>
+<li>
+<p><jump href="http://svn.apache.org/repos/asf/ant/core/trunk/ReleaseInstructions">Apache Ant</jump></p>
+</li>
+<li>
+<p><jump href="http://jakarta.apache.org/cactus/participating/release_checklist.html">Apache Cactus</jump></p>
+</li>
+</ul>
+<p>Following are links with information about mirroring:</p>
+<ul>
+<li>
+<p><jump href="http://www.apache.org/dev/mirrors.html">Apache Mirroring</jump></p>
+</li>
+<li>
+<p>Stefan Bodewig's<jump href="http://people.apache.org/~bodewig/mirror.html">Making your Downloads Mirrorable</jump></p>
+</li>
+</ul>
+<h1 id="announcements">Announcing the release</h1>
+<p>Here's a suggested list of places where to announce new FOP releases:</p>
+<ul>
+<li>
+<p>fop-dev@xmlgraphics.apache.org</p>
+</li>
+<li>
+<p>fop-users@xmlgraphics.apache.org</p>
+</li>
+<li>
+<p>general@xmlgraphics.apache.org</p>
+</li>
+<li>
+<p>general@xml.apache.org</p>
+</li>
+<li>
+<p>announce@apache.org (from your apache.org address)</p>
+</li>
+<li>
+<p>xsl-list@lists.mulberrytech.com (subscriber-only)</p>
+</li>
+<li>
+<p>xsl-fo@yahoogroups.com (subscriber-only)</p>
+</li>
+<li>
+<p>www-xsl-fo@w3.org</p>
+</li>
+<li>
+<p>docbook-apps@lists.oasis-open.org (subscriber-only)</p>
+</li>
+<li>
+<p>dita-users@yahoogroups.com (subscriber-only) (http://dita-ot.sourceforge.net/)</p>
+</li>
+<li>
+<p>http://xslfo-zone.com/news/index.jsp</p>
+</li>
+<li>
+<p>http://www.w3.org/Style/XSL/</p>
+</li>
+<li>
+<p>http://freshmeat.net/projects/fop/</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/dev/rtflib.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,394 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: RTFLib (jfor)</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 Development: RTFLib (jfor)</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<h1 id="general">General Information</h1>
+<h2 id="intro">Introduction</h2>
+<p>The RTFLib package is an open-source, <em>independent</em> package suitable for writing RTF files in a java environment. By <em>independent</em> we mean:</p>
+<ul>
+<li>
+<p>Although it is used by Apache™ FOP to generate FOP's RTF output, it is not dependent on FOP for any of its functionality.</p>
+</li>
+<li>
+<p>It does not require FOP as a front-end, nor does it even require XSL-FO for input. It essentially exposes an API of relatively high-level RTF construction routines to a host program. This means it can be used anywhere RTF output is required and java is available.</p>
+</li>
+</ul>
+<p>The FOP development team intends to keep the RTFLib package independent so that it can be used for other purposes.</p>
+<h2 id="history">History</h2>
+<p>RTFLib was originally developed by <a href="mailto:bdelacretaz@apache.org">Bertrand Delacrétaz</a> and the <a href="http://www.jfor.org">jfor</a> team. jfor was written under an Apache-style license, and the jfor team contributed the code to the Apache Software Foundation in June, 2003. RTFLib is a subset of the original jfor project, which also includes an XSL-FO parsing mechanism for a complete XSL-FO to RTF solution.</p>
+<h2 id="status">Status</h2>
+<p>Although FOP's implementation of the RTFLib package is very incomplete, the RTFLib package itself is relatively mature. RTFLib is only available in the trunk <a href="index.html#lines">line of FOP development</a> .
+<warning>This documentation is a work in progress. If you see errors or omissions, please report them to the <a href="index.html#mail-fop-dev">fop-dev mailing list</a> .</warning></p>
+<h1 id="userdoc">User Documentation</h1>
+<h2 id="userdoc-overview">Overview</h2>
+<p>Perhaps the easiest way to see how to use RTFLib is by looking at an example. A set of test documents is part of the package, and can be <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/">viewed online</a> . A quick look at the Abstract <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/TestDocument.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">TestDocument</a> class, and one of the Concrete subclasses, <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/SimpleDocument.java?rev=HEAD&amp;content-type=text/vnd.viewcvs-markup">SimpleDocument</a> will provide the basics of how to use the package.</p>
+<p>There are two basic concepts you will need to understand in order to use RTFLib:</p>
+<ul>
+<li>
+<p>Documents are created by filling bigger containers with successively smaller containers, and eventually with content.</p>
+</li>
+<li>
+<p>Attributes may be set for each container or content as it is created</p>
+</li>
+</ul>
+<p>RTFLib handles the process of converting to and writing the RTF content as the document is created. All you need to do is flush the document at the end to make sure that the last pieces get written.</p>
+<h2 id="userdoc-structure">Document Structure</h2>
+<p><warning>This section is very incomplete.</warning>
+The documentation in this section is intended to provide a high-level view of the process of building an RTF document. For more detailed API documentation of the various methods, be sure to consult the Javadocs for RTFLib.</p>
+<p>The following table summarizes the various containers that can be created:</p>
+<table>
+<thead>
+<tr>
+<th>Name</th>
+<th>Class.Method where created</th>
+<th>Attribute Set(s)</th>
+<th>Valid children</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Document Area</td>
+<td>RtfFile.startDocumentArea()</td>
+<td>Information Group, Document Formatting</td>
+<td>Section</td>
+</tr>
+<tr>
+<td>Section</td>
+<td>RtfDocumentArea.newSection()</td>
+<td>Section Formatting</td>
+<td>Paragraph, ParagraphKeepTogether, Image, List, Before (Page Heading), After (Page Footer), JforCmd</td>
+</tr>
+<tr>
+<td>Paragraph</td>
+<td>RtfSection.newParagraph()</td>
+<td>Paragraph Formatting, Character Formatting</td>
+<td>Text</td>
+</tr>
+<tr>
+<td>ParagraphKeepTogether</td>
+<td>RtfSection.newParagraphKeepTogether</td>
+<td>.</td>
+<td>.</td>
+</tr>
+<tr>
+<td>Image</td>
+<td>RtfSection.newImage</td>
+<td>.</td>
+<td>.</td>
+</tr>
+<tr>
+<td>Table</td>
+<td>RtfSection.newTable</td>
+<td>.</td>
+<td>.</td>
+</tr>
+<tr>
+<td>List</td>
+<td>RtfSection.newList</td>
+<td>.</td>
+<td>.</td>
+</tr>
+<tr>
+<td>Before (Page Heading)</td>
+<td>RtfSection.newBefore</td>
+<td>.</td>
+<td>.</td>
+</tr>
+<tr>
+<td>After (Page Footer)</td>
+<td>RtfSection.newAfter</td>
+<td>.</td>
+<td>.</td>
+</tr>
+<tr>
+<td>JforCmd</td>
+<td>RtfSection.newJforCmd</td>
+<td>.</td>
+<td>.</td>
+</tr>
+<tr>
+<td>Text</td>
+<td>RtfParagraph.newText()</td>
+<td>Character Formatting</td>
+<td>N/A</td>
+</tr>
+</tbody>
+</table>
+<h2 id="userdoc-attributes">Attributes</h2>
+<p><warning>This section is very incomplete.</warning>
+Attributes can be set for each container and piece of content in the document. The general approach is to build an RtfAttributes object containing the various attributes, then pass that RtfAttributes object to the method that creates the new container or content. See the Javadoc API documentation for RtfAttributes for details on the syntax for creating an RtfAttributes object. The following information lists the various attributes that can be set for each type of container.</p>
+<h3 id="userdoc-attr-ig">Information Group</h3>
+<p>These attributes are set when creating a Document.</p>
+<h3 id="userdoc-attr-df">Document Formatting</h3>
+<p>These attributes are set when creating a Document.</p>
+<h3 id="userdoc-attr-sf">Section Formatting</h3>
+<p>These attributes are set when creating a Section.</p>
+<h3 id="userdoc-attr-pf">Paragraph Formatting</h3>
+<p>These attributes are set when creating a Paragraph.</p>
+<table>
+<thead>
+<tr>
+<th>Description</th>
+<th>Attribute Name</th>
+<th>Attribute Value</th>
+<th>RTF Control Word</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>.</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td>Alignment</td>
+<td>.</td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td>-----------</td>
+<td>---</td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td>Align Left</td>
+<td>RtfText.ALIGN_LEFT</td>
+<td>N/A (boolean)</td>
+<td>\ql</td>
+</tr>
+<tr>
+<td>Align Right</td>
+<td>RtfText.ALIGN_RIGHT</td>
+<td>N/A (boolean)</td>
+<td>\qr</td>
+</tr>
+<tr>
+<td>Align Centered</td>
+<td>RtfText.ALIGN_CENTER</td>
+<td>N/A (boolean)</td>
+<td>\qc</td>
+</tr>
+<tr>
+<td>Align Justified</td>
+<td>RtfText.ALIGN_JUSTIFIED</td>
+<td>N/A (boolean)</td>
+<td>\qj</td>
+</tr>
+<tr>
+<td>Align Distributed</td>
+<td>RtfText.ALIGN_DISTRIBUTED</td>
+<td>N/A (boolean)</td>
+<td>\qd</td>
+</tr>
+<tr>
+<td>Kashida justification</td>
+<td>not implemented</td>
+<td>0-20 (integer)</td>
+<td>\qkN</td>
+</tr>
+<tr>
+<td>Thai Distributed justification</td>
+<td>not implemented</td>
+<td>N/A (boolean)</td>
+<td>\qt</td>
+</tr>
+<tr>
+<td>Indentation</td>
+<td>.</td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td>-------------</td>
+<td>---</td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td>Left indent body</td>
+<td>RtfText.LEFT_INDENT_BODY</td>
+<td>(int) "hundredths of a character unit" (?)</td>
+<td>\li</td>
+</tr>
+<tr>
+<td>Left indent first</td>
+<td>RtfText.LEFT_INDENT_FIRST</td>
+<td>(int) "hundredths of a character unit" (?)</td>
+<td>\fi</td>
+</tr>
+<tr>
+<td>Borders</td>
+<td>.</td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td>---------</td>
+<td>---</td>
+<td></td>
+<td></td>
+</tr>
+<tr>
+<td>Bottom single border</td>
+<td>RtfText.BDR_BOTTOM_SINGLE</td>
+<td>Boolean?</td>
+<td>brdrb\brsp40\brdrs</td>
+</tr>
+<tr>
+<td>Bottom double border</td>
+<td>RtfText.BDR_BOTTOM_DOUBLE</td>
+<td>Boolean?</td>
+<td>brdrb\brsp40\brdrdb</td>
+</tr>
+<tr>
+<td>Bottom embossed border</td>
+<td>RtfText.BDR_BOTTOM_EMBOSS</td>
+<td>Boolean?</td>
+<td>brdrb\brsp40\brdremboss</td>
+</tr>
+<tr>
+<td>bottom dotted border</td>
+<td>RtfText.BDR_BOTTOM_DOTTED</td>
+<td>Boolean?</td>
+<td>brdrb\brsp40\brdrdot</td>
+</tr>
+<tr>
+<td>bottom dashed border</td>
+<td>RtfText.BDR_BOTTOM_DASH</td>
+<td>Boolean?</td>
+<td>brdrb\brsp40\brdrdash</td>
+</tr>
+</tbody>
+</table>
+<h3 id="userdoc-attr-cf">Character Formatting</h3>
+<p>These attributes are set when creating a Paragraph, or Text.</p>
+<table>
+<thead>
+<tr>
+<th>Description</th>
+<th>Attribute Name</th>
+<th>Attribute Value</th>
+<th>RTF Control Word</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Bold</td>
+<td>RtfText.ATTR_BOLD</td>
+<td>N/A (boolean)</td>
+<td>\b</td>
+</tr>
+<tr>
+<td>Italic</td>
+<td>RtfText.ATTR_ITALIC</td>
+<td>N/A (boolean)</td>
+<td>\i</td>
+</tr>
+<tr>
+<td>Underline</td>
+<td>RtfText.ATTR_UNDERLINE</td>
+<td>N/A (boolean), or (int) 0 to turn underlining off</td>
+<td>\ul</td>
+</tr>
+<tr>
+<td>Font Size</td>
+<td>RtfText.ATTR_FONT_SIZE</td>
+<td>(int) font size in half-points</td>
+<td>\fs</td>
+</tr>
+<tr>
+<td>Font Family</td>
+<td>RtfText.ATTR_FONT_FAMILY</td>
+<td>(int) entry in document font-table</td>
+<td>\f</td>
+</tr>
+<tr>
+<td>Font Color</td>
+<td>RtfText.ATTR_FONT_COLOR</td>
+<td>(int) entry in document color-table</td>
+<td>\cf</td>
+</tr>
+<tr>
+<td>Background Color</td>
+<td>RtfText.ATTR_BACKGROUND_COLOR</td>
+<td>(int) entry in document color-table</td>
+<td>\chcbpat</td>
+</tr>
+</tbody>
+</table></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/dev/svg.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html (added)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html Sun Apr 15 05:39:50 2012
@@ -0,0 +1,156 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html lang="en">
+  <head>
+    <title>Apache™ FOP Development: SVG 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 Development: SVG Issues</h1>
+      </div>
+        <p><a href="/">Home</a>&nbsp;&raquo&nbsp;<a href="/fop/">Fop</a>&nbsp;&raquo&nbsp;<a href="/fop/dev/">Dev</a></p>
+      </div>
+      <div id="content" class="grid_16"><div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+<p>See also <a href="../trunk/graphics.html#svg">SVG User Documentation</a> for more information.</p>
+<h1 id="Examples">Examples</h1>
+<p>These examples illustrate a number of issues relating to conversion to PDF:</p>
+<table>
+<thead>
+<tr>
+<th><caption>SVG to PDF examples</caption></th>
+<th></th>
+<th>svg file</th>
+<th>png file</th>
+<th>pdf result</th>
+<th></th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td></td>
+<td>images</td>
+<td><a href="svg/images.svg">images.svg</a></td>
+<td><a href="svg/images.png">images.png</a></td>
+<td><a href="svg/images.pdf">images.pdf</a></td>
+<td></td>
+</tr>
+<tr>
+<td></td>
+<td>svg linking</td>
+<td><a href="svg/link.svg">link.svg</a></td>
+<td><a href="svg/link.png">link.png</a></td>
+<td><a href="svg/link.pdf">link.pdf</a></td>
+<td></td>
+</tr>
+<tr>
+<td></td>
+<td>gradients and patterns</td>
+<td><a href="svg/paints.svg">paints.svg</a></td>
+<td><a href="svg/paints.png">paints.png</a></td>
+<td><a href="svg/paints.pdf">paints.pdf</a></td>
+<td></td>
+</tr>
+<tr>
+<td></td>
+<td>various text and effects on text</td>
+<td><a href="svg/text.svg">text.svg</a></td>
+<td><a href="svg/text.png">text.png</a></td>
+<td><a href="svg/text.pdf">text.pdf</a></td>
+<td></td>
+</tr>
+<tr>
+<td></td>
+<td>transparent objects</td>
+<td><a href="svg/transparency.svg">transparency.svg</a></td>
+<td><a href="svg/transparency.png">transparency.png</a></td>
+<td><a href="svg/transparency.pdf">transparency.pdf</a></td>
+<td></td>
+</tr>
+</tbody>
+</table>
+<p>As can be seen most of the specific issues are handled.
+You will need Acrobat 5.0 to see transparency.
+<caption>XSL:FO to PDF examples</caption>|  | fo file | pdf result |
+|--|---------|------------|
+| embedding svg |  <a href="fo/embedding.fo">embedding.fo</a>  |  <a href="fo/embedding.fo.pdf">embedding.fo.pdf</a>  |</p>
+<h1 id="developer-notes-developernotes">Developer Notes # {#Developer+Notes}</h1>
+<p>For most output formats in FOP the SVG is simply drawn into an image with Batik. For PDF there are a set of classes to handle drawing the <a href="http://xml.apache.org/batik/architecture.html">GVT (Graphic Vector Toolkit)</a> into PDF markup.</p>
+<h2 id="Classes">Classes</h2>
+<p>These are the relevant classes, found in the package org.apache.fop.svg :</p>
+<ul>
+<li>
+<p><em>PDFGraphics2D</em> <br></br>used for drawing onto a Graphics2D into an existing pdf document, used internally to draw the svg.</p>
+</li>
+<li>
+<p><em>PDFDocumentGraphics2D</em> <br></br>used to create a pdf document and inherits from PDFGraphics2D to do the rest of the drawing. Used by the transcoder to create a standalone pdf document from an svg. Can be used independantly the same as any Graphics2D.</p>
+</li>
+<li>
+<p><em>PDFTranscoder</em> <br></br>used by Batik to transcode an svg document into a standalone pdf, via PDFDocumentGraphics2D.</p>
+</li>
+</ul>
+<h2 id="Ideas">Ideas</h2>
+<p>Batik can convert ttf to svg font. This svg font could be converted into a pdf stroked font (type 3 font).</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/dev/svg/images.pdf
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/images.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

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

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

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/images.svg
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/images.svg
------------------------------------------------------------------------------
    svn:mime-type = application/xml

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/link.pdf
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/link.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/link.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/link.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/link.svg
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/link.svg
------------------------------------------------------------------------------
    svn:mime-type = application/xml

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/paints.pdf
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/paints.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/paints.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/paints.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/paints.svg
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/paints.svg
------------------------------------------------------------------------------
    svn:mime-type = application/xml

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/text.pdf
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/text.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/text.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/text.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/text.svg
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/text.svg
------------------------------------------------------------------------------
    svn:mime-type = application/xml

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/transparency.pdf
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/transparency.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/transparency.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/transparency.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/transparency.svg
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/xmlgraphics/trunk/content/fop/dev/svg/transparency.svg
------------------------------------------------------------------------------
    svn:mime-type = application/xml



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


Mime
View raw message