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