From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: fonts / proposal
Date: Mon, 06 Aug 2001 10:29:14 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010806102656.02ad6250@server-1> (raw)
In-Reply-To: <161016672.20010803220612@bigfoot.com>
At 10:06 PM 8/3/2001 +0200, Giuseppe Bilotta wrote:
>Friday, August 03, 2001 Hans Hagen wrote:
>
>HH> Hi,
>
>HH> I'm currently working on fonts, not so much in context itself, as well as
>HH> installation. Since i want a clean way to install fonts [commercial ones
>HH> for instance] and since licence policy is always tricky, i now put
>them in
>HH> a dedicated tree texmf-fonts.
>
>I think the TeX Directory Standard puts fonts under
>
>\texmf\fonts\<type>\<class>\<vendor>\<name>
>
>e.g.
>
>\texmf\fonts\type1\public\ams\cmr
>
>or something of the sort.
right, and since i like to delete and reinstall the base path's i don't
want my own fonts or patches there -)
I think the (only) problem with this is that it fails on pure DOS
>system (8.3 naming constrictions). Since the font naming is X
>Windows-like, why don't you just use the X Windows scheme?
right, in which case one can use filemapping to map back on 8 char names
for which i provide
\usetypescript [map][berry]
>I don't find any objections. The recursive fontsynonym technique
>also allows for automagic font substitutions: if
>ec-uplr8a-slanted-167 is not available, it can be mapped to the
>closer available font (e.g. removing the 167, which would seek
>for a "default" slanted font, then removing the "slanted" etc;
>something like using a * in a fontname part under X Windows).
right, can even be automated,
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-08-06 8:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 15:32 Hans Hagen
2001-08-03 20:06 ` Giuseppe Bilotta
2001-08-04 11:45 ` Taco Hoekwater
2001-08-06 8:29 ` Hans Hagen [this message]
2001-08-07 17:59 ` Re[2]: " Giuseppe Bilotta
2001-08-08 8:32 ` Hans Hagen
2001-08-04 12:30 ` siepo
2001-08-06 8:38 ` Hans Hagen
2001-08-06 9:22 ` siep
2001-08-06 12:13 ` Hans Hagen
2001-08-06 13:14 ` siep
2001-08-07 8:40 ` Taco Hoekwater
2001-08-08 9:13 ` Hans Hagen
2001-08-08 9:34 ` siep
2001-08-08 12:13 ` 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.20010806102656.02ad6250@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).