You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is it because LinkedValue isn't available in format 2?
Reading the spec, using ranges for the weights IMHO doesn't fit well. If the user sets the VF weight to 799 and the UI still tells him it's bold, it might clash when the document then uses the static bold font for whatever reason and it's less bold than what the designer saw.
The text was updated successfully, but these errors were encountered:
@madig 1. Yes. It is because the font is specifying both a range (format 2) and a style link (format 3) for weight. (Note that this is in technical violation of the current STAT spec: “No two tables should provide information for the same axis value.” We have raised this concern in the OT spec community and are looking at how to resolve it.)
2. Re. your concern “using ranges for the weights IMHO doesn't fit well,” I agree it could be potentially confusing. Note, however, that names in STAT can be combined with precise axis values to avoid this kind of situation. For example, Photoshop displays “Bold-799” for the style name in your example.
Why are there two entries for regular in the
STAT
table (here taken from the Italic VF)?is it because
LinkedValue
isn't available in format 2?Reading the spec, using ranges for the weights IMHO doesn't fit well. If the user sets the VF weight to 799 and the UI still tells him it's bold, it might clash when the document then uses the static bold font for whatever reason and it's less bold than what the designer saw.
The text was updated successfully, but these errors were encountered: