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!

@frederik I dream of the day someone would convert fontTools feature ast objects to json and we won't use fea file anymore.

Hi @frederik It just never ends, no tracebacks. If I don’t manage to solve it with @gferreira tip I will try to prepare a dummy ufo and post it here. Thank you both!

should be fixed here: https://github.com/typemytype/GlyphConstruction/commit/01c7c9362561822a68073305c69c9fbc054ddf13 Getting kerning is advised to use font.kerning.get(pair) where it does not fail. This is similar to a normal dict. Or you can also check first if pair in font.kerning: ... thanks!

@FosterType Hey Dave. I haven’t tried that. Nice tip, I’ll give it a go. Cheers.

Thanks, @tal!

@tal said in Copying uppercase to lowercase (including kerning), and auto-add unicodes: Here's a little demo script that will copy kerning. Hmm, at least initially, when run, that causes an error: File "lib/fontObjects/doodleKerning.pyc", line 13, in _set_dirty mm4.MetricsMachineError: Glyph a is in more than one side 1 group. For now, I'll do some (partially) manual things in MetricsMachine to sort out kerning. I'll loop back with a suggested fix if I can loop back and figure something out!

@gferreira said in Best way to remove glyph from RFont?: for layerName in f.layerOrder: layer = f.getLayer(layerName) for glyphToRemove in glyphsToRemove: if glyphToRemove in layer: del layer[glyphToRemove] else: print("%s does not contain a glyph named '%s'" % (layerName, glyphToRemove)) Ahhh this makes a lot of sense now, but it's helpful to see the specific way to do it. Maybe it would be worth adding this to the docs, here? https://robofont.com/documentation/how-tos/adding-and-removing-glyphs/?highlight=remove glyphs#removing-glyphs-1 Thanks so much for the help!

Hi Andrew you added those kerning values inside RoboFont, with the Kern Center? You created the groups? I cannot reproduce this issue, could you send me a erroneous ufo file?

Like a charm. Thanks a lot!

jup, makes perfect sense, thanks!

hello jens, thanks for your help. in fact your example is what "happened" in my case. I did some very quick kerning without groups. Later on I replaced the single letters of the pairs with groups through a script. I also wanted to remove the original pair but the zero value was "overwriting" the group value. so i guess it could work with kerning update etc but the "del" way worked just fine. cheers, jo

oh thanks, will be fixed in the next version

He Ian Try to add a kerning pair with the + button at the bottom. All your kerning groups, starting with a @ will be listed in the combo box see http://doc.robofont.com/documentation/workspace/metrics/kern-center/ good luck!

even better: control-click your ufo and select "show package contents"

I don't know the difference! But in fontlab when I open a font, in the kern feature I can see that LTR kerning is interpreted like this: pos uni0631 uni0628 -225; But RTL kerning is interpreted like this: pos uni0631 uni0628 <-225 0 -225 0>; So I suppose RTL kerning should be implemented with adjustments applied to position of the glyph too, maybe I'm wrong; I'm not a pro. (see AFDKO OpenType Feature File Specification) About the kerning in RoboFont, I think there is a malfunction in the "Right to left" Option in the kerning panel. Here is what I do: I open a font which already has RTL kerning, Robofont interprets kerning correctly. I open the kerning panel and click on a class pair, the kerning shows up but order of glyphs is incorrect, I turn the "Right to Left" option on; Nothing Happens! I turn it off, now order of glyphs becomes right, even so the kerning has been implemented in RTL order.

Merci. Indeed, there is some group-group and glyph-group and glyph-glyph kerning. So no way to get directly a value out the ufo? Will try the temp dict. Thanks Frederik!

The kerning keys can be either glyph names or group names. If they are group names (starting with an @) you can edit them in with the groups objects f = CurrentFont() f.groups["@MMK_L_f"] Its possible that this group isn't not in your groups but already hard coded into the features. (normally MM is adding those kerning groups also as font.groups items) note: RoboFont does not automatically convert font.groups to feature groups. Use this extension for converting and adding groups to the feature file: http://github.com/typemytype/RoboFontExtensions/tree/master/groups2Features good luck

added to the todo list

@! got it! everything super. thank you very much.