> file foo:
>
> .nr q 1
> .nr N 1
> .af q i
> .ie (\n[q]=1)&(\n[N]=1) .tm Ho!
> .el .tm boo
> .fp 1 PR
> .fp 2 PI
> .fp 3 PB
> .fp 4 PBI
> .fp 5 CW
> .fp 6 CI
> .fp 7 CB
> .fp 8 H
> .fp 9 HB
> .ds HF 3 3 3 4 4 4 3
> .BR bold roman
>
> groff -ww -mm foo > foo.ps
>
> bug.r:4: expected `;' after scale
When I used AT&T troff at HP about 15-20 years ago, there was no
".fam" request available, and \fR *always* went to "Times Roman".
The advantage of using \f1 through \f4 in text and the .fp request
was that one could rearrange the typography of a 3000 page manual by
changing the font selected by e
On 2/18/06, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
[snip]
>
> This is not correct. The example DESC file for a PostScript printer
> given in the Troff User's Manual (CSTR 54), section 23, is as follows.
>
> position 1 = R
> position 2 = I
> position 3 = B
> position 4 = BI
> ...
>
Werner LEMBERG wrote:
I used New Century Schoolbook for fonts 1, 2, and 3, and Courier for
font 4. They were specified by four lines in the manpage macros I
was using that I had modified from the AT&T to suit my own purposes.
This is still possible.
I assume the .fam request came along when
> I used New Century Schoolbook for fonts 1, 2, and 3, and Courier for
> font 4. They were specified by four lines in the manpage macros I
> was using that I had modified from the AT&T to suit my own purposes.
This is still possible.
> I assume the .fam request came along when groff was invented
> > I don't see how this is related to the concept of accessing a font
> > position directly. \f[B] does the same, doesn't it?
>
> It does now, but in 1989-1993 there was no .fam request, and it was
> much easier to use .fp instead of \f(NB or some such thing in a
> macro file, having to change i
