A few other potential issues: Path directions can change, eg flip a component horizontally Rounding can become an issue, especially if going small or thin Subsetting is a potential issue, depending on the method Also worth knowing that any component with a transformation (scale, rotate, flip, skew, etc) is automatically decomposed when the font is generated.

hello @JustJoeDesign, thanks for the note. it’s fixed in the roboDocs fork, update coming soon to Mechanic…

component.position will be removed in future version, as it was a bug :)

@gferreira Thanks Gustavo, this is the solution I used too in the meanwhile. @frederik Looking forward to get the update!

Hey guys, I created a small script that makes sorting contours easy (at least for me) https://gist.github.com/RafalBuchner/ff73b03d1c2970182d7dbe1d6060d32b Everyone, feel free to use that. I'm not sure about the usage of the Pens though: is drawing in rearrangeOrder function done accordingly to the proper way of using pen-protocol? I was improvising a bit and I'm not sure about it. I'm working from time to time with point labels. The pen object created by me is deleting data like that: Is there any good way to make sure that when redrawing the glyph none of the data like that will be erased? Best, R

@gferreira thank you, that's perfect. I also noticed you added a my favorite autoUnicodes() function :)

There is no other way :) if the point doesn't align exactly, some points need to be moved and shifted. RF opts to modify the last point (and offcurve) of the contour that is being dragged. great!!

@RafaŁ-Buchner you’re right :) better to use the boolean glyph method then.

Wow, thank you * 10000 for the help, Frederik! I really appreciate it.

Great, this works! Thanks!

Sorry I didn’t reply earlier. I really like the new configuration! Will gladly wait for the implementation. The white outlines are maybe a bit too disturbing for some use cases.

oh, nice little bug, will be solved in the next update. It fails when ever you add a floating number which is not nice for transformations. thanks

Thank u Jens!

A robofab component will have a transformation attribute in the next version.

Ive been working for a while on a "glyph builder" thing This will be a extension, I doubt if it would be embedded in RoboFont, since it's making design decisions.

It's disabled by default cause transforming multiple glyphs can end up with a double transformation on glyphs with components, one time by the referenced glyph and other one by transforming the component itself.

hi @jhera, there are multiple ways to build accented glyphs in RoboFont. these are described here: Building accented glyphs have you tried using the Glyph Construction extension? in 2019 you don’t really need anchors to position diacritics anymore :) you can still use them (with or without underscore), but you can also use guidelines, variables, vertical metrics attributes, reference positions, etc. have a look at the docs & give it a try!

fixed thanks

Jo, thanks for the script which I'll use in the meantime. Frederik, thank you for listening and offering a built-in solution.

This will change dramatically when UFO3 gets implemented (don't know when yet...) RoboFont will follow the spec so components will refer to glyphs from the same layer.