Structure

Since the area tree will be used during the layout by the layout managers it will need to store information that affects the layout. The information such as spacing and keeps will be held in such a way that it can be @@ -27,7 +27,7 @@ discarded once the layout is finalised.

A walk-through -

Layout Managers are created from the top down. First the +

Layout Managers are created from the top down. First the page sequence creates a PageLM and a FlowLM. The PageLM will manage finding the right page model (with help from the PageSequenceMaster) and managing the balancing act between before-floats, footnotes and diff --git a/src/documentation/content/xdocs/design/extending.xml b/src/documentation/content/xdocs/design/extending.xml index 35d468422..2796f2e3d 100644 --- a/src/documentation/content/xdocs/design/extending.xml +++ b/src/documentation/content/xdocs/design/extending.xml @@ -9,7 +9,7 @@ - +

diff --git a/src/documentation/content/xdocs/design/fotree.xml b/src/documentation/content/xdocs/design/fotree.xml index a4c5c0c1d..e1573037b 100644 --- a/src/documentation/content/xdocs/design/fotree.xml +++ b/src/documentation/content/xdocs/design/fotree.xml @@ -2,7 +2,7 @@ - +

FO Tree Design of FO Tree Structure @@ -14,7 +14,7 @@

Introduction -

The FO Tree is an internal representation of the input FO document. The tree is created by building the elements and attributes from the SAX events. diff --git a/src/documentation/content/xdocs/design/properties.xml b/src/documentation/content/xdocs/design/properties.xml index bcc4983ce..713ba2ac3 100644 --- a/src/documentation/content/xdocs/design/properties.xml +++ b/src/documentation/content/xdocs/design/properties.xml @@ -2,7 +2,7 @@ - +

Properties Properties overview @@ -11,7 +11,7 @@

- +

Properties @@ -19,7 +19,7 @@ Property datatypes

The property datatypes are defined in the org.apache.fop.datatypes package, except Number and String which are java -primitives. The FOP datatypes are:

+primitives. The FOP datatypes are:

Number
String

Properties diff --git a/src/documentation/content/xdocs/design/understanding/properties.xml b/src/documentation/content/xdocs/design/understanding/properties.xml index 6261b3d8e..54d952410 100644 --- a/src/documentation/content/xdocs/design/understanding/properties.xml +++ b/src/documentation/content/xdocs/design/understanding/properties.xml @@ -28,13 +28,13 @@ the element name. Most Makers are generic and handle the attribute on any element, but it's possible to set up an element-specific property Maker. The attribute name to Maker mappings are automatically created during the code generation phase by processing the XML property -description files.

+description files.

Processing the attribute list

The PLB first looks to see if the font-size property is specified, since -it sets up relative units which can be used in other property +it sets up relative units which can be used in other property specifications. Each attribute is then handled in turn. If the attribute specifies part of a compound property such as space-before.optimum, the PLB looks to see if the attribute list also contains the "base" property @@ -59,7 +59,7 @@ defined in foproperties.xml. The keyword value is just a string, so it still needs to be parsed as described next.

The Maker also checks to see if the property is an Enumerated type and -then checks whether the value matches one of the specified enumeration +then checks whether the value matches one of the specified enumeration values.

Otherwise the Maker uses the property parser in the fo.expr package to diff --git a/src/documentation/content/xdocs/dev/configuration.xml b/src/documentation/content/xdocs/dev/configuration.xml index f73a14c5c..c85ad2038 100644 --- a/src/documentation/content/xdocs/dev/configuration.xml +++ b/src/documentation/content/xdocs/dev/configuration.xml @@ -2,11 +2,11 @@ - -

- Configuration -

- + +

+ Configuration +

Configuring FOP

diff --git a/src/documentation/content/xdocs/dev/examples.xml b/src/documentation/content/xdocs/dev/examples.xml index 210f42c5a..2542dba56 100644 --- a/src/documentation/content/xdocs/dev/examples.xml +++ b/src/documentation/content/xdocs/dev/examples.xml @@ -2,11 +2,11 @@ - -

- FO Examples -

- + +

+ FO Examples +

Example Documents Using FOP

diff --git a/src/documentation/content/xdocs/dev/extensions.xml b/src/documentation/content/xdocs/dev/extensions.xml index 3b7ab1bbf..654976a30 100644 --- a/src/documentation/content/xdocs/dev/extensions.xml +++ b/src/documentation/content/xdocs/dev/extensions.xml @@ -2,11 +2,11 @@ - -

- Extensions to FOP -

- + +

+ Extensions to FOP +

Overview

diff --git a/src/documentation/content/xdocs/dev/faq.xml b/src/documentation/content/xdocs/dev/faq.xml index 20c04de65..3a1c56f24 100644 --- a/src/documentation/content/xdocs/dev/faq.xml +++ b/src/documentation/content/xdocs/dev/faq.xml @@ -834,7 +834,7 @@ transformer.transform(xmlsource, new SAXResult(driver.getContentHandler()));Watermarks

Answer: see 3.3, or use a a region overlapping the flowing text and put - an image there: + an image there:

> From: Trevor_Campbell@kaz.com.au Use the region-before. Make it large enough to contain your image and then diff --git a/src/documentation/content/xdocs/dev/fo/embedding.fo b/src/documentation/content/xdocs/dev/fo/embedding.fo index 4570ad057..7a172a91d 100644 --- a/src/documentation/content/xdocs/dev/fo/embedding.fo +++ b/src/documentation/content/xdocs/dev/fo/embedding.fo @@ -1089,7 +1089,7 @@ Clipping - + @@ -1097,7 +1097,7 @@ Interesting Functionality - + diff --git a/src/documentation/content/xdocs/dev/index.xml b/src/documentation/content/xdocs/dev/index.xml index d73c1bd85..dfb16c81d 100644 --- a/src/documentation/content/xdocs/dev/index.xml +++ b/src/documentation/content/xdocs/dev/index.xml @@ -2,11 +2,11 @@ - -

- FOP 1.0 development -

- + +

+ FOP 1.0 development +

Introduction

@@ -56,13 +56,13 @@ This image is a demonstration of a two page document. The xml data on the left is formatted into the two pages on the right. The document contains static areasthat appear on every page, an external graphic in this case an svg document. There is a footnote on the first page and a table that goes across both pages.

The advantage of XSL is the ability to take an XML document and to format the information into a page layout. The XML document can be generated in any way, the most common would be to use XSLT. FOP takes the XML and formats the data into pages. The pages are then rendered to the requested output. -

This is a real document. The image was created by rendering the document to the svg renderer then putting the rendered pages into an svg document @@ -80,7 +80,7 @@ The goals of the Apache XML FOP Project are to deliver an XSL FO->PDF formatter

Conformance to the XML 1.0 Recommendation, XSLT 1.0 Recommendation and the XML Namespaces Recommendation is understood. Other relevant documents, such as the XPath and XLink Working Drafts, are referenced as necessary. The FOP Project will attempt to use the latest version of evolving specifications. -

To reach this aim currently the layout system is being redesigned to better handle the formatting of all different types of formatting objects. diff --git a/src/documentation/content/xdocs/dev/svg.xml b/src/documentation/content/xdocs/dev/svg.xml index 5ed6ab728..cc83bee3e 100644 --- a/src/documentation/content/xdocs/dev/svg.xml +++ b/src/documentation/content/xdocs/dev/svg.xml @@ -2,11 +2,11 @@ - -

- SVG in FOP -

- + +

+ SVG in FOP +

Introduction

@@ -70,13 +70,13 @@ to PDF: SVG to PDF examples - svg file - png file - pdf result + svg file + png file + pdf result - images - images.svg + images + images.svg images.png images.pdf @@ -123,7 +123,7 @@ You will need Acrobat 5.0 to see transparency. embedding.fo embedding.fo.pdf - +

Important Notes diff --git a/src/documentation/content/xdocs/dev/svg/text.svg b/src/documentation/content/xdocs/dev/svg/text.svg index 8ac73ec51..2cdd6179e 100644 --- a/src/documentation/content/xdocs/dev/svg/text.svg +++ b/src/documentation/content/xdocs/dev/svg/text.svg @@ -88,7 +88,7 @@ - + @@ -101,7 +101,7 @@ - + diff --git a/src/documentation/content/xdocs/examples.xml b/src/documentation/content/xdocs/examples.xml index d29906585..13c0f0737 100644 --- a/src/documentation/content/xdocs/examples.xml +++ b/src/documentation/content/xdocs/examples.xml @@ -43,7 +43,7 @@

readme.fo - uses an old version of Fop documentation for a longer example

- +

Look also into the directory examples/svg. There you find some very extensive svg examples. Just start makedoc.

diff --git a/src/documentation/content/xdocs/extensions.xml b/src/documentation/content/xdocs/extensions.xml index 4a8e75c78..d200ecd41 100644 --- a/src/documentation/content/xdocs/extensions.xml +++ b/src/documentation/content/xdocs/extensions.xml @@ -44,8 +44,8 @@ Please see the SVG page for more details. ]]> -

It works similarly to a basic-link. There is also an external-destination - property, but it isn't supported currently. See the pdfoutline.fo file in +

It works similarly to a basic-link. There is also an external-destination + property, but it isn't supported currently. See the pdfoutline.fo file in docs/examples/fo for a more complete example.

diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml index 5535db6a4..c730407ec 100644 --- a/src/documentation/content/xdocs/faq.xml +++ b/src/documentation/content/xdocs/faq.xml @@ -883,7 +883,7 @@ transformer.transform(xmlsource, new SAXResult(driver.getContentHandler()));Watermarks

Answer: see 3.3, or use a a region overlapping the flowing text and put - an image there: + an image there:

> From: Trevor_Campbell@kaz.com.au Use the region-before. Make it large enough to contain your image and then diff --git a/src/documentation/content/xdocs/fo/align.fo b/src/documentation/content/xdocs/fo/align.fo index 6c9449a7a..4887af4b6 100644 --- a/src/documentation/content/xdocs/fo/align.fo +++ b/src/documentation/content/xdocs/fo/align.fo @@ -21,9 +21,9 @@ - - - + + + diff --git a/src/documentation/content/xdocs/fo/align2.fo b/src/documentation/content/xdocs/fo/align2.fo index 8c85414d5..7c9532c25 100644 --- a/src/documentation/content/xdocs/fo/align2.fo +++ b/src/documentation/content/xdocs/fo/align2.fo @@ -21,9 +21,9 @@ - - - + + + diff --git a/src/documentation/content/xdocs/fo/embed.fo b/src/documentation/content/xdocs/fo/embed.fo index 04ec81161..2993552da 100644 --- a/src/documentation/content/xdocs/fo/embed.fo +++ b/src/documentation/content/xdocs/fo/embed.fo @@ -24,9 +24,9 @@ - - - + + + diff --git a/src/documentation/content/xdocs/fo/size.fo b/src/documentation/content/xdocs/fo/size.fo index ae6f763e2..0279c69ef 100644 --- a/src/documentation/content/xdocs/fo/size.fo +++ b/src/documentation/content/xdocs/fo/size.fo @@ -21,9 +21,9 @@ - - - + + + diff --git a/src/documentation/content/xdocs/implemented.xml b/src/documentation/content/xdocs/implemented.xml index 7f690f6ee..a3a700724 100644 --- a/src/documentation/content/xdocs/implemented.xml +++ b/src/documentation/content/xdocs/implemented.xml @@ -18,7 +18,7 @@

1) Formatting Objects -

This section follows the table "B Formatting Object Summary" in the xsl:fo specification. At the +

This section follows the table "B Formatting Object Summary" in the xsl:fo specification. At the end of each sub-section you find listed what is not implemented.

@@ -37,7 +37,7 @@

region-before

region-after

region-start

region-end

flow

static-content

diff --git a/src/documentation/content/xdocs/index.xml b/src/documentation/content/xdocs/index.xml index 3d77556dd..f58651e4b 100644 --- a/src/documentation/content/xdocs/index.xml +++ b/src/documentation/content/xdocs/index.xml @@ -2,32 +2,32 @@ - -

- FOP -

- + +

+ FOP +

Introduction

FOP (Formatting Objects Processor) is the world's first print formatter driven by XSL formatting objects and the world's first output independent formatter. It is a Java application that reads a formatting object tree and then renders the resulting pages to a specified output. Output formats - currently supported are PDF, PCL, PS, SVG, XML (area tree representation), + currently supported are PDF, PCL, PS, SVG, XML (area tree representation), Print, AWT, MIF and TXT. - The primary output target is PDF. + The primary output target is PDF.

The PDF files on this site are created using current CVS. -

The latest version of Fop is 0.20.4 and it supports the XSL-FO Version 1.0 W3C Recommendation. - You can download - Fop including a precompiled version, the source code and many example files to + You can download + Fop including a precompiled version, the source code and many example files to get you started. Pointers to introductions into xsl:fo can be found in the - resources section. Please be aware, that + resources section. Please be aware, that Fop is at the moment not a full implementation of the basic conformance level of the xsl:fo standard. You can find a list of supported flow objects and properties in the section Features and in section diff --git a/src/documentation/content/xdocs/license.xml b/src/documentation/content/xdocs/license.xml index 52fb41edc..bf1bdc4ec 100644 --- a/src/documentation/content/xdocs/license.xml +++ b/src/documentation/content/xdocs/license.xml @@ -12,7 +12,7 @@

The Apache Software License, Version 1.1

Redistribution and use in source and binary forms, with or without modification, +

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. @@ -54,7 +54,7 @@

This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally created by - James Tauber <jtauber@jtauber.com>. For more information on the Apache + James Tauber <jtauber@jtauber.com>. For more information on the Apache Software Foundation, please see http://www.apache.org/.

diff --git a/src/documentation/content/xdocs/output.xml b/src/documentation/content/xdocs/output.xml index 528c01605..fee304c53 100644 --- a/src/documentation/content/xdocs/output.xml +++ b/src/documentation/content/xdocs/output.xml @@ -3,7 +3,7 @@ "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd"> - +

Output Notes about Output Formats: Renderers @@ -27,7 +27,7 @@ different renderers.

Common Information -

Each renderer is given an area tree to render to its output format. The area tree is simply a representation of the pages and the placement of text and graphical objects on those pages. @@ -39,7 +39,7 @@ output format and associated data and flow.

Fonts and Layout - some formats (eg. PDF and AWT) rely on different -font information. The fonts for these outputs have different sizes +font information. The fonts for these outputs have different sizes for the same point size. This means that the layout can be quite different for the same fo document.

diff --git a/src/documentation/content/xdocs/relnotes.xml b/src/documentation/content/xdocs/relnotes.xml index 3f38ac19b..07ab384b2 100644 --- a/src/documentation/content/xdocs/relnotes.xml +++ b/src/documentation/content/xdocs/relnotes.xml @@ -21,7 +21,7 @@ (which includes Crimson and Xalan).

The following JARs have been updated: - Xerces to version 2.0.1, Xalan to version 2.3.1 and Batik to version 1.5beta2. + Xerces to version 2.0.1, Xalan to version 2.3.1 and Batik to version 1.5beta2.

Fop has been compiled with Jimi support this time but you still have to download diff --git a/src/documentation/content/xdocs/resources.xml b/src/documentation/content/xdocs/resources.xml index 289e68b14..d83145499 100644 --- a/src/documentation/content/xdocs/resources.xml +++ b/src/documentation/content/xdocs/resources.xml @@ -1,13 +1,13 @@ - + - +

Resources Resources useful for developing and using FOP -

FOP Relevant Specifications and Links diff --git a/src/documentation/content/xdocs/status.xml b/src/documentation/content/xdocs/status.xml index d591ed3b1..48e866650 100644 --- a/src/documentation/content/xdocs/status.xml +++ b/src/documentation/content/xdocs/status.xml @@ -3,13 +3,13 @@ "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd"> - +

FOP Status Current Status of FOP

- +

Status @@ -21,7 +21,7 @@ maintenance releases while the development is done to address various performance and design issues.

- +

Development Status

@@ -30,7 +30,7 @@ performance. The new design focusing on making it possible to be conformant to the spec and be able to handle large documents. The development effort is roughly 50% towards a developers release.

The developers release should have the following: similar functionality to previous FOP releases, a rough API and a suitable design for developers to work on more functionality. @@ -48,7 +48,7 @@ to predict any dates. xalan.jar883 kb xerces.jar1,809 kb - +

Lines of code using "find . -iname "*.java" | xargs cat | wc -l"

diff --git a/src/documentation/content/xdocs/testing.xml b/src/documentation/content/xdocs/testing.xml index 219953d5a..977170338 100644 --- a/src/documentation/content/xdocs/testing.xml +++ b/src/documentation/content/xdocs/testing.xml @@ -14,11 +14,11 @@

Running and Using Tests

-Testing is an important part of getting FOP to operate correctly and conform to the +Testing is an important part of getting FOP to operate correctly and conform to the necessary standards.

-A testing system has been set up that works with as a build target when developing +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.

@@ -26,7 +26,7 @@ is to have the tests run to verfiy that nothing working has been broken. 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. -

@@ -42,9 +42,9 @@ Then you can uncomment the lines in the build.xml file in the test target and it

Writing a Test

-A test belongs to one of a few catagories. A basic test should excercise one +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 +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.

diff --git a/src/documentation/sitemap.xmap b/src/documentation/sitemap.xmap index b7dc776a9..ab029291e 100644 --- a/src/documentation/sitemap.xmap +++ b/src/documentation/sitemap.xmap @@ -33,7 +33,7 @@ - + @@ -103,7 +103,7 @@ --> - + @@ -125,7 +125,7 @@ - @@ -149,7 +149,7 @@ - + @@ -216,7 +216,7 @@ - + @@ -386,15 +386,15 @@ - + - + - + @@ -404,7 +404,7 @@ - + @@ -594,7 +594,7 @@ - + diff --git a/src/documentation/skinconf.xml b/src/documentation/skinconf.xml index 82d35a62f..cc1b1d99d 100644 --- a/src/documentation/skinconf.xml +++ b/src/documentation/skinconf.xml @@ -16,7 +16,7 @@ jefft@apache.org - + @@ -45,7 +45,7 @@ jefft@apache.org false xml.apache.org - Apache XML + Apache XML FOP -- 2.39.5

org.apache.fop.*

67479