Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!unmvax!brainerd
From: brainerd@unmvax.unm.edu (Walt Brainerd)
Newsgroups: comp.text
Subject: Re: font families (was GNU troff)
Message-ID: <173@unmvax.unm.edu>
Date: 25 Jun 89 01:33:57 GMT
References: <779@pcrat.UUCP> <355@wjh12.harvard.edu> <8388@killer.DALLAS.TX.US> <15877@vail.ICO.ISC.COM>
Distribution: comp
Organization: University of New Mexico at Albuquerque
Lines: 12

In article <15877@vail.ICO.ISC.COM>, rcd@ico.ISC.COM (Dick Dunn) writes:
> 
> The one thing you really *don't* want to do is make \fI or .ft I change to
> italic of the current font family--that's a change to troff semantics.
> -- 

No, this is _not_ a change in troff semantics if it is in the context of
a previously executed .font.family (or whatever) command that is not
a "standard" troff command.  This is one of the things that is desired
so that one can take an existing source file and process it using
more than one font family without changing all of the usual commands
of the sort .ft I and  \fI.