diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html index fdc854a2f5d..921eb5dfbc1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-latexbug.html @@ -5,14 +5,14 @@ <p/>The LaTeX team supports LaTeX, and will deal with <em>bona fide</em> bug reports. Note that the LaTeX team does -<em>not</em> deal with contributed packages — just the software that +<em>not</em> deal with contributed packages — just the software that is part of the LaTeX distribution itself: LaTeX and the -“required” packages. +“required” packages. Furthermore, you need to be slightly careful to produce a bug report that is usable by the team. The steps are: <p/><b>1.</b> Are you still using current LaTeX? Maintenance is only -available for sufficiently up-to-date versions of LaTeX — if your +available for sufficiently up-to-date versions of LaTeX — if your LaTeX is more than two versions out of date, the bug reporting mechanisms may reject your report. <p/><b>2.</b> Has your bug already been reported? Browse the @@ -21,11 +21,11 @@ mechanisms may reject your report. to find any earlier instance of your bug. In many cases, the database will list a work-around. <p/><b>3.</b> Prepare a -<a href="FAQ-minxampl.html">“minimum” file</a> that exhibits the problem. -Ideally, such a file should contain no contributed packages — the +<a href="FAQ-minxampl.html">“minimum” file</a> that exhibits the problem. +Ideally, such a file should contain no contributed packages — the LaTeX team as a whole takes no responsibility for such packages (if -they’re supported at all, they’re supported by their authors). The -“minimum” file should be self-sufficient: if a member of the team +they’re supported at all, they’re supported by their authors). The +“minimum” file should be self-sufficient: if a member of the team should run it in a clean directory, on a system with no contributed packages, it should replicate your problem. <p/><b>4.</b> Run your file through LaTeX: the bug @@ -38,11 +38,11 @@ report via the web (7, below). latex latexbug </pre> <i>latexbug</i> asks you some questions, and then lets you describe -the bug you’ve found. It produces an output file <i>latexbug.msg</i>, -which includes the details you’ve supplied, your “minimum” example +the bug you’ve found. It produces an output file <i>latexbug.msg</i>, +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 -<i>latexbug</i> isn’t much fun.) +<i>latexbug</i> isn’t much fun.) <p/><b>6.</b> Mail the resulting file to <i>latex-bugs@latex-project.org</i>; the subject line of your email should be the same as the bug title you gave to <i>latexbug</i>. The @@ -51,7 +51,7 @@ attachments are likely to be rejected by the bug processor. <p/><b>7.</b> Connect to the <a href="http://www.latex-project.org/bugs-upload.html">latex bugs processing web page</a> -and enter details of your bug — category, summary and full +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 <em>need</em> your name and email address, as they may need to discuss the bug with you, or to advise you of a |