David Jonathan Ross

Ah, right. That's not stored separately since it is compiled from the UFO sources, but you can get it by `ttx`ing the variations TTF.

The UFOs have `fontinfo.plist`, which is used as the basis for the name table when the font is compiled (see the [build script](https://github.com/TypeNetwork/fb-Decovar/blob/master/scripts/generateInterpolatableTTFs.py)) and then `fontTools varLib` to generate the...

Ah, those come from the Decovar.designspace file...forgot about that! On Wed, Mar 15, 2017 at 8:52 AM Dave Crossland wrote: > FontView shows the axes names from the name table...

Sorry for the incomplete answer...I also had to add unregistered axes to my version of fonttools...will document this as soon as I return from my travels! On Wed, Mar 15,...

Half-solved, if I'm not mistaken. The STAT table has the axis information but not the named instance information. Between the complexity of the axes in this font and the fact...

As far as I know, there is still no tool for writing `STAT`. Maybe others know differently? I don't think I have a way to reliably write this table in...

I’ve added one similar to Amstelvar. https://github.com/TypeNetwork/fb-Decovar/pull/24 Note that this does not cover the manual addition of a STAT table. Hopefully this will be added to fonttools varLib soon, so...

totally scriptable...do we need parity between amstelvar and decovar build processes? I would do this in python instead of a shell script...

i'll make something basic tomorrow and we can always add a build system around it...not very knowledgeable about these different approaches

Well, the good news is that the latest fontTools now writes its own STAT table, so we no longer need to include a more complex build script to address it....