vmote       2003/04/05 11:51:49

  Modified:    src/documentation/content/xdocs compliance.xml gethelp.xml
  minor corrections
  Revision  Changes    Path
  1.8       +1 -1      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.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- compliance.xml    3 Apr 2003 15:29:33 -0000       1.7
  +++ compliance.xml    5 Apr 2003 19:51:49 -0000       1.8
  @@ -263,7 +263,7 @@
             <level-3 name="scaling-method" citation="§7.14.11" 
extURL="slice7.html#scaling-method" compliance-level="2" comply="no"/>
             <level-3 name="width" citation="§7.14.12" extURL="slice7.html#width" 
compliance-level="1" comply="yes"/>
  -        <level-2 name="Block and Line-related Properties" citation="§7.15 " 
  +        <level-2 name="Block and Line-related Properties" citation="§7.15" 
             <level-3 name="hyphenation-keep" citation="§7.15.1" 
extURL="slice7.html#hyphenation-keep" compliance-level="2" comply="no"/>
             <level-3 name="hyphenation-ladder-count" citation="§7.15.2" 
extURL="slice7.html#hyphenation-ladder-count" compliance-level="2" comply="no"/>
             <level-3 name="last-line-end-indent" citation="§7.15.3" 
extURL="slice7.html#last-line-end-indent" compliance-level="2" comply="no"/>
  1.5       +9 -9      xml-fop/src/documentation/content/xdocs/gethelp.xml
  Index: gethelp.xml
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/gethelp.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- gethelp.xml       5 Apr 2003 19:29:26 -0000       1.4
  +++ gethelp.xml       5 Apr 2003 19:51:49 -0000       1.5
  @@ -11,41 +11,41 @@
   However, to make wise use of its limited resources, support must be primarily 
   Go through the following checklist sequentially to determine what kind of help you 
   and where to get it:</p>
  -    <section>
  +    <section id="underlying">
         <title>Understand Underlying Technologies</title>
         <p>If you have a questions about XML, XSLT, or XSL-FO that are not directly 
related to FOP, please consult resources that are appropriate for those questions.
   FOP is an implementation of these technologies, and when you use FOP, there is a 
presumption that you have a working understanding of them.
   We have included several useful links on our <link 
href="resources.html">Resources</link> page that may help you get started.
  -    <section>
  +    <section id="compliance">
         <title>Review FOP's Standards Compliance</title>
         <p>FOP is a work in progress, and does not yet fully comply with the W3C 
XSL-FO standard.
   The developers track which standard requirements have been implemented, and have 
documented these capabilities on the <link href="compliance.html">Compliance</link> 
   If this document appears to be in error, continue down this checklist so that 
either the document or the software can be corrected.
   Otherwise, please do not submit mailing list questions or bug reports regarding 
features documented in the standard.</p>
  -    <section>
  +    <section id="doc">
         <title>Read the Documentation</title>
         <p>Review the documentation pages on this site.
   There is information about how to run FOP, how to embed it, how to add custom fonts 
  -    <section>
  +    <section id="faq">
         <title>Check the FAQs</title>
         <p>Consult the <link href="faq.html">Frequently Asked Questions (FAQ)</link> 
to see if your question has already been answered.</p>
  -    <section>
  +    <section id="user-archive">
         <title>Review FOP User Mailing List Archive</title>
         <p>It is possible that your question has already been answered but has not 
yet found its way into the FAQ.
   Links to the FOP User mailing list archives are on the <link 
href="resources.html#mailing-lists-fop-user">Resources</link> page.
  -    <section>
  +    <section id="existing-issue">
         <title>Look for an Existing Issue Report</title>
         <p>See <link href="bugs.html#issues_existing">Reported Issues</link> for 
instructions on how to use the list of open issues. Review these open issues to see if 
any match your concerns.
   If so, please do not post a mailing list question or report another issue, as these 
will only slow the development team down.</p>
  -    <section>
  +    <section id="user-mailing-list">
         <title>Submit Question to FOP User Mailing List</title>
           <li>Subscription information is on the <link 
href="resources.html#mailing-lists-fop-user">Resources</link> page.</li>
  @@ -61,13 +61,13 @@
           <li>Instead of attaching large PDF files or screen shots, include a small 
B&amp;W GIF, JPG or PNG of the area of interest.</li>
  -    <section>
  +    <section id="enter-issue">
         <title>Enter an Issue Report</title>
         <p>If, and only if, you have followed all of the above steps, and believe 
that there is a bug or needed feature that you would like to report, please enter an 
issue in Bugzilla. Never use Bugzilla to post questions, only to enter issues that 
have already been asked on the user mailing list.</p>
         <p>See <link href="bugs.html#issues_new">Reporting New Issues</link> for 
detailed instructions on how to enter an issue.
  -    <section>
  +    <section id="how-to-help">
         <title>Find Out How <em>You</em> Can Help</title>
       <p>As stated above, the FOP development team is a limited resource. Most make 
their livings doing things other than writing and supporting FOP. Perhaps you need a 
feature from the XSL-FO standard to be implemented right away, or a bug fixed, or a 
new output format, or .... If so, there are several ways that you can help:</p>

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

Reply via email to