Re: [HarfBuzz] Beginner question: What are cluster levels?

2016-01-05 Thread Jamie Dale
Thanks, I also have another question related to what I mentioned yesterday: Is there a reliable way to detect which glyphs are ligatures? My current solution checks for gaps in the cluster indices of the shaped glyph infos, but that also requires some special case handling to detect if the last

Re: [HarfBuzz] harfbuzz: Branch 'master'

2016-01-05 Thread Behdad Esfahbod
On 16-01-04 02:33 AM, Martin Hosken wrote: > Dear Behdad, > >>> So, I would add an enum to the debug message to give a debug message event >>> type. >> >> My current thinking is that everything is transferred as a text API in >> one-line messages. The client can transform that to an enum if

Re: [HarfBuzz] Beginner question: What are cluster levels?

2016-01-05 Thread Graham Douglas
On 04/01/2016 17:06, Behdad Esfahbod wrote: > Hi Jamie and Deepak, > > I'll try to get a detailed reply to this thread tomorrow. > > Cheers, > behdad > > > ___ > HarfBuzz mailing list > HarfBuzz@lists.freedesktop.org >

Re: [HarfBuzz] Beginner question: What are cluster levels?

2016-01-05 Thread Jamie Dale
I actually just wrote something to give me very similar information since I realised that my basic "this is a ligature" flag wasn't enough data, so each of my glyphs now contains the number of characters that the glyph was composed from. This, along with the cluster index of the glyph from the

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

2016-01-05 Thread Behdad Esfahbod
src/hb-open-type-private.hh|2 +- src/hb-ot-layout-common-private.hh |3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) New commits: commit 53c47c85827a7e3ca82000e3baa9aa87c5770ce9 Author: Behdad Esfahbod Date: Tue Jan 5 13:26:20 2016 +

Re: [HarfBuzz] A plea to make HarfBuzz easier to build.

2016-01-05 Thread Daniel Ribeiro Maciel
Hi Behdad, I wrote this hb.cc file. Drop it in the root of harfbuzz source tree to try it out. You will need to add both Freetype and 'hb-ucdn' to the include path though. It will *not* compile; there are a bunch of symbol redefinition problems and other seemingly (?) trivial things to fix (82