> It has to do with the backend resolving fontnames and
> expansions factors
> and so ... first I need to hear from Hartmut what he thinks
> of it.
No stress :) I'll wait silently -- just wanted to submit, what I thought to be,
useful info.
cheers, Martin
__
On 31-7-2010 8:17, Martin Althoff wrote:
Could as well be a luatex backend problem so I have to
discuss it with Taco and Hartmut.
Hans
Hi Hans,
Thanks for looking into this further. I have tried to drill down the effect
being switchable through \setupfootertexts here are my results.
In th
> Could as well be a luatex backend problem so I have to
> discuss it with Taco and Hartmut.
>
> Hans
>
Hi Hans,
Thanks for looking into this further. I have tried to drill down the effect
being switchable through \setupfootertexts here are my results.
In the example below, I get (with the s
On 29-7-2010 12:12, Martin Althoff wrote:
I hate to pick up on this again, but...
The basic Palatino, together with protrusion and small caps is causing issues.
Essentially horizontal placing of the characters fails (see previous PDF).
In the example below, I can reliably cause the effect by c
I hate to pick up on this again, but...
The basic Palatino, together with protrusion and small caps is causing issues.
Essentially horizontal placing of the characters fails (see previous PDF).
In the example below, I can reliably cause the effect by commenting out (or
not) the line with the \
> Fonts are sometimes special and when ypu load a font it's
> setting (e.g. ligatures, protrusion etc.) are frozen. To change the
> settings you need \definefontfeature before \setupbodyfont,
OK, got it. Makes sense!
Could this also be extended to \switchtobodyfont, in case I am using more then
Am 28.07.10 02:31, schrieb Martin Althoff:
When setting up protrusion, I noticed it "disappearing" despite being
defined/setup. In a text, when I changed the font from Palatino to Sabon (with
\setupbodyfont[sabon]), protrusion stopped working. Changing back to palatino, with
nothing else chan
