Thanks! Is there any formal documentation of the situation for users? Also, is the support of named instances dependent on fonts having a properly configured STAT table? i.e. having named instances only in the fvar table will result in the names not appearing correctly?

I know about the reference for Windows / DirectWrite (docs.microsoft.com/en-us/win…) but obviously that isn’t as relevant for things like Office 365 or Office for Mac. Even an informal statement somewhere would be helpful to be able to direct users to if/when they ask.

@pgconstable @robmck Is there any definitive reference online about the support (or lack thereof) for variable fonts in Microsoft Office apps?

Support for variable fonts has finally been added to @Figma: figma.com/typography/variabl… The support page has been updated accordingly: v-fonts.com/support

You can! v-fonts.com/fonts/whoa

I do have a setting in the CMS to mark axes as hidden, but it doesn’t currently affect the display of anything yet. I'll eventually make it so hidden axes are collapsed by default, but unfortunately my other (paid) projects are taking priority over those kinds of tweaks lately.

If you haven’t seen it before, they use the SF Compact variable fonts for the watchOS interface: v-fonts.com/fonts/sf-compact

Apple’s latest San Francisco variable system fonts, shipping with recent macOS updates, cover a much larger range of weights and widths than ever before, as well as axes for optical size variation and multiplexed grades. v-fonts.com/fonts/sf-pro

See also the tag for fonts with retractable serifs: v-fonts.com/tags/C114

I started working on a more detailed version of v-fonts.com/support with specific notes and support issues but it’s not quite ready for release yet.

I haven’t tested it personally, but yes they should: developer.apple.com/document…

Clarification: The Clavichord typeface is by @djrrb, not me!

We’ve got you covered there: v-fonts.com/axes/CNTR (There are probably more fonts with a contrast axis, but these are the ones that use `CNTR` for the 4-character axis code.)

A lot of small but useful new features were added to v-fonts.com recently. @PiperHaywood did a good job summarizing what’s new on the site and some of the things in the works for the future: piperhaywood.com/updates-to-…

This is starting now 🚀

There will be a big update to v-fonts.com tomorrow, including many simple but useful new features. @NickSherman and @PiperHaywood will launch the update and discuss other developments under way in the @TypographicsNYC TypeLab at 11:30 EDT: 2021.typographics.com/typela…

The bug is also still present in the latest version of iOS Safari.

Yes, WOFF is definitely preferable. WOFF2 is even better. On a related note: Any browser that supports font variations also supports WOFF2. So, for web use, you can get away with providing *only* WOFF2 versions of variable fonts.