[luatex] [Dev-luatex] Luatex 0.78.0 announcement
Hans Hagen
pragma at wxs.nl
Thu Jan 2 19:06:54 CET 2014
On 1/2/2014 10:58 AM, Paul Isambert wrote:
> Taco Hoekwater <taco at bittext.nl> a écrit:
>> Hi,
>>
>> I have just uploaded the archives for a new luatex release, 0.78.0.
>> This release merges some experimental branches, and fixes a few of the
>> outstanding bugs.
>
> Thanks Taco and the team!
>
>> * Instead of using expanded fonts, just calculate the expanded
>> width of glyphs where needed, and carry expand info in the
>> glyph nodes (all based on Hans' suggestions). All font expansion
>> functions are disabled and most are removed.
>
> Nice: now glyphs in expanded lines still have their original “font”
> field.
>
> If I’m not mistaken, the width of and expanded glyph (or kern) is:
>
> n.width + n.width * n.expansion_factor/1,000,000
>
> Is that correct?
>
> [Note that “expansion_factor” is mentionned but not documented for
> kerns.]
because expanded kerns might disappear (makes no sense to expand kerns)
or become optional
>> * New, faster (but limited) direct node access from lua, see
>> the manual for details
>
>>From what I can understand from the manual, “node.getnext(n)” is
> faster than “node.next(n)” which is faster than “n.next”; but faster
> still is “node.direct.getnext(node.direct.todirect(n))”; is that
> correct?
>
> [The “todirect” function is said to exist in both “node” and
> “node.direct”, but it is only in the latter.]
yes, but only faster in extreme cases (it's also a trade of between
readability n.next and speed node.direct.getnext(n))
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
More information about the luatex
mailing list