.logfile that this process creates. You now have two possible ways to proceed: either create a mail report to send to the bug processing mechanism (5, below), or submit your bug report via the web (7, below). 5. Process the bug-report creation file, using LaTeX itself:
latex latexbuglatexbug asks you some questions, and then lets you describe the bug you’ve found. It produces an output file latexbug.msg, which includes the details you’ve supplied, your “minimum” example file, and the log file you got after running the example. (I always need to edit the result before submitting it: typing text into latexbug isn’t much fun.) 6. Mail the resulting file to firstname.lastname@example.org; the subject line of your email should be the same as the bug title you gave to latexbug. The file latexbug.msg should be included into your message in-line: attachments are likely to be rejected by the bug processor. 7. Connect to the latex bugs processing web page and enter details of your bug — category, summary and full description, and the two important files (source and log file); note that members of the LaTeX team need your name and email address, as they may need to discuss the bug with you, or to advise you of a work-around.
Go to previous question
Go to FAQ home.
URL for this question: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexbug
Comments, suggestions, or error reports? - see “how to improve the FAQ”.
This is FAQ version 3.26, released on 2013-02-25.