I am testing the handling of variable fonts in MainType 13 Professional (13.0.0.1365) and found a reproducible discrepancy with the variable font 00WagramVAR.ttf.
The font’s fvar table contains 96 named instances. MainType, however, shows only 95 fonts.
The missing named instance is Mono Italic. [https://abcdarium.de/DATA/Pics/MainType_List_Gap.png\]
The neighboring instances are present:
Mono Light ItalicMono Medium Italic
I also exported the font tags from MainType. For this variable font, the XML contains 95 UIDs only. [https://abcdarium.de/DATA/xml/MainType_TagExport_Wagram_Tag_UID.xml\]
By assigning temporary test tags to selected named instances, I could verify the mapping between the fvar instance order and the final hexadecimal UID component:
Mono Light Italic: fvar index 79 → UID ending004FMono Italic: fvar index 80 → not shown in MainTypeMono Medium Italic: fvar index 81 → UID ending0050
From that point onward, the MainType UID index is shifted by one compared with the fvar instance index.
Mono Italic therefore cannot be selected or tagged in MainType.
Is MainType intentionally filtering this named instance, or is this a bug in the handling of named instances in variable fonts?
If useful, I can provide the font metadata and/or further test results.
