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