BUG-REPORT revision 18099
1 Groff Bug Report 2 3Please read the PROBLEMS file before sending in a bug report. 4 5Please fill in all fields, even if you think they are not relevant. 6 7Please delete the text in brackets before sending it in. 8 9Please report separate bugs separately. 10 11Send the completed form to bug-groff@prep.ai.mit.edu. 12 13GROFF VERSION: 14[The version of groff you are using. For example, `1.05'] 15 16MACHINE: 17[The machine you are using. For example, `Sun SPARCstation 2'] 18 19OS: 20[The operating system you are using. For example, `SunOS 4.1.1'] 21 22COMPILER: 23[The compiler you are used to compile groff. For example, `g++ 1.40.3'] 24 25INPUT FILES: 26[Include all the files necessary to reproduce the problem that are not 27part of the standard groff distribution. This includes font 28description files, DESC files and macro files (with the exception of 29the -ms and -mm macros: I have them). Send them as as a shell archive 30or as a uuencoded, compressed tar file. 31 32It's easier for me if you can provide an example that doesn't depend 33on any macro package, but obviously if you're reporting a problem with 34a macro package that won't be possible. Also a short example is more 35convenient than a long one, but don't worry if you can't find a short 36example. Don't say something like ``any file that X'': always send a 37definite example.] 38 39COMMAND LINE: 40[The command line that I should run in order to observe the bug. For 41example, `gtroff -Tps bug.tr'. If the command line uses -ms or -mm, 42say whether these refer to the groff versions or the Unix versions of 43the macros.] 44 45DESCRIPTION OF INCORRECT BEHAVIOUR: 46[What goes wrong when that command line is run? For example, `gtroff 47gets a segmentation fault', or `The output looks bad because the bar 48over the x is too long and is too far over to the left.' If you get 49an error message, include it here without modification: don't edit it 50to make it more readable.] 51 52SUGGESTED FIX [optional]: 53[If you can suggest a fix for the problem, include a context diff 54here. But don't delay sending in a bug report in the hope of finding 55a fix. Guesses about the cause of the bug are not usually helpful.] 56