You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-commits@xmlgraphics.apache.org by fo...@locus.apache.org on 2000/07/21 01:26:52 UTC
cvs commit: xml-fop/docs/xml-docs/fop bugs.xml compiling.xml examples.xml implemented.xml readme.xml specs.xml
fotis 00/07/20 16:26:51
Modified: docs/xml-docs/fop bugs.xml compiling.xml examples.xml
implemented.xml readme.xml specs.xml
Log:
update docs to Fop 0.14
Revision Changes Path
1.2 +19 -9 xml-fop/docs/xml-docs/fop/bugs.xml
Index: bugs.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/bugs.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bugs.xml 2000/06/23 13:16:43 1.1
+++ bugs.xml 2000/07/20 23:26:47 1.2
@@ -6,15 +6,25 @@
<s1 title="Bugs">
<s2 title="How to report bugs">
- <p>Please use the bug reporting system <jump href="http://xml.apache.org/bugs/">bugzilla
- </jump>, which is part of xml.apache.org.</p>
+ <p>Please report bugs to the discussion list fop-dev@xml.apache.org and put
+ the word [BUG] in the subject line. </p>
+ <p>Please make sure, before you report a bug, that it is not mentioned in the FAQ or
+ in the list of open bugs in the file STATUS in the start directory of the Fop
+ distribution. </p>
+ <p>Please make your description as concise as possible and send an example fo
+ file with your report, which just demonstrates the problem. Thanks for your help!</p>
</s2>
- <s2 title="Some bugs">
- <p>Colour not continued onto subsequent pages, if coloured block goes over page.
- </p>
- <p>Each page-sequence begins its page numbering with the number 1 (unless another integer is
- specified in the initial-page-number attribute). The W3C recommendations says that
- the default (auto) for initial-page-number is: The first page sequence starts with 1. For any further
- fo:page-sequence the initial number will be one greater than the last number for that sequence.</p>
+ <s2 title="Known bugs">
+ <ul>
+ <li>Colour not continued onto subsequent pages, if coloured block goes over page.</li>
+ <li>SVG linearGradients don't appear the same as in other SVG Viewers</li>
+ <li>colour not continued onto subsequent pages if coloured block goes over page </li>
+ <li>no SVG support in AWTCommandLine </li>
+ <li>keep-next doesn't work and doubles the text lines which should be moved to the next page</li>
+ <li>pdf files created with Fop don't print correctly on postscript printers</li>
+ <li>lists containing list do not keep their indentation correctly over a page boundary</li>
+ <li>id references are marked as illegally doubled, if they are first layouted at the bottom of a page
+ and then moved to the next page </li>
+ </ul>
</s2>
</s1>
1.2 +3 -4 xml-fop/docs/xml-docs/fop/compiling.xml
Index: compiling.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/compiling.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- compiling.xml 2000/06/23 13:16:43 1.1
+++ compiling.xml 2000/07/20 23:26:47 1.2
@@ -33,14 +33,13 @@
setting. It is used by the compilation software.</p>
</s3>
<s3 title="Settings in your classpath">
- <p>If you need PDFOutputHandler (an extension, which calls Fop from the XSLT processor XT) you also
- must have xp.jar and xt.jar (both can be found at <jump href="http://www.jclark.com/xml/">http://www.jclark.com/xml/
- </jump> in your classpath.
+ <p>If you want Fop to use the image library jimi, it should be in your classpath during
+ compilation.
</p>
<p>A CLASSPATH for a complete compilation of Fop could look like this, if all these jar files are in
a directory called jars (example uses windows syntax):
</p>
- <p><code>set CLASSPATH=\jars\xp.jar;\jars\xt.jar;\jars\xalan.jar;\jars\xerces.jar;\jars\bsf.jar
+ <p><code>set CLASSPATH=\jars\xalan.jar;\jars\xerces.jar;\jars\bsf.jar;\jars\jimi.jar;
</code></p>
</s3>
</s2>
1.2 +0 -3 xml-fop/docs/xml-docs/fop/examples.xml
Index: examples.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/examples.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- examples.xml 2000/06/23 13:16:43 1.1
+++ examples.xml 2000/07/20 23:26:47 1.2
@@ -7,9 +7,6 @@
<p>Examples for the use of xsl:fo can be found in the Fop distribution in
the subdirectory /docs/examples/fo.
</p>
- <p>Please be warned: At the moment FOP only supports the
- XSL Working Draft 21 April 1999 and the examples are also following this version.
- </p>
<p>At the moment the following files are part of the distribution:</p>
<ul>
<li>normal.fo - a very simple file showing the use of a 2 level of headings, normal text and a header.
1.4 +1 -1 xml-fop/docs/xml-docs/fop/implemented.xml
Index: implemented.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/implemented.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- implemented.xml 2000/07/20 16:49:15 1.3
+++ implemented.xml 2000/07/20 23:26:47 1.4
@@ -6,7 +6,7 @@
<s1 title="Features">
<s2 title="What's Implemented?">
<p>The following formatting objects and properties of the xsl-fo
- working draft (21 Apr 1999) are implemented. Please have also a look at the
+ working draft (27 March 2000) are implemented. Please have also a look at the
section on <jump href="limitations.html">limitations</jump>
</p>
</s2>
1.2 +4 -2 xml-fop/docs/xml-docs/fop/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/readme.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- readme.xml 2000/06/23 13:16:43 1.1
+++ readme.xml 2000/07/20 23:26:48 1.2
@@ -1,7 +1,7 @@
<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "sbk:/style/dtd/document.dtd">
-<!-- $Id: readme.xml,v 1.1 2000/06/23 13:16:43 fotis Exp $ -->
+<!-- $Id: readme.xml,v 1.2 2000/07/20 23:26:48 fotis Exp $ -->
<!--
Authors:
James Tauber
@@ -22,7 +22,9 @@
the case of XT) SAX events.
</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>.
+ <jump href="http://xml.apache.org/fop">http://xml.apache.org/fop</jump>. A list
+ of the committers to this project and the tasks they are working on can be found
+ in the file <jump href="http://xml.apache.org/websrc/cvsweb.cgi/xml-fop/">Status</jump>
</p>
</s2>
1.3 +1 -0 xml-fop/docs/xml-docs/fop/specs.xml
Index: specs.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/specs.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- specs.xml 2000/07/20 16:49:15 1.2
+++ specs.xml 2000/07/20 23:26:49 1.3
@@ -6,6 +6,7 @@
<s1 title="FOP Relevant Specifications">
<ul>
<li><jump href="http://www.w3.org/TR/WD-xsl/">Latest XSL-FO Working Draft (27 March 2000)</jump></li>
+ <li><jump href="http://www.renderx.com/Tests/validator/fo2000.dtd.html">A dtd for the XSL-FO Working Draft (27 March 2000) provided by N. Grigoriev from RenderX</jump></li>
<li><jump href="http://www.w3.org/TR/1999/WD-xsl-19990421/">XSL-FO Working Draft 21 Apr 1999 </jump></li>
<li><jump href="http://www.w3.org/TR/SVG">Latest SVG Working draft</jump></li>
<li><jump href="http://www.w3.org/TR/2000/WD-SVG-20000629/index.html">Supported SVG Working Draf</jump></li>