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

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

[HarfBuzz] harfbuzz: Branch 'master' - 17 commits

.ci/fail.sh | 10 +++- .circleci/config.yml| 16 +++ .travis.yml |4 - CMakeLists.txt | 36 src/Makefile.am |8 +-- src/Makefile.sources|6 --

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

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.

[HarfBuzz] harfbuzz: Changes to 'BASE'

New branch 'BASE' available with the following commits: commit 551fa2d200a06d00d054f2c8e7aad1cb4d25249b Author: Behdad Esfahbod Date: Sun Feb 25 16:32:17 2018 -0800 [BASE] Minor commit 05699fd996ed9c0e5dde8918388ac188e58df1a7 Merge: 83af6c23 3ebcd5a3 Author: Behdad

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

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