Skip to content
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

Closed
petervwyatt opened this issue Jun 2, 2023 · 3 comments
Closed

Clarify Table 93 Type 1 Form XObject Resources description #292

petervwyatt opened this issue Jun 2, 2023 · 3 comments
Assignees
Labels
ISO approved Resolved issue approved by ISO

Comments

@petervwyatt
Copy link
Member

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).

@petervwyatt
Copy link
Member Author

@MPBailey - would you care to suggest some solution now?

@petervwyatt petervwyatt assigned MPBailey and unassigned petervwyatt Oct 25, 2023
@MPBailey
Copy link

MPBailey commented Oct 26, 2023

I propose several relatively small changes in the Resources value cell in Table 93, all of which have been discussed a little under #128.

  • Make the requirement "(Sometimes required; PDF 1.2)". That terminology is used elsewhere already.
  • Change para 2 (the discussion of PDF version 1.1) to past tense and remove normative words so that it can be converted into a note (and moved to the end of the cell).
  • Para 3 is now incorrect as form XObjects must now be independent, at least as far as resources go. Replace the first sentence of that para with "In PDF 1.2 and later versions, it is strongly recommended that form XObjects be independent of the content streams in which they appear; from PDF 2.0 this is required."

Under #128 Peter suggested

"given that this description of Type 1 Form XObjects gets referenced by annot appearance streams, Type3 glyph descriptions, etc., noting those other features use Type1 Form XObjects for less knowledgeable readers will also help."

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.

@MPBailey MPBailey added the proposed solution Proposed solution is ready for review label Oct 26, 2023
@petervwyatt petervwyatt removed the help wanted Extra attention is needed label Nov 21, 2023
@petervwyatt petervwyatt assigned petervwyatt and unassigned MPBailey Nov 21, 2023
@petervwyatt
Copy link
Member Author

PDF TWG agree to @MPBailey 3 suggestions above.

@petervwyatt petervwyatt added ISO approved Resolved issue approved by ISO and removed bug Something isn't correct proposed solution Proposed solution is ready for review labels Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ISO approved Resolved issue approved by ISO
Projects
None yet
Development

No branches or pull requests

2 participants