Behaviour of \latinfamily

Thierry Bouche
Tue, 26 May 1998 16:05:22 +0200 (MET DST)

 I don't know exactly, at which point .fd files come into play.

the last point, it's the \installfamily that records what should be
output, and \endinstallfonts actually takes care of producing the fd's.

 In general, fontinst needs an .mtx file to start the reencoding
 business, which is can generate itself from .afm or .pl files.

yes, with \afmtomtx, \mtxtopl and so on...

 \installrawfont is trickier, but I suppose it is the interanl
 function which is called by higher-level \installfont macros
 and eventually produces an .fd file from a temporary .mtx file.

i don't think so, it is rather a simplified version that produces
ligfull TFMs rather than VFs (at an early  step in finst history, i
believe that 8r base fonts were done with afm2tfm, then Constantin
Kahn came with \installrawfonts...)

 > But I've never seen fontinst place any entries in a 8r.fd file, even
 > though it's created 8r.fd files for me quite happily.
 This might be a problem indeed.  The default settings of \latin_encodings
 tell fontinst to proudce OT1 and T1 only, so I don't know, why this is 
 generated in the first place.

i never use \latinfamily ;-) (because i prefered to use my own shell
scripts to build driver files rather than rely on latinfamily, but i
think \latinfamily{pbv}{} is more or less equivalent to 



so it should install  8r fonts & fd.

 > In particular, I've not seen fontinst substitute it for ui.
 I believe it does so or OT1 only because of \pounds vs. \dollar.

you mean it _should_. i also tested that and did not get what i expected.

   If there is no other doucmentation, you have
 no choice but 

writing it! ;-)
Th. B.