calls
-support use of 2 fonts simultanously; this costs the ability to
"highlight", ie to use the upper 8 colours
-define screen types "80x25bf" and "80x50bf" which use this ability
-add conditional code to deal with the weird mapping of pcvt's
supplemental fonts
to download fonts and a per-screen call to select a font
allows easier sharing of ressources in the display driver
change the parameters to the load_font driver vector to pass all
available font information
find the actual source of the common "automatically ending `eb' diversion
on exit" error. This generally means you tried something like `.Em Do not'
which accidently calls the `Do' request, which _must_ be followed by Dc.
* Add a .Me request for marking up menu entries.
* Print the source line number on the "Extraneous .Ed" error. (Duhh.)
* New requests for HTML integration: .Mt (mailto) and .Lk (link).
* Rename the .em built-in to e@ and print an error if .em is ever
accidently invoked.
Use: nroff -mdoc2html input_file...
Or, for the completely general case,
Use: groff -P-b -P-u -P-o -Tascii -ww -mdoc2html input_file ...
This was originally intended for just the new distrib/notes and other
non-man-page project documentation, but in fact it can get almost all of
the man pages right at this point.
In many cases, I would suggest that original documentation not be written
in HTML or ASCII any more. A good example would be "supported devices".
It's presently duplicated, in the install notes, the web pages, and the
man pages. If written in -mdoc, it can automatically be a man page, a www
page feature, and a printable, downloadable file. We can generate PostScript
and the "unix enhanced text" format used by more(1), as well as plain old
ascii, and all using in-tree tools.
TNF Copyright.
point them to options(4) for more details. Also point out that ipf
is necc. for ipnat to function. Oh, and convert ipnat.8 to mandoc
while I was in here... was easier to convert it then rewrite my stuff
after I noticed..
Closes PR# 4813 by Jeff Thieleke
