From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: river detection
Date: Wed, 10 Jan 2001 15:04:17 +0100 [thread overview]
Message-ID: <3.0.6.32.20010110150417.00973bf0@server-1> (raw)
In-Reply-To: <3A5C604F.EC239C0@quicknet.nl>
At 02:14 PM 1/10/01 +0100, Taco Hoekwater wrote:
>
>> >2) a perfectly simple single command like
>> > "texexec font tim" to auto-install
>> > all tim*.afm/.pfb files in a given directory ;=}}
>>
>> would ne a separate script then, more a texutil job btw
>
>In my 'spare' time, I'm working on a font interpreter
>module to be written in perl. This could be one of the
Good news!
>front-ends to that module eventually. In order to instaLL
>a font correctly, you also need some encoding information
>which requires parsing the font, so the solution is not
>as trivial as it looks on first sight.
Indeed. So, we limit ourselves to proper encodings -)
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
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-01-10 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 18:45 Ed L Cashin
2001-01-10 8:27 ` Hans Hagen
2001-01-10 16:58 ` Ed L Cashin
2001-01-10 17:38 ` Hans Hagen
2001-01-10 18:59 ` Ed L Cashin
2001-01-11 7:56 ` Hans Hagen
2001-01-11 20:21 ` Ed L Cashin
2001-01-12 14:57 ` H. Ramm
2001-01-10 10:40 ` Frans Goddijn
2001-01-10 11:29 ` Dan Seracu
2001-01-10 11:58 ` Hans Hagen
2001-01-10 11:57 ` Hans Hagen
2001-01-10 13:14 ` Taco Hoekwater
2001-01-10 14:04 ` Hans Hagen [this message]
2001-01-10 21:07 ` H. Ramm
[not found] <Hans Hagen's message of "Wed, 10 Jan 2001 18:38:13 +0100">
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=3.0.6.32.20010110150417.00973bf0@server-1 \
--to=pragma@wxs.nl \
--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).