Re: [HarfBuzz] Exposing attachment tree / Arabic joining to shaping clients

> Not sure how this can be explained, maybe someone has attempted to prevent > some fonts to get Kashida justification and maybe the detection was font > based, the reason it is still failing for IranNastaliq but not for Amiri, but > in any case it is imperfect. Amiri has a zero-width kashida

Re: [HarfBuzz] Exposing attachment tree / Arabic joining to shaping clients

On Tue, Nov 12, 2019 at 5:30 AM Ebrahim Byagowi wrote: > This is very interesting Behdad. Can this have Kashida priority also, like > what harfbuzz-old > > had. > I'm hesitant to do that. The reason I want to

Re: [HarfBuzz] Exposing attachment tree / Arabic joining to shaping clients

On Tue, Nov 12, 2019 at 7:31 PM Martin Hosken wrote: > Dear Behdad, > > > For reason that many of you know (letter-spacing, Arabic elongation, > other > > postprocessing) I like to expose attachment data to the shaping clients. > > There's two separate pieces so far: > > > > - The Arabic joining

Re: [HarfBuzz] Exposing attachment tree / Arabic joining to shaping clients

Dear Behdad, > For reason that many of you know (letter-spacing, Arabic elongation, other > postprocessing) I like to expose attachment data to the shaping clients. > There's two separate pieces so far: > > - The Arabic joining info, which is applicable to all Arabic-like fonts > even the ones

Re: [HarfBuzz] Exposing attachment tree / Arabic joining to shaping clients

This is very interesting Behdad. Can this have Kashida priority also, like what harfbuzz-old had. > [..] even the ones that do NOT use cursive joining. Guess this a property of a font rather than a buffer?