vmote 2003/03/31 15:10:59
Modified: src/documentation/content/xdocs book.xml faq.xml index.xml
src/documentation/content/xdocs/dev index.xml
Removed: src/documentation/content/xdocs implemented.xml
limitations.xml
Log:
Remove "limitations" and "implemented" pages, and all references thereto.
Revision Changes Path
1.11 +0 -2 xml-fop/src/documentation/content/xdocs/book.xml
Index: book.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/book.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- book.xml 10 Mar 2003 18:09:13 -0000 1.10
+++ book.xml 31 Mar 2003 23:10:59 -0000 1.11
@@ -31,8 +31,6 @@
<menu-item label="Ant task" href="anttask.html"/>
<menu-item label="Output Formats" href="output.html"/>
<menu-item label="Compliance" href="compliance.html"/>
- <menu-item label="Implemented" href="implemented.html"/>
- <menu-item label="Limitations" href="limitations.html"/>
</menu>
<menu label="Extras">
1.16 +8 -5 xml-fop/src/documentation/content/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/faq.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- faq.xml 26 Mar 2003 23:34:55 -0000 1.15
+++ faq.xml 31 Mar 2003 23:10:59 -0000 1.16
@@ -1660,11 +1660,14 @@
</ul>
</li>
<li>
- Something doesn't work with FOP but works with another formatter
- (AntennaHouse, PassiveTex). Check whether this is already mentioned
- in the release notes, the FOP limitations document or the FAQ. Post
- to fop-dev or open a bug on <link
- href="http://nagoya.apache.org";>bugzilla</link>.
+ In the case where something works properly with another formatter,
+ (AntennaHouse, PassiveTex, etc.) but doesn't work with FOP, please
+ check the <link href="relnotes.html">Release Notes</link>, the
+ <link href="compliance.html">FOP Standards Compliance</link> document,
+ and the remaining FAQ in this document. If not found there, look at the
+ list of <link href="bugs.html#issues_existing">Bugs Already
Reported</link>.
+ If not found there, please post a question on the fop-user mailing list
+ or <link href="bugs.html#issues_new">Open a New Bug</link>.
</li>
<li>
Question about how to use FOP, how to perform certain tasks with FOP
1.7 +3 -4 xml-fop/src/documentation/content/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/index.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.xml 18 Jan 2003 18:04:58 -0000 1.6
+++ index.xml 31 Mar 2003 23:10:59 -0000 1.7
@@ -29,10 +29,9 @@
get you started. Pointers to introductions into xsl:fo can be found in the
<link href="resources.html">resources</link> section. Please be aware, that
FOP is at the moment not a full implementation of the basic conformance level
- of the xsl:fo standard. You can find a list of supported flow objects and
properties
- in the section <link href="implemented.html">Features</link> and in section
- <link href="limitations.html">Limitations</link> in what way this support is
- limited.
+ of the xsl:fo standard. The <link href="compliance.html">FOP Compliance
+ page</link> lists all objects and properties in the standard, and indicates
+ FOP's current compliance with those features.
</p>
<p>FOP is part of Apache's XML project. The homepage of FOP is
<link href="http://xml.apache.org/fop";>http://xml.apache.org/fop</link>.
1.6 +20 -87 xml-fop/src/documentation/content/xdocs/dev/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/dev/index.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- index.xml 29 Nov 2002 22:00:32 -0000 1.5
+++ index.xml 31 Mar 2003 23:10:59 -0000 1.6
@@ -1,90 +1,23 @@
<?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>FOP 1.0 development</title>
- </header>
- <body>
- <section>
- <title>Introduction</title>
- <p>
-These pages contain information that is relevant to the
-current development of FOP.
- </p>
- <p>FOP is the world's first print formatter driven by XSL formatting
- objects and the world's first output independent formatter. It is a
- Java application that reads a formatting object tree and then
- renders the resulting pages to a specified output. <link
href="../output.html">Output formats</link>
- currently supported are PDF, PCL, PS, SVG, XML (area tree representation),
- Print, AWT, MIF and TXT.
- The primary output target is PDF.
- </p>
- <note>
-FOP - someone who is overly concerned with style, also conveniently
-can mean Formatting Object Processor.
- </note>
- <figure width="480" height="260" src="../images/document.jpg" alt="Render
Diagram" />
- <p>The latest version of Fop is 0.20.4 and it supports the
- <jump href="http://www.w3.org/TR/2001/REC-xsl-20011015/";>XSL-FO Version 1.0
- W3C Recommendation</jump>.
- You can <link href="../download.html">download</link>
- Fop including a precompiled version, the source code and many example files
to
- get you started. Pointers to introductions into xsl:fo can be found in the
- <link href="../resources.html">resources</link> section. Please be aware,
that
- Fop is at the moment not a full implementation of the basic conformance level
- of the xsl:fo standard. You can find a list of supported flow objects and
properties
- in the section <link href="../implemented.html">Features</link> and in
section
- <link href="../limitations.html">Limitations</link> in what way this support
is
- limited.
- </p>
- <p>FOP is part of Apache's XML project. The homepage of FOP is
- <jump href="http://xml.apache.org/fop";>http://xml.apache.org/fop</jump>.
- Here you can find information about using and developing with FOP.
- </p>
- <p>Users can subscribe to [EMAIL PROTECTED] by sending an email
- to <jump href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</jump>
- this is where user specific topics are discussed.
- </p>
- </section>
- <section>
- <title>Formatting</title>
- <figure width="480" height="260" src="../images/layout.jpg" alt="Formatting
Diagram" />
-<p>
-This image is a demonstration of a two page document. The xml data on the left
-is formatted into the two pages on the right. The document contains static
areasthat appear on every page, an external graphic in this case an svg document.
-There is a footnote on the first page and a table that goes across both pages.
-</p>
-<p>
-The advantage of XSL is the ability to take an XML document and to format
-the information into a page layout. The XML document can be generated
-in any way, the most common would be to use XSLT. FOP takes the XML
-and formats the data into pages. The pages are then rendered to the
-requested output.
-</p>
-<p>
-This is a real document. The image was created by rendering the document
-to the svg renderer then putting the rendered pages into an svg document
-along with the xml.
- </p>
- </section>
- <section>
- <title>FOP Objectives</title>
- <p>
-The goals of the Apache XML FOP Project are to deliver an XSL FO->PDF formatter
that is compliant to at least the Basic
- conformance level described in the W3C Recommendation from 15 October 2001,
and that complies with the 11 March 1999 Portable Document
- Format Specification (Version 1.3) from Adobe Systems.
- </p>
-
- <p>Conformance to the XML 1.0 Recommendation, XSLT 1.0 Recommendation and the
XML Namespaces Recommendation is
- understood. Other relevant documents, such as the XPath and XLink Working
Drafts, are referenced as necessary. The FOP
- Project will attempt to use the latest version of evolving specifications.
- </p>
-
- <p>To reach this aim currently the layout system is being redesigned to
-better handle the formatting of all different types of formatting objects.
- </p>
- </section>
- </body>
- </document>
+<document>
+ <header>
+ <title>Information for FOP Developers</title>
+ </header>
+ <body>
+ <section>
+ <title>Introduction</title>
+ <p>These pages contain information that should be helpful for those
developing FOP.</p>
+ <p>For basic and user information on FOP, please visit the <link
href="http://xml.apache.org/fop";>FOP homepage</link>.</p>
+ <p>It is important to understand that there are currently three lines of
development on the FOP product:</p>
+ <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".</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>
+ </body>
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
