Adrien Tétar

googlei18n/fontmake#414 also noted that E2003 is obsolete.

Cool! The same merge could be done for extractor and fontMath, I think.

Is used to regenerate unicodeTools.py when a new Unicode version comes out, does not need to be packaged.

> If so, shouldn't that be part of the build instead of including generated files in source? I guess you could do that indeed.

Okay. I take it this is mainly useful inside of defcon. Indeed, it should help avoid issues like the one I fixed in https://github.com/trufont/defcon/commit/66c493d47b15e42a3385e0745740c156f946cea0. > Backport this to master. Still...

I see well, sounds good.

FYI Adobe ufoTools uses the [HashPointPen](https://github.com/adobe-type-tools/afdko/blob/a4bb790175594c10e71f3465358c0a8f013ce1b7/python/afdko/ufotools.py#L643-L645) to store a hash and not rehint an outline that hasn't changed.

I just hit this issue with a SelectionChanged notification sent from contour, which the glyph watches then sends its own Glyph.SelectionChanged that destroys the representation. This problem affects the call...

> Does the current extractor depends on any specific version/revision/branch/commit/whatever of defcon? No.

+1, I was looking for an IcoMoon like alternative for FontAwesome.