diff options
| author | Chris Bowditch <cbowditch@apache.org> | 2012-03-09 07:55:31 +0000 |
|---|---|---|
| committer | Chris Bowditch <cbowditch@apache.org> | 2012-03-09 07:55:31 +0000 |
| commit | eba117d34f664d9cd55be96dadb9028662eaa02c (patch) | |
| tree | ef60a634679992e637d405a8b5aef3496d795319 /src | |
| parent | 202445c5d3a482c3f3767359796000ae63f573f5 (diff) | |
| download | xmlgraphics-fop-eba117d34f664d9cd55be96dadb9028662eaa02c.tar.gz xmlgraphics-fop-eba117d34f664d9cd55be96dadb9028662eaa02c.zip | |
Apache Brand compliance;
Add links to security and Apache websites
Make sure at least the titles all refer to FOP with Apacheâ„¢ prefix
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@1298724 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'src')
107 files changed, 592 insertions, 613 deletions
diff --git a/src/documentation/content/xdocs/0.95/anttask.xml b/src/documentation/content/xdocs/0.95/anttask.xml index 44550c3d7..9d01ed3ae 100644 --- a/src/documentation/content/xdocs/0.95/anttask.xml +++ b/src/documentation/content/xdocs/0.95/anttask.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,12 +19,12 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Ant task</title> + <title>Apacheâ„¢ FOP: Ant task</title> <version>$Revision$</version> </header> <body> <p> - Apache FOP provides an Ant task for automating the document build process. + Apacheâ„¢ FOP provides an Ant task for automating the document build process. </p> <section id="basics"> <title>Description</title> @@ -195,3 +195,6 @@ </body> </document> + + + diff --git a/src/documentation/content/xdocs/0.95/compiling.xml b/src/documentation/content/xdocs/0.95/compiling.xml index 98a6dfb6d..cf7b950ca 100644 --- a/src/documentation/content/xdocs/0.95/compiling.xml +++ b/src/documentation/content/xdocs/0.95/compiling.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Building from Source Code</title> + <title>Apacheâ„¢ FOP: Building from Source Code</title> <version>$Revision$</version> </header> <body> <section id="build-needed"> <title>Do You Need To Build?</title> <p> - FOP distributions are either pre-compiled binary or source. + Apacheâ„¢ FOP distributions are either pre-compiled binary or source. If you are using a binary distribution, it is already built and there is no need to build it again. See the <a href="../download.html">Download Instructions</a> for information about whether a binary or source distribution is best for your needs. @@ -137,5 +137,4 @@ </ul> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/configuration.xml b/src/documentation/content/xdocs/0.95/configuration.xml index e82a6e862..981f079eb 100644 --- a/src/documentation/content/xdocs/0.95/configuration.xml +++ b/src/documentation/content/xdocs/0.95/configuration.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Configuration</title> + <title>Apacheâ„¢ FOP: Configuration</title> <version>$Revision$</version> </header> @@ -390,5 +390,4 @@ information it finds. Check if FOP finds what you expect.</li> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/embedding.xml b/src/documentation/content/xdocs/0.95/embedding.xml index b2c802db7..a7c7ccaf8 100644 --- a/src/documentation/content/xdocs/0.95/embedding.xml +++ b/src/documentation/content/xdocs/0.95/embedding.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,8 +20,8 @@ <!-- Embedding FOP --> <document> <header> - <title>Apache FOP: Embedding</title> - <subtitle>How to Embed FOP in a Java application</subtitle> + <title>Apacheâ„¢ FOP: Embedding</title> + <subtitle>How to Embed Apacheâ„¢ FOP in a Java application</subtitle> <version>$Revision$</version> </header> @@ -29,11 +29,11 @@ <section id="overview"> <title>Overview</title> <p> - Review <a href="running.html">Running FOP</a> for important information that applies + Review <a href="running.html">Running Apacheâ„¢ FOP</a> for important information that applies to embedded applications as well as command-line use, such as options and performance. </p> <p> - To embed Apache FOP in your application, first create a new + To embed Apacheâ„¢ FOP in your application, first create a new org.apache.fop.apps.FopFactory instance. This object can be used to launch multiple rendering runs. For each run, create a new org.apache.fop.apps.Fop instance through one of the factory methods of FopFactory. In the method call you specify which output @@ -685,5 +685,4 @@ mailing list. </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/extensions.xml b/src/documentation/content/xdocs/0.95/extensions.xml index 878494ecb..e477ecc61 100644 --- a/src/documentation/content/xdocs/0.95/extensions.xml +++ b/src/documentation/content/xdocs/0.95/extensions.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Standard FOP Extensions</title> + <title>Standard Apacheâ„¢ FOP Extensions</title> <version>$Revision$</version> </header> <body> @@ -230,5 +230,4 @@ to following pages. Here is an example of FO code creating such a table-header:< </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/fonts.xml b/src/documentation/content/xdocs/0.95/fonts.xml index 423eaad11..976545c36 100644 --- a/src/documentation/content/xdocs/0.95/fonts.xml +++ b/src/documentation/content/xdocs/0.95/fonts.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Fonts</title> + <title>Apache™ FOP: Fonts</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email=""/> @@ -407,4 +407,4 @@ </section--> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/graphics.xml b/src/documentation/content/xdocs/0.95/graphics.xml index 5ecca1ea8..b82912ba6 100644 --- a/src/documentation/content/xdocs/0.95/graphics.xml +++ b/src/documentation/content/xdocs/0.95/graphics.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Graphics Formats</title> + <title>Apacheâ„¢ FOP: Graphics Formats</title> <version>$Revision$</version> </header> <body> <section id="introduction"> <title>Introduction</title> <p> - After the Apache FOP 0.94 release, the image handling subsystem has been rewritten in + After the Apacheâ„¢ FOP 0.94 release, the image handling subsystem has been rewritten in order to improve the range of supported images and image subtypes, to lower the overall memory consumption when handling images, to produce smaller output files and to increase the performance in certain areas. Of course, this causes a few changes most of @@ -77,65 +77,65 @@ <tr> <td><a href="#bmp">BMP</a> (Microsoft Windows Bitmap)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#emf">EMF</a> (Windows Enhanced Metafile)</td> <td>vector (with embedded bitmaps)</td> <td>(X)</td> - <td></td> - <td></td> + <td/> + <td/> </tr> <tr> <td><a href="#eps">EPS</a> (Encapsulated PostScript)</td> <td>metafile (both bitmap and vector), most frequently used for vector drawings</td> <td>(X)</td> - <td></td> - <td></td> + <td/> + <td/> </tr> <tr> <td>GIF (Graphics Interchange Format)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X</td> </tr> <tr> <td><a href="#jpeg">JPEG</a> (Joint Photographic Experts Group)</td> <td>bitmap</td> <td>(X)</td> - <td></td> + <td/> <td>X</td> </tr> <tr> <td><a href="#png">PNG</a> (Portable Network Graphic)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X</td> </tr> <tr> <td><a href="#svg">SVG</a> (Scalable Vector Graphics)</td> <td>vector (with embedded bitmaps)</td> - <td></td> + <td/> <td>X</td> - <td></td> + <td/> </tr> <tr> <td><a href="#tiff">TIFF</a> (Tag Image Format File)</td> <td>bitmap</td> <td>(X)</td> - <td></td> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#wmf">WMF</a> (Windows Metafile)</td> <td>vector (with embedded bitmaps)</td> - <td></td> + <td/> <td>(X)</td> - <td></td> + <td/> </tr> </table> <p> @@ -153,7 +153,7 @@ <note> <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a>! The - former simply exposes JAI's codecs using the Image I/O API but does not include all + former simply exposes JAI's codecs using the Image&nbsp;I/O API but does not include all the image manipulation functionality. </note> <section id="format-map"> @@ -185,21 +185,21 @@ </tr> <tr> <td><a href="#emf">EMF</a> (Windows Enhanced Metafile)</td> - <td></td> - <td></td> - <td></td> - <td></td> - <td></td> + <td/> + <td/> + <td/> + <td/> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#eps">EPS</a> (Encapsulated PostScript)</td> - <td></td> + <td/> <td>X [1]</td> - <td></td> - <td></td> - <td></td> - <td></td> + <td/> + <td/> + <td/> + <td/> </tr> <tr> <td>GIF (Graphics Interchange Format)</td> @@ -365,7 +365,7 @@ <section id="gif"> <title>GIF</title> <p> - GIF images are supported through an Image I/O codec. Transparency is supported but + GIF images are supported through an Image&nbsp;I/O codec. Transparency is supported but not guaranteed to work with every output format. </p> </section> @@ -380,14 +380,14 @@ through without decompression. User reports indicate that grayscale, RGB, and CMYK color spaces are all rendered properly. However, for other output formats, the JPEG images have to be decompressed. Tests have shown that there are some limitation - in some Image I/O codecs concerning images in the CMYK color space. Work-arounds are + in some Image&nbsp;I/O codecs concerning images in the CMYK color space. Work-arounds are in place but may not always work as expected. </p> </section> <section id="png"> <title>PNG</title> <p> - PNG images are supported through an Image I/O codec. Transparency is supported but + PNG images are supported through an Image&nbsp;I/O codec. Transparency is supported but not guaranteed to work with every output format. </p> </section> @@ -497,7 +497,7 @@ <p> FOP can embed TIFF images without decompression into PDF, PostScript and AFP if they have either CCITT T.4, CCITT T.6, or JPEG compression. Otherwise, a TIFF-capable - Image I/O codec is necessary for decoding the image. + Image&nbsp;I/O codec is necessary for decoding the image. </p> <p> There may be some limitation concerning images in the CMYK color space. @@ -564,4 +564,4 @@ </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/hyphenation.xml b/src/documentation/content/xdocs/0.95/hyphenation.xml index ed97c6868..1d1c63d82 100644 --- a/src/documentation/content/xdocs/0.95/hyphenation.xml +++ b/src/documentation/content/xdocs/0.95/hyphenation.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Hyphenation</title> + <title>Apacheâ„¢ FOP: Hyphenation</title> <version>$Revision$</version> </header> <body> @@ -27,7 +27,7 @@ <title>Hyphenation Support</title> <section id="intro"> <title>Introduction</title> - <p>FOP uses Liang's hyphenation algorithm, well known from TeX. It needs + <p>Apacheâ„¢ FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.</p> <p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through @@ -145,16 +145,16 @@ confirming their accuracy, or raising specific problems that we can address.</warning> <ul> - <li>The root of the pattern file is the <hyphenation-info> element.</li> - <li><hyphen-char>: its attribute "value" contains the character signalling - a hyphen in the <exceptions> section. It has nothing to do with the + <li>The root of the pattern file is the <hyphenation-info> element.</li> + <li><hyphen-char>: its attribute "value" contains the character signalling + a hyphen in the <exceptions> section. It has nothing to do with the hyphenation character used in FOP, use the XSLFO hyphenation-character property for defining the hyphenation character there. At some points a dash U+002D is hardwired in the code, so you'd better use this too (patches to rectify the situation are welcome). There is no default, if you declare exceptions with hyphenations, you must declare the hyphen-char too.</li> - <li><hyphen-min> contains two attributes: + <li><hyphen-min> contains two attributes: <ul> <li>before: the minimum number of characters in a word allowed to exist on a line immediately preceding a hyphenated word-break.</li> @@ -164,23 +164,23 @@ This element is unused and not even read. It should be considered a documentation for parameters used during pattern generation. </li> - <li><classes> contains whitespace-separated character sets. The members + <li><classes> contains whitespace-separated character sets. The members of each set should be treated as equivalent for purposes of hyphenation, usually upper and lower case of the same character. The first character of the set is the canonical character, the patterns and exceptions should only contain these canonical representation characters (except digits for weight, the period (.) as word delimiter in the patterns and the hyphen char in exceptions, of course).</li> - <li><exceptions> contains whitespace-separated words, each of which + <li><exceptions> contains whitespace-separated words, each of which has either explicit hyphen characters to denote acceptable breakage points, or no hyphen characters, to indicate that this word should - never be hyphenated, or contain explicit <hyp> elements for specifying - changes of spelling due to hyphenation (like backen -> bak-ken or - Stoffarbe -> Stoff-farbe in the old german spelling). Exceptions override - the patterns described below. Explicit <hyp> declarations don't work + never be hyphenated, or contain explicit <hyp> elements for specifying + changes of spelling due to hyphenation (like backen -> bak-ken or + Stoffarbe -> Stoff-farbe in the old german spelling). Exceptions override + the patterns described below. Explicit <hyp> declarations don't work yet (patches welcome). Exceptions are generally a bit brittle, test carefully.</li> - <li><patterns> includes whitespace-separated patterns, which are what + <li><patterns> includes whitespace-separated patterns, which are what drive most hyphenation decisions. The characters in these patterns are explained as follows: <ul> @@ -234,4 +234,4 @@ hyphenation.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/index.xml b/src/documentation/content/xdocs/0.95/index.xml index 8f1568b6b..49d07332c 100644 --- a/src/documentation/content/xdocs/0.95/index.xml +++ b/src/documentation/content/xdocs/0.95/index.xml @@ -26,7 +26,7 @@ <section id="intro"> <title>Introduction</title> <p> - The Apache FOP team is proud to present to you this production quality release. + The Apacheâ„¢ FOP team is proud to present to you this production quality release. We're still in the process of adding new features. We welcome any feedback you might have and even more, any other form of help to get the project forward. </p> @@ -51,4 +51,4 @@ </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/intermediate.xml b/src/documentation/content/xdocs/0.95/intermediate.xml index 4744185aa..e46190276 100644 --- a/src/documentation/content/xdocs/0.95/intermediate.xml +++ b/src/documentation/content/xdocs/0.95/intermediate.xml @@ -19,13 +19,13 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Intermediate Format</title> + <title>Apacheâ„¢ FOP: Intermediate Format</title> <version>$Revision$</version> </header> <body> <note> Please note that the intermediate format is an <strong>advanced feature</strong> and can be ignored by most - users of Apache FOP. + users of Apacheâ„¢ FOP. </note> <section id="introduction"> <title>Introduction</title> @@ -143,4 +143,4 @@ try { </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/knownissues_overview.xml b/src/documentation/content/xdocs/0.95/knownissues_overview.xml index 7247e6b79..53d65a2ca 100644 --- a/src/documentation/content/xdocs/0.95/knownissues_overview.xml +++ b/src/documentation/content/xdocs/0.95/knownissues_overview.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document xmlns:xi="http://www.w3.org/2001/XInclude"> <header> - <title>Apache FOP: Known Issues</title> + <title>Apacheâ„¢ FOP: Known Issues</title> <version>$Revision$</version> </header> <body> @@ -30,7 +30,7 @@ </p> <note> <p> - 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: </p> <ul> <li><a href="../bugs.html">the bug list in Bugzilla</a></li> @@ -66,5 +66,4 @@ </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/metadata.xml b/src/documentation/content/xdocs/0.95/metadata.xml index 8c273fff5..5d4185533 100644 --- a/src/documentation/content/xdocs/0.95/metadata.xml +++ b/src/documentation/content/xdocs/0.95/metadata.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>Metadata</title> + <title>Apacheâ„¢ FOP: Metadata</title> </header> <body> <section id="overview"> @@ -42,7 +42,7 @@ <title>Embedding XMP in an XSL-FO document</title> <p> As noted above, there's no officially recommended way to embed metadata in XSL-FO. - Apache FOP supports embedding XMP in XSL-FO. Currently, only support for document-level + Apacheâ„¢ FOP supports embedding XMP in XSL-FO. Currently, only support for document-level metadata is implemented. Object-level metadata will be implemented when there's interest. </p> @@ -240,4 +240,4 @@ </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/output.xml b/src/documentation/content/xdocs/0.95/output.xml index fbf277b90..16130e8e6 100644 --- a/src/documentation/content/xdocs/0.95/output.xml +++ b/src/documentation/content/xdocs/0.95/output.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <!-- Output Formats: Renderers --> <document> <header> - <title>Apache FOP Output Formats</title> + <title>Apacheâ„¢ FOP Output Formats</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -30,7 +30,7 @@ <body> <p> - FOP supports multiple output formats by using a different renderer for each format. + 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. @@ -911,6 +911,4 @@ out = proc.getOutputStream();]]></source> </section> </body> -</document> - - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/pdfa.xml b/src/documentation/content/xdocs/0.95/pdfa.xml index bfa1ae33e..e1d3f3010 100644 --- a/src/documentation/content/xdocs/0.95/pdfa.xml +++ b/src/documentation/content/xdocs/0.95/pdfa.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>PDF/A (ISO 19005)</title> + <title>Apache™ FOP: PDF/A (ISO 19005)</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email="jeremias@apache.org"/> @@ -153,4 +153,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/pdfencryption.xml b/src/documentation/content/xdocs/0.95/pdfencryption.xml index cda301aab..e743f5fff 100644 --- a/src/documentation/content/xdocs/0.95/pdfencryption.xml +++ b/src/documentation/content/xdocs/0.95/pdfencryption.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>PDF encryption.</title> + <title>Apacheâ„¢ FOP: PDF encryption.</title> <version>$Revision$</version> <authors> <person name="J.Pietschmann" email="pietsch@apache.org"/> @@ -30,7 +30,7 @@ <section> <title>Overview</title> <p> - FOP supports encryption of PDF output, thanks to Patrick + 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 @@ -222,4 +222,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/pdfx.xml b/src/documentation/content/xdocs/0.95/pdfx.xml index cf796c74d..bef2fce2a 100644 --- a/src/documentation/content/xdocs/0.95/pdfx.xml +++ b/src/documentation/content/xdocs/0.95/pdfx.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Copyright 2006 The Apache Software Foundation @@ -18,7 +18,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>PDF/X (ISO 15930)</title> + <title>Apache™ FOP: PDF/X (ISO 15930)</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email="jeremias@apache.org"/> @@ -133,4 +133,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/running.xml b/src/documentation/content/xdocs/0.95/running.xml index 38e31cc6c..26a9596c0 100644 --- a/src/documentation/content/xdocs/0.95/running.xml +++ b/src/documentation/content/xdocs/0.95/running.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Running Apache FOP</title> + <title>Running Apacheâ„¢ FOP</title> <version>$Revision$</version> </header> @@ -32,13 +32,13 @@ Java 1.4.x or later Runtime Environment. <ul> <li> - Many JREs >=1.4 contain older JAXP implementations (which often contain bugs). It's + Many JREs >=1.4 contain older JAXP implementations (which often contain bugs). It's usually a good idea to replace them with a current implementation. </li> </ul> </li> <li> - Apache FOP. The <a href="../download.html">FOP distribution</a> includes all libraries that you will + Apacheâ„¢ FOP. The <a href="../download.html">FOP distribution</a> 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: <ul> @@ -190,8 +190,8 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <title>Writing your own script</title> <p>FOP's entry point for your own scripts is the class <code>org.apache.fop.cli.Main</code>. The general pattern for the - command line is: <code>java -classpath <CLASSPATH> - org.apache.fop.cli.Main <arguments></code>. The arguments + command line is: <code>java -classpath <CLASSPATH> + org.apache.fop.cli.Main <arguments></code>. The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that @@ -202,7 +202,7 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <title>Running with java's <code>-jar</code> option</title> <p> As an alternative to the start scripts you can run <code>java - -jar path/to/build/fop.jar <arguments></code>, relying on + -jar path/to/build/fop.jar <arguments></code>, relying on FOP to build the classpath for running FOP dynamically, see <a href="#dynamical-classpath">below</a>. If you use hyphenation, you must put <code>fop-hyph.jar</code> in the <code>lib</code> @@ -210,7 +210,7 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl </p> <p>You can also run <code>java -jar path/to/fop.jar - <arguments></code>, relying on the <code>Class-Path</code> + <arguments></code>, relying on the <code>Class-Path</code> entry in the manifest file. This works if you put <code>fop.jar</code> and all jar files from the <code>lib</code> directory in a single directory. If you use hyphenation, you @@ -347,4 +347,4 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <p>If you have problems running FOP, please see the <a href="../gethelp.html">"How to get Help" page</a>.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/0.95/servlets.xml b/src/documentation/content/xdocs/0.95/servlets.xml index 07c22312d..807f19f98 100644 --- a/src/documentation/content/xdocs/0.95/servlets.xml +++ b/src/documentation/content/xdocs/0.95/servlets.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,15 +19,15 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Servlets</title> - <subtitle>How to use Apache FOP in a Servlet</subtitle> + <title>Apache™ FOP: Servlets</title> + <subtitle>How to use Apache� FOP in a Servlet</subtitle> <version>$Revision$</version> </header> <body> <section id="overview"> <title>Overview</title> <p> - 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. </p> </section> <section id="example-servlets"> diff --git a/src/documentation/content/xdocs/0.95/upgrading.xml b/src/documentation/content/xdocs/0.95/upgrading.xml index ca3257aed..3ed062e9c 100644 --- a/src/documentation/content/xdocs/0.95/upgrading.xml +++ b/src/documentation/content/xdocs/0.95/upgrading.xml @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Upgrading from an Earlier Version of Apache FOP</title> + <title>Upgrading from an Earlier Version of Apache™ FOP</title> <version>$Revision$</version> </header> <body> <section id="important"> <title>Important!</title> <p> - If you're planning to upgrade to the latest FOP version there are a few very important things + If you're planning to upgrade to the latest Apache™ FOP version there are a few very important things to consider: </p> <ul> @@ -123,4 +123,4 @@ </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/accessibility.xml b/src/documentation/content/xdocs/1.0/accessibility.xml index f3c66e06a..412519d8b 100644 --- a/src/documentation/content/xdocs/1.0/accessibility.xml +++ b/src/documentation/content/xdocs/1.0/accessibility.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>Accessibility</title> + <title>Apacheâ„¢ FOP: Accessibility</title> </header> <body> <section id="overview"> @@ -27,7 +27,7 @@ <p> This page describes the <a href="http://en.wikipedia.org/wiki/Accessibility">accessibility</a> - features of Apache FOP. + features of Apacheâ„¢ FOP. <a href="http://www.section508.gov/">Section 508</a> defines accessibility in the context of electronic documents for the USA but other countries have similar requirements. </p> @@ -164,4 +164,4 @@ </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/anttask.xml b/src/documentation/content/xdocs/1.0/anttask.xml index a543a5623..ba53fe7d1 100644 --- a/src/documentation/content/xdocs/1.0/anttask.xml +++ b/src/documentation/content/xdocs/1.0/anttask.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,12 +19,12 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Ant task</title> + <title>Apacheâ„¢ FOP: Ant task</title> <version>$Revision$</version> </header> <body> <p> - Apache FOP provides an Ant task for automating the document build process. + Apacheâ„¢ FOP provides an Ant task for automating the document build process. </p> <section id="basics"> <title>Description</title> @@ -233,5 +233,4 @@ ]]></source> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/compiling.xml b/src/documentation/content/xdocs/1.0/compiling.xml index 98a6dfb6d..cf7b950ca 100644 --- a/src/documentation/content/xdocs/1.0/compiling.xml +++ b/src/documentation/content/xdocs/1.0/compiling.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Building from Source Code</title> + <title>Apacheâ„¢ FOP: Building from Source Code</title> <version>$Revision$</version> </header> <body> <section id="build-needed"> <title>Do You Need To Build?</title> <p> - FOP distributions are either pre-compiled binary or source. + Apacheâ„¢ FOP distributions are either pre-compiled binary or source. If you are using a binary distribution, it is already built and there is no need to build it again. See the <a href="../download.html">Download Instructions</a> for information about whether a binary or source distribution is best for your needs. @@ -137,5 +137,4 @@ </ul> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/configuration.xml b/src/documentation/content/xdocs/1.0/configuration.xml index eaa788990..9adf63c46 100644 --- a/src/documentation/content/xdocs/1.0/configuration.xml +++ b/src/documentation/content/xdocs/1.0/configuration.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Configuration</title> + <title>Apacheâ„¢ FOP: Configuration</title> <version>$Revision$</version> </header> @@ -489,5 +489,4 @@ information it finds. Check if FOP finds what you expect.</li> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/embedding.xml b/src/documentation/content/xdocs/1.0/embedding.xml index 3289e68c7..de2c6404c 100644 --- a/src/documentation/content/xdocs/1.0/embedding.xml +++ b/src/documentation/content/xdocs/1.0/embedding.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,8 +20,8 @@ <!-- Embedding FOP --> <document> <header> - <title>Apache FOP: Embedding</title> - <subtitle>How to Embed FOP in a Java application</subtitle> + <title>Apache™ FOP: Embedding</title> + <subtitle>How to Embed Apache� FOP in a Java application</subtitle> <version>$Revision$</version> </header> @@ -33,7 +33,7 @@ to embedded applications as well as command-line use, such as options and performance. </p> <p> - To embed Apache FOP in your application, first create a new + To embed Apache™ FOP in your application, first create a new org.apache.fop.apps.FopFactory instance. This object can be used to launch multiple rendering runs. For each run, create a new org.apache.fop.apps.Fop instance through one of the factory methods of FopFactory. In the method call you specify which output @@ -698,5 +698,4 @@ mailing list. </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/events.xml b/src/documentation/content/xdocs/1.0/events.xml index 017775f03..27daad59b 100644 --- a/src/documentation/content/xdocs/1.0/events.xml +++ b/src/documentation/content/xdocs/1.0/events.xml @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Events/Processing Feedback</title> + <title>Apacheâ„¢ FOP: Events/Processing Feedback</title> <version>$Revision$</version> </header> <body> <section id="introduction"> <title>Introduction</title> <p> - In versions until 0.20.5, FOP used + In versions until 0.20.5, Apacheâ„¢ FOP used <a href="http://excalibur.apache.org/framework/index.html">Avalon-style Logging</a> where it was possible to supply a logger per processing run. During the redesign the logging infrastructure was switched over to @@ -446,4 +446,4 @@ producer.complain(this, "I'm tired", 23);]]></source> </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/extensions.xml b/src/documentation/content/xdocs/1.0/extensions.xml index 107f6c5b3..f8156b9f0 100644 --- a/src/documentation/content/xdocs/1.0/extensions.xml +++ b/src/documentation/content/xdocs/1.0/extensions.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Standard FOP Extensions</title> + <title>Standard Apacheâ„¢ FOP Extensions</title> <version>$Revision$</version> </header> <body> <p> By "extension", we mean any data that can be placed in the input XML document that is not addressed by the XSL-FO standard. - By having a mechanism for supporting extensions, FOP is able to add features that + By having a mechanism for supporting extensions, Apacheâ„¢ FOP is able to add features that are not covered in the specification. </p> <p> @@ -336,5 +336,4 @@ to following pages. Here is an example of FO code creating such a table-header:< </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/fonts.xml b/src/documentation/content/xdocs/1.0/fonts.xml index dcd03e548..b56f4b5e6 100644 --- a/src/documentation/content/xdocs/1.0/fonts.xml +++ b/src/documentation/content/xdocs/1.0/fonts.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Fonts</title> + <title>Apacheâ„¢ FOP: Fonts</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email=""/> @@ -31,7 +31,7 @@ <body> <section id="intro"> <title>Summary</title> - <p>The following table summarizes the font capabilities of the various FOP renderers:</p> + <p>The following table summarizes the font capabilities of the various Apache� FOP renderers:</p> <table> <tr> <th>Renderer</th> @@ -561,4 +561,4 @@ </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/graphics.xml b/src/documentation/content/xdocs/1.0/graphics.xml index 270d6b49b..b1653443a 100644 --- a/src/documentation/content/xdocs/1.0/graphics.xml +++ b/src/documentation/content/xdocs/1.0/graphics.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Graphics Formats</title> + <title>Apacheâ„¢ FOP: Graphics Formats</title> <version>$Revision$</version> </header> <body> @@ -30,7 +30,7 @@ </p> <ul> <li> - The image libraries Jimi and JAI are not supported. Instead, Apache FOP uses the + The image libraries Jimi and JAI are not supported. Instead, Apacheâ„¢ FOP uses the Image I/O API that was introduced with Java 1.4 for all bitmap codecs. </li> <li> @@ -73,65 +73,65 @@ <tr> <td><a href="#bmp">BMP</a> (Microsoft Windows Bitmap)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#emf">EMF</a> (Windows Enhanced Metafile)</td> <td>vector (with embedded bitmaps)</td> <td>(X)</td> - <td></td> - <td></td> + <td/> + <td/> </tr> <tr> <td><a href="#eps">EPS</a> (Encapsulated PostScript)</td> <td>metafile (both bitmap and vector), most frequently used for vector drawings</td> <td>(X)</td> - <td></td> - <td></td> + <td/> + <td/> </tr> <tr> <td>GIF (Graphics Interchange Format)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X</td> </tr> <tr> <td><a href="#jpeg">JPEG</a> (Joint Photographic Experts Group)</td> <td>bitmap</td> <td>(X)</td> - <td></td> + <td/> <td>X</td> </tr> <tr> <td><a href="#png">PNG</a> (Portable Network Graphic)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X</td> </tr> <tr> <td><a href="#svg">SVG</a> (Scalable Vector Graphics)</td> <td>vector (with embedded bitmaps)</td> - <td></td> + <td/> <td>X</td> - <td></td> + <td/> </tr> <tr> <td><a href="#tiff">TIFF</a> (Tag Image Format File)</td> <td>bitmap</td> <td>(X)</td> - <td></td> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#wmf">WMF</a> (Windows Metafile)</td> <td>vector (with embedded bitmaps)</td> - <td></td> + <td/> <td>(X)</td> - <td></td> + <td/> </tr> </table> <p> @@ -149,7 +149,7 @@ <note> <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a>! The - former simply exposes JAI's codecs using the Image I/O API but does not include all + former simply exposes JAI's codecs using the Image&nbsp;I/O API but does not include all the image manipulation functionality. </note> <section id="format-map"> @@ -181,21 +181,21 @@ </tr> <tr> <td><a href="#emf">EMF</a> (Windows Enhanced Metafile)</td> - <td></td> - <td></td> - <td></td> - <td></td> - <td></td> + <td/> + <td/> + <td/> + <td/> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#eps">EPS</a> (Encapsulated PostScript)</td> - <td></td> + <td/> <td>X [1]</td> - <td></td> - <td></td> - <td></td> - <td></td> + <td/> + <td/> + <td/> + <td/> </tr> <tr> <td>GIF (Graphics Interchange Format)</td> @@ -361,7 +361,7 @@ <section id="gif"> <title>GIF</title> <p> - GIF images are supported through an Image I/O codec. Transparency is supported but + GIF images are supported through an Image&nbsp;I/O codec. Transparency is supported but not guaranteed to work with every output format. </p> </section> @@ -376,14 +376,14 @@ through without decompression. User reports indicate that grayscale, RGB, and CMYK color spaces are all rendered properly. However, for other output formats, the JPEG images have to be decompressed. Tests have shown that there are some limitation - in some Image I/O codecs concerning images in the CMYK color space. Work-arounds are + in some Image&nbsp;I/O codecs concerning images in the CMYK color space. Work-arounds are in place but may not always work as expected. </p> </section> <section id="png"> <title>PNG</title> <p> - PNG images are supported through an Image I/O codec. Transparency is supported but + PNG images are supported through an Image&nbsp;I/O codec. Transparency is supported but not guaranteed to work with every output format. </p> </section> @@ -520,7 +520,7 @@ <p> FOP can embed TIFF images without decompression into PDF, PostScript and AFP if they have either CCITT T.4, CCITT T.6, or JPEG compression. Otherwise, a TIFF-capable - Image I/O codec is necessary for decoding the image. + Image&nbsp;I/O codec is necessary for decoding the image. </p> <p> There may be some limitation concerning images in the CMYK color space. @@ -587,4 +587,4 @@ </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/hyphenation.xml b/src/documentation/content/xdocs/1.0/hyphenation.xml index ed97c6868..1d1c63d82 100644 --- a/src/documentation/content/xdocs/1.0/hyphenation.xml +++ b/src/documentation/content/xdocs/1.0/hyphenation.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Hyphenation</title> + <title>Apacheâ„¢ FOP: Hyphenation</title> <version>$Revision$</version> </header> <body> @@ -27,7 +27,7 @@ <title>Hyphenation Support</title> <section id="intro"> <title>Introduction</title> - <p>FOP uses Liang's hyphenation algorithm, well known from TeX. It needs + <p>Apacheâ„¢ FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.</p> <p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through @@ -145,16 +145,16 @@ confirming their accuracy, or raising specific problems that we can address.</warning> <ul> - <li>The root of the pattern file is the <hyphenation-info> element.</li> - <li><hyphen-char>: its attribute "value" contains the character signalling - a hyphen in the <exceptions> section. It has nothing to do with the + <li>The root of the pattern file is the <hyphenation-info> element.</li> + <li><hyphen-char>: its attribute "value" contains the character signalling + a hyphen in the <exceptions> section. It has nothing to do with the hyphenation character used in FOP, use the XSLFO hyphenation-character property for defining the hyphenation character there. At some points a dash U+002D is hardwired in the code, so you'd better use this too (patches to rectify the situation are welcome). There is no default, if you declare exceptions with hyphenations, you must declare the hyphen-char too.</li> - <li><hyphen-min> contains two attributes: + <li><hyphen-min> contains two attributes: <ul> <li>before: the minimum number of characters in a word allowed to exist on a line immediately preceding a hyphenated word-break.</li> @@ -164,23 +164,23 @@ This element is unused and not even read. It should be considered a documentation for parameters used during pattern generation. </li> - <li><classes> contains whitespace-separated character sets. The members + <li><classes> contains whitespace-separated character sets. The members of each set should be treated as equivalent for purposes of hyphenation, usually upper and lower case of the same character. The first character of the set is the canonical character, the patterns and exceptions should only contain these canonical representation characters (except digits for weight, the period (.) as word delimiter in the patterns and the hyphen char in exceptions, of course).</li> - <li><exceptions> contains whitespace-separated words, each of which + <li><exceptions> contains whitespace-separated words, each of which has either explicit hyphen characters to denote acceptable breakage points, or no hyphen characters, to indicate that this word should - never be hyphenated, or contain explicit <hyp> elements for specifying - changes of spelling due to hyphenation (like backen -> bak-ken or - Stoffarbe -> Stoff-farbe in the old german spelling). Exceptions override - the patterns described below. Explicit <hyp> declarations don't work + never be hyphenated, or contain explicit <hyp> elements for specifying + changes of spelling due to hyphenation (like backen -> bak-ken or + Stoffarbe -> Stoff-farbe in the old german spelling). Exceptions override + the patterns described below. Explicit <hyp> declarations don't work yet (patches welcome). Exceptions are generally a bit brittle, test carefully.</li> - <li><patterns> includes whitespace-separated patterns, which are what + <li><patterns> includes whitespace-separated patterns, which are what drive most hyphenation decisions. The characters in these patterns are explained as follows: <ul> @@ -234,4 +234,4 @@ hyphenation.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/index.xml b/src/documentation/content/xdocs/1.0/index.xml index 297914e60..d05299d1e 100644 --- a/src/documentation/content/xdocs/1.0/index.xml +++ b/src/documentation/content/xdocs/1.0/index.xml @@ -26,7 +26,7 @@ <section id="intro"> <title>Introduction</title> <p> - The Apache FOP team is proud to present to you this production + The Apacheâ„¢ FOP team is proud to present to you this production quality codebase. FOP 1.0 provides a good subset of the W3C XSL-FO 1.0 and 1.1 Standards. Its stable, 1.0 designation provides added recognition as the productive tool it has been @@ -64,4 +64,4 @@ </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/intermediate.xml b/src/documentation/content/xdocs/1.0/intermediate.xml index 148e99360..a154ce733 100644 --- a/src/documentation/content/xdocs/1.0/intermediate.xml +++ b/src/documentation/content/xdocs/1.0/intermediate.xml @@ -19,13 +19,13 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Intermediate Format</title> + <title>Apacheâ„¢ FOP: Intermediate Format</title> <version>$Revision$</version> </header> <body> <note> Please note that the intermediate formats described here are - <strong>advanced features</strong> and can be ignored by most users of Apache FOP. + <strong>advanced features</strong> and can be ignored by most users of Apacheâ„¢ FOP. </note> <section id="introduction"> <title>Introduction</title> @@ -328,4 +328,4 @@ try { </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/knownissues_overview.xml b/src/documentation/content/xdocs/1.0/knownissues_overview.xml index 3f96a9b5c..8daa97490 100644 --- a/src/documentation/content/xdocs/1.0/knownissues_overview.xml +++ b/src/documentation/content/xdocs/1.0/knownissues_overview.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document xmlns:xi="http://www.w3.org/2001/XInclude"> <header> - <title>Apache FOP: Known Issues</title> + <title>Apacheâ„¢ FOP: Known Issues</title> <version>$Revision$</version> </header> <body> @@ -30,7 +30,7 @@ </p> <note> <p> - 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: </p> <ul> <li><a href="../bugs.html">the bug list in Bugzilla</a></li> @@ -38,7 +38,7 @@ </ul> </note> <p> - Apache FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several + 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. @@ -66,5 +66,4 @@ </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/metadata.xml b/src/documentation/content/xdocs/1.0/metadata.xml index 8c273fff5..795177583 100644 --- a/src/documentation/content/xdocs/1.0/metadata.xml +++ b/src/documentation/content/xdocs/1.0/metadata.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>Metadata</title> + <title>Apacheâ„¢ FOP: Metadata</title> </header> <body> <section id="overview"> @@ -240,4 +240,4 @@ </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/output.xml b/src/documentation/content/xdocs/1.0/output.xml index 63c84e6b0..65f808ae8 100644 --- a/src/documentation/content/xdocs/1.0/output.xml +++ b/src/documentation/content/xdocs/1.0/output.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <!-- Output Formats: Renderers --> <document> <header> - <title>Apache FOP Output Formats</title> + <title>Apacheâ„¢ FOP Output Formats</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -30,7 +30,7 @@ <body> <p> - FOP supports multiple output formats by using a different renderer for each format. + 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. @@ -974,7 +974,7 @@ Note that the value of the encoding attribute in the example is the double-byte Please refer to the <link href="#afp-resource-level-defaults">Resource Level Defaults</link> above to see what is used if the resource-level attribute is not specified. </p> - <p></p> + <p/> </section> </section> </section> @@ -1262,7 +1262,4 @@ Note that the value of the encoding attribute in the example is the double-byte </section> </body> -</document> - - - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/pdfa.xml b/src/documentation/content/xdocs/1.0/pdfa.xml index db5f56482..0b8399121 100644 --- a/src/documentation/content/xdocs/1.0/pdfa.xml +++ b/src/documentation/content/xdocs/1.0/pdfa.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>PDF/A (ISO 19005)</title> + <title>Apache™ FOP: PDF/A (ISO 19005)</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email="jeremias@apache.org"/> @@ -165,4 +165,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/pdfencryption.xml b/src/documentation/content/xdocs/1.0/pdfencryption.xml index 22d965057..6b27d9857 100644 --- a/src/documentation/content/xdocs/1.0/pdfencryption.xml +++ b/src/documentation/content/xdocs/1.0/pdfencryption.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>PDF encryption.</title> + <title>Apacheâ„¢ FOP: PDF encryption.</title> <version>$Revision$</version> <authors> <person name="J.Pietschmann" email="pietsch@apache.org"/> @@ -30,7 +30,7 @@ <section> <title>Overview</title> <p> - FOP supports encryption of PDF output, thanks to Patrick + 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 @@ -225,4 +225,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/pdfx.xml b/src/documentation/content/xdocs/1.0/pdfx.xml index cf796c74d..8eced022c 100644 --- a/src/documentation/content/xdocs/1.0/pdfx.xml +++ b/src/documentation/content/xdocs/1.0/pdfx.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Copyright 2006 The Apache Software Foundation @@ -18,7 +18,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>PDF/X (ISO 15930)</title> + <title>Apache™ FOP: PDF/X (ISO 15930)</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email="jeremias@apache.org"/> @@ -28,8 +28,8 @@ <section id="overview"> <title>Overview</title> <warning> - Support for PDF/X is available beginning with 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. </warning> <p> PDF/X is a standard which faciliates prepress digital data exchange using PDF. @@ -133,4 +133,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/running.xml b/src/documentation/content/xdocs/1.0/running.xml index 757e7aaa4..aa0b9f9fc 100644 --- a/src/documentation/content/xdocs/1.0/running.xml +++ b/src/documentation/content/xdocs/1.0/running.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Running Apache FOP</title> + <title>Running Apacheâ„¢ FOP</title> <version>$Revision$</version> </header> @@ -32,13 +32,13 @@ Java 1.4.x or later Runtime Environment. <ul> <li> - Many JREs >=1.4 contain older JAXP implementations (which often contain bugs). It's + Many JREs >=1.4 contain older JAXP implementations (which often contain bugs). It's usually a good idea to replace them with a current implementation. </li> </ul> </li> <li> - Apache FOP. The <a href="../download.html">FOP distribution</a> includes all libraries that you will + Apacheâ„¢ FOP. The <a href="../download.html">FOP distribution</a> 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: <ul> @@ -202,8 +202,8 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <title>Writing your own script</title> <p>FOP's entry point for your own scripts is the class <code>org.apache.fop.cli.Main</code>. The general pattern for the - command line is: <code>java -classpath <CLASSPATH> - org.apache.fop.cli.Main <arguments></code>. The arguments + command line is: <code>java -classpath <CLASSPATH> + org.apache.fop.cli.Main <arguments></code>. The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that @@ -214,7 +214,7 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <title>Running with java's <code>-jar</code> option</title> <p> As an alternative to the start scripts you can run <code>java - -jar path/to/build/fop.jar <arguments></code>, relying on + -jar path/to/build/fop.jar <arguments></code>, relying on FOP to build the classpath for running FOP dynamically, see <a href="#dynamical-classpath">below</a>. If you use hyphenation, you must put <code>fop-hyph.jar</code> in the <code>lib</code> @@ -222,7 +222,7 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl </p> <p>You can also run <code>java -jar path/to/fop.jar - <arguments></code>, relying on the <code>Class-Path</code> + <arguments></code>, relying on the <code>Class-Path</code> entry in the manifest file. This works if you put <code>fop.jar</code> and all jar files from the <code>lib</code> directory in a single directory. If you use hyphenation, you @@ -359,4 +359,4 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <p>If you have problems running FOP, please see the <a href="../gethelp.html">"How to get Help" page</a>.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/1.0/servlets.xml b/src/documentation/content/xdocs/1.0/servlets.xml index 07c22312d..dd2df4351 100644 --- a/src/documentation/content/xdocs/1.0/servlets.xml +++ b/src/documentation/content/xdocs/1.0/servlets.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,15 +19,15 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Servlets</title> - <subtitle>How to use Apache FOP in a Servlet</subtitle> + <title>Apacheâ„¢ FOP: Servlets</title> + <subtitle>How to use Apacheâ„¢ FOP in a Servlet</subtitle> <version>$Revision$</version> </header> <body> <section id="overview"> <title>Overview</title> <p> - 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. </p> </section> <section id="example-servlets"> diff --git a/src/documentation/content/xdocs/1.0/upgrading.xml b/src/documentation/content/xdocs/1.0/upgrading.xml index 9f5879174..a4092c758 100644 --- a/src/documentation/content/xdocs/1.0/upgrading.xml +++ b/src/documentation/content/xdocs/1.0/upgrading.xml @@ -19,15 +19,15 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Upgrading from an Earlier Version of Apache FOP</title> + <title>Upgrading from an Earlier Version of Apacheâ„¢ FOP</title> <version>$Revision$</version> </header> <body> <section id="important"> <title>Important!</title> <p> - If you're planning to upgrade to the latest 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: </p> <ul> <li> @@ -125,4 +125,4 @@ </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/bugs.xml b/src/documentation/content/xdocs/bugs.xml index 4913a7cc6..e2f36d50d 100644 --- a/src/documentation/content/xdocs/bugs.xml +++ b/src/documentation/content/xdocs/bugs.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP: Bugs and Other Trackable Issues</title> + <title>Apacheâ„¢ FOP: Bugs and Other Trackable Issues</title> <version>$Revision$</version> </header> <body> @@ -64,3 +64,6 @@ sent to the FOP developer discussion list.</li> </section> </body> </document> + + + diff --git a/src/documentation/content/xdocs/compliance.ihtml b/src/documentation/content/xdocs/compliance.ihtml index 54a1b9955..ddbbc83cf 100644 --- a/src/documentation/content/xdocs/compliance.ihtml +++ b/src/documentation/content/xdocs/compliance.ihtml @@ -19,13 +19,13 @@ <html> <head> - <title>Apache FOP Compliance Page</title> + <title>Apache™ FOP Compliance Page</title> </head> <body> <h1>W3C XSL-FO 1.1 Standard</h1> - <p>One of FOP's design goals is conformance to the <a href= + <p>One of Apache™ FOP's design goals is conformance to the <a href= "http://www.w3.org/TR/xsl/">W3C XSL-FO 1.1 standard</a>, which specifies three levels of "conformance": basic, extended, and complete. Although FOP does not currently conform to any of these levels, it is nevertheless a useful work-in-progress for many applications. The diff --git a/src/documentation/content/xdocs/dev/conventions.xml b/src/documentation/content/xdocs/dev/conventions.xml index 4fd949fdd..e0771a928 100644 --- a/src/documentation/content/xdocs/dev/conventions.xml +++ b/src/documentation/content/xdocs/dev/conventions.xml @@ -19,11 +19,11 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Development: Coding Conventions</title> + <title>Apacheâ„¢ FOP Development: Coding Conventions</title> <version>$Revision$</version> </header> <body> - <p>Acknowledgement: Some content in this guide was adapted from other Apache projects such as Avalon, Cactus, Turbine and Velocity.</p> + <p>Acknowledgement: Some content in this guide was adapted from other Apacheâ„¢ projects such as Avalon, Cactus, Turbine and Velocity.</p> <section id="svn"> <title>Subversion Repository</title> <p>Conventions in this section apply to Repository content, regardless of type:</p> @@ -184,4 +184,4 @@ Printing error messages to System.err or System.out is useless in a server-side </table> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/areas.xml b/src/documentation/content/xdocs/dev/design/areas.xml index 5b6038832..6548179de 100644 --- a/src/documentation/content/xdocs/dev/design/areas.xml +++ b/src/documentation/content/xdocs/dev/design/areas.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Design: Area Tree</title> + <title>Apacheâ„¢ FOP Design: Area Tree</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -188,4 +188,4 @@ This is useful for setting the title and organising the groups of page sequences </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/breakpos.xml b/src/documentation/content/xdocs/dev/design/breakpos.xml index 67808ee1b..bf426bbd3 100644 --- a/src/documentation/content/xdocs/dev/design/breakpos.xml +++ b/src/documentation/content/xdocs/dev/design/breakpos.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Design: Layout Managers</title> + <title>Apacheâ„¢ FOP Design: Layout Managers</title> <subtitle>Break Possibility Proposal</subtitle> <version>$Revision$</version> <authors> @@ -149,7 +149,7 @@ return potential break points.</p> examined later.</note> <p>So the Line LM will ask its child LM(s) for break possibilities until it gets back a BP whose stacking dimension <em>could</em> fill the -line. This means that the BP.stackdim.max >= LineIPD.min. It can look +line. This means that the BP.stackdim.max >= LineIPD.min. It can look for further BP, perhaps one whose stackdim.opt is closer to the LineIPD.opt. If it isn't happy with the choice of break possibilities, it can go past the end of the line to the next one, and then try to @@ -312,5 +312,4 @@ laying out all its material and then make all the Lines at once.</p> </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/configuration.xml b/src/documentation/content/xdocs/dev/design/configuration.xml index 10fe17ca1..64ba74813 100644 --- a/src/documentation/content/xdocs/dev/design/configuration.xml +++ b/src/documentation/content/xdocs/dev/design/configuration.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -17,15 +17,15 @@ --> <!-- $Id$ --> <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd" [ -<!ENTITY lsquo "‘"> -<!ENTITY rsquo "’"> -<!ENTITY ldquo "“"> -<!ENTITY rdquo "”"> +<!ENTITY lsquo "�"> +<!ENTITY rsquo "�"> +<!ENTITY ldquo "�"> +<!ENTITY rdquo "�"> ]> <document> <header> - <title>FOP: Configuration and Logging</title> + <title>Apacheâ„¢ FOP: Configuration and Logging</title> <version>$Revision$</version> </header> @@ -33,7 +33,7 @@ <section id="general"> <title>Configuration File Basics</title> - <p>The FOP configuration file is an XML file containing a + <p>The Apacheâ„¢ FOP configuration file is an XML file containing a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use.</p> @@ -56,7 +56,7 @@ to find it.</p> <section id="command-line"> <title>From the Command Line</title> <p>When you run FOP from the command-line, use the -“<code>-c</code>” command-line option with the path to the +&ldquo;<code>-c</code>&rdquo; command-line option with the path to the configuration file as the option value.</p> </section> @@ -100,7 +100,7 @@ configuration object with the user agent as described above.</p> <title>The Configuration File</title> <p>The top-level element is arbitrary. You may give it any name that is useful for you, e.g. <code><fop-configuration -version="2"></code>.</p> +version="2"></code>.</p> <p>Inside the top-level element the configuration may contain three sections: <code>userAgent</code>, <code>renderers</code>, and <code>hyphenation</code>. At the moment of this writing the @@ -110,7 +110,7 @@ not used by FOP.</p> <code>renderer</code>. There may be one subsection for each type of renderer. The renderers are identified by their MIME type, which is given in the <code>mime</code> attribute. For example: -<code><renderer mime="application/pdf"></code>. The content +<code><renderer mime="application/pdf"></code>. The content of each <code>renderer</code> subsection depends on the type of renderer.</p> <p>The PDF renderer (MIME type <code>application/pdf</code>) has @@ -163,8 +163,7 @@ more information on creating and modifying hyphenation within FOP.</p> <p>Font configuration information is included in the FOP configuration file as describe above. It is documented in more detail at <link href="../fonts.html">FOP: Fonts</link>. Note -especially the section entitled <link -href="../fonts.html#register">Register Fonts with FOP</link>.</p> +especially the section entitled <link href="../fonts.html#register">Register Fonts with FOP</link>.</p> </section> <section id="logging"> @@ -182,7 +181,7 @@ to use. For example:</p> systems. On Java 1.4 systems JDK 1.4 is the default.</code></p> <p>Secondly, you configure the selected logging package. How this is done depends on the logging package. The most important -feature is the log level. The default is level “info”. An +feature is the log level. The default is level &ldquo;info&rdquo;. An example configuration file for SimpleLog is:</p> <source> # logging level for all loggers, default info @@ -193,7 +192,7 @@ org.apache.commons.logging.simplelog.log.xxxxx=debug org.apache.commons.logging.simplelog.log.org.apache.fop.pdf=trace </source> <p>FOP uses several named loggers. When you set the logging level -for all loggers to “info”, you get a decent small amount +for all loggers to &ldquo;info&rdquo;, you get a decent small amount of information about application progress. The debugging and especially the trace levels produce a lot of output. If you need these logging levels, @@ -203,5 +202,4 @@ bear the name of their package, their class or of a superclass.</p> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/embedding.xml b/src/documentation/content/xdocs/dev/design/embedding.xml index ab4bcf282..075e4b152 100644 --- a/src/documentation/content/xdocs/dev/design/embedding.xml +++ b/src/documentation/content/xdocs/dev/design/embedding.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Design: Embedding FOP in Other Applications</title> + <title>Apache™ FOP Design: Embedding Apache� FOP in Other Applications</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -31,7 +31,7 @@ <section id="intro"> <title>Introduction</title> <p> -This is the design for the external interface when FOP is to be embedded +This is the design for the external interface when Apache™ FOP is to be embedded inside another java application. </p> <p> @@ -146,5 +146,4 @@ remove redundancies. </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/extending.xml b/src/documentation/content/xdocs/dev/design/extending.xml index db242acf2..f383ee186 100644 --- a/src/documentation/content/xdocs/dev/design/extending.xml +++ b/src/documentation/content/xdocs/dev/design/extending.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Design: Extensions</title> + <title>Apacheâ„¢ FOP Design: Extensions</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -31,7 +31,7 @@ <section id="intro"> <title>Introduction</title> <p> -FOP provides an extension mechanism to add extra functionality. There +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. </p> @@ -124,7 +124,7 @@ to result in a text box referencing the following PDF action:</p> <title>Work In Progress</title> <ul> <li>mathml extension</li> - <li>another xml -> svg extension</li> + <li>another xml -> svg extension</li> <li>svg text normal text if that can be handled otherwise stroked this is done automatically</li> </ul> </section> @@ -137,5 +137,4 @@ to result in a text box referencing the following PDF action:</p> </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/fotree.xml b/src/documentation/content/xdocs/dev/design/fotree.xml index c379866ae..03f98d830 100644 --- a/src/documentation/content/xdocs/dev/design/fotree.xml +++ b/src/documentation/content/xdocs/dev/design/fotree.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Design: FO Tree</title> + <title>Apacheâ„¢ FOP Design: FO Tree</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -140,4 +140,4 @@ The Unknown object is mainly used to provide information to the user.</p> </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/images.xml b/src/documentation/content/xdocs/dev/design/images.xml index e2aebcb94..ee6b3dc6f 100644 --- a/src/documentation/content/xdocs/dev/design/images.xml +++ b/src/documentation/content/xdocs/dev/design/images.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Design: Images</title> + <title>Apacheâ„¢ FOP Design: Images</title> <version>$Revision$</version> </header> <body> @@ -35,7 +35,7 @@ keep a list of invalid image urls.</p> <p>We have a number of different caching schemes that are possible.</p> <p>All images are referred to using the url given in the XSL:FO after removing "url('')" wrapping. This does -not include any sort of resolving such as relative -> absolute. The +not include any sort of resolving such as relative -> absolute. The external graphic in the FO Tree and the image area in the Area Tree only have the url as a reference. The images are handled through a static interface in ImageFactory.</p> @@ -148,5 +148,4 @@ renderer and the image can be released from the image cache.</p> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/index.xml b/src/documentation/content/xdocs/dev/design/index.xml index 4a6a41770..2ea9ee201 100644 --- a/src/documentation/content/xdocs/dev/design/index.xml +++ b/src/documentation/content/xdocs/dev/design/index.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Design: Introduction</title> + <title>Apache™ FOP Design: Introduction</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -31,9 +31,9 @@ The redesign is mainly focusing on parts of the layout process (converting the F 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.</note> <section id="black-box"> <title>The Black Box View</title> - <p>From a user's standpoint, FOP is a black box that an xml file as input, performs some magic, then creates the desired output:</p> + <p>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:</p> <table> - <caption>FOP from a User's Standpoint</caption> + <caption>Apache� FOP from a User's Standpoint</caption> <tr> <th>Process</th> <th>Result</th> @@ -157,4 +157,4 @@ However, most of them have been discussed at length among the developers, and ar </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/layout.xml b/src/documentation/content/xdocs/dev/design/layout.xml index 86686c485..394fa4763 100644 --- a/src/documentation/content/xdocs/dev/design/layout.xml +++ b/src/documentation/content/xdocs/dev/design/layout.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Design: Layout</title> + <title>Apacheâ„¢ FOP Design: Layout</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -404,4 +404,4 @@ Dashed and dotted borders have been implemented in PDF</td> </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/optimise.xml b/src/documentation/content/xdocs/dev/design/optimise.xml index a5f3004ec..9b23e931d 100644 --- a/src/documentation/content/xdocs/dev/design/optimise.xml +++ b/src/documentation/content/xdocs/dev/design/optimise.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Design: Optimisations</title> + <title>Apacheâ„¢ FOP Design: Optimisations</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -31,7 +31,7 @@ <section id="intro"> <title>Introduction</title> <p> -FOP should be able to handle very large documents. A document can be +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. </p> @@ -71,5 +71,4 @@ is to make the page and all children serializable. </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/parsing.xml b/src/documentation/content/xdocs/dev/design/parsing.xml index f218eb887..f3b4a383c 100644 --- a/src/documentation/content/xdocs/dev/design/parsing.xml +++ b/src/documentation/content/xdocs/dev/design/parsing.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,13 +19,13 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Design: Input Parsing</title> + <title>Apacheâ„¢ FOP Design: Input Parsing</title> <version>$Revision$</version> </header> <body> <section id="intro"> <title>Introduction</title> - <p>Parsing is the process of reading the XSL-FO input and making the information in it available to FOP.</p> + <p>Parsing is the process of reading the XSL-FO input and making the information in it available to Apacheâ„¢ FOP.</p> </section> <section id="input"> <title>SAX for Input</title> @@ -73,4 +73,4 @@ Instead, FOP takes SAX events and builds its own tree-like structure. Why?</p> </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/pdf-library.xml b/src/documentation/content/xdocs/dev/design/pdf-library.xml index 88a14a9eb..f6562cc83 100644 --- a/src/documentation/content/xdocs/dev/design/pdf-library.xml +++ b/src/documentation/content/xdocs/dev/design/pdf-library.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Design: PDF Library</title> + <title>Apacheâ„¢ FOP Design: PDF Library</title> <version>$Revision$</version> </header> @@ -28,7 +28,7 @@ <section id="intro"> <title>Introduction</title> -<p>The PDF Library is an independant package of classes in FOP. These class +<p>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 <code>org.apache.fop.pdf.*</code>.</p> </section> @@ -88,5 +88,4 @@ The method is: byte[] toPDF().</p> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/properties.xml b/src/documentation/content/xdocs/dev/design/properties.xml index 879f287b0..769ab608a 100644 --- a/src/documentation/content/xdocs/dev/design/properties.xml +++ b/src/documentation/content/xdocs/dev/design/properties.xml @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Design: Properties</title> + <title>Apache™ FOP Design: Properties</title> <version>$Revision$</version> <authors> <person name="Karen Lease" email=""/> @@ -205,12 +205,12 @@ for all ColorType properties. Since the generic specification doesn't include the inherited or default elements, these should be set in each property which is based on GenericColor. Here is an example:</p> <p> - <code><property type='generic'> - <name>background-color</name> - <use-generic>GenericColor</use-generic> - <inherited>false</inherited> - <default>transparent</default> - </property></code> + <code><property type='generic'> + <name>background-color</name> + <use-generic>GenericColor</use-generic> + <inherited>false</inherited> + <default>transparent</default> + </property></code> </p> <p>A generic property specification can include all of the elements defined for the property element in the DTD, including the description @@ -377,4 +377,4 @@ the result is a Property object, and the actual value may be accessed <p>The Refined FO Tree is the result of the Refinement process.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/renderers.xml b/src/documentation/content/xdocs/dev/design/renderers.xml index e1cf8a532..2e21db864 100644 --- a/src/documentation/content/xdocs/dev/design/renderers.xml +++ b/src/documentation/content/xdocs/dev/design/renderers.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Design: Renderers</title> + <title>Apacheâ„¢ FOP Design: Renderers</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -226,4 +226,4 @@ If two renderers have the same font metrics then it is possible to use the same </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/startup.xml b/src/documentation/content/xdocs/dev/design/startup.xml index 9281af08b..db1742135 100644 --- a/src/documentation/content/xdocs/dev/design/startup.xml +++ b/src/documentation/content/xdocs/dev/design/startup.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,13 +19,13 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Design: Startup, Environment, Control</title> + <title>Apacheâ„¢ FOP Design: Startup, Environment, Control</title> <version>$Revision$</version> </header> <body> <section id="intro"> <title>Introduction</title> - <p>Startup is the process of getting 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.</p> + <p>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.</p> </section> <section id="status"> <title>Status</title> @@ -53,4 +53,4 @@ </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/svg.xml b/src/documentation/content/xdocs/dev/design/svg.xml index f5ea6e8ae..1d4f72d04 100644 --- a/src/documentation/content/xdocs/dev/design/svg.xml +++ b/src/documentation/content/xdocs/dev/design/svg.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,16 +20,17 @@ <document> <header> - <title>FOP Design: SVG</title> + <title>Apacheâ„¢ FOP Design: SVG</title> <version>$Revision$</version> </header> <body> <section id="intro"> <title>Introduction</title> - <p>SVG is rendered through Batik.</p><p>The XML from the XSL:FO document + <p>SVG is rendered through Apacheâ„¢ Batik.</p><p>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.</p><p>This DOM is then available to - be rendered by the renderer.</p><p>SVG is rendered in the renderers via an XMLHandler in the FOUserAgent. This XML handler is used to render the SVG. The + be rendered by the renderer.</p><p>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.</p><p>This creates the necessary PDF information to @@ -86,5 +87,4 @@ </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/design/useragent.xml b/src/documentation/content/xdocs/dev/design/useragent.xml index 36032a519..5ee7f29e2 100644 --- a/src/documentation/content/xdocs/dev/design/useragent.xml +++ b/src/documentation/content/xdocs/dev/design/useragent.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Design: User Agent</title> + <title>Apacheâ„¢ FOP Design: User Agent</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -31,7 +31,7 @@ <section id="intro"> <title>Introduction</title> <p> -Technically the user agent is FOP in the role of determining the +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. @@ -111,5 +111,4 @@ Interactive Features: </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/doc.xml b/src/documentation/content/xdocs/dev/doc.xml index c75994ec1..fe9e656ed 100644 --- a/src/documentation/content/xdocs/dev/doc.xml +++ b/src/documentation/content/xdocs/dev/doc.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,13 +19,13 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Development: Managing Documentation</title> + <title>Apacheâ„¢ FOP Development: Managing Documentation</title> <version>$Revision$</version> </header> <body> <section id="general"> <title>General Information</title> - <p>All raw documentation content is managed in the FOP SVN repository. + <p>All raw documentation content is managed in the Apacheâ„¢ FOP SVN repository. Updates should be committed to the repository, then the repository files are used to generate usable output. The remaining discussions on this page assume that the SVN repository is the starting place for processing. The path to the documentation is src/documentation/content/xdocs.</p> @@ -163,4 +163,4 @@ The path to the documentation is src/documentation/content/xdocs.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/extensions.xml b/src/documentation/content/xdocs/dev/extensions.xml index 769a663af..3a5f499d5 100644 --- a/src/documentation/content/xdocs/dev/extensions.xml +++ b/src/documentation/content/xdocs/dev/extensions.xml @@ -20,13 +20,13 @@ <document> <header> - <title>FOP Development: Adding an Extension</title> + <title>Apacheâ„¢ FOP Development: Adding an Extension</title> <version>$Revision$</version> </header> <body> <section id="overview"> <title>Overview</title> - <p>For documentation of standard FOP extensions, see the <link href="../trunk/extensions.html">User FOP Extensions</link> document.</p> + <p>For documentation of standard Apacheâ„¢ FOP extensions, see the <link href="../trunk/extensions.html">User FOP Extensions</link> document.</p> <p> If the default funtionality of FOP needs to be extended for some reason then you can write an extension. @@ -61,5 +61,4 @@ See also <link href="../examples.html">Examples</link> for more examples.</li> </ol> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/faq.xml b/src/documentation/content/xdocs/dev/faq.xml index 6d534ae7c..ae15eaabd 100644 --- a/src/documentation/content/xdocs/dev/faq.xml +++ b/src/documentation/content/xdocs/dev/faq.xml @@ -18,7 +18,7 @@ <!-- $Id$ --> <!DOCTYPE faqs PUBLIC "-//APACHE//DTD FAQ V1.3//EN" "http://forrest.apache.org/dtd/faq-v13.dtd"> -<faqs title="FOP Development: FAQ"> +<faqs title="Apache™ FOP Development: FAQ"> <part id="part_general"> <title>General Questions</title> <faq> @@ -62,5 +62,4 @@ </answer> </faq> </part> -</faqs> - +</faqs>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/fonts.xml b/src/documentation/content/xdocs/dev/fonts.xml index 095830197..9d2f63905 100644 --- a/src/documentation/content/xdocs/dev/fonts.xml +++ b/src/documentation/content/xdocs/dev/fonts.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Development: Fonts</title> + <title>Apache™ FOP Development: Fonts</title> <version>$Revision$</version> </header> <body> @@ -29,7 +29,7 @@ <ul> <li>refactor existing font logic for better clarity and to reduce duplication</li> <li>parse registered font metric information on-the-fly (to make sure most up-to-date parsing is used??)</li> - <li>resolve whether the FontBBox, StemV, and ItalicAngle font metric information is important or not -- if so, parse the .pfb file to extract it when building the FOP xml metric file</li> + <li>resolve whether the FontBBox, StemV, and ItalicAngle font metric information is important or not -- if so, parse the .pfb file to extract it when building the Apache� FOP xml metric file</li> <li>handle fonts registered at the operating system (through AWT)</li> <li>add support for parsing OpenType fonts</li> </ul> @@ -87,4 +87,4 @@ If not, the Font logic should resolve the TypeFace and TypeFaceFamily if possibl </body> </document> -<!-- Last Line of $RCSfile$ --> +<!-- Last Line of $RCSfile$ -->
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/implement.xml b/src/documentation/content/xdocs/dev/implement.xml index 8ed1ccbe0..6f8a4a05c 100644 --- a/src/documentation/content/xdocs/dev/implement.xml +++ b/src/documentation/content/xdocs/dev/implement.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,15 +19,15 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Development: Implementation Overview</title> - <subtitle>Following a Document Through FOP</subtitle> + <title>Apache™ FOP Development: Implementation Overview</title> + <subtitle>Following a Document Through Apache� FOP</subtitle> <version>$Revision$</version> <authors> <person name="Arved Sandstrom" email=""/> </authors> </header> <body> - <p>The purpose of this document is to tie together the 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> + <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> <section> <title>Overview</title> <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> @@ -107,4 +107,4 @@ correct place. </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/index.xml b/src/documentation/content/xdocs/dev/index.xml index f6b62aba3..357402026 100644 --- a/src/documentation/content/xdocs/dev/index.xml +++ b/src/documentation/content/xdocs/dev/index.xml @@ -25,9 +25,9 @@ <body> <section id="intro"> <title>Introduction</title> - <p>These pages contain information that should be helpful for those developing FOP. + <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 <link href="http://xml.apache.org/fop">FOP homepage</link>.</p> + <p>For basic and user information on FOP, please visit the <link href="http://xml.apache.org/fop">Apacheâ„¢ FOP homepage</link>.</p> </section> <section id="lines"> <title>Development</title> @@ -162,4 +162,4 @@ To unsubscribe: Send email to <link href="mailto:fop-dev-unsubscribe@xmlgraphics </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/release.xml b/src/documentation/content/xdocs/dev/release.xml index da614bee0..19e6eac2c 100644 --- a/src/documentation/content/xdocs/dev/release.xml +++ b/src/documentation/content/xdocs/dev/release.xml @@ -19,13 +19,13 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Development: Release Mechanics</title> + <title>Apacheâ„¢ FOP Development: Release Mechanics</title> <version>$Revision$</version> </header> <body> <section id="intro"> <title>Introduction</title> - <p>This page documents the process of creating a FOP release. + <p>This page documents the process of creating a Apacheâ„¢ FOP release. FOP releases are coordinated by one member of the team (currently Christian Geisert), so others do not ordinarily need to use this information. 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 was assembled from Christian Geisert's notes. It will be expanded in the future as he has time.</p> @@ -60,8 +60,8 @@ The purpose of documenting it here is to facilitate consistency, ensure that the <li>Copy <code>test/fotree/disabled-testcases.xml</code> and <code>test/layoutengine/disabled-testcases.xml</code> to the new version directory - <code><version>/fotree/disabled-testcases.xml</code> and - <code><version>/layoutengine/disabled-testcases.xml</code>. + <code><version>/fotree/disabled-testcases.xml</code> and + <code><version>/layoutengine/disabled-testcases.xml</code>. Copy <code>known-issues.xml</code> to the new version directory. Copy <code>knownissues-overview.xml</code> from the current to the new version directory, and update the <code>xi:include</code> @@ -156,4 +156,4 @@ The purpose of documenting it here is to facilitate consistency, ensure that the </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/rtflib.xml b/src/documentation/content/xdocs/dev/rtflib.xml index ffc8c8c56..c61f486bf 100644 --- a/src/documentation/content/xdocs/dev/rtflib.xml +++ b/src/documentation/content/xdocs/dev/rtflib.xml @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Development: RTFLib (jfor)</title> + <title>Apacheâ„¢ FOP Development: RTFLib (jfor)</title> <version>$Revision$</version> </header> <body> @@ -30,7 +30,7 @@ <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>Although it is used by FOP to generate FOP's RTF output, it is not dependent on FOP for any of its functionality.</li> + <li>Although it is used by Apacheâ„¢ FOP to generate FOP's RTF output, it is not dependent on FOP for any of its functionality.</li> <li>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.</li> @@ -39,7 +39,7 @@ This means it can be used anywhere RTF output is required and java is available. </section> <section id="history"> <title>History</title> - <p>RTFLib was originally developed by <link href="mailto:bdelacretaz@apache.org">Bertrand Delacrétaz</link> and the <link href="http://www.jfor.org">jfor</link> 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> + <p>RTFLib was originally developed by <link href="mailto:bdelacretaz@apache.org">Bertrand Delacrétaz</link> and the <link href="http://www.jfor.org">jfor</link> 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> </section> <section id="status"> <title>Status</title> @@ -324,4 +324,4 @@ A quick look at the Abstract <link href="http://cvs.apache.org/viewcvs.cgi/xml-f </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/svg.xml b/src/documentation/content/xdocs/dev/svg.xml index 3ac8029f0..b76626c5e 100644 --- a/src/documentation/content/xdocs/dev/svg.xml +++ b/src/documentation/content/xdocs/dev/svg.xml @@ -20,7 +20,7 @@ <document> <header> - <title>FOP Development: SVG Issues</title> + <title>Apacheâ„¢ FOP Development: SVG Issues</title> <version>$Revision$</version> </header> <body> @@ -34,7 +34,7 @@ to PDF: <table> <caption>SVG to PDF examples</caption> <tr> - <th></th> + <th/> <th>svg file</th> <th>png file</th> <th>pdf result</th> @@ -79,7 +79,7 @@ You will need Acrobat 5.0 to see transparency. <table> <caption>XSL:FO to PDF examples</caption> <tr> - <th></th> + <th/> <th>fo file</th> <th>pdf result</th> </tr> @@ -133,5 +133,4 @@ This svg font could be converted into a pdf stroked font </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/testing.xml b/src/documentation/content/xdocs/dev/testing.xml index 92589d589..1b962530c 100644 --- a/src/documentation/content/xdocs/dev/testing.xml +++ b/src/documentation/content/xdocs/dev/testing.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Development: Testing</title> + <title>Apache™ FOP Development: Testing</title> <version>$Revision$</version> </header> <body> <section id="build"> <title>"Build" Testing</title> - <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> + <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><link href="http://gump.cocoondev.org/xml-fop.html">Gump build for the Trunk</link></li> <li><link href="http://gump.cocoondev.org/xml-fop-maintenance.html">Gump build for the Maintenance Branch</link></li> @@ -43,7 +43,7 @@ The tests do not check the output, but only ensure that something is generated a <title>Layout Engine Testing</title> <p> The <link href="http://svn.apache.org/viewcvs.cgi/xmlgraphics/fop/trunk/test/layoutengine/"><code>test/layoutengine</code></link> - directory in the repository contains a test suite for checking the functionality of FOP's + 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 <link href="http://wiki.apache.org/xmlgraphics-fop/HowToCreateLayoutEngineTests">Wiki page</link>. </p> @@ -64,7 +64,7 @@ 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 +"<cvs_repository>/test/reference/" directory. This jar will be dynamically loaded to create the reference output. </p> </section> @@ -114,7 +114,7 @@ test works as would be expected against the current build. <section> <title>How Testing Works</title> <p> -The tests are stored in the "<svn_repository>/test" directory. +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/> @@ -150,5 +150,4 @@ testing is how the SVG image is embedded inside the flow of the fo document. </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/dev/tools.xml b/src/documentation/content/xdocs/dev/tools.xml index 1d0675a10..6f00fd6d6 100644 --- a/src/documentation/content/xdocs/dev/tools.xml +++ b/src/documentation/content/xdocs/dev/tools.xml @@ -19,13 +19,13 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP Development: Developer Tools</title> + <title>Apacheâ„¢ FOP Development: Developer Tools</title> <version>$Revision$</version> </header> <body> <p> This page documents items that may be helpful to other developers, - especially to those who are new to FOP. Exhaustive treatment of these + 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. @@ -129,4 +129,4 @@ Note that this manual applies to the command-line version of SVN.</li> <p>Additional notes on setting up FOP within an IDE (ex. Eclipse) in the <fork href="http://wiki.apache.org/xmlgraphics-fop/FOPIDESetupGuide">Wiki</fork>.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/download.xml b/src/documentation/content/xdocs/download.xml index 9d7988e61..ab379fe44 100644 --- a/src/documentation/content/xdocs/download.xml +++ b/src/documentation/content/xdocs/download.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>Apache FOP: Downloading A Distribution</title> + <title>Apacheâ„¢ FOP: Downloading A Distribution</title> <version>$Revision$</version> </header> <body> <section id="dist-type"> <title>Binary or Source?</title> <p> - Most FOP users will want to download the latest binary distribution, + 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> @@ -175,4 +175,4 @@ </section> </body> </document> -<!-- Last Line of $RCSfile$ --> +<!-- Last Line of $RCSfile$ -->
\ No newline at end of file diff --git a/src/documentation/content/xdocs/examples.xml b/src/documentation/content/xdocs/examples.xml index 5df3c5804..f64a0d702 100644 --- a/src/documentation/content/xdocs/examples.xml +++ b/src/documentation/content/xdocs/examples.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,14 +20,14 @@ <document> <header> - <title>Examples</title> + <title>Apacheâ„¢ FOP Examples</title> <version>$Revision$</version> </header> <body> <section> - <title>Example Documents Using FOP</title> + <title>Example Documents Using Apacheâ„¢ FOP</title> <p> - These examples have been rendered using FOP: + These examples have been rendered using Apacheâ„¢ FOP: </p> <table> <caption>Generated examples</caption> diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml index 2fd6e16ca..c4ddc6054 100644 --- a/src/documentation/content/xdocs/faq.xml +++ b/src/documentation/content/xdocs/faq.xml @@ -20,9 +20,9 @@ <faqs title="FOP FAQ"> <part id="part-general"> - <title>General questions</title> + <title>Apacheâ„¢ FOP: General questions</title> <faq id="fop-general"> - <question>What is FOP?</question> + <question>What is Apacheâ„¢ FOP?</question> <answer> <p> FOP is a print formatter for <link href="#XSLFO">XSL formatting diff --git a/src/documentation/content/xdocs/fo.xml b/src/documentation/content/xdocs/fo.xml index 6546478c9..ba2402cfe 100644 --- a/src/documentation/content/xdocs/fo.xml +++ b/src/documentation/content/xdocs/fo.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <document> <header> - <title>XSL-FO Input</title> + <title>Apacheâ„¢ FOP: XSL-FO Input</title> <subtitle>Basic Help for Using XML, XSLT, and XSL-FO</subtitle> <version>$Revision$</version> </header> @@ -28,7 +28,7 @@ <section id="overview"> <title>Overview</title> <p> - FOP uses XSL-FO as input. + 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 is <fork href="http://www.dpawson.co.uk/xsl/">Dave Pawson's XSL FAQ</fork>. @@ -79,7 +79,7 @@ For other fonts, use font editing sofware or operating system utilities (such as <p> The handful of basic XML character entities that do exist are the ampersand, apostrophe, less-than, greater-than, and single-quote characters. These are needed to distinguish markup tags from content, and to distinguish character entities from content. -To avoid parser complaints about illegal characters and entities in your input, ensure that ampersands in text and attributes are written as &amp;, "<" is written as &lt;, and ">" as &gt;. +To avoid parser complaints about illegal characters and entities in your input, ensure that ampersands in text and attributes are written as &amp;, "<" is written as &lt;, and ">" as &gt;. It is not necessary everywhere, but it is wise to do so anyway, just to be sure. </p> <p> @@ -95,7 +95,7 @@ It is not necessary everywhere, but it is wise to do so anyway, just to be sure. If the parser complains about illegal bytes or characters in the input, or there are unexpected characters in the output, this is usually the result of a character encoding problem. See the <link href="http://www.dpawson.co.uk/xsl">XSL FAQ</link> for additional information. Many software packages that produce XML, including XSLT processors, use UTF-8 encoding as a default. -If you view their output with something not aware of the encoding, like Notepad for Win95/98/ME/NT, funny characters are displayed. A Å is a giveaway. +If you view their output with something not aware of the encoding, like Notepad for Win95/98/ME/NT, funny characters are displayed. A � is a giveaway. </p> </section> </section> diff --git a/src/documentation/content/xdocs/gethelp.xml b/src/documentation/content/xdocs/gethelp.xml index 8a0a41439..f94bf0544 100644 --- a/src/documentation/content/xdocs/gethelp.xml +++ b/src/documentation/content/xdocs/gethelp.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,12 +19,12 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP: Getting Help</title> + <title>Apacheâ„¢ FOP: Getting Help</title> <subtitle>Checklist for Finding Appropriate Resources</subtitle> <version>$Revision$</version> </header> <body> - <p>The FOP developer community is eager to help you maximize the usefulness of FOP. + <p>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:</p> diff --git a/src/documentation/content/xdocs/index.xml b/src/documentation/content/xdocs/index.xml index 3d29dd1a9..0b05b6e2b 100644 --- a/src/documentation/content/xdocs/index.xml +++ b/src/documentation/content/xdocs/index.xml @@ -33,6 +33,10 @@ 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. </p> + <p>The Apacheâ„¢ FOP project is part of the <a href="http://www.apache.org">Apacheâ„¢</a> + Software Foundation, which is a wider community of users and developers of open + source projects. + </p> <figure width="480" height="260" src="images/document.jpg" alt="Render Diagram" /> <p> A stable release of the latest version of FOP (<link href="1.0/">1.0</link>) is diff --git a/src/documentation/content/xdocs/knownissues.xml b/src/documentation/content/xdocs/knownissues.xml index ea39b2974..7c63fb69d 100644 --- a/src/documentation/content/xdocs/knownissues.xml +++ b/src/documentation/content/xdocs/knownissues.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document xmlns:xi="http://www.w3.org/2001/XInclude"> <header> - <title>Apache FOP: Known Issues</title> + <title>Apacheâ„¢ FOP: Known Issues</title> <version>$Revision$</version> </header> <body> <section> <title>Known issues</title> <p> - This page lists currently known issues in the FOP codebase. Please note that this list is generated + 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. </p> @@ -40,7 +40,7 @@ </ul> </note> <p> - Apache FOP has an extensive automated testing infrastructure. Parts of this infrastructure are several + 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. diff --git a/src/documentation/content/xdocs/license.xml b/src/documentation/content/xdocs/license.xml index 3a3da8887..b3b552a84 100644 --- a/src/documentation/content/xdocs/license.xml +++ b/src/documentation/content/xdocs/license.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,15 +20,15 @@ <document> <header> - <title>Apache FOP License</title> + <title>Apacheâ„¢ FOP License</title> <version>$Revision$</version> </header> <body> <section> <title>License</title> <p> - All new Apache FOP releases will be licensed under the <strong>Apache License, version 2.0</strong>. - Releases until version 0.20.5 are released unter the Apache License, version 1.1. + All new Apacheâ„¢ FOP releases will be licensed under the <strong>Apacheâ„¢ License, version 2.0</strong>. + Releases until version 0.20.5 are released unter the Apacheâ„¢ License, version 1.1. </p> <p> To inspect the license terms please consult the LICENSE and NOTICE files in the root diff --git a/src/documentation/content/xdocs/maillist.xml b/src/documentation/content/xdocs/maillist.xml index 93a6b6cbe..ec5e274dc 100644 --- a/src/documentation/content/xdocs/maillist.xml +++ b/src/documentation/content/xdocs/maillist.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP: Mailing List Resources</title> + <title>Apacheâ„¢ FOP: Mailing List Resources</title> <version>$Revision$</version> </header> <body> @@ -37,7 +37,7 @@ If you are using Microsoft Outlook, this setting can be found at the "Mail Forma <p>For help in understanding email acronyms, see the <jump href="http://www.lingo2word.com/lists/acronym_listA.html">Lingo2Word Acronym List</jump>, or the <jump href="http://www.keno.org/web_design/acronyms.htm">Keno Internet Services Internet Glossary</jump>.</p> </section> <section id="fop-user"> - <title>FOP Users Mailing List</title> + <title>Apacheâ„¢ FOP Users Mailing List</title> <p>Use this forum to discuss topics of interest to FOP users.</p> <section id="fop-user-archive"> <title>Archives</title> @@ -69,8 +69,7 @@ If you are using Microsoft Outlook, this setting can be found at the "Mail Forma <li>To <strong>unsubscribe</strong>: Send email to <link href="mailto:fop-users-unsubscribe@xmlgraphics.apache.org">fop-users-unsubscribe@xmlgraphics.apache.org</link>.</li> </ul> </section> - <note>You can find the developer mailing list on the <link -href="dev/index.html#mail-fop-dev">Development pages</link>.</note> + <note>You can find the developer mailing list on the <link href="dev/index.html#mail-fop-dev">Development pages</link>.</note> <section id="fop-user-policy"> <title>Submitting a Question</title> <p>FOP support is primarily <em>self-service</em>. The FOP User Mailing List serves as a backup to the self-service documentation for cases where either the documentation is deficient or where users have unusual circumstances. FOP developers and users are happy to help answer questions that are <em>appropriate to the forum</em> (i.e. FOP-specific), and that are <em>submitted after appropriate preparation</em>. To ensure that your question is not <strong>abusive</strong> of this policy, please use the following checklist:</p> diff --git a/src/documentation/content/xdocs/news-data.xml b/src/documentation/content/xdocs/news-data.xml index 62908926c..1fec872df 100644 --- a/src/documentation/content/xdocs/news-data.xml +++ b/src/documentation/content/xdocs/news-data.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -17,9 +17,15 @@ --> <!-- $Id$ --> <news> - <item date="2010-07-21" title="Apache FOP 1.0 Released"> + <item date="2012-02-24" title="New committer"> + <p>Welcome Glenn Adams!</p> + </item> + <item date="2011-11-17" title="New committer"> + <p>Welcome Mehdi Houshmand!</p> + </item> + <item date="2010-07-21" title="Apacheâ„¢ FOP 1.0 Released"> <p> - The Apache FOP team is delighted to present you a production grade + The Apacheâ„¢ FOP team is delighted to present you a production grade release of the new FOP codebase. This release contains many bug fixes and new features. See the <a href="1.0/releaseNotes_1.0.html">Release Notes</a> for a list of @@ -29,18 +35,18 @@ <item date="2009-12-14" title="New committer"> <p>Welcome Pascal Sancho!</p> </item> - <item date="2008-08-05" title="Apache FOP 0.95 Released"> + <item date="2008-08-05" title="Apacheâ„¢ FOP 0.95 Released"> <p> - The Apache FOP team is delighted to present you a production grade + The Apacheâ„¢ FOP team is delighted to present you a production grade release of the new FOP codebase. This release contains many bug fixes and new features. See the <a href="0.95/releaseNotes_0.95.html">Release Notes</a> for a list of the most important changes. </p> </item> - <item date="2008-03-16" title="Apache FOP 0.95beta Released"> + <item date="2008-03-16" title="Apacheâ„¢ FOP 0.95beta Released"> <p> - The Apache FOP team is delighted to present you a beta version of the + The Apacheâ„¢ FOP team is delighted to present you a beta version of the next production grade release of the new FOP codebase. This release contains many bug fixes and new features. See the <a href="0.95/releaseNotes_0.95beta.html">Release Notes</a> for a list of @@ -53,8 +59,8 @@ <item date="2007-10-15" title="New Committer"> <p>Welcome Adrian Cumiskey!</p> </item> - <item date="2007-08-24" title="Apache FOP 0.94 Released"> - <p>The Apache FOP team is pleased to present you the second production + <item date="2007-08-24" title="Apacheâ„¢ FOP 0.94 Released"> + <p>The Apacheâ„¢ FOP team is pleased to present you the second production grade release of the new FOP codebase. This release contains many bug fixes and new features. See the Release Notes for a list of the most important changes.</p> @@ -62,9 +68,9 @@ <item date="2007-01-26" title="New Committer"> <p>Welcome Jay Bryant!</p> </item> - <item date="2007-01-09" title="Apache FOP 0.93 released"> + <item date="2007-01-09" title="Apacheâ„¢ FOP 0.93 released"> <p> - The Apache FOP team is proud to present to you the first + The Apacheâ„¢ FOP team is proud to present to you the first production grade release of the new FOP codebase. This release has the new API first introduced in release 0.92 beta. It contains again many bug fixes and new features. @@ -73,7 +79,7 @@ <item date="2006-10-16" title="New Committer"> <p>Welcome Vincent Hennebert!</p> </item> - <item date="2006-04-18" title="Apache FOP 0.92 beta released"> + <item date="2006-04-18" title="Apacheâ„¢ FOP 0.92 beta released"> <p> A second "beta" grade release of the new FOP codebase with a modified and now considered stable API. The release contains many bug fixes as well as @@ -82,7 +88,7 @@ go to a 1.0 release! </p> </item> - <item date="2005-12-23" title="Apache FOP 0.91 beta released"> + <item date="2005-12-23" title="Apacheâ„¢ FOP 0.91 beta released"> <p> One month after the initial release we're happy present a "beta" grade release of the new FOP codebase. It's mostly a bug fix release but also @@ -90,9 +96,9 @@ on the initial release! </p> </item> - <item date="2005-11-22" title="Apache FOP 0.90 alpha 1 released"> + <item date="2005-11-22" title="Apacheâ„¢ FOP 0.90 alpha 1 released"> <p> - The Apache FOP team is proud to present to you the largely rewritten + The Apacheâ„¢ FOP team is proud to present to you the largely rewritten codebase which is finally in a state where you can start to use it. It has taken over three years to get this far and over two years without a new release from the FOP project. @@ -106,12 +112,12 @@ <item date="2005-09-08" title="New Committer"> <p>Welcome Manuel Mall!</p> </item> - <item date="2004-10-20" title="Creation of the Apache XML Graphics project"> + <item date="2004-10-20" title="Creation of the Apacheâ„¢ XML Graphics project"> <p> The Apache Board of Directors agreed to the creation of the - <a href="http://xmlgraphics.apache.org">Apache XML Graphics</a> + <a href="http://xmlgraphics.apache.org">Apacheâ„¢ XML Graphics</a> project which will be comprised of Batik and FOP. Both former - Apache XML subprojects are in this way complying with the Board's desire + Apacheâ„¢ XML subprojects are in this way complying with the Board's desire to improve project oversight. Both project teams also see additional benefits of working more closely together. </p> @@ -134,7 +140,7 @@ <item date="2003-11-29" title="New Committer"> <p>Welcome Peter Herweg!</p> </item> - <item date="2003-07-18" title="Apache FOP 0.20.5 released"> + <item date="2003-07-18" title="Apacheâ„¢ FOP 0.20.5 released"> <p>Changes since 0.20.4 include:</p> <ul> <li>Added support for PDF encryption</li> @@ -163,13 +169,13 @@ <item date="2003-06-29" title="New Committer"> <p>Welcome Glen Mazza!</p> </item> - <item date="2003-05-23" title="Apache FOP 0.20.5 Release Candidate 3 available"> + <item date="2003-05-23" title="Apacheâ„¢ FOP 0.20.5 Release Candidate 3 available"> <p> See the full text of the <a href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=fop-dev@xml.apache.org&msgNo=5429">announcement</a>. </p> </item> - <item date="2003-02-18" title="Apache FOP 0.20.5 Release Candidate 2 available"> + <item date="2003-02-18" title="Apacheâ„¢ FOP 0.20.5 Release Candidate 2 available"> <p> See the full text of the <a href="http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=fop-dev@xml.apache.org&msgNo=4509">announcement</a>. diff --git a/src/documentation/content/xdocs/news.xml b/src/documentation/content/xdocs/news.xml index 29a1e3f98..978314977 100644 --- a/src/documentation/content/xdocs/news.xml +++ b/src/documentation/content/xdocs/news.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>News</title> + <title>Apacheâ„¢ FOP News</title> <version>$Revision$</version> </header> <body> diff --git a/src/documentation/content/xdocs/quickstartguide.xml b/src/documentation/content/xdocs/quickstartguide.xml index 4ea1d0110..2020e4b36 100644 --- a/src/documentation/content/xdocs/quickstartguide.xml +++ b/src/documentation/content/xdocs/quickstartguide.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,13 +19,13 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP: Quick Start Guide</title> - <subtitle>Everything you need to start using and appreciating Apache FOP quickly.</subtitle> + <title>Apacheâ„¢ FOP: Quick Start Guide</title> + <subtitle>Everything you need to start using and appreciating Apacheâ„¢ FOP quickly.</subtitle> <version>$Revision$</version> </header> <body> <section id="essentials"> - <title>FOP Essentials</title> + <title>Apacheâ„¢ FOP Essentials</title> <p>The goal of this <strong>Quick Start Guide</strong> is to help novice users get Apache FOP up and running quickly. Typically, you'll need to:</p> <ol> <li><link href="download.html">Download FOP</link></li> diff --git a/src/documentation/content/xdocs/resources.xml b/src/documentation/content/xdocs/resources.xml index 708f10334..d976f9859 100644 --- a/src/documentation/content/xdocs/resources.xml +++ b/src/documentation/content/xdocs/resources.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,8 +20,8 @@ <!-- FOP Relevant Specifications and links --> <document> <header> - <title>FOP: Other Resources</title> - <subtitle>Resources useful for developing and using FOP</subtitle> + <title>Apacheâ„¢ FOP: Other Resources</title> + <subtitle>Resources useful for developing and using Apacheâ„¢ FOP</subtitle> <version>$Revision$</version> </header> <body> diff --git a/src/documentation/content/xdocs/site.xml b/src/documentation/content/xdocs/site.xml index 8a13a45c0..d7ca6f5e1 100644 --- a/src/documentation/content/xdocs/site.xml +++ b/src/documentation/content/xdocs/site.xml @@ -1,4 +1,4 @@ -<?xml version="1.0"?> +<?xml version="1.0" encoding="UTF-8"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -31,6 +31,7 @@ <license label="License" href="license.html"/> <asf-sponsorship label="ASF Sponsorship Program" href="http://www.apache.org/foundation/sponsorship.html"/>" <asf-thanks label="ASF Thanks" href="http://www.apache.org/foundation/thanks.html"/>" + <asf-security label="Security" href="http://www.apache.org/security/"/> <!-- <all_site label="Full HTML" href="wholesite.html"/> <all_sitePDF label="Full PDF" href="wholesite.pdf"/> @@ -60,7 +61,7 @@ <!-- BEGIN Version 0.95 documentation tab --> - <trunk label="FOP 0.95" href="0.95/" tab="previousversion"> + <trunk label="Apacheâ„¢ FOP 0.95" href="0.95/" tab="previousversion"> <about label="About" href="index.html"/> <release label="Release Notes" href="releaseNotes_0.95.html"/> <changes label="Changes (0.95)" href="changes_0.95.html"/> @@ -68,7 +69,7 @@ <knownissues label="Known Issues" href="knownissues_overview.html"/> <upgrading label="Upgrading" href="upgrading.html"/> - <using label="Using FOP"> + <using label="Using Apacheâ„¢ FOP"> <build label="Build" href="compiling.html"/> <config label="Configure" href="configuration.html"/> <run label="Run" href="running.html"/> @@ -98,14 +99,14 @@ <!-- BEGIN Version 1.0 documentation tab --> - <trunk label="FOP 1.0" href="1.0/" tab="stableversion"> + <trunk label="Apacheâ„¢ FOP 1.0" href="1.0/" tab="stableversion"> <about label="About" href="index.html"/> <release label="Release Notes" href="releaseNotes_1.0.html"/> <changes label="Changes (1.0)" href="changes_1.0.html"/> <knownissues label="Known Issues" href="knownissues_overview.html"/> <upgrading label="Upgrading" href="upgrading.html"/> - <using label="Using FOP"> + <using label="Using Apacheâ„¢ FOP"> <build label="Build" href="compiling.html"/> <config label="Configure" href="configuration.html"/> <run label="Run" href="running.html"/> @@ -137,11 +138,11 @@ <!-- BEGIN Trunk documentation tab --> - <trunk label="FOP Trunk (dev)" href="trunk/" tab="develversion"> + <trunk label="Apacheâ„¢ FOP Trunk (dev)" href="trunk/" tab="develversion"> <about label="About" href="index.html"/> <upgrading label="Upgrading" href="upgrading.html"/> - <using label="Using FOP"> + <using label="Using Apacheâ„¢ FOP"> <build label="Build" href="compiling.html"/> <config label="Configure" href="configuration.html"/> <run label="Run" href="running.html"/> diff --git a/src/documentation/content/xdocs/status.xml b/src/documentation/content/xdocs/status.xml index fa52809e5..8a6ea5dce 100644 --- a/src/documentation/content/xdocs/status.xml +++ b/src/documentation/content/xdocs/status.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,8 +20,8 @@ <!-- Status --> <document> <header> - <title>FOP Status</title> - <subtitle>Current Status of FOP</subtitle> + <title>Apacheâ„¢ FOP Status</title> + <subtitle>Current Status of Apacheâ„¢ FOP</subtitle> <version>$Revision$</version> </header> <body> @@ -29,7 +29,7 @@ <title>Status</title> <p>[last updated 5 July 2010]</p> <p> - FOP version 0.95 was released on 5 August 2008. FOP version 1.0 was released on 21 July 2010. + Apacheâ„¢ FOP version 0.95 was released on 5 August 2008. Apacheâ„¢ FOP version 1.0 was released on 21 July 2010. </p> </section> <section> diff --git a/src/documentation/content/xdocs/team.xml b/src/documentation/content/xdocs/team.xml index 3747a7f58..4735b74a8 100644 --- a/src/documentation/content/xdocs/team.xml +++ b/src/documentation/content/xdocs/team.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.3//EN" "http://forrest.apache.org/dtd/document-v13.dtd"> <document> <header> - <title>FOP: Development Team</title> + <title>Apacheâ„¢ FOP: Development Team</title> <version>$Revision$</version> </header> <body> @@ -57,8 +57,8 @@ is a web/WAP/Palm developer from Laguna Beach, California, USA. A recent XML/XSL-FO convert, he has been nit-picking FAQs & assorted web pages since his first webmaster position @brain.com in 1996. Most - important creation? He's got a couple of cool kids.</li> - <li id="jm"><link href="mailto:jeremias@apache.org">Jeremias Märki</link> (JM) + important creation? He's got a couple of cool kids.</li> + <li id="jm"><link href="mailto:jeremias@apache.org">Jeremias M�rki</link> (JM) is an independent software engineer and consultant from Lucerne, Switzerland. He's also the creator of <fork href="http://barcode4j.sourceforge.net">Barcode4J</fork>. See his <fork href="http://www.jeremias-maerki.ch">home page</fork> for more information @@ -67,7 +67,7 @@ <li id="sp"><link href="mailto:spepping@apache.org">Simon Pepping</link> (SP) came to FOP from the TeX/LaTeX world. See his <fork href="http://www.leverkruid.eu">home page</fork> for some of his private projects.</li> - <li id="jp"><link href="mailto:pietsch@apache.org">Jörg Pietschmann</link> (JP)</li> + <li id="jp"><link href="mailto:pietsch@apache.org">J�rg Pietschmann</link> (JP)</li> <li id="ps"><link href="mailto:tcho@club-internet.fr">Pascal Sancho</link> (PS) is an XML developper from Aix-en-Provence (France). He works on software solutions for rendering various kind of documents on various supports, more specifically taking care diff --git a/src/documentation/content/xdocs/trunk/accessibility.xml b/src/documentation/content/xdocs/trunk/accessibility.xml index f3c66e06a..412519d8b 100644 --- a/src/documentation/content/xdocs/trunk/accessibility.xml +++ b/src/documentation/content/xdocs/trunk/accessibility.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>Accessibility</title> + <title>Apacheâ„¢ FOP: Accessibility</title> </header> <body> <section id="overview"> @@ -27,7 +27,7 @@ <p> This page describes the <a href="http://en.wikipedia.org/wiki/Accessibility">accessibility</a> - features of Apache FOP. + features of Apacheâ„¢ FOP. <a href="http://www.section508.gov/">Section 508</a> defines accessibility in the context of electronic documents for the USA but other countries have similar requirements. </p> @@ -164,4 +164,4 @@ </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/anttask.xml b/src/documentation/content/xdocs/trunk/anttask.xml index a543a5623..ba53fe7d1 100644 --- a/src/documentation/content/xdocs/trunk/anttask.xml +++ b/src/documentation/content/xdocs/trunk/anttask.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,12 +19,12 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Ant task</title> + <title>Apacheâ„¢ FOP: Ant task</title> <version>$Revision$</version> </header> <body> <p> - Apache FOP provides an Ant task for automating the document build process. + Apacheâ„¢ FOP provides an Ant task for automating the document build process. </p> <section id="basics"> <title>Description</title> @@ -233,5 +233,4 @@ ]]></source> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/compiling.xml b/src/documentation/content/xdocs/trunk/compiling.xml index 0a8bf3486..7bfa165b5 100644 --- a/src/documentation/content/xdocs/trunk/compiling.xml +++ b/src/documentation/content/xdocs/trunk/compiling.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Building from Source Code</title> + <title>Apacheâ„¢ FOP: Building from Source Code</title> <version>$Revision$</version> </header> <body> @@ -35,7 +35,7 @@ <!-- /text for released versions --> <!-- text for trunk --> <p> - FOP snapshots are either pre-compiled binary or source. + Apacheâ„¢ FOP snapshots are either pre-compiled binary or source. If you are using a binary snapshot, it is already built and there is no need to build it again. If you got the source code from a repository snapshot or via Subversion you will need to build FOP. See the <a href="../download.html">Download Instructions</a> for information about where to obtain binary or repository snapshots, and whether a @@ -144,5 +144,4 @@ </ul> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/configuration.xml b/src/documentation/content/xdocs/trunk/configuration.xml index aae353922..cd1e1dfc3 100644 --- a/src/documentation/content/xdocs/trunk/configuration.xml +++ b/src/documentation/content/xdocs/trunk/configuration.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Configuration</title> + <title>Apacheâ„¢ FOP: Configuration</title> <version>$Revision$</version> </header> @@ -27,7 +27,7 @@ <section id="general"> <title>Configuration File Basics</title> <p> - The FOP configuration file is an XML file containing a variety of settings that are useful + The Apacheâ„¢ FOP configuration file is an XML file containing a variety of settings that are useful for controlling FOP's behavior, and for helping it find resources that you wish it to use. </p> <p> @@ -522,5 +522,4 @@ information it finds. Check if FOP finds what you expect.</li> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/embedding.xml b/src/documentation/content/xdocs/trunk/embedding.xml index 3881c4599..24c74f970 100644 --- a/src/documentation/content/xdocs/trunk/embedding.xml +++ b/src/documentation/content/xdocs/trunk/embedding.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <!-- Embedding FOP --> <document> <header> - <title>Apache FOP: Embedding</title> + <title>Apacheâ„¢ FOP: Embedding</title> <subtitle>How to Embed FOP in a Java application</subtitle> <version>$Revision$</version> </header> @@ -29,11 +29,11 @@ <section id="overview"> <title>Overview</title> <p> - Review <a href="running.html">Running FOP</a> for important information that applies + Review <a href="running.html">Running Apacheâ„¢ FOP</a> for important information that applies to embedded applications as well as command-line use, such as options and performance. </p> <p> - To embed Apache FOP in your application, first create a new + To embed Apacheâ„¢ FOP in your application, first create a new org.apache.fop.apps.FopFactory instance. This object can be used to launch multiple rendering runs. For each run, create a new org.apache.fop.apps.Fop instance through one of the factory methods of FopFactory. In the method call you specify which output @@ -749,5 +749,4 @@ mailing list. </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/events.xml b/src/documentation/content/xdocs/trunk/events.xml index 017775f03..27daad59b 100644 --- a/src/documentation/content/xdocs/trunk/events.xml +++ b/src/documentation/content/xdocs/trunk/events.xml @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Events/Processing Feedback</title> + <title>Apacheâ„¢ FOP: Events/Processing Feedback</title> <version>$Revision$</version> </header> <body> <section id="introduction"> <title>Introduction</title> <p> - In versions until 0.20.5, FOP used + In versions until 0.20.5, Apacheâ„¢ FOP used <a href="http://excalibur.apache.org/framework/index.html">Avalon-style Logging</a> where it was possible to supply a logger per processing run. During the redesign the logging infrastructure was switched over to @@ -446,4 +446,4 @@ producer.complain(this, "I'm tired", 23);]]></source> </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/extensions.xml b/src/documentation/content/xdocs/trunk/extensions.xml index ef9b6f6c2..02d83db96 100644 --- a/src/documentation/content/xdocs/trunk/extensions.xml +++ b/src/documentation/content/xdocs/trunk/extensions.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Standard FOP Extensions</title> + <title>Standard Apacheâ„¢ FOP Extensions</title> <version>$Revision$</version> </header> <body> <p> By "extension", we mean any data that can be placed in the input XML document that is not addressed by the XSL-FO standard. - By having a mechanism for supporting extensions, FOP is able to add features that + By having a mechanism for supporting extensions, Apacheâ„¢ FOP is able to add features that are not covered in the specification. </p> <p> @@ -336,5 +336,4 @@ to following pages. Here is an example of FO code creating such a table-header:< </section> </section> </body> -</document> - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/fonts.xml b/src/documentation/content/xdocs/trunk/fonts.xml index 57b9b98f9..f3481607d 100644 --- a/src/documentation/content/xdocs/trunk/fonts.xml +++ b/src/documentation/content/xdocs/trunk/fonts.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Fonts</title> + <title>Apacheâ„¢ FOP: Fonts</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email=""/> @@ -31,7 +31,7 @@ <body> <section id="intro"> <title>Summary</title> - <p>The following table summarizes the font capabilities of the various FOP renderers:</p> + <p>The following table summarizes the font capabilities of the various Apache� FOP renderers:</p> <table> <tr> <th>Renderer</th> @@ -576,4 +576,4 @@ </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/graphics.xml b/src/documentation/content/xdocs/trunk/graphics.xml index 270d6b49b..b1653443a 100644 --- a/src/documentation/content/xdocs/trunk/graphics.xml +++ b/src/documentation/content/xdocs/trunk/graphics.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Graphics Formats</title> + <title>Apacheâ„¢ FOP: Graphics Formats</title> <version>$Revision$</version> </header> <body> @@ -30,7 +30,7 @@ </p> <ul> <li> - The image libraries Jimi and JAI are not supported. Instead, Apache FOP uses the + The image libraries Jimi and JAI are not supported. Instead, Apacheâ„¢ FOP uses the Image I/O API that was introduced with Java 1.4 for all bitmap codecs. </li> <li> @@ -73,65 +73,65 @@ <tr> <td><a href="#bmp">BMP</a> (Microsoft Windows Bitmap)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#emf">EMF</a> (Windows Enhanced Metafile)</td> <td>vector (with embedded bitmaps)</td> <td>(X)</td> - <td></td> - <td></td> + <td/> + <td/> </tr> <tr> <td><a href="#eps">EPS</a> (Encapsulated PostScript)</td> <td>metafile (both bitmap and vector), most frequently used for vector drawings</td> <td>(X)</td> - <td></td> - <td></td> + <td/> + <td/> </tr> <tr> <td>GIF (Graphics Interchange Format)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X</td> </tr> <tr> <td><a href="#jpeg">JPEG</a> (Joint Photographic Experts Group)</td> <td>bitmap</td> <td>(X)</td> - <td></td> + <td/> <td>X</td> </tr> <tr> <td><a href="#png">PNG</a> (Portable Network Graphic)</td> <td>bitmap</td> - <td></td> - <td></td> + <td/> + <td/> <td>X</td> </tr> <tr> <td><a href="#svg">SVG</a> (Scalable Vector Graphics)</td> <td>vector (with embedded bitmaps)</td> - <td></td> + <td/> <td>X</td> - <td></td> + <td/> </tr> <tr> <td><a href="#tiff">TIFF</a> (Tag Image Format File)</td> <td>bitmap</td> <td>(X)</td> - <td></td> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#wmf">WMF</a> (Windows Metafile)</td> <td>vector (with embedded bitmaps)</td> - <td></td> + <td/> <td>(X)</td> - <td></td> + <td/> </tr> </table> <p> @@ -149,7 +149,7 @@ <note> <a href="http://jai-imageio.dev.java.net/">JAI Image I/O Tools</a> is not the same as the <a href="http://java.sun.com/javase/technologies/desktop/media/jai/">JAI library</a>! The - former simply exposes JAI's codecs using the Image I/O API but does not include all + former simply exposes JAI's codecs using the Image&nbsp;I/O API but does not include all the image manipulation functionality. </note> <section id="format-map"> @@ -181,21 +181,21 @@ </tr> <tr> <td><a href="#emf">EMF</a> (Windows Enhanced Metafile)</td> - <td></td> - <td></td> - <td></td> - <td></td> - <td></td> + <td/> + <td/> + <td/> + <td/> + <td/> <td>X [1]</td> </tr> <tr> <td><a href="#eps">EPS</a> (Encapsulated PostScript)</td> - <td></td> + <td/> <td>X [1]</td> - <td></td> - <td></td> - <td></td> - <td></td> + <td/> + <td/> + <td/> + <td/> </tr> <tr> <td>GIF (Graphics Interchange Format)</td> @@ -361,7 +361,7 @@ <section id="gif"> <title>GIF</title> <p> - GIF images are supported through an Image I/O codec. Transparency is supported but + GIF images are supported through an Image&nbsp;I/O codec. Transparency is supported but not guaranteed to work with every output format. </p> </section> @@ -376,14 +376,14 @@ through without decompression. User reports indicate that grayscale, RGB, and CMYK color spaces are all rendered properly. However, for other output formats, the JPEG images have to be decompressed. Tests have shown that there are some limitation - in some Image I/O codecs concerning images in the CMYK color space. Work-arounds are + in some Image&nbsp;I/O codecs concerning images in the CMYK color space. Work-arounds are in place but may not always work as expected. </p> </section> <section id="png"> <title>PNG</title> <p> - PNG images are supported through an Image I/O codec. Transparency is supported but + PNG images are supported through an Image&nbsp;I/O codec. Transparency is supported but not guaranteed to work with every output format. </p> </section> @@ -520,7 +520,7 @@ <p> FOP can embed TIFF images without decompression into PDF, PostScript and AFP if they have either CCITT T.4, CCITT T.6, or JPEG compression. Otherwise, a TIFF-capable - Image I/O codec is necessary for decoding the image. + Image&nbsp;I/O codec is necessary for decoding the image. </p> <p> There may be some limitation concerning images in the CMYK color space. @@ -587,4 +587,4 @@ </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/hyphenation.xml b/src/documentation/content/xdocs/trunk/hyphenation.xml index 699534ee1..e6f666826 100644 --- a/src/documentation/content/xdocs/trunk/hyphenation.xml +++ b/src/documentation/content/xdocs/trunk/hyphenation.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Apache FOP: Hyphenation</title> + <title>Apacheâ„¢ FOP: Hyphenation</title> <version>$Revision$</version> </header> <body> @@ -27,13 +27,13 @@ <title>Hyphenation Support</title> <section id="intro"> <title>Introduction</title> - <p>FOP uses Liang's hyphenation algorithm, well known from TeX. It needs + <p>Apacheâ„¢ FOP uses Liang's hyphenation algorithm, well known from TeX. It needs language specific pattern and other data for operation.</p> <p>Because of <a href="#license-issues">licensing issues</a> (and for convenience), all hyphenation patterns for FOP are made available through the <a class="fork" href="http://offo.sourceforge.net/hyphenation/index.html">Objects For Formatting Objects</a> project.</p> - <note>If you have made improvements to an existing FOP hyphenation pattern, + <note>If you have made improvements to an existing Apacheâ„¢ FOP hyphenation pattern, or if you have created one from scratch, please consider contributing these to OFFO so that they can benefit other FOP users as well. Please inquire on the <a href="../maillist.html#fop-user">FOP User @@ -145,16 +145,16 @@ confirming their accuracy, or raising specific problems that we can address.</warning> <ul> - <li>The root of the pattern file is the <hyphenation-info> element.</li> - <li><hyphen-char>: its attribute "value" contains the character signalling - a hyphen in the <exceptions> section. It has nothing to do with the + <li>The root of the pattern file is the <hyphenation-info> element.</li> + <li><hyphen-char>: its attribute "value" contains the character signalling + a hyphen in the <exceptions> section. It has nothing to do with the hyphenation character used in FOP, use the XSLFO hyphenation-character property for defining the hyphenation character there. At some points a dash U+002D is hardwired in the code, so you'd better use this too (patches to rectify the situation are welcome). There is no default, if you declare exceptions with hyphenations, you must declare the hyphen-char too.</li> - <li><hyphen-min> contains two attributes: + <li><hyphen-min> contains two attributes: <ul> <li>before: the minimum number of characters in a word allowed to exist on a line immediately preceding a hyphenated word-break.</li> @@ -164,23 +164,23 @@ This element is unused and not even read. It should be considered a documentation for parameters used during pattern generation. </li> - <li><classes> contains whitespace-separated character sets. The members + <li><classes> contains whitespace-separated character sets. The members of each set should be treated as equivalent for purposes of hyphenation, usually upper and lower case of the same character. The first character of the set is the canonical character, the patterns and exceptions should only contain these canonical representation characters (except digits for weight, the period (.) as word delimiter in the patterns and the hyphen char in exceptions, of course).</li> - <li><exceptions> contains whitespace-separated words, each of which + <li><exceptions> contains whitespace-separated words, each of which has either explicit hyphen characters to denote acceptable breakage points, or no hyphen characters, to indicate that this word should - never be hyphenated, or contain explicit <hyp> elements for specifying - changes of spelling due to hyphenation (like backen -> bak-ken or - Stoffarbe -> Stoff-farbe in the old german spelling). Exceptions override - the patterns described below. Explicit <hyp> declarations don't work + never be hyphenated, or contain explicit <hyp> elements for specifying + changes of spelling due to hyphenation (like backen -> bak-ken or + Stoffarbe -> Stoff-farbe in the old german spelling). Exceptions override + the patterns described below. Explicit <hyp> declarations don't work yet (patches welcome). Exceptions are generally a bit brittle, test carefully.</li> - <li><patterns> includes whitespace-separated patterns, which are what + <li><patterns> includes whitespace-separated patterns, which are what drive most hyphenation decisions. The characters in these patterns are explained as follows: <ul> @@ -234,4 +234,4 @@ hyphenation.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/index.xml b/src/documentation/content/xdocs/trunk/index.xml index 8ded0e106..91a3ec65e 100644 --- a/src/documentation/content/xdocs/trunk/index.xml +++ b/src/documentation/content/xdocs/trunk/index.xml @@ -26,7 +26,7 @@ <section id="intro"> <title>Introduction</title> <p> - <strong>FOP Trunk</strong> is the name for the current + Apacheâ„¢ <strong>FOP Trunk</strong> is the name for the current development code as found in the <a href="ext:svn-repo/trunk">Subversion repository</a>. This section of the FOP web site provides the documentation for @@ -47,4 +47,4 @@ </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/intermediate.xml b/src/documentation/content/xdocs/trunk/intermediate.xml index 148e99360..171ae4e6a 100644 --- a/src/documentation/content/xdocs/trunk/intermediate.xml +++ b/src/documentation/content/xdocs/trunk/intermediate.xml @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Intermediate Format</title> + <title>Apacheâ„¢ FOP: Intermediate Format</title> <version>$Revision$</version> </header> <body> @@ -30,7 +30,7 @@ <section id="introduction"> <title>Introduction</title> <p> - Apache FOP now provides two different so-called intermediate formats. The first one + Apacheâ„¢ FOP now provides two different so-called intermediate formats. The first one (let's call it the area tree XML format) is basically a 1:1 XML representation of FOP's area tree as generated by the layout engine. The area tree is conceptually defined in the <a href="http://www.w3.org/TR/2001/REC-xsl-20011015/slice1.html#section-N742-Formatting">XSL-FO specification in chapter 1.1.2</a>. @@ -328,4 +328,4 @@ try { </section> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/metadata.xml b/src/documentation/content/xdocs/trunk/metadata.xml index 8c273fff5..5d4185533 100644 --- a/src/documentation/content/xdocs/trunk/metadata.xml +++ b/src/documentation/content/xdocs/trunk/metadata.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>Metadata</title> + <title>Apacheâ„¢ FOP: Metadata</title> </header> <body> <section id="overview"> @@ -42,7 +42,7 @@ <title>Embedding XMP in an XSL-FO document</title> <p> As noted above, there's no officially recommended way to embed metadata in XSL-FO. - Apache FOP supports embedding XMP in XSL-FO. Currently, only support for document-level + Apacheâ„¢ FOP supports embedding XMP in XSL-FO. Currently, only support for document-level metadata is implemented. Object-level metadata will be implemented when there's interest. </p> @@ -240,4 +240,4 @@ </ul> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/output.xml b/src/documentation/content/xdocs/trunk/output.xml index cf88bd321..9b6a3edc9 100644 --- a/src/documentation/content/xdocs/trunk/output.xml +++ b/src/documentation/content/xdocs/trunk/output.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -20,7 +20,7 @@ <!-- Output Formats: Renderers --> <document> <header> - <title>Apache FOP Output Formats</title> + <title>Apacheâ„¢ FOP Output Formats</title> <version>$Revision$</version> <authors> <person name="Keiron Liddle" email="keiron@aftexsw.com"/> @@ -30,7 +30,7 @@ <body> <p> - FOP supports multiple output formats by using a different renderer for each format. + 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. @@ -1089,7 +1089,7 @@ Note that the value of the encoding attribute in the example is the double-byte Please refer to the <link href="#afp-resource-level-defaults">Resource Level Defaults</link> above to see what is used if the resource-level attribute is not specified. </p> - <p></p> + <p/> </section> </section> </section> @@ -1377,7 +1377,4 @@ Note that the value of the encoding attribute in the example is the double-byte </section> </body> -</document> - - - +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/pdfa.xml b/src/documentation/content/xdocs/trunk/pdfa.xml index db5f56482..0b8399121 100644 --- a/src/documentation/content/xdocs/trunk/pdfa.xml +++ b/src/documentation/content/xdocs/trunk/pdfa.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>PDF/A (ISO 19005)</title> + <title>Apache™ FOP: PDF/A (ISO 19005)</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email="jeremias@apache.org"/> @@ -165,4 +165,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/pdfencryption.xml b/src/documentation/content/xdocs/trunk/pdfencryption.xml index 3562bb591..2d8fdfb10 100644 --- a/src/documentation/content/xdocs/trunk/pdfencryption.xml +++ b/src/documentation/content/xdocs/trunk/pdfencryption.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>PDF encryption.</title> + <title>Apacheâ„¢ FOP: PDF encryption.</title> <version>$Revision$</version> <authors> <person name="J.Pietschmann" email="pietsch@apache.org"/> @@ -30,7 +30,7 @@ <section> <title>Overview</title> <p> - FOP supports encryption of PDF output, thanks to Patrick + 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 @@ -298,4 +298,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/pdfx.xml b/src/documentation/content/xdocs/trunk/pdfx.xml index cf796c74d..bef2fce2a 100644 --- a/src/documentation/content/xdocs/trunk/pdfx.xml +++ b/src/documentation/content/xdocs/trunk/pdfx.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Copyright 2006 The Apache Software Foundation @@ -18,7 +18,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "document-v20.dtd"> <document> <header> - <title>PDF/X (ISO 15930)</title> + <title>Apache™ FOP: PDF/X (ISO 15930)</title> <version>$Revision$</version> <authors> <person name="Jeremias Märki" email="jeremias@apache.org"/> @@ -133,4 +133,4 @@ Fop fop = fopFactory.newFop(MimeConstants.MIME_PDF, userAgent); </p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/running.xml b/src/documentation/content/xdocs/trunk/running.xml index 49ba7efd8..6bfa6bb3f 100644 --- a/src/documentation/content/xdocs/trunk/running.xml +++ b/src/documentation/content/xdocs/trunk/running.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,7 +19,7 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Running Apache FOP</title> + <title>Running Apacheâ„¢ FOP</title> <version>$Revision$</version> </header> @@ -32,13 +32,13 @@ Java 1.4.x or later Runtime Environment. <ul> <li> - Many JREs >=1.4 contain older JAXP implementations (which often contain bugs). It's + Many JREs >=1.4 contain older JAXP implementations (which often contain bugs). It's usually a good idea to replace them with a current implementation. </li> </ul> </li> <li> - Apache FOP. The <a href="../download.html">FOP distribution</a> includes all libraries that you will + Apacheâ„¢ FOP. The <a href="../download.html">FOP distribution</a> 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: <ul> @@ -209,8 +209,8 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <title>Writing your own script</title> <p>FOP's entry point for your own scripts is the class <code>org.apache.fop.cli.Main</code>. The general pattern for the - command line is: <code>java -classpath <CLASSPATH> - org.apache.fop.cli.Main <arguments></code>. The arguments + command line is: <code>java -classpath <CLASSPATH> + org.apache.fop.cli.Main <arguments></code>. The arguments consist of the options and infile and outfile specifications as shown above for the standard scripts. You may wish to review the standard scripts to make sure that @@ -221,7 +221,7 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <title>Running with java's <code>-jar</code> option</title> <p> As an alternative to the start scripts you can run <code>java - -jar path/to/build/fop.jar <arguments></code>, relying on + -jar path/to/build/fop.jar <arguments></code>, relying on FOP to build the classpath for running FOP dynamically, see <a href="#dynamical-classpath">below</a>. If you use hyphenation, you must put <code>fop-hyph.jar</code> in the <code>lib</code> @@ -229,7 +229,7 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl </p> <p>You can also run <code>java -jar path/to/fop.jar - <arguments></code>, relying on the <code>Class-Path</code> + <arguments></code>, relying on the <code>Class-Path</code> entry in the manifest file. This works if you put <code>fop.jar</code> and all jar files from the <code>lib</code> directory in a single directory. If you use hyphenation, you @@ -366,4 +366,4 @@ Fop [options] [-fo|-xml] infile [-xsl file] [-awt|-pdf|-mif|-rtf|-tiff|-png|-pcl <p>If you have problems running FOP, please see the <a href="../gethelp.html">"How to get Help" page</a>.</p> </section> </body> -</document> +</document>
\ No newline at end of file diff --git a/src/documentation/content/xdocs/trunk/servlets.xml b/src/documentation/content/xdocs/trunk/servlets.xml index 07c22312d..dd2df4351 100644 --- a/src/documentation/content/xdocs/trunk/servlets.xml +++ b/src/documentation/content/xdocs/trunk/servlets.xml @@ -1,4 +1,4 @@ -<?xml version="1.0" standalone="no"?> +<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with @@ -19,15 +19,15 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Servlets</title> - <subtitle>How to use Apache FOP in a Servlet</subtitle> + <title>Apacheâ„¢ FOP: Servlets</title> + <subtitle>How to use Apacheâ„¢ FOP in a Servlet</subtitle> <version>$Revision$</version> </header> <body> <section id="overview"> <title>Overview</title> <p> - 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. </p> </section> <section id="example-servlets"> diff --git a/src/documentation/content/xdocs/trunk/upgrading.xml b/src/documentation/content/xdocs/trunk/upgrading.xml index ceb5b120b..3376a42d7 100644 --- a/src/documentation/content/xdocs/trunk/upgrading.xml +++ b/src/documentation/content/xdocs/trunk/upgrading.xml @@ -19,14 +19,14 @@ <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V2.0//EN" "http://forrest.apache.org/dtd/document-v20.dtd"> <document> <header> - <title>Upgrading from an Earlier Version of Apache FOP</title> + <title>Upgrading from an Earlier Version of Apacheâ„¢ FOP</title> <version>$Revision$</version> </header> <body> <section id="important"> <title>Important!</title> <p> - If you're planning to upgrade to the latest FOP version there are a few very important things + If you're planning to upgrade to the latest Apacheâ„¢ FOP version there are a few very important things to consider: </p> <ul> @@ -119,4 +119,4 @@ </ul> </section> </body> -</document> +</document>
\ No newline at end of file |