You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xmlgraphics.apache.org by bu...@apache.org on 2012/10/24 06:04:05 UTC
svn commit: r835960 [13/18] - in
/websites/staging/xmlgraphics/trunk/content: ./ batik/ batik/dev/
batik/tools/ batik/using/ batik/using/scripting/ commons/ fop/ fop/0.95/
fop/1.0/ fop/1.1/ fop/dev/ fop/dev/design/ fop/trunk/
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/implement.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/implement.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/implement.html Wed Oct 24 04:04:00 2012
@@ -330,11 +330,12 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a></div> -->
- <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>
+ <div class="section-content"><h1 id="apachetm-fop-development-implementation-overview">Apache(tm) FOP Development: Implementation Overview</h1>
+<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-wzxhzdk9wzxhzdk10">Overview <a id="Overview"></a></h1>
+<h2 id="overview-wzxhzdk9wzxhzdk10">Overview <a id="Overview"></a></h2>
<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-wzxhzdk11wzxhzdk12">Startup <a id="Startup"></a></h1>
+<h2 id="startup-wzxhzdk11wzxhzdk12">Startup <a id="Startup"></a></h2>
<ul>
<li>
<p>The job starts in <em>apps.Fop.main()</em> .</p>
@@ -346,7 +347,7 @@ $(document).ready(function () {
<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-wzxhzdk13wzxhzdk14">Formatting Object Tree <a id="Formatting+Object+Tree"></a></h1>
+<h2 id="formatting-object-tree-wzxhzdk13wzxhzdk14">Formatting Object Tree <a id="Formatting+Object+Tree"></a></h2>
<table>
<thead>
<tr>
@@ -377,12 +378,12 @@ $(document).ready(function () {
</tr>
</tbody>
</table>
-<h1 id="layout-wzxhzdk15wzxhzdk16">Layout <a id="Layout"></a></h1>
+<h2 id="layout-wzxhzdk15wzxhzdk16">Layout <a id="Layout"></a></h2>
<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-wzxhzdk17wzxhzdk18">Area Tree <a id="Area+Tree"></a></h1>
+<h2 id="area-tree-wzxhzdk17wzxhzdk18">Area Tree <a id="Area+Tree"></a></h2>
<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-wzxhzdk19wzxhzdk20">Rendering <a id="Rendering"></a></h1>
+<h2 id="rendering-wzxhzdk19wzxhzdk20">Rendering <a id="Rendering"></a></h2>
<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>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/index.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/index.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/index.html Wed Oct 24 04:04:00 2012
@@ -330,17 +330,18 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="introduction-wzxhzdk2wzxhzdk3">Introduction <a id="intro"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-development-general-information">Apache(tm) FOP Development: General Information</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="introduction-wzxhzdk2wzxhzdk3">Introduction <a id="intro"></a></h2>
<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="development-wzxhzdk6wzxhzdk7">Development <a id="lines"></a></h1>
+<h2 id="development-wzxhzdk6wzxhzdk7">Development <a id="lines"></a></h2>
<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="getting-involved-wzxhzdk10wzxhzdk11">Getting Involved <a id="involved"></a></h1>
-<h2 id="understand-apache-roles-wzxhzdk12wzxhzdk13">Understand Apache Roles # <a id="apache-roles"></a></h2>
+<h3 id="understand-apache-roles-wzxhzdk12wzxhzdk13">Understand Apache Roles # <a id="apache-roles"></a></h3>
<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="how-you-can-help-wzxhzdk14wzxhzdk15">How you can help # <a id="fop-tasks"></a></h2>
+<h3 id="how-you-can-help-wzxhzdk14wzxhzdk15">How you can help # <a id="fop-tasks"></a></h3>
<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>
@@ -377,10 +378,10 @@ The SVN repository URL for the trunk is:
<p>Implementing new features.</p>
</li>
</ul>
-<h2 id="understand-fop-related-standards-wzxhzdk16wzxhzdk17">Understand FOP-related standards # <a id="fop-standards"></a></h2>
+<h3 id="understand-fop-related-standards-wzxhzdk16wzxhzdk17">Understand FOP-related standards # <a id="fop-standards"></a></h3>
<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="review-the-developer-documentation-wzxhzdk18wzxhzdk19">Review the Developer Documentation # <a id="doc"></a></h2>
-<h2 id="understand-fops-design-wzxhzdk20wzxhzdk21">Understand FOP's Design # <a id="design"></a></h2>
+<h3 id="review-the-developer-documentation-wzxhzdk18wzxhzdk19">Review the Developer Documentation # <a id="doc"></a></h3>
+<h3 id="understand-fops-design-wzxhzdk20wzxhzdk21">Understand FOP's Design # <a id="design"></a></h3>
<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>
@@ -432,7 +433,7 @@ Our design documentation may not always
<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="subscribe-to-the-fop-commits-mailing-list-wzxhzdk24wzxhzdk25">Subscribe to the fop-commits Mailing List # <a id="mail-fop-cvs"></a></h2>
+<h3 id="subscribe-to-the-fop-commits-mailing-list-wzxhzdk24wzxhzdk25">Subscribe to the fop-commits Mailing List # <a id="mail-fop-cvs"></a></h3>
<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>
@@ -462,9 +463,9 @@ Our design documentation may not always
<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="download-and-use-the-developers-code-using-subversion-wzxhzdk26wzxhzdk27">Download and Use the Developers' Code Using Subversion # <a id="dev-code"></a></h2>
+<h3 id="download-and-use-the-developers-code-using-subversion-wzxhzdk26wzxhzdk27">Download and Use the Developers' Code Using Subversion # <a id="dev-code"></a></h3>
<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="submitting-patches-wzxhzdk28wzxhzdk29">Submitting Patches # <a id="patches"></a></h2>
+<h3 id="submitting-patches-wzxhzdk28wzxhzdk29">Submitting Patches # <a id="patches"></a></h3>
<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>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/release.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/release.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/release.html Wed Oct 24 04:04:00 2012
@@ -330,11 +330,12 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a></div> -->
- <div class="section-content"><p><version>$Revision: 1310603 $</version></p>
-<h1 id="introduction-wzxhzdk2wzxhzdk3">Introduction <a id="intro"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-development-release-mechanics">Apache(tm) FOP Development: Release Mechanics</h1>
+<p><version>$Revision: 1310603 $</version></p>
+<h2 id="introduction-wzxhzdk2wzxhzdk3">Introduction <a id="intro"></a></h2>
<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-wzxhzdk5wzxhzdk6">Checklist <a id="checklist"></a></h1>
+<h2 id="checklist-wzxhzdk5wzxhzdk6">Checklist <a id="checklist"></a></h2>
<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>
@@ -454,7 +455,7 @@ $(document).ready(function () {
<p>Deploy the maven bundle.</p>
</li>
</ul>
-<h1 id="resources-wzxhzdk7wzxhzdk8">Resources <a id="other-checklists"></a></h1>
+<h2 id="resources-wzxhzdk7wzxhzdk8">Resources <a id="other-checklists"></a></h2>
<p>The following is a sample of some other project release checklists, which might be consulted for ideas:</p>
<ul>
<li>
@@ -476,7 +477,7 @@ $(document).ready(function () {
<p>Stefan Bodewig's<jump href="http://people.apache.org/~bodewig/mirror.html">Making your Downloads Mirrorable</jump></p>
</li>
</ul>
-<h1 id="announcing-the-release-wzxhzdk9wzxhzdk10">Announcing the release <a id="announcements"></a></h1>
+<h2 id="announcing-the-release-wzxhzdk9wzxhzdk10">Announcing the release <a id="announcements"></a></h2>
<p>Here's a suggested list of places where to announce new FOP releases:</p>
<ul>
<li>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/rtflib.html Wed Oct 24 04:04:00 2012
@@ -330,9 +330,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="general-information-wzxhzdk2wzxhzdk3">General Information <a id="general"></a></h1>
-<h2 id="introduction-wzxhzdk4wzxhzdk5">Introduction # <a id="intro"></a></h2>
+ <div class="section-content"><h1 id="apachetm-fop-development-rtflib-jfor">Apache(tm) FOP Development: RTFLib (jfor)</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="general-information-wzxhzdk2wzxhzdk3">General Information <a id="general"></a></h2>
+<h3 id="introduction-wzxhzdk4wzxhzdk5">Introduction # <a id="intro"></a></h3>
<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>
@@ -343,13 +344,13 @@ $(document).ready(function () {
</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-wzxhzdk6wzxhzdk7">History # <a id="history"></a></h2>
+<h3 id="history-wzxhzdk6wzxhzdk7">History # <a id="history"></a></h3>
<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-wzxhzdk8wzxhzdk9">Status # <a id="status"></a></h2>
+<h3 id="status-wzxhzdk8wzxhzdk9">Status # <a id="status"></a></h3>
<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="user-documentation-wzxhzdk12wzxhzdk13">User Documentation <a id="userdoc"></a></h1>
-<h2 id="overview-wzxhzdk14wzxhzdk15">Overview # <a id="userdoc-overview"></a></h2>
+<h3 id="overview-wzxhzdk14wzxhzdk15">Overview # <a id="userdoc-overview"></a></h3>
<p>Perhaps the easiest way to see how to use RTFLib is by looking at an example. A set of test documents is part of the package, and can be <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/">viewed online</a> . A quick look at the Abstract <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/TestDocument.java?rev=HEAD&content-type=text/vnd.viewcvs-markup">TestDocument</a> class, and one of the Concrete subclasses, <a href="http://cvs.apache.org/viewcvs.cgi/xml-fop/src/java/org/apache/fop/rtf/rtflib/testdocs/SimpleDocument.java?rev=HEAD&content-type=text/vnd.viewcvs-markup">SimpleDocument</a> will provide the basics of how to use the package.</p>
<p>There are two basic concepts you will need to understand in order to use RTFLib:</p>
<ul>
@@ -361,7 +362,7 @@ $(document).ready(function () {
</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="document-structure-wzxhzdk16wzxhzdk17">Document Structure # <a id="userdoc-structure"></a></h2>
+<h3 id="document-structure-wzxhzdk16wzxhzdk17">Document Structure # <a id="userdoc-structure"></a></h3>
<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>
@@ -443,16 +444,16 @@ The documentation in this section is int
</tr>
</tbody>
</table>
-<h2 id="attributes-wzxhzdk20wzxhzdk21">Attributes # <a id="userdoc-attributes"></a></h2>
+<h3 id="attributes-wzxhzdk20wzxhzdk21">Attributes # <a id="userdoc-attributes"></a></h3>
<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="information-group-wzxhzdk24wzxhzdk25">Information Group ## <a id="userdoc-attr-ig"></a></h3>
+<h4 id="information-group-wzxhzdk24wzxhzdk25">Information Group ## <a id="userdoc-attr-ig"></a></h4>
<p>These attributes are set when creating a Document.</p>
-<h3 id="document-formatting-wzxhzdk26wzxhzdk27">Document Formatting ## <a id="userdoc-attr-df"></a></h3>
+<h4 id="document-formatting-wzxhzdk26wzxhzdk27">Document Formatting ## <a id="userdoc-attr-df"></a></h4>
<p>These attributes are set when creating a Document.</p>
-<h3 id="section-formatting-wzxhzdk28wzxhzdk29">Section Formatting ## <a id="userdoc-attr-sf"></a></h3>
+<h4 id="section-formatting-wzxhzdk28wzxhzdk29">Section Formatting ## <a id="userdoc-attr-sf"></a></h4>
<p>These attributes are set when creating a Section.</p>
-<h3 id="paragraph-formatting-wzxhzdk30wzxhzdk31">Paragraph Formatting ## <a id="userdoc-attr-pf"></a></h3>
+<h4 id="paragraph-formatting-wzxhzdk30wzxhzdk31">Paragraph Formatting ## <a id="userdoc-attr-pf"></a></h4>
<p>These attributes are set when creating a Paragraph.</p>
<table>
<thead>
@@ -592,7 +593,7 @@ Attributes can be set for each container
</tr>
</tbody>
</table>
-<h3 id="character-formatting-wzxhzdk32wzxhzdk33">Character Formatting ## <a id="userdoc-attr-cf"></a></h3>
+<h4 id="character-formatting-wzxhzdk32wzxhzdk33">Character Formatting ## <a id="userdoc-attr-cf"></a></h4>
<p>These attributes are set when creating a Paragraph, or Text.</p>
<table>
<thead>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/svg.html Wed Oct 24 04:04:00 2012
@@ -330,9 +330,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+ <div class="section-content"><h1 id="apachetm-fop-development-svg-issues">Apache(tm) FOP Development: SVG Issues</h1>
+<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-wzxhzdk2wzxhzdk3">Examples <a id="Examples"></a></h1>
+<h2 id="examples-wzxhzdk2wzxhzdk3">Examples <a id="Examples"></a></h2>
<p>These examples illustrate a number of issues relating to conversion to PDF:</p>
<table>
<thead>
@@ -393,9 +394,9 @@ You will need Acrobat 5.0 to see transpa
<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-wzxhzdk6wzxhzdk7">Developer Notes <a id="Developer+Notes"></a></h1>
+<h2 id="developer-notes-wzxhzdk6wzxhzdk7">Developer Notes <a id="Developer+Notes"></a></h2>
<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-wzxhzdk8wzxhzdk9">Classes # <a id="Classes"></a></h2>
+<h3 id="classes-wzxhzdk8wzxhzdk9">Classes # <a id="Classes"></a></h3>
<p>These are the relevant classes, found in the package org.apache.fop.svg :</p>
<ul>
<li>
@@ -408,7 +409,7 @@ You will need Acrobat 5.0 to see transpa
<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-wzxhzdk10wzxhzdk11">Ideas # <a id="Ideas"></a></h2>
+<h3 id="ideas-wzxhzdk10wzxhzdk11">Ideas # <a id="Ideas"></a></h3>
<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>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/testing.html Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="build-testing-wzxhzdk2wzxhzdk3">"Build" Testing <a id="build"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-development-testing">Apache(tm) FOP Development: Testing</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="build-testing-wzxhzdk2wzxhzdk3">"Build" Testing <a id="build"></a></h2>
<p>Apache™ projects use an automated build tool called "gump" to create nightly builds from the SVN repository. Gump sends "nag" messages if the build fails. This can be considered a sort of basic test of the build process. To view the most recent logs of the gump builds:</p>
<ul>
<li>
@@ -341,32 +342,32 @@ $(document).ready(function () {
<p><a href="http://gump.cocoondev.org/xml-fop-maintenance.html">Gump build for the Maintenance Branch</a> </p>
</li>
</ul>
-<h1 id="basicapi-testing-wzxhzdk5wzxhzdk6">Basic/API Testing <a id="basic"></a></h1>
+<h2 id="basicapi-testing-wzxhzdk5wzxhzdk6">Basic/API Testing <a id="basic"></a></h2>
<p>There is a group of basic API tests that are included in the build process. For these tests to occur, JUnit must be available to Ant (simply copy junit.jar into Ant's lib directory). The build will then report error(s) if the high-level APIs for Driver and the Transcoders fail. The tests do not check the output, but only ensure that something is generated and without exceptions.</p>
-<h1 id="layout-engine-testing-wzxhzdk7wzxhzdk8">Layout Engine Testing <a id="layoutengine"></a></h1>
+<h2 id="layout-engine-testing-wzxhzdk7wzxhzdk8">Layout Engine Testing <a id="layoutengine"></a></h2>
<p>The <a href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/test/layoutengine/"></a> directory in the repository contains a test suite for checking the functionality of Apache� FOP's layout engine. For information on how to create test cases for the layout engine, please visit the <a href="http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests">Wiki page</a> .</p>
-<h1 id="functional-testing-wzxhzdk9wzxhzdk10">Functional Testing <a id="functional"></a></h1>
+<h2 id="functional-testing-wzxhzdk9wzxhzdk10">Functional Testing <a id="functional"></a></h2>
<p><warning>The "functional" testing section on this page is currently inoperative.</warning></p>
<h2 id="running-and-using-tests-wzxhzdk13wzxhzdk14">Running and Using Tests # <a id="Running+and+Using+Tests"></a></h2>
<p>Testing is an important part of getting FOP to operate correctly and conform to the necessary standards.</p>
<p>A testing system has been set up that works with as a build target when developing with FOP. A developer can run the tests after making changes to the code, the aim is to have the tests run to verfiy that nothing working has been broken.</p>
<p>To setup the testing the developer must place a reference fop.jar in the "<cvs_repository>/test/reference/" directory. This jar will be dynamically loaded to create the reference output.</p>
-<h2 id="w3c-testsuite-wzxhzdk16wzxhzdk17">W3C TestSuite # <a id="W3C+TestSuite"></a></h2>
+<h3 id="w3c-testsuite-wzxhzdk16wzxhzdk17">W3C TestSuite # <a id="W3C+TestSuite"></a></h3>
<p>The testing is set up so that you can download the testsuite from<jump href="http://www.w3.org/Style/XSL/TestSuite/">http://www.w3.org/Style/XSL/TestSuite/</jump>, unzip the file into the base directory of FOP. Then you can uncomment the lines in the build.xml file in the test target and itwill run through all the tests in the testsuite distribution.</p>
-<h2 id="writing-a-test-wzxhzdk20wzxhzdk21">Writing a Test # <a id="Writing+a+Test"></a></h2>
+<h3 id="writing-a-test-wzxhzdk20wzxhzdk21">Writing a Test # <a id="Writing+a+Test"></a></h3>
<p>A test belongs to one of a few catagories. A basic test should excercise one element in a number of situations such as changing a property. This should have at least one normal value, one border value and one invalid value. If the property can be of different types then this should also be included.</p>
<p>A bug test is a test that is specifically aimed at a problem with FOP. That is, the test is not excercising the specification but rather a problem with FOP in handling a particular situation that is not exposed with the other testing.</p>
<p>A system test is one that tests the abitlity of FOP to handle a number of different elements together.</p>
<p>A test can consist of a complete fo document or a part of the document such as some elements that will be placed into the flow of a standard document.</p>
-<h2 id="submitting-a-test-wzxhzdk22wzxhzdk23">Submitting a Test # <a id="Submitting+a+Test"></a></h2>
+<h3 id="submitting-a-test-wzxhzdk22wzxhzdk23">Submitting a Test # <a id="Submitting+a+Test"></a></h3>
<p>If you have a test which you think would be useful you should supply the test and a diff to the appropriate test suite xml file. Make sure that the test works as would be expected against the current build.</p>
-<h2 id="how-testing-works-wzxhzdk24wzxhzdk25">How Testing Works # <a id="How+Testing+Works"></a></h2>
+<h3 id="how-testing-works-wzxhzdk24wzxhzdk25">How Testing Works # <a id="How+Testing+Works"></a></h3>
<p>The tests are stored in the "<svn_repository>/test" directory.</p>
<p>You can run the tests by specifying the build target "test" ie:<br></br> <code>ant.sh test</code> (Unix)<br></br> <code>ant test</code> (Windows)<br></br></p>
<p>This will then compare the current code in the local src directory to a specified release of FOP. Any differences between the current code and the output from the reference version will be reported. If the test previously passed then the test run will have failed.</p>
<p>The testing is done by reading a test suite xml file, which corresponds to the standard testsuite.dtd supplied from w3c. This xml file contains a test xml file and an xsl file (which may simply copy the file). It also contains information such as if the test has passed and any comments.</p>
<p>For FOP the testing is done by rendering all the testing documents using the XML renderer. The XML files are then compared to see if there are any differences.</p>
-<h2 id="svg-testing-wzxhzdk33wzxhzdk34">SVG Testing # <a id="SVG+Testing"></a></h2>
+<h3 id="svg-testing-wzxhzdk33wzxhzdk34">SVG Testing # <a id="SVG+Testing"></a></h3>
<p>The testing of SVG is not part of this testing system. SVG is tested for its rendering accuracy by using the transcoding mechanism via <a href="http://xmlgraphics.apache.org/batik/">Apache Batik</a> . So that the only part that needs testing is how the SVG image is embedded inside the flow of the fo document.</p></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/dev/tools.html Wed Oct 24 04:04:00 2012
@@ -330,9 +330,10 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a> » <a href="/fop/dev/">Dev</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
+ <div class="section-content"><h1 id="apachetm-fop-development-developer-tools">Apache(tm) FOP Development: Developer Tools</h1>
+<p><version>$Revision: 1298724 $</version></p>
<p>This page documents items that may be helpful to other developers, especially to those who are new to Apache™ FOP. Exhaustive treatment of these topics is better suited to other fora, but the information presented here is intended to deal with FOP-specific issues related to these tools, especially "gotchas", and to help developers get jump-started.</p>
-<h1 id="developer-checklist-wzxhzdk3wzxhzdk4">Developer Checklist <a id="checklist"></a></h1>
+<h2 id="developer-checklist-wzxhzdk3wzxhzdk4">Developer Checklist <a id="checklist"></a></h2>
<p>Here is a (probably not comprehensive) list of tools you will need to be a successful FOP developer:</p>
<ul>
<li>
@@ -351,17 +352,17 @@ $(document).ready(function () {
<p>JUnit (see <a href="testing.html#basic">Basic Testing</a> ).</p>
</li>
</ul>
-<h1 id="general-developer-information-wzxhzdk5wzxhzdk6">General Developer Information <a id="general"></a></h1>
+<h2 id="general-developer-information-wzxhzdk5wzxhzdk6">General Developer Information <a id="general"></a></h2>
<p>See <a href="http://www.apache.org/dev/contributors.html">the Apache Contributors Tech Guide</a> for useful information and links for Apache developers, including help with tools and procedures.</p>
-<h1 id="subversion-svn-wzxhzdk7wzxhzdk8">Subversion (SVN) <a id="svn"></a></h1>
-<h2 id="general-wzxhzdk9wzxhzdk10">General # <a id="svn_general"></a></h2>
+<h2 id="subversion-svn-wzxhzdk7wzxhzdk8">Subversion (SVN) <a id="svn"></a></h2>
+<h3 id="general-wzxhzdk9wzxhzdk10">General # <a id="svn_general"></a></h3>
<p>Visit <a href="http://xmlgraphics.apache.org/repo.html">Apache XML Graphics Code Repositories</a> for useful information.</p>
<p>You will need a SVN client to be able to gain access to the FOP repository. For general SVN information, visit <a href="http://subversion.tigris.org">Subversion Home</a> . A comprehensive list of clients for all operating systems and many IDEs can be found at <a href="http://subversion.tigris.org/project_links.html">the Subversion Links page</a> . For Microsoft Windows we recommend <a href="http://tortoisesvn.tigris.org">TortoiseSVN</a> . The command-line client that comes with Subversion is also very easy to use.</p>
-<h2 id="step-by-step-instruction-for-downloading-fop-using-the-svn-command-line-client-wzxhzdk11wzxhzdk12">Step-by-step instruction for downloading FOP using the SVN command-line client # <a id="svn_download"></a></h2>
+<h3 id="step-by-step-instruction-for-downloading-fop-using-the-svn-command-line-client-wzxhzdk11wzxhzdk12">Step-by-step instruction for downloading FOP using the SVN command-line client # <a id="svn_download"></a></h3>
<p>On the command-line (Windows or Unix), simply run:</p>
<p>svn co http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/ fop-trunk</p>
<p>This will download the FOP trunk into the directory "fop-trunk".</p>
-<h2 id="step-by-step-instructions-for-downloading-fop-using-tortoisesvn-on-windows-wzxhzdk13wzxhzdk14">Step-by-step instructions for downloading FOP using TortoiseSVN (on Windows) # <a id="tortoisesvn_download"></a></h2>
+<h3 id="step-by-step-instructions-for-downloading-fop-using-tortoisesvn-on-windows-wzxhzdk13wzxhzdk14">Step-by-step instructions for downloading FOP using TortoiseSVN (on Windows) # <a id="tortoisesvn_download"></a></h3>
<ul>
<li>
<p>Create a new, empty directory in a place of your choice.</p>
@@ -376,7 +377,7 @@ $(document).ready(function () {
<p>Click "OK" and the download should begin.</p>
</li>
</ul>
-<h2 id="creating-patches-wzxhzdk15wzxhzdk16">Creating Patches # <a id="patches"></a></h2>
+<h3 id="creating-patches-wzxhzdk15wzxhzdk16">Creating Patches # <a id="patches"></a></h3>
<ul>
<li>
<p><code>cd</code> to a directory that contains all of the changes that you wish to include in the patch. To comprehend the entire distribution, <code>cd</code> to the top directory where you checked out the sources.</p>
@@ -391,7 +392,7 @@ $(document).ready(function () {
<p>If you are running TortoiseSVN, you can select "Create Patch..." in the TortoiseSVN context menu.</p>
</li>
</ul>
-<h2 id="documentation-wzxhzdk17wzxhzdk18">Documentation # <a id="svn-doc"></a></h2>
+<h3 id="documentation-wzxhzdk17wzxhzdk18">Documentation # <a id="svn-doc"></a></h3>
<ul>
<li>
<p>[online resource]<jump href="http://subversion.tigris.org">The Subversion Home Page</jump>.</p>
@@ -403,7 +404,7 @@ $(document).ready(function () {
<p>[online resource]<jump href="http://subversion.tigris.org/project_links.html">Comprehensive list of links to documentation and Subversion clients and plugins.</jump></p>
</li>
</ul>
-<h1 id="integrated-development-environments-ides-wzxhzdk19wzxhzdk20">Integrated Development Environments (IDEs) <a id="ide"></a></h1>
+<h2 id="integrated-development-environments-ides-wzxhzdk19wzxhzdk20">Integrated Development Environments (IDEs) <a id="ide"></a></h2>
<p>An IDE is not required, but will generally be found to be helpful, especially for serious debugging and refactoring.</p>
<p>Borland's JBuilder 7/8 does not support Ant builds unless you have the Enterprise Edition (which is quite expensive). This causes problems with any code that is generated by the Ant build. First, you must run the Ant build before you can use the IDE. Second, when you are editing in the IDE, you must be editing the generated files, which means that you must make any changes to the source files in another editor. This is less serious for development on the trunk, but in the maintenance branch, all source files were "generated".</p>
<p>Sun ONE Studio Four does support Ant, but seems to use a built-in version, and as of this writing chokes on the FOP build file, saying that it is not valid. There is awkward because there is no official DTD for Ant, and it may be merely an Ant version issue.</p>
Modified: websites/staging/xmlgraphics/trunk/content/fop/download.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/download.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/download.html Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="binary-or-source-wzxhzdk2wzxhzdk3">Binary or Source? <a id="dist-type"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-downloading-a-distribution">Apache(tm) FOP: Downloading A Distribution</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="binary-or-source-wzxhzdk2wzxhzdk3">Binary or Source? <a id="dist-type"></a></h2>
<p>Most Apache™ FOP users will want to download the latest binary distribution, which is ready to run "out of the box." However, a source distribution will be preferable if you fall into one of the following categories:</p>
<ul>
<li>
@@ -344,9 +345,9 @@ $(document).ready(function () {
<p>You wish to build a local copy of the API documentation (javadocs).</p>
</li>
</ul>
-<h1 id="binary-download-wzxhzdk5wzxhzdk6">Binary Download <a id="binary"></a></h1>
+<h2 id="binary-download-wzxhzdk5wzxhzdk6">Binary Download <a id="binary"></a></h2>
<p>Binary distributions include "-bin" in their names, and can be downloaded from a <a href="http://www.apache.org/dyn/closer.cgi/xmlgraphics/fop">FOP Distribution mirror</a> . Nightly builds of trunk code can be downloaded here: <a href="http://ci.apache.org/projects/xmlgraphics/fop/snapshots/">Nightly Snapshots</a> .</p>
-<h1 id="source-download-wzxhzdk7wzxhzdk8">Source Download <a id="source"></a></h1>
+<h2 id="source-download-wzxhzdk7wzxhzdk8">Source Download <a id="source"></a></h2>
<p>There are several ways to obtain a source distribution. Please note that they are listed from least current to most current:</p>
<ul>
<li>
@@ -399,7 +400,7 @@ $(document).ready(function () {
</tbody>
</table>
<p>With any source distribution, you will need to build FOP from the source files. For details please see the "Build" page on the documentation tab for the version you've downloaded.</p>
-<h1 id="archive-download-wzxhzdk9wzxhzdk10">Archive Download <a id="archives"></a></h1>
+<h2 id="archive-download-wzxhzdk9wzxhzdk10">Archive Download <a id="archives"></a></h2>
<p>FOP Archive distributions are linked from the upper portion of the Apache FOP Download Mirror Page and can be downloaded from the FOP Archives <a href="http://archive.apache.org/dist/xmlgraphics/fop/binaries/">binaries</a> & <a href="http://archive.apache.org/dist/xmlgraphics/fop/source/">source</a> links.</p></div>
</div>
Modified: websites/staging/xmlgraphics/trunk/content/fop/examples.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/examples.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/examples.html Wed Oct 24 04:04:00 2012
@@ -330,8 +330,9 @@ $(document).ready(function () {
<div id="content" class="grid_16">
<!-- <div id="breadcrumb"><a href="/">Home</a> » <a href="/fop/">Fop</a></div> -->
- <div class="section-content"><p><version>$Revision: 1298724 $</version></p>
-<h1 id="example-documents-using-apachewzxhzdk4-fop-wzxhzdk2wzxhzdk3">Example Documents Using Apache™ FOP <a id="Example+Documents+Using+Apache%E2%84%A2+FOP"></a></h1>
+ <div class="section-content"><h1 id="apachetm-fop-examples">Apache(tm) FOP Examples</h1>
+<p><version>$Revision: 1298724 $</version></p>
+<h2 id="example-documents-using-apachewzxhzdk4-fop-wzxhzdk2wzxhzdk3">Example Documents Using Apache™ FOP <a id="Example+Documents+Using+Apache%E2%84%A2+FOP"></a></h2>
<p>These examples have been rendered using Apache™ FOP:</p>
<table>
<thead>
@@ -398,7 +399,7 @@ $(document).ready(function () {
</ul>
<p>Also, in the directory examples/fo/pagination you will find a suite of examples showing the use of XSL-FO pagination.</p>
<p>Developers will find the first steps to a test suite for all implemented formatting objects and properties in test/xml in the source distribution.</p>
-<h1 id="images-examples-wzxhzdk6wzxhzdk7">Images Examples <a id="Images+Examples"></a></h1>
+<h2 id="images-examples-wzxhzdk6wzxhzdk7">Images Examples <a id="Images+Examples"></a></h2>
<p>Embedding images in FO:</p>
<table>
<thead>
@@ -435,7 +436,7 @@ $(document).ready(function () {
</tbody>
</table>
<p>Look also into the directory examples/fo/svg. There you find some very extensive SVG examples.</p>
-<h1 id="instream-foreign-object-examples-wzxhzdk8wzxhzdk9">Instream Foreign Object Examples <a id="Instream+Foreign+Object+Examples"></a></h1>
+<h2 id="instream-foreign-object-examples-wzxhzdk8wzxhzdk9">Instream Foreign Object Examples <a id="Instream+Foreign+Object+Examples"></a></h2>
<p>Instream Foreign Object images in FO, there are more on the <a href="dev/svg.html">SVG Page</a> :</p>
<table>
<thead>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org