Yeah, I actually found that out myself as I'd added an assert that the
number of characters was never zero... and then I pasted in some Arabic and
it fired due to what you mentioned (multiple glyphs in a sequence with the
same cluster index).
I'm not too concerned by this though, as it's my unders
On 06/01/2016 14:37, Jonathan Kew wrote:
> On 6/1/16 14:17, Behdad Esfahbod wrote:
>> On 16-01-05 09:17 PM, Jamie Dale wrote:
>>> 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
>>>
On 6/1/16 14:17, Behdad Esfahbod wrote:
On 16-01-05 09:17 PM, Jamie Dale wrote:
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 gly
On 16-01-05 09:17 PM, Jamie Dale wrote:
> 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 w
src/hb-uniscribe.cc |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit e6d5e4c3106180cb22253c2c278b40f7c4c98f2f
Author: Behdad Esfahbod
Date: Wed Jan 6 12:29:50 2016 +
[uniscribe] Fix negative advance
This happens with at least one test font I have.
test/shaping/texts/in-tree/shaper-hangul/MANIFEST|1 +
test/shaping/texts/in-tree/shaper-hebrew/MANIFEST|1 +
test/shaping/texts/in-tree/shaper-tibetan/MANIFEST |1 +
test/shaping/texts/in-tree/shaper-use/MANIFEST |1 +
test/shaping/t
