ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Cc: ntg-context@ntg.nl, pragma@wxs.nl
Subject: Re: fonts / proposal
Date: Tue, 07 Aug 2001 10:40:20 +0200	[thread overview]
Message-ID: <3B6FA974.7DBA7E50@elvenkind.com> (raw)
In-Reply-To: <200108061409.QAA29928@plane.elvenkind.com>

siep@elvenkind.com wrote:
>
> What about letting out-of-the-box pdftex and dvips read the same
> mapfiles that they would read outside Context, and letting Context use
> kpsewhich for all its file searching, and that any non-standard
> behaviour would have to be explicitly turned on in a configuration file?

One way out of this should be create font-name mapping entries for the
new system. the 'fontname' directory in your TeX tree. Then users can
decide for themselves whether or not they want the new-style names.

I don't really know how this works though, and I am not too eager to
find out how it *should* work (and it doesn't solve the IMO nastiest
problem:
2 times [a-z0-9] is just not enough for the family name to be anywhere 
near meaningful: most big vendors have more than 36*36 font families
available).

-- 
groeten,

Taco


  reply	other threads:[~2001-08-07  8:40 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
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 [this message]
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=3B6FA974.7DBA7E50@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).