Behdad Esfahbod
Behdad Esfahbod
Rewriting freetype's use of hb-ft.cc to a trimmed-down version is possible, it wouldn't even require the locking and caching mechanisms since inside freetype's use there won't be multiple threads. @rcombs...
> Rewriting freetype's use of hb-ft.cc to a trimmed-down version is possible, it wouldn't even require the locking and caching mechanisms since inside freetype's use there won't be multiple threads....
> But how does that get us any closer to a solution? I had misunderstood the original proposal. I think we still need the full hb-ft.cc implementation.
All I can say is that we still don't see a feasible way out of the current situation unfortunately.
Sounds related to the GDEF change we made and reverted. The carrying-forward of the flags is wrong... Anyway. I'll check later. This was just me speculating based on the title.
> unless you mean the old behavior was also wrong. Yes.
Simon found problems with pre-2.7.0 HB-no-GDEF. We tried to address, broke others. Even then there's more issues. I'll try to write them down here soon.
Let's revive this issue and figure out what needs to be fixed.
Fixed by https://github.com/harfbuzz/harfbuzz/pull/3365 ?
Can you send me the font in question please?