xmlgraphics-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From c...@apache.org
Subject svn commit: r1415921 - /xmlgraphics/site/trunk/content/fop/bugs.mdtext
Date Sat, 01 Dec 2012 06:21:39 GMT
Author: clay
Date: Sat Dec  1 06:21:39 2012
New Revision: 1415921

URL: http://svn.apache.org/viewvc?rev=1415921&view=rev
Log:
fixing nesting

Modified:
    xmlgraphics/site/trunk/content/fop/bugs.mdtext

Modified: xmlgraphics/site/trunk/content/fop/bugs.mdtext
URL: http://svn.apache.org/viewvc/xmlgraphics/site/trunk/content/fop/bugs.mdtext?rev=1415921&r1=1415920&r2=1415921&view=diff
==============================================================================
--- xmlgraphics/site/trunk/content/fop/bugs.mdtext (original)
+++ xmlgraphics/site/trunk/content/fop/bugs.mdtext Sat Dec  1 06:21:39 2012
@@ -25,11 +25,11 @@ User reports of bugs and requests for en
 
 - Enter a new issue report at [The FOP issue database (Bugzilla)](http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop)
. 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 the issue involves
a specific input or output file, then please include the following information in the bug
report (preferably as one or more attachments):
 
-   - an input XSL-FO file (if you generate the XSL-FO file from an input XML using XSLT,
then please directly provide the result of the transformation--the XSL-FO output--not the
XML input and XSLT). Please try and make the XSL-FO input as small as possible; Ideally it
would contain nothing more than the minimum needed to demonstrate the problem. By doing this
you increase your chance that a developer will take the time to look at your file.
-   - a resulting output file, preferably in PDF format, unless the issue being reported involves
a different output format; In which case please provide the output in that format;
-   - a copy of the FOP configuration file you used (e.g., `fop.xconf`), if applicable;
-   - if FOP was invoked using the command line (or an equivalent), then a dump of both the
input command line and any console output (stderr or stdout) produced; if the report involves
an exception, be sure to include the full stack trace;
-   - information describing the version of FOP you are using and the platform (and OS) on
which you are invoking FOP;
-   - if the report applies to the use of a specific font other than one of the built-in,
base 14 fonts, then information that describes where to obtain the font. If the font is not
freely available, please describe your problem on the [fop-users](maillist.html#fop-user "FOP
users mailing list") mailing list, where a developer may step up and ask you to send them
the font privately for investigation purpose.
-
+    - an input XSL-FO file (if you generate the XSL-FO file from an input XML using XSLT,
then please directly provide the result of the transformation--the XSL-FO output--not the
XML input and XSLT). Please try and make the XSL-FO input as small as possible; Ideally it
would contain nothing more than the minimum needed to demonstrate the problem. By doing this
you increase your chance that a developer will take the time to look at your file.
+    - a resulting output file, preferably in PDF format, unless the issue being reported
involves a different output format; In which case please provide the output in that format;
+    - a copy of the FOP configuration file you used (e.g., `fop.xconf`), if applicable;
+    - if FOP was invoked using the command line (or an equivalent), then a dump of both the
input command line and any console output (stderr or stdout) produced; if the report involves
an exception, be sure to include the full stack trace;
+    - information describing the version of FOP you are using and the platform (and OS) on
which you are invoking FOP;
+    - if the report applies to the use of a specific font other than one of the built-in,
base 14 fonts, then information that describes where to obtain the font. If the font is not
freely available, please describe your problem on the [fop-users](maillist.html#fop-user "FOP
users mailing list") mailing list, where a developer may step up and ask you to send them
the font privately for investigation purpose.
+ 
 - After submission, a copy of your bug report will be automatically sent to the FOP developer
discussion list.



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: commits-help@xmlgraphics.apache.org


Mime
View raw message