Glyph distortion after union

[khaledhosny]

Using this script on ReemKufi-Regular.ufo.zip:

import sys
from booleanOperations import BooleanOperationManager
from defcon import Font

ufo = Font(sys.argv[1])
manager = BooleanOperationManager()
for glyph in ufo:
    contours = list(glyph)
    glyph.clearContours()
    manager.union(contours, glyph.getPointPen())
ufo.save(sys.argv[1].replace(".ufo", "-new.ufo"))

Results in several distorted glyphs: arMeem.isol, arHeh.fina and arHeh.fina1:

[anthrotype]

hm.. that's not good.
Does re-locating the contours' starting point make any difference?

[khaledhosny]

Changing the start points makes no difference, but moving the horizontal contour so that its first point is not directly above the point in the other contour “fixes” the distortion.

[jamesgk]

I dug into this a bit and have a theory on why this is happening. If I'm correct, the code here:

booleanOperations/Lib/booleanOperations/flatten.py

Line 877 in ebeaf6b

if flatSegment[0] == inputSegment.flat[0] and flatSegment[-1] != inputSegment.flat[-1]:

is trying to match an input curve (from the original glyph) with an output curve (from the union-ed polygon) by their first points. It searches for t values in the input curve for the last point on the output curve, and if it doesn't find one, as it might not in the example here, it just drops an entire segment because it assumes at least one would be found:

booleanOperations/Lib/booleanOperations/flatten.py

Line 924 in ebeaf6b

if tValues:

I'm not sure if I'm right on the mark in diagnosing the actual issue, and I certainly don't know what the solution would be at this point. But maybe this is a start.

[jamesgk]

cc @typemytype

This is almost certainly a duplicate of #27, and of notofonts/nototools#268 (comment). Basically it's a pretty big issue with BooleanOperations. The code is pretty complex though; I'm hesitant to make any changes for fear of breaking something else.

[marekjez86]

@jamesgk @anthrotype @typemytype @behdad : I will be at AtypI, jamesgk will be at AtypI. @anthrotype I think you will be there also (and I think you own this code).

Could we meet on Wednesday, 14/Sep evening over some food and beer (water or any non-alcoholic drink of your choice if you don't drink alcohol) and fix it?

@khaledhosny : would be be able to help with testing it (will you be around during AtypI)? I would test for any regressions over the next 24 hours after the fix is checked in (ending on Friday, 16/Sep) using our pipeline (as of today we produce 639 different OTF files including one that causes the problem). If there were any issues most likely they'd appear early, but if there were none I'd know on Friday. If there were any issues we could fix them on Thursday or Friday...

What do you think? I want it fixed soon :-)

[behdad]

Code is owned by @typemytype . But indeed, all of us (including Khaled and Cosimo) will be at ATypI, so we should get together and tackle this one there. Looks like Wednesday after dinner might work after all. Let's aim for that.

[khaledhosny]

Wednesday sounds fine.

[anthrotype]

sounds like a plan! 👍

[typemytype]

date set!

gr Frederik
www.typemytype.com

On 06 Sep 2016, at 12:42, Cosimo Lupo notifications@github.com wrote:

sounds like a plan! 👍

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #32 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ABIp1usM5civmLuPBcK8ckU5hf8a_4Frks5qnUN7gaJpZM4JIH_o.

[anthrotype]

I managed somehow to fix the issue, by simply using the updated pyclipper extension!

Also see the other screenshots at #27 (comment)

pyclipper is also available on PyPI https://pypi.org/project/pyclipper/ with pre-compiled wheels for all Mac, Win and Linux!

I'll send a PR soon 💃

[behdad]

Awesome! Now we need something else to do on Wednesday night!

[typemytype]

Warsaw nightlife ????? with T-shirts showing those tricky unions :)

gr Frederik
www.typemytype.com

On 10 Sep 2016, at 21:28, Behdad Esfahbod notifications@github.com wrote:

Awesome! Now we need something else to do on Wednesday night!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #32 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/ABIp1r2nFxxk0BeZpTbAPgetMqMMoD-bks5qowT6gaJpZM4JIH_o.

[behdad]

I'm looking into arranging a dinner. Stay tuned.