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.
>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
>How would your scripts handle `real' oldstyle figure and small caps
>fonts and expert sets? The character sets of these don't seem to be
>entirely standardized. I think that was the reason why I needed
>low-level fontinst macros to use my Times OSF&SC fonts even though I had
>expected the high-level latinfamily fontinst macro to generate the vfs
>and tfms that I wanted.
right, and i think in this respect fontinst is more powerful; the thing
that i have in mind are for users (like me) who have not the faintest idea
about what font tricks can be done.
in a later stage i will certainly look into expert fonts and alike [maybe
taco wants to extend afm2tfm a bit for this], and there i definitely need
your expertise in the font field -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | [EMAIL PROTECTED]
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
-------------------------------------------------------------------------
