| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Adress issue #350
For some reason our stack copy of the current node gets double-freed.
Since the “components” field will probably vanish soon, we can get by
for now by skipping the explicit free.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Fix issue #351
The letterspace node handler dereferences kern values of non-existant
character information under some circumstances, causing Luatex to crash.
To avoid this crash, check more thoroughly for the presence of the
fields accessed.
Discovered by @schlcht
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This addresses one error reported by u/priyadarshan:
https://github.com/lualatex/luaotfload/issues/310
Some chained node field access got garbled during the update to nuts.
|
|
|
|
|
|
|
|
|
| |
Fix https://github.com/lualatex/luaotfload/issues/297
Interword glue hasn’t been considered yet. This again adapts the
relevant logic from Context to our letterspacing method. The code is
deliberately simplistic and will most likely not address all
constellations of a glue preceding a character.
|
| |
|
|
|
|
| |
Letterspacing should be functional again.
|
|
|
|
|
|
|
|
|
| |
This is an experiment: The character kerning callback has been converted
in its entirety to utilize the not-so-new direct node API. Since the
translation was mechanical only to a certain extent, this may have
introduced errors. On the other hand, the revised code resembles its
distant ancestor in Context’s ``typo-krn.lua`` much more closely again,
which may come in handy in the future.
|
|
|
|
|
|
| |
fix https://github.com/lualatex/luaotfload/issues/258
This fix was proposed by /u/saidai-no on Github.
|
|
|