Andreas Harder wrote:
>> I've a curious problem: With Palatino or Latin Modern kerning seems to
>> work as intended, but what's the matter with Minion (example below)?
> This appears to be caused by the fact that in MinionPro most
> (not all, but most) of the kerning is specified via kern c
Andreas Harder wrote:
>> I've a curious problem: With Palatino or Latin Modern kerning seems to
>> work as intended, but what's the matter with Minion (example below)?
> This appears to be caused by the fact that in MinionPro most
> (not all, but most) of the kerning is specified via kern cl
>> I've a curious problem: With Palatino or Latin Modern kerning
seems to
>> work as intended, but what's the matter with Minion (example below)?
> This appears to be caused by the fact that in MinionPro most
> (not all, but most) of the kerning is specified via kern classes.
Than you for expl
Andreas Harder wrote:
Hello,
I've a curious problem: With Palatino or Latin Modern kerning seems to
work as intended, but what's the matter with Minion (example below)?
This appears to be caused by the fact that in MinionPro most
(not all, but most) of the kerning is specified via kern classe
Hello,
I've a curious problem: With Palatino or Latin Modern kerning seems to work as
intended, but what's the matter with Minion (example below)?
\setupcolors[state=start]
% \mainlanguage[de]
\definefontfeature[basekerned][default][mode=base]
\definefontfeature[nodekerned][default][mode=nod