Received: by nummer-3.proteosys id <01C19443.9309CE44@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:09 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.9309CE44" x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 x-to: LATEX-L%DHDURZ1.BITNET@uga.cc.uga.edu Content-class: urn:content-classes:message Subject: Magsteps/design sizes Date: Wed, 8 Jan 1992 02:07:00 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Don Hosek" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 512 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.9309CE44 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Regarding the issue of magsteps vs design sizes and how much more incompatible LaTeX would be from plain should we avoid scaled fonts in lfonts.tex, my observations: - Adding true design-sized fonts for the missing holes would add some 30-40 fonts to the system at most (and I think this may be a generous estimate). - This means that LaTeX files would need some fonts that aren't part of the default set. This has been true to a certain extent in the past, but now becomes more dramatic. - My experience has been that plain-based sites almost always begin to adopt LaTeX and over time LaTeX becomes the dominant macro package. The primary exception is where TeX use tends to have a strong personality directing it which is rare in multi-user environments. The most common case where someone is likely to be plain-only is in a single user situation. In these cases, there would need to be additional files installed which might not otherwise be used. - On the other hand, the change is intended to be part of the LaTeX3 upgrade so will only affect someone who's going through the trouble of installing all the new LaTeX stuff anyway so why not add the extra fonts into the package. Personally, I'm inclined to say that if it's complete at the time of the LaTeX3 release, perhaps LaTeX3 should be ec-based rather than cm-based! (Assuming of course that the math font problem is addressed... TeX's math typesetting looks so flexible at first blush doesn't it? fooled ya!) - By the way, if memory serves (and it usually doesn't) ec/dc has something like the Sauter scaling built in so getting 18pt, 24pt etc. type should not be too horrible. -dh ------_=_NextPart_001_01C19443.9309CE44 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Magsteps/design sizes

Regarding the issue of magsteps vs design sizes and = how much more
incompatible LaTeX would be from plain should we = avoid scaled
fonts in lfonts.tex, my observations:

- Adding true design-sized fonts for the missing holes = would add
  some 30-40 fonts to the system at most (and I = think this may be
  a generous estimate).
- This means that LaTeX files would need some fonts = that aren't
  part of the default set. This has been true to = a certain extent
  in the past, but now becomes more = dramatic.
- My experience has been that plain-based sites = almost always
  begin to adopt LaTeX and over time LaTeX = becomes the dominant
  macro package. The primary exception is where = TeX use tends to
  have a strong personality directing it which = is rare in
  multi-user environments. The most common case = where someone is
  likely to be plain-only is in a single user = situation. In these
  cases, there would need to be additional files = installed which
  might not otherwise be used.
- On the other hand, the change is intended to be = part of the
  LaTeX3 upgrade so will only affect someone = who's going through
  the trouble of installing all the new LaTeX = stuff anyway so
  why not add the extra fonts into the package. = Personally, I'm
  inclined to say that if it's complete at the = time of the LaTeX3
  release, perhaps LaTeX3 should be ec-based = rather than
  cm-based! (Assuming of course that the math = font problem is
  addressed... TeX's math typesetting looks so = flexible at first
  blush doesn't it? fooled ya!)
- By the way, if memory serves (and it usually = doesn't) ec/dc has
  something like the Sauter scaling built in so = getting 18pt,
  24pt etc. type should not be too = horrible.

-dh

------_=_NextPart_001_01C19443.9309CE44--