From: siep@elvenkind.com
Cc: ntg-context@ntg.nl
Subject: Re: fonts / proposal
Date: Mon, 6 Aug 2001 11:22:45 +0200 (CEST) [thread overview]
Message-ID: <200108061017.MAA29360@plane.elvenkind.com> (raw)
In-Reply-To: <5.1.0.14.1.20010806103249.02acead0@server-1>
On 6 Aug, Hans Hagen wrote:
> At 12:30 PM 8/4/2001 +0000, siepo@cybercomm.nl wrote:
>
>> > (5) typescript files will mape symbolic names in an efficient way
>>
>>What do you mean by efficient?
>
> say
>
> \usetypescript [palatino] [ec]
>
> and
>
> \usetypescript [times] [ec[
>
> and then use \palatino and \times to swhich between font collections.
>
> Also, to be able to combine predefined typescripts.
>
>> > (6) map files will be loaded at run time [when enabled]
>>
>>What do you mean by this?
>
> that, instead of editing the pdftex.map file, context will instruct pdftex
> to load the map files needed.
For me, it is a frequent source of confusion when Context does things
its own way. Filesearching deviating from kpsewhich filesearch was one
example; mapfile loading different from what dvips and pdftex do on
their own would be another.
>>Is there going to be LaTeX support?
>
> The current tools and texmf tree is rather tuned for latex. I think latex
> users are already served by fontinst and all those fd files. Bu
Well, I am primarily a LaTeX user, but would welcome an alternative to
fontinst and would certainly like to have a single font setup for all
TeX macro packages. For regular text fonts, creating fd files should be
no big deal, and maybe I could contribute there.
Siep
next prev parent reply other threads:[~2001-08-06 9:22 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 [this message]
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=200108061017.MAA29360@plane.elvenkind.com \
--to=siep@elvenkind.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).