From: William Victor Mote Date: Sat, 5 Apr 2003 19:51:49 +0000 (+0000) Subject: minor corrections X-Git-Tag: Root_Temp_KnuthStylePageBreaking~1667 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=3a2b98f316d780f95ef369c5aad21f7840982793;p=xmlgraphics-fop.git minor corrections git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196209 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/src/documentation/content/xdocs/compliance.xml b/src/documentation/content/xdocs/compliance.xml index 833491561..7825ea6b1 100644 --- a/src/documentation/content/xdocs/compliance.xml +++ b/src/documentation/content/xdocs/compliance.xml @@ -263,7 +263,7 @@ want it to. - + diff --git a/src/documentation/content/xdocs/gethelp.xml b/src/documentation/content/xdocs/gethelp.xml index a3321475e..0fdc2bae0 100644 --- a/src/documentation/content/xdocs/gethelp.xml +++ b/src/documentation/content/xdocs/gethelp.xml @@ -11,41 +11,41 @@ However, to make wise use of its limited resources, support must be primarily self-service. Go through the following checklist sequentially to determine what kind of help you need, and where to get it:

-
+
Understand Underlying Technologies

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 Resources page that may help you get started.

-
+
Review FOP's Standards Compliance

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 Compliance page. 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.

-
+
Read the Documentation

Review the documentation pages on this site. There is information about how to run FOP, how to embed it, how to add custom fonts etc.

-
+
Check the FAQs

Consult the Frequently Asked Questions (FAQ) to see if your question has already been answered.

-
+
Review FOP User Mailing List Archive

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 Resources page.

-
+
Look for an Existing Issue Report

See Reported Issues 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.

-
+
Submit Question to FOP User Mailing List
  • Subscription information is on the Resources page.
    • @@ -61,13 +61,13 @@ Filter out any confidential material.
  • Instead of attaching large PDF files or screen shots, include a small B&W GIF, JPG or PNG of the area of interest.
-
+
Enter an Issue Report

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.

See Reporting New Issues for detailed instructions on how to enter an issue.

-
+
Find Out How <em>You</em> Can Help

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: