svn commit: r840159 - in /websites/staging/xmlgraphics/trunk/content: ./ fop/bugs.html

[bu...@apache.org]

Author: buildbot
Date: Fri Nov 30 14:12:53 2012
New Revision: 840159

Log:
Staging update by buildbot for xmlgraphics

Modified:
    websites/staging/xmlgraphics/trunk/content/   (props changed)
    websites/staging/xmlgraphics/trunk/content/fop/bugs.html

Propchange: websites/staging/xmlgraphics/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Nov 30 14:12:53 2012
@@ -1 +1 @@
-1415641
+1415643

Modified: websites/staging/xmlgraphics/trunk/content/fop/bugs.html
==============================================================================
--- websites/staging/xmlgraphics/trunk/content/fop/bugs.html (original)
+++ websites/staging/xmlgraphics/trunk/content/fop/bugs.html Fri Nov 30 14:12:53 2012
@@ -366,10 +366,10 @@ $(document).ready(function () {
 <p>Enter a new issue report at <a href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop">The FOP issue database (Bugzilla)</a> . 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):</p>
 </li>
 <li>
-<p>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.</p>
+<p>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.</p>
 </li>
 <li>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;</li>
-<li>a copy of the FOP configuration file you used (e.g., fop.xconf), if applicable;</li>
+<li>a copy of the FOP configuration file you used (e.g., <code>fop.xconf</code>), if applicable;</li>
 <li>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;</li>
 <li>information describing the version of FOP you are using and the platform (and OS) on which you are invoking FOP;</li>
 <li>



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