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
Type3 FontDescriptors FontName confusion #11
Comments
|
Then how would you know the name of the font, such as for display in a processor's UX? |
|
So are you saying "Table 110 — Entries in a Type 3 font dictionary" is incorrect then and needs BaseFont? |
|
did some reading of code and here is the situation... For Type 3 fonts, the name comes from the The Since Type 3 fonts are either always subset or never subset (depending on how you look at it), there is never a need to have the |
|
Proposed solution: change Table 120 — Entries common to all font descriptors, FontName to say: (Required for non-Type 3 fonts) |
|
Just saying "Required for non-Type 3 fonts" doesn't say it shall not be there for Type 3, which leads to two problems:
It may be going a bit overboard, but: (Required for fonts other than Type 3) The PostScript name of the font. For Type 3 fonts that include a Name entry in the Type 3 font dictionary, this name shall match the value of that key. For all fonts other than Type 3 this name shall be the same as the value of BaseFont in the font or CIDFont dictionary that refers to this font descriptor. |
ISO 32000-2:2020 "Table 120 — Entries common to all font descriptors" FontName is described as "(Required) The PostScript name of the font. This name shall be the same as the value of BaseFont in the font or CIDFont dictionary that refers to this font descriptor."
Type3 fonts don't have BaseName as defined by Table 110 so therefore the FontDescriptor FontName should be not required for Type3.
The text was updated successfully, but these errors were encountered: