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 ke...@apache.org on 2001/08/14 10:40:50 UTC
cvs commit: xml-fop/docs/xml-docs/fop configuration.xml embedding.xml readme.xml todo.xml
keiron 01/08/14 01:40:50
Modified: docs/xml-docs/fop configuration.xml embedding.xml readme.xml
todo.xml
Log:
some minor updates, typos, a bit more info on embedding
new version number
Revision Changes Path
1.3 +2 -1 xml-fop/docs/xml-docs/fop/configuration.xml
Index: configuration.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/configuration.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- configuration.xml 2000/12/14 18:11:27 1.2
+++ configuration.xml 2001/08/14 08:40:50 1.3
@@ -12,7 +12,8 @@
configuration files are xml files, so keep them at least well-formed ;-)
</p>
<p>The file userconfig.xml is not read automatically, but the user must specify its use on
- the command line. See <jump href="running.html">Running Fop</jump> for details.
+ the command line. See <jump href="running.html">Running Fop</jump>
+ or <jump href="embedding.html">Embedding Fop</jump> for details.
</p>
</s2>
<s2 title="setting up hyphenation">
1.10 +6 -0 xml-fop/docs/xml-docs/fop/embedding.xml
Index: embedding.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/embedding.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- embedding.xml 2001/08/10 13:57:32 1.9
+++ embedding.xml 2001/08/14 08:40:50 1.10
@@ -28,6 +28,12 @@
driver.run();
]]></source>
+ <p>To setup the user config file you can do the following
+ </p>
+ <source><![CDATA[
+ userConfigFile = new File(userConfig);
+ options = new Options(userConfigFile);
+]]></source>
<p>Once the Driver is set up, the render method
is called. Depending on whether DOM or SAX is being used, the
1.10 +1 -1 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.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- readme.xml 2001/06/06 12:34:07 1.9
+++ readme.xml 2001/08/14 08:40:50 1.10
@@ -11,7 +11,7 @@
like XT or Xalan) or can be passed in memory as a DOM Document or (in
the case of XT) SAX events.
</p>
- <p>The latest version of Fop is 0.18 and it supports the xsl:fo candidate release.
+ <p>The latest version of Fop is 0.20.1 and it supports the xsl:fo candidate release.
You can <jump href="download.html">download</jump>
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
1.2 +8 -1 xml-fop/docs/xml-docs/fop/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/xml-fop/docs/xml-docs/fop/todo.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- todo.xml 2001/08/10 13:57:32 1.1
+++ todo.xml 2001/08/14 08:40:50 1.2
@@ -41,6 +41,12 @@
values properly (including ones that change depending on the element) and
all possible values.
</p>
+ <p>
+To see if a property is implemented then look in the src/codegen/foproperties.xml file.
+ </p>
+ <p>
+To see if a particular element uses this property then look in the element code. This is generally found in the package org.apache.fop.fo.flow.*.
+ </p>
</s3>
<s3 title="Property Resolution">
<p>
@@ -118,8 +124,9 @@
</s3>
<s3 title="stream encoding">
<p>
-support for different encoding on different types of streams
+Support for different encoding on different types of streams
in pdf document.
+For example images.
</p>
</s3>
<s3 title="svg features">
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org