(In reply to comment #23)
> (In reply to comment #22)
>
> > On Chrome Linux and Android we already switched to harfbuzz-ng. So, first step is to figure out who still uses harfbuzz.old and switch them over.
>
> To my knowledge, all upstream WebKit ports using harfbuzz directly are using harfbuzz-ng.
How about the Qt port?
If that is indeed the case we should remove all harfbuzz.old helper code.
(In reply to comment #23)
> (In reply to comment #22)
>
> > On Chrome Linux and Android we already switched to harfbuzz-ng. So, first step is to figure out who still uses harfbuzz.old and switch them over.
>
> To my knowledge, all upstream WebKit ports using harfbuzz directly are using harfbuzz-ng.
How about the Qt port?
If that is indeed the case we should remove all harfbuzz.old helper code.