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 ch...@apache.org on 2002/12/10 10:38:18 UTC
cvs commit: xml-fop/src/documentation/content/xdocs compliance.xml faq.xml news.xml status.xml
chrisg 2002/12/10 01:38:18
Modified: src/documentation/content/xdocs Tag: fop-0_20_2-maintain
compliance.xml faq.xml news.xml status.xml
Log:
Updated docs from trunk
Revision Changes Path
No revision
No revision
1.4.2.2 +29 -9 xml-fop/src/documentation/content/xdocs/compliance.xml
Index: compliance.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compliance.xml,v
retrieving revision 1.4.2.1
retrieving revision 1.4.2.2
diff -u -r1.4.2.1 -r1.4.2.2
--- compliance.xml 9 Dec 2002 02:27:50 -0000 1.4.2.1
+++ compliance.xml 10 Dec 2002 09:38:17 -0000 1.4.2.2
@@ -165,14 +165,33 @@
<level-3 name="border-right-color" compliance-level="1" comply="yes"/>
<level-3 name="border-right-style" compliance-level="1" comply="yes"/>
<level-3 name="border-right-width" compliance-level="1" comply="yes"/>
- <level-3 name="padding-before" compliance-level="1" comply="yes"/>
- <level-3 name="padding-after" compliance-level="1" comply="yes"/>
- <level-3 name="padding-start" compliance-level="1" comply="yes"/>
- <level-3 name="padding-end" compliance-level="1" comply="yes"/>
- <level-3 name="padding-top" compliance-level="1" comply="yes"/>
- <level-3 name="padding-bottom" compliance-level="1" comply="yes"/>
- <level-3 name="padding-left" compliance-level="1" comply="yes"/>
- <level-3 name="padding-right" compliance-level="1" comply="yes"/>
+ <level-3 name="padding-before" compliance-level="1" comply="yes">
+ <comment>only one value allowed</comment>
+ <comment>only implemented for blocks</comment>
+ <comment>can't be used to make extra space (use indents + spaces instead)</comment>
+ <comment>can be used to control how much the background-color extends beyond the content rectangle</comment>
+ </level-3>
+ <level-3 name="padding-after" compliance-level="1" comply="yes">
+ <comment>same limitations as padding-before</comment>
+ </level-3>
+ <level-3 name="padding-start" compliance-level="1" comply="yes">
+ <comment>same limitations as padding-before</comment>
+ </level-3>
+ <level-3 name="padding-end" compliance-level="1" comply="yes">
+ <comment>same limitations as padding-before</comment>
+ </level-3>
+ <level-3 name="padding-top" compliance-level="1" comply="yes">
+ <comment>same limitations as padding-before</comment>
+ </level-3>
+ <level-3 name="padding-bottom" compliance-level="1" comply="yes">
+ <comment>same limitations as padding-before</comment>
+ </level-3>
+ <level-3 name="padding-left" compliance-level="1" comply="yes">
+ <comment>same limitations as padding-before</comment>
+ </level-3>
+ <level-3 name="padding-right" compliance-level="1" comply="yes">
+ <comment>same limitations as padding-before</comment>
+ </level-3>
</level-2>
<level-2 name="Common Font Properties">
<level-3 name="font-family" compliance-level="1" comply="yes"/>
@@ -233,7 +252,7 @@
<level-2 name="Area Dimension Properties">
<level-3 name="block-progression-dimension" compliance-level="1" comply="no"/>
<level-3 name="content-height" compliance-level="2" comply="no"/>
- <level-3 name="content-width" compliance-level="1" comply="no"/>
+ <level-3 name="content-width" compliance-level="2" comply="no"/>
<level-3 name="height" compliance-level="1" comply="yes"/>
<level-3 name="inline-progression-dimension" compliance-level="1" comply="no"/>
<level-3 name="max-height" compliance-level="3" comply="no"/>
@@ -374,6 +393,7 @@
<level-3 name="ends-row" compliance-level="2" comply="no"/>
<level-3 name="number-columns-repeated" compliance-level="1" comply="no"/>
<level-3 name="number-columns-spanned" compliance-level="1" comply="yes"/>
+ <level-3 name="number-rows-spanned" compliance-level="1" comply="yes"/>
<level-3 name="starts-row" compliance-level="2" comply="no"/>
<level-3 name="table-layout" compliance-level="2" comply="no"/>
<level-3 name="table-omit-footer-at-break" compliance-level="2" comply="yes"/>
1.3.2.3 +32 -14 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.3.2.2
retrieving revision 1.3.2.3
diff -u -r1.3.2.2 -r1.3.2.3
--- faq.xml 9 Dec 2002 03:07:50 -0000 1.3.2.2
+++ faq.xml 10 Dec 2002 09:38:17 -0000 1.3.2.3
@@ -302,8 +302,8 @@
whether you got them right.
</p>
<p>
- You can use the <link>FOP DTD</link> or <link>FOP Schema</link> to
- validate your soure. This will catch most, but still not all problems.
+ You may find it helpful to use the <link href="#FO-validate">validation tools</link> to validate your
+FO document. This will catch most problems, but should not be relied upon to catch all.
</p>
<p>
If you use XSLT, problems in your style sheet and in your source XML
@@ -874,24 +874,35 @@
<p>(Still applicable in 0.20.3?)</p>
</answer>
</faq>
+ <faq id="PDF-postprocess">
+ <question>What tools are available for post-processing my PDF document?</question>
+ <answer>
+ <ul>
+ <li>The most popular one that we are aware of is <link href="http://www.lowagie.com/iText">iText</link>, which has tools for adding security features, document properties, watermarks, and many other features to PDF files. See also Joerg Pietschmann's <link href="http://marc.theaimsgroup.com/?l=fop-dev&m=102002975028427&w=2">posting on PDF Encryption</link> for an example of Java application using iText.</li>
+ <li>You can use Adobe Acrobat (the full version, not the Reader) to process the file manually or with scripting that it supports.</li>
+ </ul>
+ </answer>
+ </faq>
<faq>
- <question>PDF encryption, PDF protection (read-only)</question>
+ <question>How do I add security features (encryption, for example) to my PDF document?</question>
<answer>
- <p>use some other tool to postprocess the PDF (itext, or something?)</p>
+ <p>FOP does not currently support this feature. Possible workarounds include those mentioned in the <link href="#PDF-postprocess">PDF Post-Processing FAQ</link>.</p>
</answer>
</faq>
<faq>
- <question>Watermarks</question>
+ <question>How do I add document properties (title, author, etc.) to my PDF document?</question>
<answer>
- <p> Answer: see 3.3, or use a a region overlapping the flowing text and put
- an image there:
-</p>
- <p> > From: Trevor_Campbell@kaz.com.au
- Use the region-before. Make it large enough to contain your image and then
- include a block (and if required an absolutely positioned block-container)
- with your image in the static-content for the region-before.
- Could use some code here...
- </p>
+ <p>FOP does not currently support this feature. Possible workarounds include those mentioned in the <link href="#PDF-postprocess">PDF Post-Processing FAQ</link>.</p>
+ </answer>
+ </faq>
+ <faq>
+ <question>How do I add watermarks to my PDF document?</question>
+ <answer>
+ <p>FOP does not currently support this feature. Possible workarounds:</p>
+ <ul>
+ <li>See the <link href="#PDF-postprocess">PDF Post-Processing FAQ</link>.</li>
+ <li>(submitted by Trevor_Campbell@kaz.com.au) Place an image in a region that overlaps the flowing text. For example, make region-before large enough to contain your image. Then include a block (if necessary, use an absolutely positioned block-container) containing the watermark image in the static-content for the region-before.</li>
+ </ul>
</answer>
</faq>
<faq>
@@ -1339,6 +1350,13 @@
Insert a graphic. GIF, PNG SVG, whatever.
</li>
</ul>
+ </answer>
+ </faq>
+ <faq id="FO-validate">
+ <question>(FO) How do I validate my FO document?</question>
+ <answer>
+ <p><link href="http://www.renderx.com">RenderX</link> has provided an <link href="http://www.renderx.com/Tests/validator/fo.dtd.html">Unofficial DTD for FO Documents</link>. This document may be helpful in validating general FO issues.</p>
+ <p>FOP also maintains an <link href="http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-fop/docs/foschema/fop.xsd?rev=HEAD&content-type=text/plain">Unofficial FOP Schema</link> in the FOP CVS Repository. This document can be used either to validate against the FO standard, or against the actual FOP implementation. See the notes near the beginning of the document for instructions on how to use it.</p>
</answer>
</faq>
<faq>
1.3.2.2 +4 -0 xml-fop/src/documentation/content/xdocs/news.xml
Index: news.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/news.xml,v
retrieving revision 1.3.2.1
retrieving revision 1.3.2.2
diff -u -r1.3.2.1 -r1.3.2.2
--- news.xml 9 Dec 2002 02:27:50 -0000 1.3.2.1
+++ news.xml 10 Dec 2002 09:38:17 -0000 1.3.2.2
@@ -8,6 +8,10 @@
</header>
<body>
<section>
+ <title>22 November 2002 - New Committer</title>
+ <p>Welcome Victor Mote!</p>
+ </section>
+ <section>
<title>9 November 2002 - New Committer</title>
<p>Welcome Oleg Tkachenko!</p>
</section>
1.5.2.2 +1 -1 xml-fop/src/documentation/content/xdocs/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/status.xml,v
retrieving revision 1.5.2.1
retrieving revision 1.5.2.2
diff -u -r1.5.2.1 -r1.5.2.2
--- status.xml 9 Dec 2002 02:27:50 -0000 1.5.2.1
+++ status.xml 10 Dec 2002 09:38:17 -0000 1.5.2.2
@@ -73,7 +73,7 @@
<section>
<title>Maintenance Status</title>
<p>
-Latest maintenance release was FOP 0.20.5 on 24th November 2002.
+Latest maintenance release will be FOP 0.20.5 on TBA.
See <link href="relnotes.html">release notes</link> for more
details. Releases will be made periodically to address minor bugs
and compatibility.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-cvs-help@xml.apache.org