Re: compilation is stuck! (problems with postscript fonts on unix)

["Uwe Koloska" <uwe.koloska@mailbox.tu-dresden.de>]

You wrote on Son, 05 Nov 2000:
>At 08:45 PM 11/3/00 +0100, you wrote:
>
>>Ok, so I have added MKTEXTFM = 0 to my texmf.cnf file, and this helps.
>
>Interesting, since in texexec I set this env var to 0 but maybe not
>correctly for unix. Can someone check this?

I have downloaded the context beta yesterday with texexec 2.3 (BTW: in the
modul header there is version=2000.03.25) and there is no MKTEXTFM in it. 
But I am no perl expert so if it is set in a file sourced by texexec ...

>in context, font names are resolved as late as possible, and ber [you can
>search for a file font-ber.tex and take a look] maps the fonts to berry
>names, which I suppose you use. 
>

Why do you use the URW name for palatino?  AFAIK the URW font is an exact
replacement for the adobe one (in terms of metrics) and so teTeX uses the
adobe names for the standard 35 postscript fonts and only substitutes the
pfb-files.

So with my (regarding to fonts) non modified teTeX beta the adobe names
has to be used for the standard 35 postscript fonts:

\definefontsynonym [Palatino-Roman]             [pplr8t]  [encoding=ec]
\definefontsynonym [Palatino-Italic]            [pplri8t] [encoding=ec]
\definefontsynonym [Palatino-Slanted]           [pplro8t] [encoding=ec]
\definefontsynonym [Palatino-Bold]              [pplb8t]  [encoding=ec]
\definefontsynonym [Palatino-BoldItalic]        [pplbi8t] [encoding=ec]
\definefontsynonym [Palatino-BoldSlanted]       [pplbo8t] [encoding=ec]

Uwe

-- 
mailto:koloska@rcs.urz.tu-dresden.de
http://rcswww.urz.tu-dresden.de/~koloska/
--                                    --
right now the web page is in german only
but this will change as time goes by ;-)