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/documentation/content/xdocs/dev | |
| 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/documentation/content/xdocs/dev')
29 files changed, 129 insertions, 142 deletions
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 |