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
> > directly into the
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 strongly
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.
> but I like to kno
About why "isn't", I guess harfbuzz has developed before DirectWrite, but I
like to know if a separate API for substitution and positioning a
possibility? Or, is accepting glyphs instead on input [and later as
an optimization, hb_shape without positioning] a possibility? Have a look
at hb-directwri