-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aptos Narrow v2.00 PostScript Names appear to be incorrect #1150
Comments
This is also the case for a good deal of variable-source Microsoft fonts for quite a while now. I recall there also being more issues other than bad PostScript names which mainly cause printing issues somewhere down the line. In the past I have also tried to open issues on the dedicated Office forum on Feedback (Preview) and on the Feedback Hub to no avail, so I got a bit frustrated. My understanding is that the font metadata quality assurance is mostly checking if it works correctly on the browser and on the WYSIWYG canvas of the desktop applications, and there does not seem to be much effort to validate elsewhere. To my surprise, even then, there is quite a lot of inconsistency. My biggest pet peeve is the slow abandonment of high-quality hinting. All newer families have either subpar hinting or none at all, in detriment to the overwhelming majority of Windows desktop PC users. |
Yes. That appears to be a complete waste of time. |
As a Microsoft Windows user from as early as I could read, I would be more than happy to volunteer and engage in giving meaningful feedback if it would trickle down and benefit users, and I hope I can be proven wrong on the frustrating experience that has been the norm so far. Here is a noncomprehensive list of these questionable PostScript names:
|
These fonts are static fonts generated from the Variable Font versions of these fonts. During that process, these PostScript names are generated. They list the coordinates of the static fonts in the design space of the variable font. We have recently changed our font building tools to not use this method anymore. As we release new versions of the fonts to fix other issues, the new fonts will have more conventional PS names like "Sitka-Display-Bold-Italic". An update to Aptos is being prepared as I write this. |
Thanks, @robmck-ms. I should add that the metadata of these variable-source static instance fonts haphazardly differ from the same named variations which might trip weird font selection and configuration bugs. The Windows OS fonts additionally have metadata issues of their own that warrant some scrutiny. Sitka Italic, as an example, shares PostScript names with its own Roman brother. Here are a few examples:
|
The PostScript Names (nameID=6) in the four Aptos Narrow v2.00 fonts appear to be incorrect.
Style -
nameID 6
Regular -
AptosNarrow-1900000-5a0000
Italic -
AptosNarrowI-1900000-5a0000
Bold -
AptosNarrow-2bc0000-560000
Bold Italic -
AptosNarrowI-2bc0000-560000
None of the other fonts in the super-family are like this.
So this appears to be an oversight.
Note: while checking these I also noticed the nameIDs referenced in the
STAT
tables in these static fonts are not correct.In some cases the nameIDs referenced do not exist in the
name
table.So if an application actually used the
STAT
table it would have missing/incorrect info.The text was updated successfully, but these errors were encountered: