diff options
-rw-r--r-- | ChangeLog | 14 | ||||
-rw-r--r-- | tmac/TESTING-HINTS | 20 |
2 files changed, 34 insertions, 0 deletions
@@ -1,5 +1,19 @@ 2007-02-01 Eric S. Raymond <esr@thyrsus.com> + * tmac/TESTING-HINTS: Added. + +2007-02-01 Eric S. Raymond <esr@thyrsus.com> + + Enable the support for Bell archaisms on .SC, so the -r bell + switch is no longer needed to format old AT&T papers like + the EQN user guide. + + * tmac/s.tmac (.SC, .UC, .P1, .P2) [bell]: New macros. + + * tmac/groff_ms.man, doc/groff.texinfo, NEWS: Document `-r bell'. + +2007-02-01 Eric S. Raymond <esr@thyrsus.com> + Add some Bell labs extensions to the -ms macros. * tmac/s.tmac (.SC, .UC, .P1, .P2) [bell]: New macros. diff --git a/tmac/TESTING-HINTS b/tmac/TESTING-HINTS new file mode 100644 index 00000000..5b51bef5 --- /dev/null +++ b/tmac/TESTING-HINTS @@ -0,0 +1,20 @@ +Here are some hints about testing modifications to macro packages +and manual pages. + +1. Use groff's `-ww' option to catch potential problems. + Ideally, there shouldn't be any warnings. + +2. For a well-formedness check, run doclifter (http://catb,org/~esr/doclifter) + against your page. This tool was written to lift pages to XML, but as a + side effect it acts as a validator that will warn you of potential problems + and non-portable constructs. + +3. The two most important groff client types are X terminal emulators + and Postscript printers. Eyeball-check your output under both. + +4. The colorized man output of the Midnight Commander (what you get by + pressing the F3 key on a man page) is good for making small errors + more visible. + +5. Try different terminal line lengths, say, 80 and 100 characters. + |