Received: by nummer-3.proteosys id <01C19443.93C2B7BC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:10 +0100 In-Reply-To: Don Hosek's message of Tue, 7 Jan 92 16:05:00 PST <9201080006.AA09782@ufer.ZIB-Berlin.DE> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.93C2B7BC" Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> X-MimeOLE: Produced By Microsoft Exchange V6.5 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-to: LATEX-L%DHDURZ1.BITNET@vm.gmd.de Content-class: urn:content-classes:message Subject: Sebastian is right, as usual (was: NFSS2 alpha comments) Date: Wed, 8 Jan 1992 10:08:10 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rainer Schoepf" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 516 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.93C2B7BC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Don writes: Not that it's necessarily practical but it is possible to check the availability of a TFM file from TeX: - Switch to \batchmode - Attempt to load the font - If the font is not available, \meaning\fontname expands to "select font nullfont" 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? But this leads us too far... Rainer ------_=_NextPart_001_01C19443.93C2B7BC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sebastian is right, as usual (was: NFSS2 alpha = comments)

Don writes:

   Not that it's necessarily practical but = it is possible to check
   the availability of a TFM file from = TeX:

   - Switch to \batchmode
   - Attempt to load the font
   - If the font is not available, = \meaning\fontname expands to
     "select font = nullfont"

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?

But this leads us too far...

Rainer

------_=_NextPart_001_01C19443.93C2B7BC--