[HarfBuzz] Why harfbuzz doesn't handle ligature carets itself?
ebraminio at gmail.com
Sat Dec 15 08:06:41 UTC 2018
Now makes sense. Thanks Khaled.
So maybe we should handle or accept some callback for that or doing that at
least when GDEF/lcar info is available for the glyph? I mean, anything to
I guess playing with such details of hb_buffer with considering the
original text, just like Kashida justification, will be harder to get for
clients (the reason ligature carets API is not used AFAICS, in addition to
not being that popular on the fonts itself) so providing some lightweight
and unofficial wrapper at least, lcar with dividing fallback, can make
sense I guess.
On Sat, Dec 15, 2018 at 2:30 AM Khaled Hosny <dr.khaled.hosny at gmail.com>
> On Fri, Dec 14, 2018 at 07:00:43PM +0330, Ebrahim Byagowi wrote:
> > Hey there, just occurred to me this [hopefully not deeply incorrect] why
> > harfbuzz itself doesn't handle ligature carets, distributing the ligature
> > cluster advance with ignorable clusters followed by using GDEF/lcar info,
> > with falling back to equal dividing?
> The current API does not allow for such fallback as it takes in glyph
> index only, but you need text string of the ligature. You will also need
> to do grapheme clusters segmentation which (IIRC) HarfBuzz does not
> currently fully handle.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HarfBuzz