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.

Thank you for the response. I get it, I think. Address two different problems with the processes for addressing those issues, rather than conflate the code of one problem with the "solution" for the other. Cheers. Now to get the kerning part right!

hello @HB888, it sounds like your glyphs have wrong unicode values. you can check them using the Inspector panel – for example, the unicode for A must be 0041, for B must be 0042, etc: if the unicodes are off, you can set them automatically in the selected glyphs using this simple script: font = CurrentFont() for glyph in font.selectedGlyphs: glyph.autoUnicodes() please give this a try, and let us know if it solves the problem. cheers

he Martin you need to generate a binary first yourself, see the docs of RoboChrome Generate your font via RoboFont as usual. For the sbix format you need to generate a TTF, it won’t work with OTFs. If you click the Export to font button now, RoboChrome will know where to look for the TTF you just generated, and will save a copy with a _sbix suffix. hope this helps!

hehe, good catch!

Okay, I think that fixes it! I will probably evolve this a bit further, but here is the code now: https://gist.github.com/arrowtype/a3c4445cd6b9a6174f885eccff38e1c9 (Caveat: Not sure whether it would work for UFOZ)

I just remembered that I asked this question - so sorry for the delayed response! ThemeManager is exactly the kind of solution I was looking for. I'll try it out. Thank you so much!

good it disappeared! enjoy

If public.default is the name of a layer, but it is not set as the default layer, the UFO will not save, and pops up with "The document [file-name] could not be saved. The file isn’t in the correct format." Output window: Traceback (most recent call last): File "lib/doodleDocument.pyc", line 186, in writeSafelyToURL_ofType_forSaveOperation_error_ File "lib/fontObjects/doodleFont.pyc", line 224, in save File "/Applications/RoboFont_3-5b2.app/Contents/Resources/lib/python3.7/defcon/objects/font.py", line 823, in save AssertionError Weird edge case, but took me a while to figure out when I ran into it. The UFO was a generated instance, and I had manually returned it to the foreground (default), background layer naming scheme, so it could work with some of my inelegant scripts.

thanks!!!

No idea, I guess it is a bug in Glyphs...

this should work again...

thanks for the link!

hello @bahman, another option is to include the shared libraries in the extension using git subtree – see the notes here. cheers!

The error is self-explanatory. You are trying to subscript an object which you think is a list or dict, but actually is None. This means that you tried to do: None[something] This error means that you attempted to index an object that doesn't have that functionality. You might have noticed that the method sort() that only modify the list have no return value printed – they return the default None. 'NoneType' object is not subscriptable is the one thrown by python when you use the square bracket notation object[key] where an object doesn't define the getitem method . This is a design principle for all mutable data structures in Python.

you can store your tool specific data in the data folder! defcon has an api for reading and writing files, not for folders inside the data folder. font = CurrentFont() defconFont = font.naked() print(defconFont) print(defconFont.data.fileNames) # data must be bytes defconFont.data["com.bahman.superKernTool.as.bytes"] = b"myData" myData = dict() myData["superkern"] = "foo" defconFont.data["com.bahman.superKernTool.as.plist"] = plistlib.dumps(myData) defconFont.save('test.ufo') good luck

good you found it! kerning values has to be set very precise. Did the extension DesignSpaceEditor show this kern error in the report? good luck!

ehum, if the data is incorrect its hard to find a solution for this issue. MM is build as such this doesn't happen :) I dont know what should happen in this case: MM should not create empty kern groups MM should not return empty list for not existing groups as fallback MM should not remove that pair with the missing group. Maybe MM should report, so it gets fixed first. (but there are many edge cases to report...) (Maybe this is a case for ufonormalizer?)

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

continue here https://github.com/typemytype/GlyphConstruction/issues/52