X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1427" "Thu" "30" "December" "1993" "22:48:00" "+0200" "Joerg Knappen Uni-Mainz" "KNAPPEN@VKPMZD.KPH.UNI-MAINZ.DE" nil "39" "No more magnified fonts!" "^Date:" nil nil "12" nil nil]) Return-Path: Received: from sc.ZIB-Berlin.DE (mailserv) by dagobert.ZIB-Berlin.DE (4.1/SMI-4.0/24.6.93) id AA23045; Thu, 30 Dec 93 22:53:13 +0100 Received: from mail.cs.tu-berlin.de by sc.ZIB-Berlin.DE (4.1/SMI-4.0-sc/03.06.93) id AA04672; Thu, 30 Dec 93 22:53:06 +0100 Received: from tubvm.cs.tu-berlin.de by mail.cs.tu-berlin.de with SMTP id AA23661 (5.65c8/IDA-1.4.4(mail.m4[1.12]) for <@MAIL.CS.TU-BERLIN.DE:Schoepf@SC.ZIB-BERLIN.DE>); Thu, 30 Dec 1993 22:53:05 +0100 Message-Id: <199312302153.AA23661@mail.cs.tu-berlin.de> Received: from TUBVM.CS.TU-BERLIN.DE by tubvm.cs.tu-berlin.de (IBM VM SMTP V2R2) with BSMTP id 4199; Thu, 30 Dec 93 22:53:26 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin MAILER@DHDURZ1) by TUBVM.CS.TU-BERLIN.DE (LMail V1.2a/1.8a) with BSMTP id 4197; Thu, 30 Dec 1993 22:53:27 +0200 Received: from VM.URZ.UNI-HEIDELBERG.DE (NJE origin LISTSERV@DHDURZ1) by VM.URZ.UNI-HEIDELBERG.DE (LMail V1.2a/1.8a) with BSMTP id 5905; Thu, 30 Dec 1993 22:52:36 +0000 Reply-To: Mailing list for the LaTeX3 project Date: Thu, 30 Dec 1993 22:48:00 +0200 From: Joerg Knappen Uni-Mainz Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: No more magnified fonts! Status: R X-Status: X-Keywords: X-UID: 1242 Shall LaTeX2e continue the use of magnified cm-fonts ? With optical scaled fonts at each size, LaTeX documents look much better. Since these are available both for the OT1 fontencoding (Sauter tools) and the new T1 fontencoding (edit dcstdedt.tex appropriately), there is no need to stay with any fonts \magstepwhatever. May I ask the LaTeX3 team to make the Sauter fonts default for LaTeX2e ? --J"org Knappen. P.S. I configured LaTeX2e at our site to use the Sauter fonts, making the font definition files very compact. However, some trial definitions do not work, see the snippet below. % The reordering of macro parameters is an artefact from NFSS-1, which made % the re-writing of this file easier. \def\sauter@family#1#2#3#4#5{% \DeclareFontShape{#1}{#2}{#4}{#5}{% % The following line failed, but the functionality can be achieved with a % little more effort. Note the strange looking `\#37'. % <5> <6> <7> <8> <9> <10> gen * #3 %% does not work! Therefore... <5> #35 <6> #36 <7> #37 <8> #38 <9> #39 <10> #310 <10.95> #311 % looks ugly, but {#3}11 does not work <12> #312 <14.4> #314 <17.28> #317 <20.74> #320 <24.88> #325 }{}% } % end of definition of sauter@family. % An example follows: %% DCR medium \DeclareFontFamily{T1}{cmr}{}{} \sauter@family{T1}{cmr}{dcr}{m}{n} \sauter@family{T1}{cmr}{dcsl}{m}{sl} \sauter@family{T1}{cmr}{dcti}{m}{it} \sauter@family{T1}{cmr}{dccsc}{m}{sc} % [...]