There was a post in the OpenType mailing list.
I have redacted the names of his two colleagues that he names as they were published in a closed mailing list.
There is a discussion about Windows 10 Fall update 17th October in the Serif lounge.In my talk at ATypI (video herehttps://www.youtube.com/watch?v=Pef_yujD4eM&t=1239s), I mentioned that I was working on creating an open process for people to propose design axes for registration, and for review and discussion of those proposals. That is done and ready for anyone to start participating.
For this process, I have created a project on GitHub: https://github.com/Microsoft/OpenTypeDe ... onAxisTags
To participate, you'll need a GitHub account.
The intent of the process is to end up with a set of registered design axes that are useful and that actually get used! In general, I think a smaller set of registered axes that get used will be more helpful for the type industry and for users than to have a lot of registered axes with many that are used infrequently.
The process is set up in a way that, hopefully, will lead to that result: an axis can't get registered without it getting discussed and unless there are commitments to use it.
Note that you'll always be able to use custom axes (per the OT spec, uppercase tags please!) in variable fonts. So, if you have something you want to use in your fonts but haven't found others that also want to use it, you won't be blocked.
Also note that registered axes don't necessarily have to be intended for use in variable fonts. Static, non-variable fonts can include a STAT table to describe relationships within a family, and design axis tags are used in that table.
For details on the process, follow the link above: it will take you to the README page for the project. And if you have questions, feel free to ask here or to privately contact me or my MS colleagues, [redacted here] or [redacted here].
https://community.serif.com/discussion/ ... th-october
Most of that thread, interesting in its own right, is mostly not relevant here, but I did mention the Bahnschrift font that is bundled in with that update and there was a short discussion about variable fonts and a gentleman kindly provided an interesting link.
https://www.wired.com/2016/09/apple-goo ... c-history/
As I mentioned earlier in this post it was a few days ago that I learned of the existence of variable fonts.
What interests me is this.
I tried using the Bahnschrift font in the Serif PagePlus X7 desktop publishing program, the X7 version is not the latest version, that being X9 and development of PagePlus has now stopped.
The Bahnschrift font worked well in PagePlus X7.
Very good, but why? How?
Does installing a variable font automatically, in Windows 10 at-least-version-something, cause lots of "conventional" (for want of a better word at present), fonts to be generated locally, or what?
I have not yet actually installed a variable font myself. The Bahnschrift font was installed automatically during a Windows 10 update.
How does this all affect FontCreator development please?
Can we discuss variable fonts please?
Monday 27 November 2017