dce@mips.COM (David Elliott) (03/02/88)
We've spent a lot of time in the past few months fighting with the
AT&T System V.3 documentation sources.
In particular, the stuff is filled with things like
\f3words to be in bold\f1
Correct me if I'm wrong, but I thought that the proper way to do
this is
\f3words to be in bold\fP
That way, you don't screw up macros that use .ft to put the font
back the way it was.
This really affects headers. There are cases in which a header
is printed containing a "\f3name\f1 Manual". At the end of the
header, the font is put back to what it was, and the result is
that the rest of the text is bold.
In general, I can't see how the AT&T manuals could have been produced
with the sources we got.
Can anyone help with this mess?
--
David Elliott dce@mips.com or {ames,prls,pyramid,decwrl}!mips!dcegwyn@brl-smoke.ARPA (Doug Gwyn ) (03/03/88)
In article <1736@quacky.mips.COM> dce@mips.COM (David Elliott) writes:
- \f3words to be in bold\f1
- Correct me if I'm wrong, but I thought that the proper way to do
- this is
- \f3words to be in bold\fP
- That way, you don't screw up macros that use .ft to put the font
- back the way it was.
The fonts don't stack; only the one most recent previous font is remembered.
Although \f3...\f1 is a bit sloppy, if the following text is indeed intended
to be in font 1 (regular), then this usage isn't technically wrong.