-
Notifications
You must be signed in to change notification settings - Fork 2
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
Clarify Table 93 Type 1 Form XObject Resources description #292
Comments
@MPBailey - would you care to suggest some solution now? |
I propose several relatively small changes in the Resources value cell in Table 93, all of which have been discussed a little under #128.
Under #128 Peter suggested
I've been unable to find anything in the current text stating that a Type 3 font is represented as form XObjects (it uses contents streams, but they are not identified as XObjects). This is a good thing because our discussions under #128 concluded that the process to find resources should be different for a Type 3 font CharString/Font from that for an XObject. On the other hand, appearance streams are explicitly described as being form XObjects. But this is already explicitly called out in the bullet list in 8.10.1, and the Appearance Streams clause (12.5.5) includes a cross-reference to Form XObjects (8.10). So I don't think anything more is required here. |
PDF TWG agree to @MPBailey 3 suggestions above. |
At the request of the PDF TWG, this errata is being split out from errata #128 to focus on improvements to wording in Table 93 and the Resources entry - specifically the historic discussion and ensuring appropriate normative requirements (file format, processor) and alignment with other changes from errata #128 (Type3 glyph descriptions) and #291 (Linearization).
The text was updated successfully, but these errors were encountered: