Received: by nummer-3.proteosys id <01C19443.93A2A024@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:10 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.93A2A024" 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 Content-class: urn:content-classes:message Subject: RE: re: fontdef issues Date: Wed, 8 Jan 1992 09:35:00 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "malcolm" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 515 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.93A2A024 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable i hate to take issue with rainer, but plain (at least as documented in the book), does contain three references to magstepped fonts. i would agree that these are not directly accessible (being preloaded, and not actually used in any of the bare bones macros in plain), and of course that is the one area of plain which can be modified while retaining the `name' plain. but still... yes, i expect to use both latex and plain-based macros as i wend my unstructured way through life. and just as i scale up my postscript fonts way beyond their design sizes, i'll tend to use CM at odd sizes too (btw: i find cminch scaled 500 to be quite convenient). i confess i rather like the idea of an integrated environment where a missing font is automagically generated on the fly. right now this tends to take us back into the realms of computer science departments or dedicated hackers. until a commercial (aargh, i said it, wash my fingers!) outfit implements such as a robust and easy to install program, it may tend to create rather than reduce barriers. malcolm ------_=_NextPart_001_01C19443.93A2A024 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: re: fontdef issues

i hate to take issue with rainer, but plain
(at least as documented in the book), does
contain three references to  magstepped
fonts. i would agree that these are not = directly
accessible (being preloaded, and not actually
used in any of the bare bones macros in = plain),
and of course that is the one area of plain = which
can be modified while retaining the `name' = plain.
but still...

yes, i expect to use both latex and plain-based
macros as i wend my unstructured way through
life. and just as i scale up my postscript = fonts
way beyond their design sizes, i'll tend to
use CM<design-size> at odd sizes too (btw: = i
find cminch scaled 500 to be quite = convenient).

i confess i rather like the idea of an = integrated
environment where a missing font is = automagically
generated on the fly. right now this tends to = take
us back into the realms of computer science = departments
or dedicated hackers. until a commercial (aargh, i = said it,
wash my fingers!) outfit implements such as a = robust
and easy to install program, it may tend to = create
rather than reduce barriers.

malcolm

------_=_NextPart_001_01C19443.93A2A024--