<menu label="Project">
<menu-item label="Status" href="status.html"/>
- <menu-item label="Changes" href="changes.html"/>
+ <!--
+ <menu-item label="Changes" href="changes.html"/>
<menu-item label="Todo" href="todo.html"/>
+ -->
</menu>
<menu label="Using FOP">
<menu-item label="Basics" href="index.html"/>
</menu>
<menu label="Design">
- <menu-item label="Resolved" href="../design/index.html"/>
+ <!--<menu-item label="Resolved" href="../design/index.html"/>-->
+ <menu-item label="Resolved" href="http://xml.apache.org/fop/design/index.html"/>
<external label="Unresolved (Wiki)" href="http://nagoya.apache.org/wiki/apachewiki.cgi?FOPProjectPages"/>
<menu-item label="SVG" href="svg.html"/>
<menu-item label="Fonts" href="fonts.html"/>
<ul>
<li>The oldest is the one that releases are currently generated from, and is also called the "maintenance branch". Because of limitations in its design, the FOP committers decided to freeze new development on this branch, and are providing only bug fixes. This branch is tagged as "fop-0_20_2-maintain" in the CVS repository.</li>
<li>The main development line is the future of FOP. It was spawned from the "maintenance" branch, but had to quickly be "broken" so that the needed redesign could be dropped into place. It is currently not as mature as the "maintenance" branch, but has far greater long-term prospects. It is also known as the "root" or "trunk" or "redesign".</li>
- <li>The "Alt Design" is exactly that: an alternative design approach. Because its efforts are largely complementary and parallel to the main development branch, and because it is expected to be merged at some point into the trunk, it is <link href="../design/alt.design/index.html">documented separately</link>. The authors of this effort are currently in the process of merging their work into the trunk.</li>
+ <li>The "Alt Design" is exactly that: an alternative design approach. Because its efforts are largely complementary and parallel to the main development branch, and because it is expected to be merged at some point into the trunk, it is <link href="http://xml.apache.org/fop/design/alt.design/index.html">documented separately</link>. The authors of this effort are currently in the process of merging their work into the trunk.</li>
</ul>
<p>Please note that patches for enhancements to the maintenance branch will generally not be considered. Bug fixes are welcome there, but new developers are strongly encouraged to apply their efforts to the trunk development line.</p>
<p>Because there is a fair amount of common information between the maintenance and trunk development lines, we attempt to document them together, highlighting differences only where needed.</p>
</section>
<section id="design">
<title>Understand FOP's Design</title>
- <p>The design for FOP is specified under the <link href="../design/index.html">Design</link> section. This is where the information on how FOP is developed and designed
+ <p>The design for FOP is specified under the <link href="http://xml.apache.org/fop/design/index.html">Design</link> section. This is where the information on how FOP is developed and designed
internally will be kept.
</p>
</section>
</section>
<section id="input">
<title>Input Sources</title>
- <p>The input XSL-FO document is always handled internally as SAX (see the <link href="design/parsing.html">Parsing Design Document</link> for the rationale).
+ <p>The input XSL-FO document is always handled internally as SAX (see the <link href="http://xml.apache.org/fop/design/parsing.html">Parsing Design Document</link> for the rationale).
However, the input itself can be provided in a variety of ways to FOP, which normalizes the input (if necessary) into SAX events:</p>
<ul>
<li><strong>SAX Events through SAX Handler</strong>: <code>FOTreeBuilder</code> is the SAX Handler which is obtained through <code>getContentHandler</code> on <code>Driver</code>.</li>
projects / xmlgraphics-fop.git / commitdiff