It's been great to see the excitement and interest in variable fonts, and to see people beginning to experiment and build prototypes. There's one concern I have in this early phase, though: the risk of jumping the gun with stuff not fully ready.
When our teams at Adobe, Apple, Google and Microsoft got together to develop the OpenType Font Variations spec, one thing we set out as a priority was to ensure interoperability: to agree on a specification and ensure that our platforms conformed so that font developers and users could be confident that variable fonts would behave the same on all platforms. When we announced the technology, this spirit of collaboration and desire for interoperability on our part seemed to be something that was greatly appreciated. But I'm worried that, in excitement to jump on board, people may overlook some of the details needed to ensure interoperability.
I've seen some vendors starting to market "variable fonts". Yet, I'm not yet aware of any tool chain that fully supports all of the new formats in OpenType 1.8, and all of the requirements for OT 1.8 variable fonts. Of course, it's possible to craft a file conforming to the new formats with nothing more than a binary editor, though doubt many would go through such a tedious process to build a font.
For example, a required table for OT 1.8 variable fonts is to have a 'STAT' table. But I'm not aware of any font tools that support this table yet. Similarly, the 'MVAR' table would be needed to support any variation in font metrics, but I'm not yet aware of tools that support that either.
With these things in mind, I thought it would be useful to start a discussion thread focusing on the readiness of tools that fully support the variable font spec. I invite different tool vendors to provide occasional updates regarding what parts of the OT 1.8 spec their tools do or don't yet support.
the VF mechanism, especially that included in CFF2, is much more powerful then everyone expected. Period.
This gives an overview of current level of support, and what's next. Note that this was just pushed live: it may take up to a day to be visible outside the United States.
Extend build tools to allow building without a Superpolator designspace file and UFO source fonts.
Some key additions: varLib support for
- GDEF variation store (for GDEF and GPOS variation data).
- HVAR, VVAR
- GSUB and GPOS feature variations
Some key gaps that remain: MVAR, STAT and CFF2
Others that are closer to this work can provide more complete/accurate details.
What is different is just the command 'buildMasterOTFs': it now expects a different directory tree of source material. This version of the AFDKO will work with the 'AdobeVariableFont.otf" OpenSource files at https://github.com/adobe-fonts/adobe-variable-font-prototype.
- Read Roberts
I also very much appreciate that they call out that this is still work in progress, and that it would be premature to start releasing variable fonts. It won't be long until platforms and tools are fully supporting the OT 1.8 spec, and it's worth waiting a few more months to have fonts that will work the same on all platforms.
But please play around with it and report problmes.
This version is required to build the current version of the 'AdobeVariableFont.otf" OpenSource files at https://github.com/adobe-fonts/adobe-variable-font-prototype.
- It uses version 3.9.1 of the fonttools module.
- bug fixes
- the 'tx' tool can now emit instances specified by the user design vector into the different output modes.
The update was just posted: it make take up to 24 hrs to become visible outside the USA.
- Read Roberts