A list of unresolved reported bugs can be found at FOP Open Bugs (Bugzilla). If you have an interest in an issue already reported, please consider the following:

• If you have insight that may help developers solve an existing problem, please add comments and/or file attachments to the existing issue.
• If you would like to track the status of the issue, consider adding your email address to the list of "CC" recipients, so that you will receive an email as changes are made to the issue.

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 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 the issue involves a specific input or output file, then you MUST include the following information in the bug report (preferably as one or more attachments):
  • an input XSL-FO file (an input XML plus XSLT file is not acceptable, unless and only if the issue being reported is related to the built-in XSLT transform processing convenience function provided by FOP); this input SHOULD be maximally minimal, which means that it should contain nothing more than the minimum needed to demonstrate the problem; if you do not take the effort to provide a maximally minimal input FO file, then you will be subsequently asked to do so before the bug is processed;
  • a resulting output file, preferably in PDF format; if the issue being reported involves a different output format, then provide both a PDF output file and the output file for the output format for which the report applies;
  • a copy of the FOP configuration file you used (e.g., fop.xconf);
  • 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, then this MUST include the full stack back 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.
• After submission, a copy of your bug report will be automatically sent to the FOP developer discussion list. If additional information is needed to process the bug, then the bug will be set to the NEEDSINFO state, and you will be asked to provide the additional information. You can avoid this extra step by being diligent about providing all of the information indicated above.