From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/5204
Path: main.gmane.org!not-for-mail
From: siep@elvenkind.com
Newsgroups: gmane.comp.tex.context
Subject: Re: fonts / proposal
Date: Mon, 6 Aug 2001 11:22:45 +0200 (CEST)
Sender: owner-ntg-context@let.uu.nl
Message-ID: <200108061017.MAA29360@plane.elvenkind.com>
References: <5.1.0.14.1.20010806103249.02acead0@server-1>
Reply-To: siep@elvenkind.com
NNTP-Posting-Host: coloc-standby.netfonds.no
Mime-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
X-Trace: main.gmane.org 1035395808 32071 80.91.224.250 (23 Oct 2002 17:56:48 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 23 Oct 2002 17:56:48 +0000 (UTC)
Cc: ntg-context@ntg.nl
Original-To: pragma@wxs.nl
In-Reply-To: <5.1.0.14.1.20010806103249.02acead0@server-1>
Xref: main.gmane.org gmane.comp.tex.context:5204
X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:5204

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