vmote       2002/12/09 10:23:13

  Modified:    src/documentation/content/xdocs faq.xml
  Add FAQ for FO validation, and refer other FAQs to it.
  Revision  Changes    Path
  1.4       +9 -2      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
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- faq.xml   29 Nov 2002 22:00:31 -0000      1.3
  +++ faq.xml   9 Dec 2002 18:23:13 -0000       1.4
  @@ -301,8 +301,8 @@
             whether you got them right.
  -          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 
             If you use XSLT, problems in your style sheet and in your source XML
  @@ -1338,6 +1338,13 @@
               Insert a graphic. GIF, PNG SVG, whatever.
  +      </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 
 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>

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to