Matthew Butterick

> We know that the code point given to a glyph is implied by the final name (left column), why not shuffle that name around? All my glyphs have a...

> instead of swapping out glyphs via Unicode override, swap the names in the left column AFAICT the problem with this workaround that OT feature code is tied to the...

Right. To my mind, if I’m making new names in the GOADB, and then I have to rename all the glyphs in the feature file, I might as well just...

My (perhaps incorrect) expectation based on the docs is that the GOADB can reorder the glyphs, but otherwise the resulting font retains the existing glyph order within the source. Thus...

The workaround, of course, is just to generate a GOADB file with the glyphs in the same order as the PFA, which I have done. I’m just observing that the...

I don’t use UFO, nor do I use the Python interface to `makeotfexe`.

> You don’t have to use the Python interface to makeotfexe (don’t know how to do that, even). [Docs:](https://adobe-type-tools.github.io/afdko/MakeOTFUserGuide.html#using-makeotf) “`makeotf` is a command shell that calls the Python™ script `makeotf.py`”

I”m embedding `makeotfexe` in a larger application so the Python wrapper is unnecessary.

Always grateful for improvements, but inasmuch as my question sort of led to reopening this issue, please don’t feel that you need to investigate on my account. `travis-racket` works great...

> Yeah, that seems sufficient. FWIW, I’ve had the `sudo: false` line uncommented in all my `.travis.yml` files for a while ([for instance](https://github.com/mbutterick/pollen/blob/master/.travis.yml)), and the Racket installers still get downloaded...