[HarfBuzz] HarfBuzz API design

Ed Trager ed.trager at gmail.com
Wed Aug 19 13:05:11 PDT 2009

Thanks, Behdad,

And BTW, I'm thrilled to see these recent emails providing detalied
outlines and explanation of the reasoning for the HarfBuzz API ... It
sounds like HarfBuzz is really maturing, and I can't wait to see the

Best - Ed

On Wed, Aug 19, 2009 at 3:54 PM, Behdad Esfahbod<behdad at behdad.org> wrote:
> On 08/19/2009 03:16 PM, Ed Trager wrote:
>> Hi, everyone,
>>> I don't have much to say about the actual font-related parts of the
>>> proposal. But I do think it's perhaps a bad idea to reuse the same
>>> buffer for text input and glyph output. Is memory that tight? Might a
>>> user not want to be able to query the text back out even after
>>> shaping?
>> I was wondering about this too : When selecting or highlighting shaped
>> text (to copy/paste/do something else to it) surely a shaper like
>> HarfBuzz needs to provide convenient access / mapping back to the
>> underlying Unicode text ?
> A shaper just converts text to glyphs, giving back the cluster mapping too.
> The rest is done by the client.  The client sure has the text somewhere
> already.  there's no point in keeping a separate copy by HarfBuzz.
> behdad
>> - Ed

More information about the HarfBuzz mailing list