OpenType 1.8 introduced a 'meta' (metadata) table
, which Apple had previously started using. But Microsoft and Apple worked out together a couple of new entries for this table: "Design languages" and "Supported languages".
These are meant to supersede the 'OS/2' code page and Unicode range fields, which can't scale beyond Unicode 5.2 (ran out of bits), never worked well because it was never clear what a set bit actually meant, and which did not make an important distinction between what a font is capable of displaying
versus what the font is designed for
We actually defined these new fields over a year or maybe two before OT1.8 was published (they were documented in Apple's TT spec), and in Windows we started supporting these in DirectWrite APIs and using them in fonts in the first Windows 10 release (summer 2015). But there wasn't an OT spec update until September 2016.
At any rate, I'm wondering whether support for these fields has started to get into tools and whether any foundries are starting to put them into fonts?
We'd like to start making more use of these fields in Windows. (If you look at the Fonts control panel in Windows 7 or later, it reports "Designed for" information, but up to now that comes from a separate data file, not from fonts themselves, and we only maintained that data for Windows and Office fonts. The 'meta' table of individual fonts is where this belongs, however.) So, I'm hoping they start getting included in more fonts.
Are people aware of the 'meta' table and including it in their fonts?