From: Christian Geisert <chrisg@apache.org>
Date: Tue, 10 Dec 2002 09:38:17 +0000 (+0000)
Subject: Updated docs from trunk
X-Git-Tag: fop-0_20_5rc~4
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=d3dfbafc1e46001f6f0ed7e17e84071de272afbd;p=xmlgraphics-fop.git

Updated docs from trunk


git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/fop-0_20_2-maintain@195758 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/src/documentation/content/xdocs/compliance.xml b/src/documentation/content/xdocs/compliance.xml
index 3a3a3c940..c8ef48700 100644
--- a/src/documentation/content/xdocs/compliance.xml
+++ b/src/documentation/content/xdocs/compliance.xml
@@ -165,14 +165,33 @@ want it to.</comment>
           <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 @@ want it to.</comment>
         <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 @@ want it to.</comment>
           <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"/>
diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml
index 0ced0b6d1..ccdabc69f 100644
--- a/src/documentation/content/xdocs/faq.xml
+++ b/src/documentation/content/xdocs/faq.xml
@@ -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 @@ transformer.transform(xmlsource, new SAXResult(driver.getContentHandler()));</so
         <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&amp;m=102002975028427&amp;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>
@@ -1341,6 +1352,13 @@ class rendtest {
         </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&amp;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>
       <question>(XML) Complaints about &amp;nbsp;. How do I get a non-breaking
       space in FO?</question>
diff --git a/src/documentation/content/xdocs/news.xml b/src/documentation/content/xdocs/news.xml
index 9a45b8c14..8827f8ebe 100644
--- a/src/documentation/content/xdocs/news.xml
+++ b/src/documentation/content/xdocs/news.xml
@@ -7,6 +7,10 @@
     <title>News</title>
   </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>
diff --git a/src/documentation/content/xdocs/status.xml b/src/documentation/content/xdocs/status.xml
index 48e866650..c6dd8cb04 100644
--- a/src/documentation/content/xdocs/status.xml
+++ b/src/documentation/content/xdocs/status.xml
@@ -73,7 +73,7 @@ to predict any dates.
   <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.