X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1400" "Mon" "8" "March" "93" "11:00:44" "GMT" "spqr@MINSTER.YORK.AC.UK" "spqr@MINSTER.YORK.AC.UK" nil "30" "Re: Fonts and LaTeX 3" "^Date:" nil nil "3"]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/1.9.92 ) id AA12979; Mon, 8 Mar 93 12:16:19 +0100 Received: from vm.urz.Uni-Heidelberg.de (vm.hd-net.uni-heidelberg.de) by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/19.6.92) id AA03586; Mon, 8 Mar 93 12:16:04 +0100 Message-Id: <9303081116.AA03586@sc.zib-berlin.dbp.de> Received: from DHDURZ1 by vm.urz.Uni-Heidelberg.de (IBM VM SMTP V2R2) with BSMTP id 3407; Mon, 08 Mar 93 12:16:14 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 4809; Mon, 08 Mar 93 12:16:06 CET Received: from DHDURZ1 by DHDURZ1 (Mailer R2.08 R208004) with BSMTP id 4807; Mon, 08 Mar 93 12:16:04 CET Reply-To: Mailing list for the LaTeX3 project Date: Mon, 8 Mar 93 11:00:44 GMT From: spqr@MINSTER.YORK.AC.UK Sender: Mailing list for the LaTeX3 project To: Multiple Recipients of Subject: Re: Fonts and LaTeX 3 Status: R X-Status: X-Keywords: X-UID: 1000 > Sometimes I'd like to keep cmtt (or, indeed, cmsf) and only replace cmr > with a PS font. But this requires some work because font encoding between > MF fonts and PS fonts normally differ slightly. So I'd like commands to > switch between different font encodings. Frank has implemented this in NFSS2, due out imminently. he says (and I tend to agree) that the neatest solution is to standardize on DC encoding for CM, and use dc-encoded PS fonts [1]. then the issue goes away (though the encoding-change stuff is there if needed) > I'd like to be able to turn _off_ ligatures at large point sizes because > ligatures look to cramped. But this can't be done from a macro > unfortunately, you'd have to have to build tfm's for different point why not, indeed > A solution to some of this is to write a program, say, xfm2sty, that takes > a font metric file (or a bunch of metric files of the same font family) > and writes a macro that contains commands to manipulate fonts. Say, Adobe > Garamond gives rise to a macro \AdobeGaramond that switches to Adobe > Garamond Regular at \family{garamond}\selectfont\rm, SemiBold at \bf, etc. i think a "program" is overkill. a Makefile, perhaps? its just a question of tacking the appropriate tools together, isn't it? sebastian [1] tools available from ftp.tex.ac.uk:pub/archive/fonts/postscript/dcps, but don't use the font names there