| PROBLEMS (55839) | PROBLEMS (69626) |
|---|---|
| 1This file describes various problems that have been encountered in 2compiling, installing and running groff. Suggestions for additions or 3other improvements to this file are welcome. 4 | 1This file describes various problems that have been encountered in 2compiling, installing and running groff. Suggestions for additions or 3other improvements to this file are welcome. 4 |
| 5---------------------------------------------------------------------- 6 7* My document says that the current year is 19100, not 2000. 8 9In groff, as in traditional troff, the yr number register yields the 10year minus 1900. Unfortunately, there is a longstanding bug in the 11Troff User's Manual <http://cm.bell-labs.com/cm/cs/cstr/54.ps.gz>, 12which incorrectly claims that yr is the last two digits of the year. 13This claim was never true of either Unix troff or of groff. 14 15If your text looks like this: 16 17 .\" Wrong: 18 This document was formatted in 19\n(yr. 19 20you can correct it as follows: 21 22 This document was formatted in \n[year]. 23 24or, if you want to be portable to older troff versions, as follows: 25 26 .nr y4 1900+\n(yr 27 This document was formatted in \n(y4. 28 29---------------------------------------------------------------------- 30 |
|
| 5* I get lots of `numeric overflow' error messages whenever I run | 31* I get lots of `numeric overflow' error messages whenever I run |
| 6groff; I compiled groff with AT&T C++ 2.0 with an ANSI C compiler. | 32 groff; I compiled groff with AT&T C++ 2.0 with an ANSI C compiler. |
| 7 8Make sure -DCFRONT_ANSI_BUG is included in DEFINES in the top-level 9Makefile. If that doesn't solve the problem, define INT_MIN as 10-INT_MAX in libgroff/lib.h. 11 | 33 34Make sure -DCFRONT_ANSI_BUG is included in DEFINES in the top-level 35Makefile. If that doesn't solve the problem, define INT_MIN as 36-INT_MAX in libgroff/lib.h. 37 |
| 12* I get errors when I try to compile groff with Sun C++ version 5.0 or 5.1. | 38---------------------------------------------------------------------- |
| 13 | 39 |
| 40* I get errors when I try to compile groff with Sun C++ version 5.0 41 or 5.1. 42 |
|
| 14This is a known problem; see Sun bug #4301919. As of this writing, no 15patch is available. Use GCC 2.95.2 or later instead. 16 | 43This is a known problem; see Sun bug #4301919. As of this writing, no 44patch is available. Use GCC 2.95.2 or later instead. 45 |
| 46---------------------------------------------------------------------- 47 |
|
| 17* I get errors when I try to compile groff with Sun C++ version 3 or | 48* I get errors when I try to compile groff with Sun C++ version 3 or |
| 18earlier. | 49 earlier. |
| 19 20Groff requires header files that are moderately compatible with AT&T 21C++ and ANSI C. With some versions of Sun C++, the supplied header 22files need some of the following changes to meet this requirement: 23<string.h> must declare the mem* functions, (just add `#include 24<memory.h>' to <string.h>); the first argument to fopen and freopen 25should be declared as `const char *'; the first argument to fread 26should be declared as `void *'; the first argument to fwrite should be | 50 51Groff requires header files that are moderately compatible with AT&T 52C++ and ANSI C. With some versions of Sun C++, the supplied header 53files need some of the following changes to meet this requirement: 54<string.h> must declare the mem* functions, (just add `#include 55<memory.h>' to <string.h>); the first argument to fopen and freopen 56should be declared as `const char *'; the first argument to fread 57should be declared as `void *'; the first argument to fwrite should be |
| 27declared as `const void *'; malloc should be declared to return `void 28*'; in 29*__builtin_alloca(int); }' should be added; declarations of getopt(), 30optarg, optind and opterr should be added to <stdlib.h>; in 31<sys/signal.h> the return type and the second argument type of 32signal() should be changed to be `void (*)(int)'. | 58declared as `const void *'; malloc should be declared to return 59`void *'; in <alloca.h>, the declaration `extern "C" { void 60*__builtin_alloca(int); }' should be added; in <sys/signal.h> the 61return type and the second argument type of signal() should be changed 62to be `void (*)(int)'. |
| 33 34You can either change them in place, or copy them to some other 35directory and include that directory with a -I option. 36 | 63 64You can either change them in place, or copy them to some other 65directory and include that directory with a -I option. 66 |
| 67---------------------------------------------------------------------- 68 69* The configure script fails on OS/390 Unix. 70 71There is a bug in the Language Environment (LE) whereby the test 72program for static destructors fails. You will see the message 73'configure: error: a working C++ compiler is required' 74 75Applying PTF UQ42006 is supposed to fix this, but the test program is 76still returning the wrong value (1). To work around this problem, you 77can comment out the following in the configure script (near line 956). 78This will effectively bypass the test (static constructors and 79destructors do actually work properly): 80 81#if { (eval echo configure:957: \"$ac_link\") 1>&5; (eval $ac_link) 2>&5; } && test -s conftest${ac_exeext} && (./conftest; exit) 2>/dev/null 82#then 83 echo "$ac_t""yes" 1>&6 84#else 85# echo "configure: failed program was:" >&5 86# cat conftest.$ac_ext >&5 87# rm -fr conftest* 88# echo "$ac_t""no" 1>&6;{ echo "configure: error: a working C++ compiler is required" 1>&2; exit 1; } 89#fi 90 91---------------------------------------------------------------------- 92 |
|
| 37* I get errors when I try to compile groff with DEC C++. 38 39Fix the declaration of write() in <unistd.h> so that the second 40argument is a const char *. Fix the declaration of open() in 41<sys/file.h> so that the first argument is a const char *. 42 | 93* I get errors when I try to compile groff with DEC C++. 94 95Fix the declaration of write() in <unistd.h> so that the second 96argument is a const char *. Fix the declaration of open() in 97<sys/file.h> so that the first argument is a const char *. 98 |
| 99---------------------------------------------------------------------- 100 101* On a host using Unix make (e.g. Solaris), if you are compiling for 102 multiple architectures by building in a subdirectory, the make stops 103 with a message like this: 104 105 make: Fatal error: Don't know how to make target `assert.o' 106 107 or like this: 108 109 make: Fatal error: Can't find /u/src/groff/src/include/Makefile.sub': No such file or directory 110 111This occurs because GNU make and Unix make handle VPATH differently, 112and the groff build relies on GNU make's VPATH handling. 113 114Use GNU make to work around the problem. In Solaris 8, GNU make is 115on the Software Companion CD and is installed as /opt/sfw/bin/gmake. 116 117---------------------------------------------------------------------- 118 |
|
| 43* On Ultrix, the make stops with the message 44 45 *** Error code 1 46 47 Stop. 48 49for no apparent reason. 50 51Use GNU make. 52 | 119* On Ultrix, the make stops with the message 120 121 *** Error code 1 122 123 Stop. 124 125for no apparent reason. 126 127Use GNU make. 128 |
| 129---------------------------------------------------------------------- 130 |
|
| 53* I'm having problems compiling groff on 386BSD 0.1. 54 55If you're using ash as /bin/sh, you'll need the following patch. 56 57*** gendef.sh.org Sun Jun 30 13:30:36 1991 58--- gendef.sh Sun Feb 28 10:23:49 1993 59*************** 60*** 3,9 **** --- 12 unchanged lines hidden (view full) --- 73! defs="#define $x" 74 shift 75 for def 76 do 77 78You'll also need to change dirnamemax.c so that it doesn't use 79pathconf(). 80 | 131* I'm having problems compiling groff on 386BSD 0.1. 132 133If you're using ash as /bin/sh, you'll need the following patch. 134 135*** gendef.sh.org Sun Jun 30 13:30:36 1991 136--- gendef.sh Sun Feb 28 10:23:49 1993 137*************** 138*** 3,9 **** --- 12 unchanged lines hidden (view full) --- 151! defs="#define $x" 152 shift 153 for def 154 do 155 156You'll also need to change dirnamemax.c so that it doesn't use 157pathconf(). 158 |
| 159---------------------------------------------------------------------- 160 |
|
| 81* While compiling on Xenix, ranlib libgroff.a fails. 82 83The system ranlib can't handle externals longer than 40 characters. 84Use the ranlib included in demon.co.uk:/pub/xenix/g++-1.40.3a.v1 85instead. 86 | 161* While compiling on Xenix, ranlib libgroff.a fails. 162 163The system ranlib can't handle externals longer than 40 characters. 164Use the ranlib included in demon.co.uk:/pub/xenix/g++-1.40.3a.v1 165instead. 166 |
| 167---------------------------------------------------------------------- 168 169* There are many empty `Makefile.dep' files. Is this a bug? 170 171No. Real dependency files are created with a `make depend' call. 172 173---------------------------------------------------------------------- 174 |
|
| 87* Groff can't handle my troff document. It works fine with AT&T troff. 88 89Read the section on incompatibilities in gtroff(1). Try using the -C 90option. Alternatively there's the sed script in tmac/fixmacros.sed 91which will attempt to edit a file of macros so that it can be used 92with groff without the -C flag. 93 | 175* Groff can't handle my troff document. It works fine with AT&T troff. 176 177Read the section on incompatibilities in gtroff(1). Try using the -C 178option. Alternatively there's the sed script in tmac/fixmacros.sed 179which will attempt to edit a file of macros so that it can be used 180with groff without the -C flag. 181 |
| 94* groff -Tdvi produces dvi files that use fonts at weird magnifications. | 182---------------------------------------------------------------------- |
| 95 | 183 |
| 184* groff -Tdvi produces dvi files that use fonts at weird 185 magnifications. 186 |
|
| 96Yes, it does. You may need to compile fonts with Metafont at these | 187Yes, it does. You may need to compile fonts with Metafont at these |
| 97magnifications. The CompileFonts script in the devdvi/generate 98directory may help you to do this. (It will take a *long* time.) | 188magnifications. The CompileFonts script in the devdvi/generate 189directory may help you to do this. (It will take a *long* time.) |
| 99 | 190 |
| 191---------------------------------------------------------------------- 192 |
|
| 100* pic output is not centered horizontally; pictures sometimes run off | 193* pic output is not centered horizontally; pictures sometimes run off |
| 101the bottom of the page. | 194 the bottom of the page. |
| 102 | 195 |
| 103The macro package you are using is not supplying appropriate definitions 104of PS and PE. Give groff a -mpic option. | 196The macro package you are using is not supplying appropriate 197definitions of PS and PE. Give groff a -mpic option. |
| 105 | 198 |
| 106* I'm having problems including PostScript illustrations using the PSPIC 107macro. | 199---------------------------------------------------------------------- |
| 108 | 200 |
| 201* I'm having problems including PostScript illustrations using the 202 PSPIC macro. 203 |
|
| 109A PostScript document must meet three requirements in order to be 110included with the PSPIC macro: it must comply with the Adobe Document 111Structuring Conventions; it must contain a BoundingBox line; it must 112be ``well-behaved''. The BoundingBox line should be of the form: 113 114 %%BoundingBox: llx lly urx ury 115 116where llx, lly, urx, ury are the coordinates of the lower left x, 117lower left y, upper right x, upper right y of the bounding box of 118marks on the page expressed as integers in the default PostScript 119coordinate system (72 units per inch, origin at bottom left corner). 120A useful tactic is to print out the illustration by itself (you may 121need to add a `showpage' at the end), and physically measure the 122bounding box. For more detail on these requirements, read the 123specification of Encapsulated PostScript format. (This is available 124from the Adobe file server; send a message with a body of `help' to 125ps-file-server@adobe.com.) 126 | 204A PostScript document must meet three requirements in order to be 205included with the PSPIC macro: it must comply with the Adobe Document 206Structuring Conventions; it must contain a BoundingBox line; it must 207be ``well-behaved''. The BoundingBox line should be of the form: 208 209 %%BoundingBox: llx lly urx ury 210 211where llx, lly, urx, ury are the coordinates of the lower left x, 212lower left y, upper right x, upper right y of the bounding box of 213marks on the page expressed as integers in the default PostScript 214coordinate system (72 units per inch, origin at bottom left corner). 215A useful tactic is to print out the illustration by itself (you may 216need to add a `showpage' at the end), and physically measure the 217bounding box. For more detail on these requirements, read the 218specification of Encapsulated PostScript format. (This is available 219from the Adobe file server; send a message with a body of `help' to 220ps-file-server@adobe.com.) 221 |
| 222---------------------------------------------------------------------- 223 |
|
| 127* I've configured groff for A4 paper, but gtroff still seems to think | 224* I've configured groff for A4 paper, but gtroff still seems to think |
| 128that the length of a page (as returned by \n(.p) is 11 inches. | 225 that the length of a page (as returned by \n(.p) is 11 inches. |
| 129 130This is intentional. The PAGE option is used only by grops. For 131compatibility with ditroff, the default page length in gtroff is 132always 11 inches. The page length can be changed with the `pl' 133request. 134 | 226 227This is intentional. The PAGE option is used only by grops. For 228compatibility with ditroff, the default page length in gtroff is 229always 11 inches. The page length can be changed with the `pl' 230request. 231 |
| 232---------------------------------------------------------------------- 233 |
|
| 135* Groff doesn't use the font names I'm used to. 136 137Use the `ftr' request. See gtroff(1). 138 | 234* Groff doesn't use the font names I'm used to. 235 236Use the `ftr' request. See gtroff(1). 237 |
| 238---------------------------------------------------------------------- 239 |
|
| 139* I get errors using the Unix -ms macros with groff -e -C. 140 141Apply this change: 142 143*** /usr/lib/ms/ms.eqn Tue Apr 25 02:14:28 1989 144--- ms.eqn Sun Nov 11 10:33:59 1990 145*************** 146*** 22,29 **** --- 11 unchanged lines hidden (view full) --- 158 .de EN 159! .if \\n(.k>0 .br 160 .di 161+ .ds 10 \\*(EZ\\ 162 .rm EZ 163 .nr ZN \\n(dn 164 .if \\n(ZN>0 .if \\n(YE=0 .LP 165 | 240* I get errors using the Unix -ms macros with groff -e -C. 241 242Apply this change: 243 244*** /usr/lib/ms/ms.eqn Tue Apr 25 02:14:28 1989 245--- ms.eqn Sun Nov 11 10:33:59 1990 246*************** 247*** 22,29 **** --- 11 unchanged lines hidden (view full) --- 259 .de EN 260! .if \\n(.k>0 .br 261 .di 262+ .ds 10 \\*(EZ\\ 263 .rm EZ 264 .nr ZN \\n(dn 265 .if \\n(ZN>0 .if \\n(YE=0 .LP 266 |
| 267---------------------------------------------------------------------- |
|
| 166 | 268 |
| 167* gpic doesn't accept the syntax `chop N M' for chopping both ends of a 168line. | 269* gpic doesn't accept the syntax `chop N M' for chopping both ends of 270 a line. |
| 169 170The correct syntax is `chop N chop M'. 171 | 271 272The correct syntax is `chop N chop M'. 273 |
| 172* With gpic -t, when I print `line ->; box' using a dvi to ps 173program, the arrow head sticks through into the inside of the box. | 274---------------------------------------------------------------------- |
| 174 | 275 |
| 175The dvi to ps program should be modified to set the line cap and 176line join parameters to 1 while printing tpic specials. | 276* With gpic -t, when I print `line ->; box' using a dvi to ps program, 277 the arrow head sticks through into the inside of the box. |
| 177 | 278 |
| 279The dvi to ps program should be modified to set the line cap and line 280join parameters to 1 while printing tpic specials. 281 282---------------------------------------------------------------------- 283 |
|
| 178* When I print the output groff -Tps, the output is always shifted up | 284* When I print the output groff -Tps, the output is always shifted up |
| 179by about 0.7 inches; I'm using 8.5x11 inch paper. | 285 by about 0.7 inches; I'm using 8.5x11 inch paper. |
| 180 181Make sure that PAGE is defined to be `letter' in the top-level 182Makefile. 183 | 286 287Make sure that PAGE is defined to be `letter' in the top-level 288Makefile. 289 |
| 290---------------------------------------------------------------------- 291 |
|
| 184* When I try to print the output of groff -Tps, I get no output at all | 292* When I try to print the output of groff -Tps, I get no output at all |
| 185from the printer, and the log file shows the error 186%%[ error: undefined; offendingcommand: BP ]%% 187I'm using TranScript spooling software. | 293 from the printer, and the log file shows the error 294 %%[ error: undefined; offendingcommand: BP ]%% 295 I'm using TranScript spooling software. |
| 188 189This is a bug in the page reversal filter in early versions of 190TranScript. Change the `broken' parameter in 191/usr/local/lib/groff/font/devps/DESC to 7. 192 | 296 297This is a bug in the page reversal filter in early versions of 298TranScript. Change the `broken' parameter in 299/usr/local/lib/groff/font/devps/DESC to 7. 300 |
| 193* When I preview groff -Tps output using the Sun OpenWindows 2.0 pageview 194program, all the pages are displayed on top of each other. | 301---------------------------------------------------------------------- |
| 195 | 302 |
| 303* When I preview groff -Tps output using the Sun OpenWindows 2.0 304 pageview program, all the pages are displayed on top of each other. 305 |
|
| 196This is a defect in pageview. Change the `broken' parameter in 197/usr/local/lib/groff/font/devps/DESC to 2. 198 | 306This is a defect in pageview. Change the `broken' parameter in 307/usr/local/lib/groff/font/devps/DESC to 2. 308 |
| 309---------------------------------------------------------------------- 310 |
|
| 199* With groff -TX75, -TX100 or -X, I can only view the first page. 200 201The left mouse button brings up a menu that allows you to view other 202pages. 203 | 311* With groff -TX75, -TX100 or -X, I can only view the first page. 312 313The left mouse button brings up a menu that allows you to view other 314pages. 315 |
| 316---------------------------------------------------------------------- 317 |
|
| 204* When I print the output of groff -Tdvi, I just get a black dot in | 318* When I print the output of groff -Tdvi, I just get a black dot in |
| 205upper left corner. | 319 upper left corner. |
| 206 207Some dvi drivers (notably early versions of xtex) do not correctly 208handle dvi files that use a resolution different from that used by dvi 209files produced by TeX. Try getting a more up to date driver. 210 | 320 321Some dvi drivers (notably early versions of xtex) do not correctly 322handle dvi files that use a resolution different from that used by dvi 323files produced by TeX. Try getting a more up to date driver. 324 |
| 325---------------------------------------------------------------------- 326 |
|
| 211* I get lots of errors when I use groff with the AT&T -mm macros. 212 213The AT&T -mm macros need a few changes to work with groff; `make 214install.dwbmm' will copy your -mm macros to groff's macro directory 215and make the necessary changes. You may need to edit the commands for 216the install.mm target in the Makefile. Alternatively use the groff 217-mm macros. 218 | 327* I get lots of errors when I use groff with the AT&T -mm macros. 328 329The AT&T -mm macros need a few changes to work with groff; `make 330install.dwbmm' will copy your -mm macros to groff's macro directory 331and make the necessary changes. You may need to edit the commands for 332the install.mm target in the Makefile. Alternatively use the groff 333-mm macros. 334 |
| 335---------------------------------------------------------------------- 336 |
|
| 219* gtroff doesn't understand lines like `.ce99' with no space between | 337* gtroff doesn't understand lines like `.ce99' with no space between |
| 220the name of the request or macro and the arguments. | 338 the name of the request or macro and the arguments. |
| 221 | 339 |
| 222Gtroff requires a space between macro or request and its arguments | 340gtroff requires a space between macro or request and its arguments |
| 223because it allows the use of long names for macros and requests. You 224can use the -C option or the `cp' request to put gtroff into a 225compatibility mode in which it is not possible to use long names for 226macros but in which no space is required between macros and their 227arguments. The use of compatibility mode is strongly discouraged. 228 | 341because it allows the use of long names for macros and requests. You 342can use the -C option or the `cp' request to put gtroff into a 343compatibility mode in which it is not possible to use long names for 344macros but in which no space is required between macros and their 345arguments. The use of compatibility mode is strongly discouraged. 346 |
| 347---------------------------------------------------------------------- 348 |
|
| 229* gtroff gives warnings about lines like 230 .ev \" a comment | 349* gtroff gives warnings about lines like 350 .ev \" a comment |
| 231(with a tab after the .ev). | 351 (with a tab after the .ev). |
| 232 233A tab character cannot be used as a substitute for a space character 234(except in one case: between a control character at the beginning of a 235line and the name of a macro or request). For example, in Unix troff | 352 353A tab character cannot be used as a substitute for a space character 354(except in one case: between a control character at the beginning of a 355line and the name of a macro or request). For example, in Unix troff |
| 356 |
|
| 236 .ps \" restore the previous point size | 357 .ps \" restore the previous point size |
| 358 |
|
| 237(with a tab after the .ps) will NOT restore the previous point-size; 238instead it will be silently ignored. Since this is very likely to be 239an error, gtroff can give a warning about it. If you want to align 240comments, you can do it like this: | 359(with a tab after the .ps) will NOT restore the previous point-size; 360instead it will be silently ignored. Since this is very likely to be 361an error, gtroff can give a warning about it. If you want to align 362comments, you can do it like this: |
| 363 |
|
| 241 .ev\" \" a comment 242 | 364 .ev\" \" a comment 365 |
| 366---------------------------------------------------------------------- 367 |
|
| 243* I don't like the page headers and footers produced by groff -man. 244 245There seem to be many different styles of page header and footer 246produced by different versions of the -man macros. You will need to 247modify macros/tmac.an to suit your personal taste. For example, if 248you want the center of the page header to say | 368* I don't like the page headers and footers produced by groff -man. 369 370There seem to be many different styles of page header and footer 371produced by different versions of the -man macros. You will need to 372modify macros/tmac.an to suit your personal taste. For example, if 373you want the center of the page header to say |
| 374 |
|
| 249 System Programmer's Manual | 375 System Programmer's Manual |
| 376 |
|
| 250you will need to change the line | 377you will need to change the line |
| 378 |
|
| 251 .el .ds an-extra3 \"System Programmer's Manual | 379 .el .ds an-extra3 \"System Programmer's Manual |
| 380 |
|
| 252to | 381to |
| 382 |
|
| 253 .el .ds an-extra3 System Programmer's Manual 254 | 383 .el .ds an-extra3 System Programmer's Manual 384 |
| 255* While formatting a manual page, groff complains about not being able to 256break lines. The problem seems to be caused by a line like: | 385---------------------------------------------------------------------- 386 387* While formatting a manual page, groff complains about not being able 388 to break lines. The problem seems to be caused by a line like: |
| 257 .TP \w'label'+2 258 259The -man documentation says that the default scale indicator for TP 260macro is `n'. The groff -man macros implement this correctly, so that 261the argument will be evaluated as if it were | 389 .TP \w'label'+2 390 391The -man documentation says that the default scale indicator for TP 392macro is `n'. The groff -man macros implement this correctly, so that 393the argument will be evaluated as if it were |
| 394 |
|
| 262 \w'label'n+2n | 395 \w'label'n+2n |
| 396 |
|
| 263The Unix -man macros don't implement this correctly (probably because 264it's hard to do in Unix troff); they just append `n' to the entire 265argument, so that it will be evaluated as if it were | 397The Unix -man macros don't implement this correctly (probably because 398it's hard to do in Unix troff); they just append `n' to the entire 399argument, so that it will be evaluated as if it were |
| 400 |
|
| 266 \w'label'u+2n | 401 \w'label'u+2n |
| 402 |
|
| 267The solution is to fix the manual page: | 403The solution is to fix the manual page: |
| 404 |
|
| 268 .TP \w'label'u+2 269 | 405 .TP \w'label'u+2 406 |
| 407---------------------------------------------------------------------- 408 |
|
| 270* I'm having problems formatting Ultrix man pages with groff -man. 271 272The Ultrix man pages use a number of non-standard extensions to the 273Unix man macros. One solution is to use the Ultrix -man macros with 274groff. Rename /usr/local/lib/groff/tmac/tmac.an to 275/usr/local/lib/groff/tmac/tmac.an.gnu, copy /usr/lib/tmac/tmac.an to 276/usr/local/lib/groff/tmac/tmac.an and apply the following patch (from 277Frank Wortner): --- 16 unchanged lines hidden (view full) --- 294! .if \\$12 .if !\\$5 .ds ]F\^ 295 .ie !\\$4 .}S \\$2 \\$1 "\\$3\f\\$1\\$4\\*(]F" "\\$5" "\\$6" "\\$7" "\\$8" "\\$9" 296 .el \\$3 297 .}f 298 299Another possible solution is to install tmac/man.ultrix as 300/usr/local/lib/groff/tmac/man.local. 301 | 409* I'm having problems formatting Ultrix man pages with groff -man. 410 411The Ultrix man pages use a number of non-standard extensions to the 412Unix man macros. One solution is to use the Ultrix -man macros with 413groff. Rename /usr/local/lib/groff/tmac/tmac.an to 414/usr/local/lib/groff/tmac/tmac.an.gnu, copy /usr/lib/tmac/tmac.an to 415/usr/local/lib/groff/tmac/tmac.an and apply the following patch (from 416Frank Wortner): --- 16 unchanged lines hidden (view full) --- 433! .if \\$12 .if !\\$5 .ds ]F\^ 434 .ie !\\$4 .}S \\$2 \\$1 "\\$3\f\\$1\\$4\\*(]F" "\\$5" "\\$6" "\\$7" "\\$8" "\\$9" 435 .el \\$3 436 .}f 437 438Another possible solution is to install tmac/man.ultrix as 439/usr/local/lib/groff/tmac/man.local. 440 |
| 441---------------------------------------------------------------------- 442 |
|
| 302* I'm having problems formatting HP-UX 9.0 man pages with groff -man. 303 304Rename /usr/local/lib/groff/tmac/tmac.an to (for example) 305/usr/local/lib/groff/tmac/tmac.gan, copy HP's tmac.an into 306/usr/local/lib/groff/tmac/tmac.an, and either put `.cp 1' at the 307beginning or filter it (and any files it .so's) through 308tmac/fixmacros.sed. 309 | 443* I'm having problems formatting HP-UX 9.0 man pages with groff -man. 444 445Rename /usr/local/lib/groff/tmac/tmac.an to (for example) 446/usr/local/lib/groff/tmac/tmac.gan, copy HP's tmac.an into 447/usr/local/lib/groff/tmac/tmac.an, and either put `.cp 1' at the 448beginning or filter it (and any files it .so's) through 449tmac/fixmacros.sed. 450 |
| 451---------------------------------------------------------------------- 452 |
|
| 310* I'm having problems formatting man pages produced by the perl | 453* I'm having problems formatting man pages produced by the perl |
| 311wrapman script. | 454 wrapman script. |
| 312 313Some versions of wrapman have a superfluous blank line before the .TH 314line. This must be deleted. Then either use groff -C, or apply the 315following patch: 316 317*** wrapman.~2~ Sun Jan 19 12:10:24 1992 318--- wrapman Tue Aug 10 02:06:41 1993 319*************** --- 62 unchanged lines hidden (view full) --- 382 .nr % 0 \\" start at page 1 383! .\\"'; __END__ ##### From here on it's a standard manual page ##### 384 .TH $PROG 1 "$month $mday, 19$year" 385 .SH NAME 386 $prog \\- whatever 387 .SH SYNOPSIS 388 389 | 455 456Some versions of wrapman have a superfluous blank line before the .TH 457line. This must be deleted. Then either use groff -C, or apply the 458following patch: 459 460*** wrapman.~2~ Sun Jan 19 12:10:24 1992 461--- wrapman Tue Aug 10 02:06:41 1993 462*************** --- 62 unchanged lines hidden (view full) --- 525 .nr % 0 \\" start at page 1 526! .\\"'; __END__ ##### From here on it's a standard manual page ##### 527 .TH $PROG 1 "$month $mday, 19$year" 528 .SH NAME 529 $prog \\- whatever 530 .SH SYNOPSIS 531 532 |
| 390* When I preview documents using -TX75 or -TX100, the layout is not the same 391as when I print the document with -Tps: the line and page breaks come 392in different places. | 533---------------------------------------------------------------------- |
| 393 | 534 |
| 535* When I preview documents using -TX75 or -TX100, the layout is not 536 the same as when I print the document with -Tps: the line and page 537 breaks come in different places. 538 |
|
| 394Use groff -X -Tps. 395 | 539Use groff -X -Tps. 540 |
| 541---------------------------------------------------------------------- 542 |
|
| 396* When I try to run gxditview, I get the error: | 543* When I try to run gxditview, I get the error: |
| 397Error: Widget viewport has zero width and/or height | 544 Error: Widget viewport has zero width and/or height |
| 398 399This error means you haven't correctly installed the application 400defaults file, GXditview.ad; ``make install'' does this for you 401automatically, so either you didn't do ``make install'', or you don't 402have imake configured correctly. 403 | 545 546This error means you haven't correctly installed the application 547defaults file, GXditview.ad; ``make install'' does this for you 548automatically, so either you didn't do ``make install'', or you don't 549have imake configured correctly. 550 |
| 551---------------------------------------------------------------------- 552 |
|
| 404* groff uses up an enormous amount of memory processing large files. | 553* groff uses up an enormous amount of memory processing large files. |
| 405I'm using 386BSD 0.1. | 554 I'm using 386BSD 0.1. |
| 406 407386BSD includes an old version of g++, 1.39, which has a bug that 408causes a major memory leak in gtroff. Apply the following fix to g++ 409and recompile groff: 410 411*** cplus-decl.c.~1~ Mon Aug 6 05:28:59 1990 412--- cplus-decl.c Wed Jun 5 08:55:04 1991 413*************** --- 17 unchanged lines hidden (view full) --- 431 get_identifier (OPERATOR_DELETE_FORMAT), 432! build_tree_list (NULL_TREE, current_class_decl), 433 NULL_TREE, LOOKUP_NORMAL); 434 else if (TYPE_USES_VIRTUAL_BASECLASSES (current_class_type)) 435 exprstmt = build_x_delete (ptr_type_node, current_class_decl, 0); 436 else 437 exprstmt = 0; 438 | 555 556386BSD includes an old version of g++, 1.39, which has a bug that 557causes a major memory leak in gtroff. Apply the following fix to g++ 558and recompile groff: 559 560*** cplus-decl.c.~1~ Mon Aug 6 05:28:59 1990 561--- cplus-decl.c Wed Jun 5 08:55:04 1991 562*************** --- 17 unchanged lines hidden (view full) --- 580 get_identifier (OPERATOR_DELETE_FORMAT), 581! build_tree_list (NULL_TREE, current_class_decl), 582 NULL_TREE, LOOKUP_NORMAL); 583 else if (TYPE_USES_VIRTUAL_BASECLASSES (current_class_type)) 584 exprstmt = build_x_delete (ptr_type_node, current_class_decl, 0); 585 else 586 exprstmt = 0; 587 |
| 588---------------------------------------------------------------------- 589 |
|
| 439* Where can I get grap? 440 | 590* Where can I get grap? 591 |
| 441Grap is not freely available, but there is a nawk script implementing 442an extended subset of grap available for ftp as 443ftp.informatik.uni-rostock.de:/pub/local/software/prag-1.0.shar.gz. | 592Ted Faber <faber@lunabase.org> has written a freely available grap: |
| 444 | 593 |
| 594 http://www.lunabase.org/~faber/Vault/software/grap/ 595 596---------------------------------------------------------------------- 597 |
|
| 445* How can I use groff with an old LaserJet printer that doesn't work | 598* How can I use groff with an old LaserJet printer that doesn't work |
| 446with groff -Tlj4? | 599 with groff -Tlj4? |
| 447 448You have at least 3 options: 449 450- use groff -Tps with GNU Ghostscript; 451 452- use groff -Tdvi with a TeX .dvi to Laserjet driver; 453 454- use groff with the LaserJet driver in Chris Lewis' psroff package | 600 601You have at least 3 options: 602 603- use groff -Tps with GNU Ghostscript; 604 605- use groff -Tdvi with a TeX .dvi to Laserjet driver; 606 607- use groff with the LaserJet driver in Chris Lewis' psroff package |
| 455(available for ftp from: 456ftp.uunet.ca:/distrib/chris_lewis/psroff3.0pl17). | 608 (available for ftp from: 609 ftp.uunet.ca:/distrib/chris_lewis/psroff3.0pl17). |
| 457 | 610 |
| 611---------------------------------------------------------------------- 612 |
|
| 458* Groff seems to generate level 3 Postscript, but my printer is only a | 613* Groff seems to generate level 3 Postscript, but my printer is only a |
| 459level 1 or 2 PostScript printer. | 614 level 1 or 2 PostScript printer. |
| 460 461In fact groff generates only level 1 PostScript. The `%!PS-Adobe-3.0' 462comment at the beginning of PostScript output generated by groff 463indicates that the file conforms to version 3.0 of the Adobe Document 464Structuring Conventions. The output generated by groff should be 465printable on any PostScript printer. Problems with groff output's not 466printing are most often caused by the spooling system. 467 | 615 616In fact groff generates only level 1 PostScript. The `%!PS-Adobe-3.0' 617comment at the beginning of PostScript output generated by groff 618indicates that the file conforms to version 3.0 of the Adobe Document 619Structuring Conventions. The output generated by groff should be 620printable on any PostScript printer. Problems with groff output's not 621printing are most often caused by the spooling system. 622 |
| 623---------------------------------------------------------------------- 624 |
|
| 468* The \n(st and \n(sb registers don't seem to work. I thought \w set | 625* The \n(st and \n(sb registers don't seem to work. I thought \w set |
| 469them to the height and depth of its argument, but the registers always 470seem to be 0. | 626 them to the height and depth of its argument, but the registers 627 always seem to be 0. |
| 471 472\n(st and \n(sb aren't supposed to give the height and depth of the 473string rather they give the minimum and maximum vertical displacement 474of the baseline. For example for \v'2u'\v'-3u', \n(st will be 1 and 475\n(sb will be -2. The height and depth of the string is available in 476the \n[rst] and \n[rsb] registers: these are groff extensions. 477 | 628 629\n(st and \n(sb aren't supposed to give the height and depth of the 630string rather they give the minimum and maximum vertical displacement 631of the baseline. For example for \v'2u'\v'-3u', \n(st will be 1 and 632\n(sb will be -2. The height and depth of the string is available in 633the \n[rst] and \n[rsb] registers: these are groff extensions. 634 |
| 635---------------------------------------------------------------------- 636 |
|
| 478* On an SGI system, how can I make the man command use groff? 479 480From David Hinds <dhinds@allegro.stanford.edu> (some of these steps 481are unnecessary if you install with the `g' Makefile variable defined 482as empty): 483 484Create a script called 'eqn': 485 --- 68 unchanged lines hidden --- | 637* On an SGI system, how can I make the man command use groff? 638 639From David Hinds <dhinds@allegro.stanford.edu> (some of these steps 640are unnecessary if you install with the `g' Makefile variable defined 641as empty): 642 643Create a script called 'eqn': 644 --- 68 unchanged lines hidden --- |