Received: by nummer-3.proteosys id <01C19443.96FBF1DC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:15 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.96FBF1DC" 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: Sebastian is right, as usual (was: NFSS2 alpha comments) Date: Thu, 9 Jan 1992 12:59:30 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 530 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.96FBF1DC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Rainer writes: > I didn't think of that. Still, there is the problem, that for a random > font name TeX might still produce an error while scanning it. Example: = If > "\font\xyz=3Dcmr15.28 " is generated what will the run-of-the-mill TeX > implementation do? You are right (of course!). > > But this leads us too far... Not at all, it is at the heart of what the NFSS can and, in this case, cannot do. chris ------_=_NextPart_001_01C19443.96FBF1DC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Sebastian is right, as usual (was: NFSS2 alpha = comments)

Rainer writes:

> I didn't think of that. Still, there is the = problem, that for a random
> font name TeX might still produce an error while = scanning it. Example: If
> "\font\xyz=3Dcmr15.28 " is generated = what will the run-of-the-mill TeX
> implementation do?
You are right (of course!).

>
> But this leads us too far...
Not at all, it is at the heart of what the NFSS can = and, in this case,
cannot do.


chris


------_=_NextPart_001_01C19443.96FBF1DC--