Wow, awesome. That’s exactly what I was looking for. Thanks for the pointers!

thanks for your example!!

Batch supports both flavors inside a woff. It’s up to you to pick one, each of them has benefits and downsides. OTF will be close to the original while a TTF is mostly converted. A TTF flavored one can contain TTF hinting... Good luck

One other thing that might be worth investigating is whether toggling auto saving in preferences reduces the amount it happens (I think it has for me)

Makes sense. Thanks so much for your help!

Dear Frederik, thank you for your answer! Why would an alternate version get a unicode value? It’s not allowed to provide two glyphs with the same unicode value. Thinking from a typesetting point of view: which one should it take? I see, so … there’s no problem here, but it’s actually right that the alternates named e.g. A.alt or A.ss01 don’t have the same unicode value as A itself … thank you for clarifying this. I would recommend you to write an OpenType feature to switch the A to the alternate A.ss01 in InDesign: I see! So it seems I’ll try to read the Robofont page on features and the documentation from Adobe and then I can hopefully figure out what to write in that feature file as now it’s completely empty. I mean, maybe this feature files needs to have lines like the following: # Script and language coverage languagesystem DFLT dflt; languagesystem latn dflt; And afterwards I could manually add what you proposed for A–Z and 0–9 in ss01, ss02, and ss03. feature ss01 { sub A by A.ss01; # ... } ss01; I saw something like A.alt in some free and open source .ufo files and was wondering what it is, i.e. why would I write .alt instead of some styleset like .ss01 … EDIT: I just discovered an article about opentype features on i love typography dot com which lists features like aalt “All alternates“, calt “Contextual alternates“, salt “Stylistic alternates”, et cetera (which I already know from CSS). So I think for another stylistic version of the figures 0–9, salt would be a kinda semantically correct feature name.

@frederik awesome, thanks very much. Surprised I've never encountered this until now!

RoboFont 3 is a paid upgrade. Your old RoboFont 1 license will not work. You can still download older versions here: http://robofont.com/downloads/

legends, thanks for the help!!

@erik In most cases that's probably already true, or needs a small edit. This may be true if you look at the people’s current techniques, but I also wouldn’t be surprised if people who get better at drawing for interpolation in the coming years will be able to get away without “normal” intermediate masters in situations where they might have previously needed them (especially if any of this Higher Order Interpolation stuff breaks through to standard font technology).

@frederik Thanks. I'll give it a try.

As a very belated response, the above code snippet wasn't really helping me, because (if I'm remembering correctly) RoboFont gets into a sort of "locked" state when this alert appears, so I couldn't figure out how to use the diffing script to peer into both states of the file. How I did solve the problem was by removing my files from my auto-syncing Dropbox folder, and simply trusting GitHub and hard drive backups. I believe that the syncing of Dropbox was somehow messing up when there were updates to many files at once, as happens in UFOs.

mmm, RF could use the changes I’ve committed to vanilla. see https://github.com/typesupply/vanilla/blob/master/Lib/vanilla/vanillaList.py#L196 for vanilla you can also provide the state, image and if the menu item is enabled.

@pieterpjotr super enjoy!!

But then I have to handle all the glyph changes somehow, like this: from mojo.events import addObserver, removeObserver, postEvent class DummyController(object): def __init__(self): self.glyph = CurrentGlyph() addObserver(self, "currentGlyphChanged", "currentGlyphChanged") self.addSelectionObserver() def currentGlyphChanged(self, notification): self.removeSelectionObserver() self.glyph = notification["glyph"] self.addSelectionObserver() postEvent("selectionChanged") def glyphSelectionChanged(self, notification): postEvent("selectionChanged") def addSelectionObserver(self): if self.glyph is not None: self.glyph.addObserver(self, "glyphSelectionChanged", "Glyph.SelectionChanged") def removeSelectionObserver(self): if self.glyph is not None: self.glyph.removeObserver(self, "Glyph.SelectionChanged") class DummyObserver(): def __init__(self): addObserver(self, "selectionChanged", "selectionChanged") def selectionChanged(self, notification): self.glyph = notification["glyph"] if self.glyph is not None: print(self.glyph.selectedPoints, self.glyph.selectedComponents) DummyController() DummyObserver() I was thinking there might be something like this already built in.

Those could be added, I guess. Where features are generated for a given set of ufo files.

Wow, that fixed it. I have no idea how I managed to unknowingly do that. Thanks!

@frederik huehue, ok, so we have to live with that

Great! Works! thanks a lot (I thought that since getGlyph() is BaseEventTool method, it will be more 'proper' to use it instead of CurrentGlyph() )

There are some non-ascii characters in your fea file. You can remove the non-ascii by right-clicking the UFO file and choosing Show Package Contents; open the feature.fea file in a code editor and remove the second line. I hope this makes sense. Or wait until the update is posted. This issue is fixed and will be present in the next update. for your reference: https://github.com/typesupply/ufo2fdk/commit/a792785fb6bd146215d8af8f7a74fbdcad19138b