From 81d5469fd47ab83a50ee83c0279586e4df45469b Mon Sep 17 00:00:00 2001
From: William Victor Mote
Date: Sat, 5 Apr 2003 19:29:26 +0000
Subject: [PATCH] Fix link to "Asking Questions ..." Normalize and clean up
content.
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196208 13f79535-47bb-0310-9956-ffa450edef68
---
src/documentation/content/xdocs/bugs.xml | 36 ++---
src/documentation/content/xdocs/gethelp.xml | 132 +++++++++---------
src/documentation/content/xdocs/resources.xml | 23 +--
3 files changed, 89 insertions(+), 102 deletions(-)
diff --git a/src/documentation/content/xdocs/bugs.xml b/src/documentation/content/xdocs/bugs.xml
index 8effa92e4..767d94b7f 100644
--- a/src/documentation/content/xdocs/bugs.xml
+++ b/src/documentation/content/xdocs/bugs.xml
@@ -30,40 +30,20 @@ an email as changes are made to the issue.
Unreported Issues (Reporting New Issues)
User reports of bugs and requests for enhancements are extremely
important parts of FOP development, and we appreciate the time you take to help
-us track these issues down.
-To help us ensure that the bug database is as useful as it should be, please
-use the following checklist if you are considering reporting a new issue:
-
-
Is your issue really a request to comply with some aspect of the
-XSL-FO standard?
-If so, please do not enter a bug report.
-The developers already carefully track which standard requirements have been
-implemented.
-Other enhancement requests are welcome, but please be sure to mark
-the issue as an enhancement.
-
Is your issue addressed by an FAQ? If so, please do not
-enter a bug report unless the FAQ did not adequately address your issue.
-
Has this issue already been reported? If so, please do not
-report it again, as this will only slow the development team down.
-See section above for a list of issues that have already been reported.
-
Do you know how to write a good bug report?
-Please review the
-Apache Bug
-Writing Guidelines before submitting your report.
-
If, and only if, you have passed all of the above steps, please
-enter a new bug report at
-The
-FOP bug database (Bugzilla).
+us track these issues down.
+
+
To help us ensure that the bug database is as useful as it should be, please
+use the Getting Help checklist to determine whether a bug report should be entered.
+
Review the Apache Bug Writing Guidelines before submitting your report.
+
Enter a new issue report at The FOP issue database (Bugzilla).
You will be asked to login to an existing Bugzilla account or to create a new
one.
When entering the bug report, please make your description complete and concise.
If appropriate, attach a minimal fo file to your report which demonstrates the
problem.
-
After submission, a copy of your bug report will be automatically
+
After submission, a copy of your bug report will be automatically
sent to the FOP developer discussion list.
-
+
-
- FOP Relevant Specifications and Links
-
- Mailing Lists (and archives)
+
+ Mailing Lists and Archives
+
+ General Information
For the Apache mailing lists, see
Apache XML Mailing Lists
for detailed subscription information.
-
+
Before posting questions to the lists, review "How To Ask Questions The Smart Way".
+
+ FOP User Mailing List
Use this forum to discuss topics of interest to FOP users.
@@ -56,7 +58,7 @@ To unsubscribe: Send email to
FOP Developer Mailing List
Use this forum to discuss topics related to FOP development,
@@ -90,7 +92,7 @@ To unsubscribe: Send email to
XSL:FO Mailing List (at W3C)
Use this forum to ask general XSL-FO questions.
@@ -105,7 +107,7 @@ Subscription administration information can be found at
Specifications
@@ -140,7 +142,7 @@ Subscription administration information can be found at
Tutorials/Articles
@@ -160,7 +162,7 @@ Subscription administration information can be found at
Related/Useful Products