On 6 Aug, Hans Hagen wrote:
> At 12:30 PM 8/4/2001 +0000, [EMAIL PROTECTED] 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
