Add FAQ for FO validation, and refer other FAQs to it.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@195755 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 9 insertions, 2 deletions

diff --git a/src/documentation/content/xdocs/faq.xml b/src/documentation/content/xdocs/faq.xml
index c730407ec..ffca87748 100644
--- a/src/documentation/content/xdocs/faq.xml
+++ b/src/documentation/content/xdocs/faq.xml
@@ -301,8 +301,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
@@ -1341,6 +1341,13 @@ class rendtest {
       </answer>
     </faq>
     <faq>
+      <question id="FO-validate">(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>
       <answer>