Re: [HarfBuzz] Why harfbuzz isn't/couldn't/shouldn't provide separate [optional] API for glyph/positioning?

2018-03-07 Thread Behdad Esfahbod
On Sun, Feb 25, 2018 at 10:46 PM, Nikolay Sivov wrote: > On 2/26/2018 5:28 AM, Behdad Esfahbod wrote: > > > > Two things stand out: > > > > - There's a lot of duplicate info going into both calls, > > > > - There's also a lot data coming out of the first call just to go

Re: [HarfBuzz] Why harfbuzz isn't/couldn't/shouldn't provide separate [optional] API for glyph/positioning?

2018-02-25 Thread Nikolay Sivov
On 2/26/2018 5:28 AM, Behdad Esfahbod wrote: > > Two things stand out: > >   - There's a lot of duplicate info going into both calls, > >   - There's also a lot data coming out of the first call just to go > directly into the second; namely pCharPropsand pGlyphProps. > > Those two very

Re: [HarfBuzz] Why harfbuzz isn't/couldn't/shouldn't provide separate [optional] API for glyph/positioning?

2018-02-25 Thread Behdad Esfahbod
Hi Ebrahim, On Sat, Feb 24, 2018 at 11:33 AM, Ebrahim Byagowi wrote: > About why "isn't", I guess harfbuzz has developed before DirectWrite, > That's not the reason. Uniscribe API also had the separation. Initially I had wanted to allow it, but eventually didn't. Read on.