Behdad Esfahbod
Behdad Esfahbod
> Any tips to print useful debug messages from Harfbuzz at runtime? Try building with `HB_DEBUG_BLOB` or `HB_DEBUG` or `HB_DEBUG=100`. The first one might be enough for this problem.
> is it this the reason of: > freetype2/bin/lib/libfreetype.a(autofit.c.obj):autofit.c:(.text+0x4009): undefined reference to `hb_ft_font_create'? Not *really*. You need to link HarfBuzz as well.
I definitely have thought about this option. For example, that's what I did in Glyphy. But I don't see it solving much of the problem in our case. It helps...
Thanks. Interesting. For libass uses I would have guessed that people will build freetype without harfbuzz and then build harfbuzz with freetype. The "freetype WITH harfbuzz" is only relevant to...
Right. I agree.
We would love to help but we don't know of any good solution currently. Splitting our tarball into two or three is a major nuisance to us and our downstream...
I would argue, a better solution is that freetype can duplicate hb-ft. With some coordination we can probably make that work without too much resource duplication. Let me think about...
> I believe that moving `hb-ft` into freetype That doesn't work. `hb-ft` uses harfbuzz-internal machinery. It would need to be rewritten to freetype facilities and C, instead of C++ if...
Another problem is that currently we include hb-ft in libharfbuzz.so. So removing it will be an ABI break for linux distros. I suggest we do that for harfbuzz 4.0.0. We...