Return-Path: X-Original-To: apmail-xmlgraphics-commits-archive@www.apache.org Delivered-To: apmail-xmlgraphics-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7129FD528 for ; Mon, 15 Oct 2012 03:58:12 +0000 (UTC) Received: (qmail 83288 invoked by uid 500); 15 Oct 2012 03:58:12 -0000 Mailing-List: contact commits-help@xmlgraphics.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@xmlgraphics.apache.org Delivered-To: mailing list commits@xmlgraphics.apache.org Received: (qmail 83273 invoked by uid 99); 15 Oct 2012 03:58:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 03:58:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 03:58:01 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 4CA31238899C for ; Mon, 15 Oct 2012 03:57:08 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r835093 [2/3] - in /websites/staging/xmlgraphics/trunk/content: ./ commons/ fop/ fop/0.95/ fop/1.0/ fop/dev/ fop/dev/design/ fop/trunk/ Date: Mon, 15 Oct 2012 03:56:40 -0000 To: commits@xmlgraphics.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121015035708.4CA31238899C@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/knownissues_overview.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/knownissues_overview.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/knownissues_overview.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: Known Issues + Apache™ FOP: Known Issues @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project

+ @@ -332,7 +332,7 @@ $(document).ready(function () {

$Revision: 1298724 $

Known issues # {#Known+issues}

This page lists currently known issues in the current release.

For additional information on known issues in Apacheâ¢ FOP, please have a look at the following pages, too:

For additional information on known issues in Apache™ FOP, please have a look at the following pages, too:

the bug list in Bugzilla
@@ -341,7 +341,7 @@ $(document).ready(function () {
the task list in the Wiki

Apacheâ¢ FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.

Apache™ FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.

FO Tree ## {#FO+Tree}

This section lists disabled test cases in the test suite for the FO tree tests, at the time of the release.

demo-test-failure.fo (demo test failure):

TODO: Add missing description in disabled-testcases.xml!

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/metadata.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/metadata.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/metadata.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: Metadata + Apache™ FOP: Metadata @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/output.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/output.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/output.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Output Formats + Apache™ FOP Output Formats @@ -323,14 +323,14 @@ $(document).ready(function () {

The Apache™ FOP Project

$Revision: 1298724 $

Apacheâ¢ FOP supports multiple output formats by using a different renderer for each format. The renderers do not all have the same set of capabilities, sometimes because of the output format itself, sometimes because some renderers get more development attention than others.

Apache™ FOP supports multiple output formats by using a different renderer for each format. The renderers do not all have the same set of capabilities, sometimes because of the output format itself, sometimes because some renderers get more development attention than others.

General Information

Fonts

Most FOP renderers use a FOP-specific system for font registration. However, the Java2D/AWT and print renderers use the Java AWT package, which gets its font information from the operating system registration. This can result in several differences, including actually using different fonts, and having different font metrics for the same font. The net effect is that the layout of a given FO document can be quite different between renderers that do not use the same font information.

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfa.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfa.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfa.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: PDF/A (ISO 19005) + Apache™ FOP: PDF/A (ISO 19005) @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfencryption.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: PDF encryption. + Apache™ FOP: PDF encryption. @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project

@@ -331,7 +331,7 @@ $(document).ready(function () {

$Revision: 1298724 $

Overview

Apacheâ¢ FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited.

Apache™ FOP supports encryption of PDF output, thanks to Patrick C. Lankswert. This feature is commonly used to prevent unauthorized viewing, printing, editing, copying text from the document and doing annotations. It is also possible to ask the user for a password in order to view the contents. Note that there already exist third party applications which can decrypt an encrypted PDF without effort and allow the aforementioned operations, therefore the degree of protection is limited.

For further information about features and restrictions regarding PDF encryption, look at the documentation coming with Adobe Acrobat or the technical documentation on the Adobe web site.

Usage (command line) # {#Usage+%28command+line%29}

Encryption is enabled by supplying any of the encryption related options.

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfx.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfx.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/pdfx.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: PDF/X (ISO 15930) + Apache™ FOP: PDF/X (ISO 15930) @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project

@@ -331,7 +331,7 @@ $(document).ready(function () {

$Revision: 1298724 $

Overview

Support for PDF/X is available beginning with Apacheâ¢ FOP version 0.93. This feature is new and may not be 100% complete, yet. Feedback is welcome. +

Support for PDF/X is available beginning with Apache™ FOP version 0.93. This feature is new and may not be 100% complete, yet. Feedback is welcome. PDF/X is a standard which faciliates prepress digital data exchange using PDF. Currently, only PDF/X-3:2003 is implemented out of the many different flavours of PDF/X profiles. PDF/X-3:2003 is documented in ISO 15930-6:2003(E) . More info on PDF/X can be found on the PDF/X info site .

Implementation Status

PDF/X-3:2003 is implemented to the degree that FOP supports the creation of the elements described in ISO 15930-6.

Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/running.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Running Apacheâ¢ FOP + Running Apache™ FOP @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project

@@ -340,7 +340,7 @@ $(document).ready(function () {

Apacheâ¢ FOP. The FOP distribution includes all libraries that you will need to run a basic FOP installation. These can be found in the [fop-root]/lib directory. These libraries include the following:

Apache™ FOP. The FOP distribution includes all libraries that you will need to run a basic FOP installation. These can be found in the [fop-root]/lib directory. These libraries include the following:

Apache XML Graphics Commons , an shared library for Batik and FOP.
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/servlets.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/servlets.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/servlets.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: Servlets + Apache™ FOP: Servlets @@ -323,15 +323,15 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
-
How to use Apacheâ¢ FOP in a Servlet$Revision: 1298724 $
+
How to use Apache™ FOP in a Servlet$Revision: 1298724 $

Overview
-
This page discusses topic all around using Apacheâ¢ FOP in a servlet environment.
+
This page discusses topic all around using Apache™ FOP in a servlet environment.

Example Servlets in the FOP distribution

In the directory {fop-dir}/src/java/org/apache/fop/servlet, you'll find a working example of a FOP-enabled servlet.

The servlet is automatically built when you build Apache FOP using the supplied Ant script. After building the servlet, drop fop.war into the webapps directory of Apache Tomcat (or any other web container). Then, you can use URLs like the following to generate PDF files:
Modified: websites/staging/xmlgraphics/trunk/content/fop/1.0/upgrading.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/1.0/upgrading.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/1.0/upgrading.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Upgrading from an Earlier Version of Apacheâ¢ FOP + Upgrading from an Earlier Version of Apache™ FOP @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Important!
-
If you're planning to upgrade to the latest Apacheâ¢ FOP version there are a few very important things to consider:
+
If you're planning to upgrade to the latest Apache™ FOP version there are a few very important things to consider:
- More than half of the codebase has been rewritten over the last three years. With version 0.93 the code has reached production level , and continues to improve with version 0.94.
  Modified: websites/staging/xmlgraphics/trunk/content/fop/bugs.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/bugs.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/bugs.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: Bugs and Other Trackable Issues + Apache™ FOP: Bugs and Other Trackable Issues @@ -323,7 +323,7 @@ $(document).ready(function () {
  
  The Apache™ FOP Project
  -
  +
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/conventions.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Development: Coding Conventions + Apache™ FOP Development: Coding Conventions @@ -323,14 +323,14 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
$Revision: 1298724 $
-
Acknowledgement: Some content in this guide was adapted from other Apacheâ¢ projects such as Avalon, Cactus, Turbine and Velocity.
+
Acknowledgement: Some content in this guide was adapted from other Apache™ projects such as Avalon, Cactus, Turbine and Velocity.

Subversion Repository

Conventions in this section apply to Repository content, regardless of type:
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/breakpos.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/breakpos.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/breakpos.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Layout Managers + Apache™ FOP Design: Layout Managers @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/embedding.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Embedding Apacheï¿½ FOP in Other Applications + Apache™ FOP Design: Embedding Apacheï¿½ FOP in Other Applications @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
This is the design for the external interface when Apacheâ¢ FOP is to be embedded inside another java application.
+
This is the design for the external interface when Apache™ FOP is to be embedded inside another java application.

Common places where FOP is embedded is in a report production application of a server side application such asCocoon.

Settings

User Agent ## {#User+Agent}
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/extending.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/extending.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/extending.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Extensions + Apache™ FOP Design: Extensions @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
Apacheâ¢ FOP provides an extension mechanism to add extra functionality. There are a number of different types of extensions that apply to different steps when converting FO into the rendered output.
+
Apache™ FOP provides an extension mechanism to add extra functionality. There are a number of different types of extensions that apply to different steps when converting FO into the rendered output.

Extensions

SVG Graphic - This applies to svg and any other xml document that can be converted into svg in the output. All that is required is the element mapping for the xml and a converter that changes the document into svg. This conversion is done in the FO Tree. The conversion is done by the top level element of the namespace or in the case of an external image a Converter.

XML Document - Instead of converting the document into svg it can be passed directly to the renderer. The renderer will need to have a handler for the xml document. This handler can add information directly to the output document.
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/fotree.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/fotree.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/fotree.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: FO Tree + Apache™ FOP Design: FO Tree @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/images.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Images + Apache™ FOP Design: Images @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+ Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/index.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/index.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/index.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Introduction + Apache™ FOP Design: Introduction @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+ @@ -332,7 +332,7 @@ $(document).ready(function () {
$Revision: 1298724 $ The articles in this section pertain mainly to the redesign or trunk line of development. The redesign is mainly focusing on parts of the layout process (converting the FO tree into the Area Tree). Therefore other (non-layout) sections in this document are probably largely accurate for the maintenance branch, but should be used with care in that context.

The Black Box View
-
From a user's standpoint, Apacheâ¢ FOP is a black box that an xml file as input, performs some magic, then creates the desired output:
+
From a user's standpoint, Apache™ FOP is a black box that an xml file as input, performs some magic, then creates the desired output:
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/layout.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/layout.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/layout.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Layout + Apache™ FOP Design: Layout @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+ Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/optimise.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/optimise.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/optimise.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Optimisations + Apache™ FOP Design: Optimisations @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+ @@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
Apacheâ¢ FOP should be able to handle very large documents. A document can be supplied using SAX and the information should be passed entirely through the system, from fo elements to rendered output as soon as possible.
+
Apache™ FOP should be able to handle very large documents. A document can be supplied using SAX and the information should be passed entirely through the system, from fo elements to rendered output as soon as possible.

A top level block area, immediately below the flow, can be added to the page layout as soon as the element is complete.

The fo elements used to construct a page can be discarded as soon as the layout for the page is complete. Some information may be stored in the area tree of the page in order to handle unresolved page references and links.

Once the layout of a page has been completed, all elements are fully resolved, then the page can be rendered. Some renderers may support out of order rendering of pages.
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/parsing.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/parsing.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/parsing.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Input Parsing + Apache™ FOP Design: Input Parsing @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
Parsing is the process of reading the XSL-FO input and making the information in it available to Apacheâ¢ FOP.
+
Parsing is the process of reading the XSL-FO input and making the information in it available to Apache™ FOP.

SAX for Input

The two standard ways of dealing with XML input are SAX and DOM. SAX basically creates events as it parses an XML document in a serial fashion; a program using SAX (and not storing anything internally) will only see a small window of the document at any point in time, and can never look forward in the document. DOM creates and stores a tree representation of the document, allowing a view of the entire document as an integrated whole. One issue that may seem counter-intuitive to some new FOP developers, and which has from time to time been contentious, is that FOP uses SAX for input. (DOM can be used as input as well, but it is converted into SAX events before entering FOP, effectively negating its advantages).

Since FOP essentially needs a tree representation of the FO input, at first glance it seems to make sense to use DOM. Instead, FOP takes SAX events and builds its own tree-like structure. Why?
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/pdf-library.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/pdf-library.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/pdf-library.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: PDF Library + Apache™ FOP Design: PDF Library @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
The PDF Library is an independant package of classes in Apacheâ¢ FOP. These class provide a simple way to construct documents and add the contents. The classes are found in org.apache.fop.pdf.* .
+
The PDF Library is an independant package of classes in Apache™ FOP. These class provide a simple way to construct documents and add the contents. The classes are found in org.apache.fop.pdf.* .

PDF Document # {#PDF+Document}

This is where most of the document is created and put together.

It sets up the header, trailer and resources. Each page is made and added to the document. There are a number of methods that can be used to create/add certain PDF objects to the document.
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/renderers.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/renderers.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/renderers.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Renderers + Apache™ FOP Design: Renderers @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/startup.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/startup.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/startup.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: Startup, Environment, Control + Apache™ FOP Design: Startup, Environment, Control @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+ @@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
Startup is the process of getting Apacheâ¢ FOP bootstrapped and creating basic objects. Environment includes acquiring user options, instantiating any frameworks, setting up logging, etc. Control includes the basic logic for tieing the various subsystems together properly.
+
Startup is the process of getting Apache™ FOP bootstrapped and creating basic objects. Environment includes acquiring user options, instantiating any frameworks, setting up logging, etc. Control includes the basic logic for tieing the various subsystems together properly.

Status

To Do
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
SVG is rendered through Apacheâ¢ Batik.
+
SVG is rendered through Apache™ Batik.

The XML from the XSL:FO document is converted into an SVG DOM with batik. This DOM is then set as the Document on the Foreign Object area in the Area Tree.

This DOM is then available to be rendered by the renderer.

SVG is rendered in the renderers via an XMLHandler in the FOUserAgent. This XML handler is used to render the SVG. The SVG is rendered by using batik. Batik converts the SVG DOM into an internal structure that can be drawn into a Graphics2D. So for PDF we use a PDFGraphics2D to draw into.
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/design/useragent.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/design/useragent.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/design/useragent.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Design: User Agent + Apache™ FOP Design: User Agent @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
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.
+
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.

The user agent is used by the formatting process to determine certain user definable values.

It will enable the customisation of values for generating and rendering the document.

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.
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/doc.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Development: Managing Documentation + Apache™ FOP Development: Managing Documentation @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

General Information
-
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 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.

Design Principles
Modified: websites/staging/xmlgraphics/trunk/content/fop/dev/extensions.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/dev/extensions.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/dev/extensions.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Development: Adding an Extension + Apache™ FOP Development: Adding an Extension @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Overview
-
For documentation of standard Apacheâ¢ FOP extensions, see the User FOP Extensions document.
+
For documentation of standard Apache™ FOP extensions, see the User FOP Extensions document.

If the default funtionality of FOP needs to be extended for some reason then you can write an extension.

There are three types of extensions possible:
Following a Document Through Apacheï¿½ FOP$Revision: 1298724 $
-
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.
+
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.

Overview

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.

Startup
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 Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Development: General Information + Apache™ FOP Development: General Information @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,8 +331,8 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
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.
-
For basic and user information on FOP, please visit the Apacheâ¢ FOP homepage .
+
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.
+
For basic and user information on FOP, please visit the Apache™ FOP homepage .

Development

The main development happens on "FOP Trunk". The SVN repository URL for the trunk is:

http://svn.apache.org/repos/asf/xmlgraphics/fop/trunk/
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 Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Development: Release Mechanics + Apache™ FOP Development: Release Mechanics @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1310603 $

Introduction
-
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.
+
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.

The checklist below is based on a combination of input from from Christian Geisert and Simon Pepping.

Checklist
@@ -335,7 +335,7 @@ $(document).ready(function () {
The RTFLib package is an open-source, independent package suitable for writing RTF files in a java environment. By independent we mean:
- -
  Although it is used by Apacheâ¢ FOP to generate FOP's RTF output, it is not dependent on FOP for any of its functionality.
  +
  Although it is used by Apache™ FOP to generate FOP's RTF output, it is not dependent on FOP for any of its functionality.
- 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.
  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 Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Development: SVG Issues + Apache™ FOP Development: SVG Issues @@ -323,7 +323,7 @@ $(document).ready(function () {
  
  The Apache™ FOP Project
  -
  +
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 Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Development: Testing + Apache™ FOP Development: Testing @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+ @@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

"Build" Testing
-
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:
+
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:
- Gump build for the Trunk
  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 Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Development: Developer Tools + Apache™ FOP Development: Developer Tools @@ -323,14 +323,14 @@ $(document).ready(function () {
  
  The Apache™ FOP Project
  -
  +
$Revision: 1298724 $
-
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.
+
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.

Developer Checklist

Here is a (probably not comprehensive) list of tools you will need to be a successful FOP developer:
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Binary or Source?
-
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:
+
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:
- You wish to modify FOP.
  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 Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP Examples + Apache™ FOP Examples @@ -323,15 +323,15 @@ $(document).ready(function () {
  
  The Apache™ FOP Project
  -
  +
$Revision: 1298724 $
-
Example Documents Using Apacheâ¢ FOP # {#Example+Documents+Using+Apache%E2%84%A2+FOP}
-
These examples have been rendered using Apacheâ¢ FOP:
+
Example Documents Using Apache™ FOP # {#Example+Documents+Using+Apache%E2%84%A2+FOP}
+
These examples have been rendered using Apache™ FOP:
Modified: websites/staging/xmlgraphics/trunk/content/fop/faq.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/faq.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/faq.html Mon Oct 15 03:56:36 2012 @@ -330,8 +330,8 @@ $(document).ready(function () {
Questions
-
1. Apacheâ¢ FOP: General questions
-
1.1. What is Apacheâ¢ FOP?
+
1. Apache™ FOP: General questions
+
1.1. What is Apache™ FOP?

FOP is a print formatter for XSL formatting objects .

It can be used to render an XML file containing XSL formatting objects into a page layout. The main target is PDF but other rendering targets are supported, such as AWT, PCL, text and direct printing.

1.2. What can I do with FOP?
Modified: websites/staging/xmlgraphics/trunk/content/fop/fo.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/fo.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/fo.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: XSL-FO Input + Apache™ FOP: XSL-FO Input @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
Basic Help for Using XML, XSLT, and XSL-FO$Revision: 1298724 $

Overview
-
Apacheâ¢ FOP uses XSL-FO as input. It is the responsibility of the user to make sure that the XSL-FO submitted to FOP is correct. The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another good FAQ isDave Pawson's XSL FAQ.
+
Apache™ FOP uses XSL-FO as input. It is the responsibility of the user to make sure that the XSL-FO submitted to FOP is correct. The tutorial items presented here are not comprehensive, but are of the FAQ variety. Another good FAQ isDave Pawson's XSL FAQ.

XML Issues

Special Characters

When entering special (non-ASCII) characters in XML, the general rule is to use the applicable Unicode character instead of trying to use a character entity as you would with HTML. Remember that HTML is an SGML document type. SGML has a limited character set, which requires it to use character entities to represent special characters. One of the improvements of XML over SGML (and thus HTML) is native support for Unicode. Basic XML has only a handful of character entities, primarily because it doesn't really need more.
Modified: websites/staging/xmlgraphics/trunk/content/fop/gethelp.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/gethelp.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/gethelp.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: Getting Help + Apache™ FOP: Getting Help @@ -323,14 +323,14 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
Checklist for Finding Appropriate Resources$Revision: 1298724 $
-
The Apacheâ¢ FOP developer community is eager to help you maximize the usefulness of FOP. However, to make wise use of its limited resources, support must be primarily self-service. Go through the following checklist sequentially to determine what kind of help you need, and where to get it:
+
The Apache™ FOP developer community is eager to help you maximize the usefulness of FOP. However, to make wise use of its limited resources, support must be primarily self-service. Go through the following checklist sequentially to determine what kind of help you need, and where to get it:

Understand Underlying Technologies

If you have a questions about XML, XSLT, or XSL-FO that are not directly related to FOP, please consult resources that are appropriate for those questions. FOP is an implementation of these technologies, and when you use FOP, there is a presumption that you have a working understanding of them. We have included several useful links on our Resources page that may help you get started.

Understand FOP's Limitations
Modified: websites/staging/xmlgraphics/trunk/content/fop/index.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/index.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/index.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP + Apache™ FOP @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,8 +331,8 @@ $(document).ready(function () {
$Revision: 1298724 $

Introduction
-
Apacheâ¢ FOP (Formatting Objects Processor) is a print formatter driven by XSL formatting objects (XSL-FO) and an output independent formatter. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. Output formats currently supported include PDF, PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a lesser extent, RTF and TXT. The primary output target is PDF.
-
The Apacheâ¢ FOP project is part of the Apacheâ¢ Software Foundation, which is a wider community of users and developers of open source projects. +
Apache™ FOP (Formatting Objects Processor) is a print formatter driven by XSL formatting objects (XSL-FO) and an output independent formatter. It is a Java application that reads a formatting object (FO) tree and renders the resulting pages to a specified output. Output formats currently supported include PDF, PS, PCL, AFP, XML (area tree representation), Print, AWT and PNG, and to a lesser extent, RTF and TXT. The primary output target is PDF.
+
The Apache™ FOP project is part of the Apache™ Software Foundation, which is a wider community of users and developers of open source projects.
A stable release of the latest version of FOP ( 1.0 ) is available. It's the third stable release after the large redesign effort and implements a large subset of the XSL-FO Version 1.1 W3C Recommendation .

Support for each of the standard's objects and properties is detailed in FOP Compliance . Download options include a precompiled version, source code, and many example files to get you started. Resources include links to XSL-FO introductions and many other useful references. A checklist for Getting Help will guide you toward maximizing the usefulness of FOP.
Modified: websites/staging/xmlgraphics/trunk/content/fop/knownissues.html ============================================================================== --- websites/staging/xmlgraphics/trunk/content/fop/knownissues.html (original) +++ websites/staging/xmlgraphics/trunk/content/fop/knownissues.html Mon Oct 15 03:56:36 2012 @@ -1,7 +1,7 @@ - Apacheâ¢ FOP: Known Issues + Apache™ FOP: Known Issues @@ -323,7 +323,7 @@ $(document).ready(function () {

The Apache™ FOP Project
-
+
@@ -331,7 +331,7 @@ $(document).ready(function () {
$Revision: 1298724 $

Known issues # {#Known+issues}
-
This page lists currently known issues in the Apacheâ¢ FOP codebase. Please note that this list is generated from data in FOP's code repository (Trunk) and may not exactly represent the list of issues in the latest release.
+
This page lists currently known issues in the Apache™ FOP codebase. Please note that this list is generated from data in FOP's code repository (Trunk) and may not exactly represent the list of issues in the latest release.

For additional information on known issues in Apache FOP, please have a look at the following pages, too:

@@ -341,7 +341,7 @@ $(document).ready(function () {
the task list in the Wiki

-
Apacheâ¢ FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.
+
Apache™ FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several sets of test cases. When a test case is listed in disabled-testcases.xml it is disabled in the JUnit tests during the normal build process. This indicates a problem in the current codebase. When a bug is fixed or a missing feature is added the entry for the relevant test case(s) are removed.

FO Tree ## {#FO+Tree}

This section lists currently disabled test cases in the test suite for the FO tree tests. The data for this section comes from test/fotree/disabled-testcases.xml .

demo-test-failure.fo (demo test failure):

TODO: Add missing description in disabled-testcases.xml!
--------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org For additional commands, e-mail: commits-help@xmlgraphics.apache.org

The Apache™ FOP Project

Known issues # {#Known+issues}

FO Tree ## {#FO+Tree}

The Apache™ FOP Project

The Apache™ FOP Project

General Information

Fonts

The Apache™ FOP Project

The Apache™ FOP Project

Overview

Usage (command line) # {#Usage+%28command+line%29}

The Apache™ FOP Project

Overview

Implementation Status

The Apache™ FOP Project

The Apache™ FOP Project

Overview

Example Servlets in the FOP distribution

The Apache™ FOP Project

Important!

The Apache™ FOP Project

The Apache™ FOP Project

Subversion Repository

The Apache™ FOP Project

The Apache™ FOP Project

The Apache™ FOP Project

Introduction

Settings

User Agent ## {#User+Agent}

The Apache™ FOP Project

Introduction

Extensions

The Apache™ FOP Project

The Apache™ FOP Project

The Apache™ FOP Project

The Black Box View

The Apache™ FOP Project

The Apache™ FOP Project

Introduction

The Apache™ FOP Project

Introduction

SAX for Input

The Apache™ FOP Project

Introduction

PDF Document # {#PDF+Document}

The Apache™ FOP Project

The Apache™ FOP Project

Introduction

Status

To Do

The Apache™ FOP Project

Introduction

The Apache™ FOP Project

Introduction

The Apache™ FOP Project

General Information

Design Principles

The Apache™ FOP Project

Overview

The Apache™ FOP Project

Overview

Startup

The Apache™ FOP Project

Introduction

Development

The Apache™ FOP Project

Introduction

Checklist

The Apache™ FOP Project

The Apache™ FOP Project

The Apache™ FOP Project

"Build" Testing

The Apache™ FOP Project

Developer Checklist

The Apache™ FOP Project

Binary or Source?

The Apache™ FOP Project

Example Documents Using Apacheâ¢ FOP # {#Example+Documents+Using+Apache%E2%84%A2+FOP}

Example Documents Using Apache™ FOP # {#Example+Documents+Using+Apache%E2%84%A2+FOP}

Questions

Example Documents Using Apacheâ¢ FOP # {#Example+Documents+Using+Apache%E2%84%A2+FOP}

1. Apacheâ¢ FOP: General questions

1.1. What is Apacheâ¢ FOP?