48af41221f
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.
|
||
|---|---|---|
| .. | ||
| dist | ||
| lib | ||
| libexec | ||
| usr.bin | ||
| usr.sbin | ||
| Makefile | ||
| README | ||
README
$NetBSD: README,v 1.5 2003/12/04 23:32:37 keihan Exp $ Organization of Sources: This directory hierarchy is using a new organization that separates the GNU sources from the BSD-style infrastructure used to build the GNU sources. The GNU sources are kept in the standard GNU source tree layout under: dist/* The build infrastructure uses the normal BSD way under: lib/* usr.bin/* The makefiles in the above hierarchy will "reach over" into the GNU sources (src/gnu/dist) for everything they need. Maintenance Strategy: The sources under src/gnu/dist are generally a combination of some published distribution plus changes that we submit to the maintainers and that are not yet published by them. There are a few files that are never expected to be submitted to the FSF, (i.e. BSD-style makefiles and such) and those generally should stay in src/gnu/lib or src/gnu/usr.bin (the BSD build areas). Make sure all changes made to the GNU sources are submitted to the appropriate maintainer, but only after coordinating with the NetBSD maintainers by sending your proposed submission to the <tech-toolchain@NetBSD.org> mailing list. Only send the changes to the third-party maintainers after consensus has been reached.