Bug Reports

Please only submit one issue per form, otherwise there's a chance that the report might be closed while some of the issues haven't been resolved.

Bug reports for LaTeX packages should be accompanied by a minimal working example (MWE) that illustrates the problem and the associated log file. The MWE isn't required for applications (such as makeglossaries). Before reporting a bug, please check to see if it's listed in the FAQs or the Bug Tracker. Version numbers that end with "b" indicate a beta (prototype) release. Version numbers that end with "a" indicate an alpha (unstable) release.

Note: the free software provided here (including my class files and packages on CTAN) are funded by my book sales. While I'm keen to remove bugs from my code, book production has to take priority over bug fixes, so please don't expect a rapid response.

A minimal working example (.tex and corresponding .log) is required for packages (e.g. glossaries) but is optional for applications (e.g. makeglossaries)
Category^*		Not listed?
Version^*		How do I find the version number?
Summary^*
Name
Email^*		(Will only be used to reply to your message.)
Link related to bug report(s)		(Enter a comma-separated list of ID numbers if you want to cross-reference related bug report(s))
Message^*
Minimal Working Example
Accompanying Log File
.jdr or .ajr File		(For jpgfdraw bug reports, optional)
The following fields are required for applications (e.g. makeglossaries) but not needed for packages (e.g glossaries)
Java/Perl Version:
Operating System:

^*Required fields