Working on some interactive @variablefonts web demos and it was the perfect excuse to use the drippy version of @OHnoTypeCo’s Cheee typeface.
https://t.co/Va2ZCu22D6
@pgconstable @robmck 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?
@pgconstable @robmck I know about the reference for Windows / DirectWrite (https://t.co/o12PDookeW) 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.
Support for variable fonts has finally been added to @Figma:
https://t.co/nskStbxNa4
The support page has been updated accordingly:
https://t.co/JybP3XcXwt
@adamtwar@glyphe 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.
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.
https://t.co/KhcWvzp37N
vartype is now LIVE! ⚡️✨ The beta for our new kinetic variable font tool is ready to go with appearances from a few fancy folks: @FaireProjects@djrrb@vectrotype and [@]beatloz.
Upload any vfont and get fully-tunable kinetic sketches 🌿
→ https://t.co/UbNZHUZP22
@d_ver@frankrausch We’ve got you covered there: https://t.co/8N29RSf7ul
(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 https://t.co/VGiUcxo8xP recently. @PiperHaywood did a good job summarizing what’s new on the site and some of the things in the works for the future:
https://t.co/S8L0SPQNjD
There will be a big update to https://t.co/VGiUcxo8xP 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:
https://t.co/KQW2mVdYSx
There will be a big update to https://t.co/VGiUcxo8xP 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:
https://t.co/KQW2mVdYSx
@typethoughts 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.