Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!decwrl!hplabs!sdcrdcf!sdcsmb!sea!eggert From: eggert@sm.unisys.com (Paul Eggert) Newsgroups: comp.text Subject: Re: inherent troff faults Message-ID: Date: 12 Jun 88 01:26:49 GMT References: <1309@goanna.oz> Organization: Unisys Santa Monica Lines: 24 In article <1309@goanna.oz> isaac@goanna.oz (Isaac Balbin) writes that given .EQ gfont C .EN .sh 2 "The $call$ function" his (eqn | ditroff -me) formatter prints "function" in roman, not bold as it should. This may arise from a common problem: in some buggy ditroffs, \fP doesn't work if you're switching among fonts not mounted by default. A workaround is to place a directive like .fp 4 C at the start of the input, substituting some unused font number for `4'. This will permanently mount font C, dodging the bug. Balbin also writes: I once heard from an unnamed very well known guru that these things can be fixed, but then lots of documentation would be broken. The bug I've described has been fixed in our ditroff, and it doesn't break any documentation. Perhaps the guru was referring to the fact that \fX...\fP doesn't nest, but this doesn't seem to be the problem here.