* Don't use GROFF_CSH_HACK. It would change the "#! /bin/sh" to just
":", and this causes trouble for some shells. For example, if
CONFIG_SHELL=/bin/ksh, when the groff build uses ${CONFIG_SHELL} to
run a script that has been modified in this way, ksh sees the ":" and
decided to run the script under /bin/sh instead.
* Use SH_SCRIPT_SED_CMD="1s,/bin/sh,${CONFIG_SHELL},"
to edit the "#! /bin/sh" line, to ensure that scripts
are always run under the correct shell.
bdf.ms:270: fatal error: input stack limit exceeded (probable
infinite loop)
that appears when building the xorg-docs package.
Problem reported to current-users by Kouichirou Hiratsuka.
Fix provided by groff maintainer, Werner Lemberg.
Groff
-----
o The argument of the command line option `-I' is now also passed to troff
and grops, specifying a directory to search for files on the command line,
files named in `so' and `psbb' requests, and files named in \X'ps: file'
and \X'ps: import' escapes.
o If option `-V' is used more than once, the commands will be both printed
on standard error and run.
Troff
-----
o Two new read-only, string-valued registers `.m' and `.M' return the
name of the current drawing and background color, respectively.
o New read-only register `.U' which is set to 1 if in safer mode and set
to 0 if in unsafe mode.
o An input encoding file for latin-5 (a.k.a. ISO 8859-9) has been added.
Example use:
groff -Tdvi -mlatin5 my_file > my_file.dvi
Note that some output devices don't support all glyphs of this encoding.
o If the `return' request is called with an argument, it exits twice,
namely the current macro and the macro one level higher. This is
used to define a wrapper macro for `return' in trace.tmac.
o For completeness, two new requests have been added: `dei1' and `ami1'.
They are equivalent to `dei' and `ami', respectively, but the macros
are executed with compatibility mode off (similar to `de1' and `am1').
o New command line option `-I' to specify a directory for files (both
those on the command line and those named in `psbb' requests). This is
also handled by the groff wrapper program.
o Since version 1.19 you can say `.vs 0'. Older versions emit a warning
and convert this to `.vs \n[.V]'.
This hasn't been documented properly. Note that `.vs 0' isn't saved in a
diversion since it doesn't result in vertical motion.
Pic
___
o Dashed and dotted ellipses have been implemented.
Tbl
---
o New key character `x' to make tbl call a user-defined macro on a table
cell. Patch by Heinz-Jürgen Oertel <hj.oertel@surfeu.de>.
Grohtml
-------
o New option `-j' to emit output splitted into multiple files.
Grops
-----
o New command line option `-I' to specify a directory to search for files
on the command line and files named in \X'ps: import' and \X'ps: file'
escapes. This is also handled by the groff wrapper program.
o The default value for the `broken' keyword in the DESC file is now 0.
Grolj4
------
o A new man page `lj4_font(5)' documents how fonts are accessed with
grolj4.
o The built-in fonts for LJ4 and newer PCL 5 devices have been completely
revised, mainly to access as much glyphs as possible. The provided
metric files should be compatible with recent PCL 5 printers also.
Additionally, font description files have been added for the Arial and
Times New Roman family, the MS symbol, and Wingdings fonts.
Hpftodit
--------
o Completely revised to handle HP TrueType metric files also. See the
hpftodit manual page for more details.
Macro Packages
--------------
o www.tmac: New macro `JOBNAME' to split output into multiple files.
o In mdoc, multiple calls to `.Lb' are now supported in the LIBRARY
section.
doesn't substitute that into Makefile.in anywhere. This will cause it to lose
when compiling as a host tools and CPPFLAGS contains -I's into the compat
area (solaris loses here for instance). Fix by adding CPPFLAGS onto CFLAGS
and CCFLAGS definitions
http://www.ffii.org/cgi-bin/viewcvs.cgi/groff/Makefile.comm
(The previous fixes still ended up with syntactically-invalid shell
code for the 'for' loops, which would fail on some versions of linux.
The ignore-error marking for the command would allow the build to finish,
but it would leave extraneous "Failed" bits in the build output.)
