<menu-item label="Basics" href="index.html"/>
</menu>
<menu label="Design">
- <!--<menu-item label="Resolved" href="../design/index.html"/>-->
- <menu-item label="Resolved" href="http://xml.apache.org/fop/design/index.html"/>
+ <menu-item label="Resolved" href="../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"/>
<menu-item label="API Doc" href="api-doc.html"></menu-item>
<menu-item label="Walk-Thru" href="implement.html"/>
<external label="Patch queue" href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Fop&short_desc=%5BPATCH%5D&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&namedcmd=Fop+all&newqueryname=fop+patch+queue&tofooter=1&order=Reuse+same+sort+as+last+time"/>
+ <menu-item label="Conventions" href="conventions.html"/>
</menu>
<menu label="Test">
<menu-item label="Testing" href="testing.html"/>
</menu>
<menu label="Deploy">
<menu-item label="Doc Mgmt" href="doc.html"/>
+ <menu-item label="Release" href="release.html"/>
<external label="Bugs" href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Fop&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.component"/>
</menu>
<menu label="Resources">
<menu-item label="FAQs" href="faq.html"/>
- <menu-item label="Examples" href="examples.html"/>
<menu-item label="Tools" href="tools.html"/>
<external label="ViewCVS" href="http://cvs.apache.org/viewcvs.cgi/xml-fop"/>
- <menu-item label="PDF" href="pdf.html"/>
- <menu-item label="Postscript" href="ps.html"/>
+ </menu>
+ <menu label="SubPackages">
+ <menu-item label="RTFlib" href="rtflib.html"></menu-item>
</menu>
</book>
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
-
-<document>
- <header>
- <title>FO Examples</title>
- </header>
- <body>
- <section>
- <title>Example Documents Using FOP</title>
- <p>
- These examples have been rendered using FOP.
- </p>
- </section>
- <section>
- <title>Images Examples</title>
- <p>
-Embedding images in FO:
- </p>
- <table>
- <caption>Images in FO</caption>
- <tr>
- <th>description</th>
- <th>fo file</th>
- <th>pdf result</th>
- </tr>
- <tr>
- <td>align in larger viewport</td>
- <td><link href="../fo/align.fo">align.fo</link></td>
- <td><link href="../fo/align.fo.pdf">align.fo.pdf</link></td>
- </tr>
- <tr>
- <td>align in smaller viewport</td>
- <td><link href="../fo/align2.fo">align2.fo</link></td>
- <td><link href="../fo/align2.fo.pdf">align2.fo.pdf</link></td>
- </tr>
- <tr>
- <td>scaling image</td>
- <td><link href="../fo/size.fo">size.fo</link></td>
- <td><link href="../fo/size.fo.pdf">size.fo.pdf</link></td>
- </tr>
- </table>
- </section>
- <section>
- <title>Instream Foreign Object Examples</title>
- <p>
-Instream Foreign Object images in FO, there are more on the
-<link href="svg.html">SVG Page</link>:
- </p>
- <table>
- <caption>Embedding instream-foreign-object</caption>
- <tr>
- <th>description</th>
- <th>fo file</th>
- <th>pdf result</th>
- </tr>
- <tr>
- <td>embedding svg in viewport</td>
- <td><link href="../fo/embed.fo">embed.fo</link></td>
- <td><link href="../fo/embed.fo.pdf">embed.fo.pdf</link></td>
- </tr>
- </table>
- </section>
- </body>
-</document>
-
<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="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>
+ <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>
</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="http://xml.apache.org/fop/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="../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 id="mail-fop-dev">
<title>Subscribe to the fop-dev Mailing List</title>
<p>Use this forum to discuss topics related to FOP development, including patch submissions, bug reports, and design issues. Please <em>do not</em> use it for XML support, XSLT support, XSL-FO support, or even FOP support.
-Resources for these and other topics can be found on the <link href="../resources.html">FOP User Resources</link> page.
+Appropriate mailing lists for these topics can be found on the <link href="../maillist.html">FOP Mailing List</link> page.
</p>
<ul>
<li>
</li>
</ul>
</li>
- <li>Before posting questions to any list, see "<link href="../resources.html#mailing-lists-general">General Information</link>".</li>
+ <li>Before posting questions to any list, see "<link href="../maillist.html#general">General Information</link>".</li>
<li>
See <link href="http://xml.apache.org/mail.html#fop-dev_fop-cvs">Apache XML Mailing Lists</link>
for detailed subscription information.
<p>When changes are committed to the code repository, a record of the diffs is emailed to the fop-cvs mailing list. FOP developers are encouraged to subscribe to this list because it helps in following the progress of the project.
</p>
<ul>
+ <li>Review the archives at <link href="http://marc.theaimsgroup.com/?l=fop-cvs&r=1&w=2">Mailing list ARChives</link> (MARC) at the AIMS group (search).</li>
<li>Subscribe by sending an email to <link href="mailto:fop-cvs-subscribe@xml.apache.org">fop-cvs-subscribe@xml.apache.org</link>.</li>
</ul>
</section>
</ul>
<p>One of the committers will test your patch and consider its implications for the project. They will then either commit it to the repository or explain on the issue why they did not. Depending on the work load and skill-sets of the various committers, it may take some time before a a submitted patch is addressed.</p>
</section>
- <section id="code-conventions">
- <title>Coding Conventions</title>
- <p>As mentioned in <link href="http://xml.apache.org/source.html">Apache XML Project Guidelines</link>,
- <strong>all Java Language source code in the repository must be written in conformance to the</strong>
- <link href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html">Code Conventions
- for the Java Programming Language</link> as published by Sun. Additionally we agreed on 4
- spaces (no tabs) for indenting.</p>
- <p>If you don't like those conventions, just use your own standards while developing and reformat the source before
- committing with a tool like <link href="http://astyle.sourceforge.net/">astyle</link> (Artistic Style).
- </p>
- </section>
</section>
</body>
</document>
+++ /dev/null
-<?xml version="1.0" standalone="no"?>
-
-<!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
-
-<document>
- <header>
- <title>PDF (Developer Information)</title>
- </header>
- <body>
- <section>
- <title>Resources</title>
- <ul>
- <li><link href="http://partners.adobe.com/asn/developer/technotes/acrobatpdf.html">Acrobat/PDF Technical Notes</link></li>
- </ul>
- </section>
- </body>
-</document>
-
-<!-- Last Line of $RCSfile$ -->
+++ /dev/null
-<?xml version="1.0" standalone="no"?>
-
-<!-- $Id$ -->
-<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN"
- "http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd">
-
-<document>
- <header>
- <title>Postscript (Developer Information)</title>
- </header>
- <body>
- <section>
- <title>Resources</title>
- <ul>
- <li><link href="http://partners.adobe.com/asn/developer/technotes/postscript.html">Postscript Technical Notes</link></li>
- </ul>
- </section>
- </body>
-</document>
-
-<!-- Last Line of $RCSfile$ -->
projects / xmlgraphics-fop.git / commitdiff