14 Oct
2022
14 Oct
'22
5:37 p.m.
On Fri Oct 14 16:44:58 2022 +0000, Fabian Maurer wrote:
I think it is because an applied lookup can lead to another lookup being applied, i.e. restart from 0 again. Not sure though. The way it works in dwrite right now, which is how it works in harfbuzz I took this from:
``` foreach feature in features foreach lookup in feature.lookups { for first subtable that matches -> apply this subtable and return } ``` So, it shouldn't skip lookups after some lookup was applied, it should skip subtables after first match, but still iterate through all lookups. That's a major difference. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1055#note_10758