Re: Metafont and Context

["Wolfgang Werners-Lucchini" <wwl@musensturm.de>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=Default, Size: 3371 bytes --]

Hallo!

> > > Has anybody written typescripts for one of the Metafonts available
> > > at CTAN and can send me an example or two?
> 
> I've added a Metafont example to my page:
> 
>     http://home.salamander.com/~wmcclain/context-help.html#newfont-mf
> 
> I don't know much about Metafont, and your comments (as always) are
> welcome. 
> 
> In particular, I have two questions:
> 
> (1) I don't specify encoding, because I'm not sure how encoding
> interacts with MF. Is it even required? The typescript works without
> encoding references.
> 
> (2) texexec + pdftex do not generate .pk files like xdvi does. Is that
> an option I've missed? In the example I give I first create a .dvi
> version of the file and have xdvi create the .pk files, which then can
> be read by pdftex.
> 
> -Bill

Thank you very much for your work!

Some questions about the typescript:

> % Typescript for the Duerer metafont typeface.
> %
> % The ``Informal'' is a serifed variation; I assign it to
> % italic so that we can access both it and slanted in the same
> % setup.
> %
> \starttypescript [serif] [duerer]
                                               ^ no [name] her?
>   \definefontsynonym [Duerer-Roman]       [cdr10]  
>   \definefontsynonym [Duerer-Bold]        [cdb10]  
>   \definefontsynonym [Duerer-Slanted]     [cdsl10] 
>   \definefontsynonym [Duerer-Informal]    [cdi10] 
> \stoptypescript
>
> \starttypescript [sans] [duerer]
                                                ^ no [name] her?
>  \definefontsynonym [Duerer-Sans]        [cdss10]  
> \stoptypescript
>
> \starttypescript [mono] [duerer]
                                                 ^ no [name] her?
>   \definefontsynonym [Duerer-Mono]        [cdtt10]  
> \stoptypescript
>
> \starttypescript [serif] [duerer] [name]
>   \definefontsynonym [Serif]              [Duerer-Roman]
>   \definefontsynonym [SerifBold]          [Duerer-Bold]
>   \definefontsynonym [SerifSlanted]       [Duerer-Slanted]
>   \definefontsynonym [SerifItalic]        [Duerer-Informal]
> \stoptypescript
>
> \starttypescript [sans] [duerer] [name]
>   \definefontsynonym [Sans]               [Duerer-Sans]
> \stoptypescript
>
> \starttypescript [mono] [duerer] [name]
>   \definefontsynonym [Mono]               [Duerer-Mono]
> \stoptypescript
>
> \starttypescript [Duerer] 
>   \definetypeface [Duerer] [rm] [serif] [duerer] [default] 
                                                                      ^
what is this 5th parameter for? I have to set this to the fontname?
>   \definetypeface [Duerer] [ss] [sans] [duerer] [default] 
>   \definetypeface [Duerer] [tt] [mono] [duerer] [default] 
> \stoptypescript

Why is there no section [size] needed? What are the defaults? I see, that
Duerer is designed only in one size. This is not always the case
with metafonts. For example, I should can say things like:

  Use font with designsize 10pt for all the fontsizes lower and equal to
10pt and scale acoordingly. 
  Use font with designsize 11pt for the fontsize 11pt.
  Use font with designsize 14.4pt for fontsizes from 12pt to infinity and
scale them.

What about encoding? For example, an OT1 font doesn't contains german
umlauts, a T1 font does. 

By the way, there is also a typescript-section [special]. What can I do
with this?

I will report about my attempts about my font 'bunt' in a second mail.

Gruß, Wolfgang