From: Hans Hagen <pragma@wxs.nl>
Cc: bourbaki@bigfoot.com, ntg-context@ntg.nl
Subject: Re: Re[3]: Enabling protruding
Date: Thu, 24 Jan 2002 17:05:11 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20020124170237.02d7b700@server-1> (raw)
In-Reply-To: <20020124163607.31770881.taco@elvenkind.com>
At 04:36 PM 1/24/2002 +0100, Taco Hoekwater wrote:
>On Thu, 24 Jan 2002 14:45:25 +0100
>"Hans Hagen" <pragma@wxs.nl> wrote:
>
> > sure, but the main problem is that one cannot ask the filesystem what
> fonts
> > there are (try to open a font file from within tex); also, building this
> > into context only for cmr is not worth the trouble and slowing down
> overhead
>
>Well, actually, this works ...
>
>\newif\iffontexists
>
>\def\testfont#1{{\batchmode
> \global\fontexistsfalse
> \font\junk=#1\junk
> \ifdim\fontdimen5\junk>0pt
> \global\fontexiststrue
> \fi }}
>
>\testfont{cmr10 }
>\testfont{cmmmr10 }
i know -)
actually i had this for some time (and in font-ini.tex there is still the
leftover:)
% safer but sometimes introducing newlines in the log
%
% \batchmode
% \font\lastloadedfont\fontfile\somefontspec\relax
% \errorstopmode
% \edef\lastfontname{\fontname\lastloadedfont}%
% \ifx\lastfontname\nullfontname
% \showmessage{\m!fonts}{10}{\fontfile}%
% \expandafter\font\csname#1\endcsname=\defaultfontfile\somefontspec\relax
% \else
% \expandafter\let\csname#1\endcsname\lastloadedfont
% \fi
as commented: newlines in th elog, and i hate an ungly log
a pitty that a decent test didn't make it into etex
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
fall-back web server:
www.pragma-pod.nl
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-01-24 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 16:28 Giuseppe Bilotta
2002-01-23 17:21 ` Hans Hagen
2002-01-23 18:44 ` Re[2]: " Giuseppe Bilotta
2002-01-24 10:32 ` Hans Hagen
2002-01-24 11:10 ` Re[3]: " Giuseppe Bilotta
2002-01-24 13:45 ` Hans Hagen
2002-01-24 15:36 ` Taco Hoekwater
2002-01-24 16:05 ` Hans Hagen [this message]
2002-01-25 14:47 ` Re[5]: " Giuseppe Bilotta
2002-04-15 11:08 ` no hanging punctuation Albrecht Kauffmann
2002-04-18 9:05 ` Lutz Haseloff
2002-04-18 10:19 ` Patrick Gundlach
2002-04-18 10:33 ` Lutz Haseloff
2002-04-18 12:10 ` Bill McClain
2002-01-25 15:38 ` Enabling protruding Bill McClain
2002-01-25 16:15 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.1.0.14.1.20020124170237.02d7b700@server-1 \
--to=pragma@wxs.nl \
--cc=bourbaki@bigfoot.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).