Re: mfonts.tex from manuals

Re: mfonts.tex from manuals

[Mojca Miklavec]

piskala upendran wrote:
> hi, Mojca
>
> The complain about the fonts is 8t encoding. use 8r
> encoding. it should work ok.
>
> I got the palatino font using 8r encoding using the
> following.
>
> \usetypescript [adobekb][\defaultencoding]
> \usetypescript [palatino][\defaultencoding]
> \setupbodyfont[palatino,10pt]
>
> it should compile ok.

Thank you very much. I replaced
    \usetypescriptfile[type-buy]
with
    \usetypescript [adobekb][\defaultencoding]
which finally worked.

Installing cont-fnt as Hans suggested didn't have any influence at all.


However, now some really strange bug(?) appeared.
\type{\whatevercommand} doesn't work inside \starttabulate ...
\stoptabulate. This is only true for MikTeX, everywhere else it works
OK. \starttabulate and \type{\whatevercommand} both work when they are
used separately, but fail when \type comes inside \starttabulate.

It may be that MikTeX is a bit "old" (27.10.), but there is no newer
version available yet, so I hope that the problem will go away with
the next version.

Mojca


! Missing $ inserted.
<inserted text>
                $
<to be read again>
                   \atop
\tabulatecontent ->\NC \type {\atop
                                    } \NC \NR
\fulltabulatecontent ...dcontent \tabulatecontent
                                                  \tabulatetailcontent \remo...

\processtabulate ...sa \crcr \fulltabulatecontent
                                                  \crcr }}\ifnum \nofautotab...
l.4 \stoptabulate

?

Re: Re: mfonts.tex from manuals

[Taco Hoekwater]

Mojca Miklavec wrote:
> piskala upendran wrote:
> 
> Thank you very much. I replaced
>     \usetypescriptfile[type-buy]
> with
>     \usetypescript [adobekb][\defaultencoding]
> which finally worked.
> 
> Installing cont-fnt as Hans suggested didn't have any influence at all.

The problem is caused by the (no longer valid) Palatino => uplXXX
mapping in type-dis.tex (current distributions only ship the URW
metrics under the Adobe name, not using the URW naming).

Those mappings will go away soon, and then this will be no longer
a problem.

> It may be that MikTeX is a bit "old" (27.10.), but there is no newer
> version available yet, so I hope that the problem will go away with
> the next version.

Yes, the problem will go away. It was fixed in the 2005.11.24 or so.

Cheers, Taco