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 ColorSpace for 3D Data Streams #18

Closed
lrosenthol opened this issue Jan 11, 2021 · 3 comments
Closed

Clarify ColorSpace for 3D Data Streams #18

lrosenthol opened this issue Jan 11, 2021 · 3 comments
Labels
ISO approved Resolved issue approved by ISO

Comments

@lrosenthol
Copy link
Collaborator

Table 311, entry ColorSpace

The RGB colour space in which the 3D artwork’s colour values are encoded. Valid values are the name DeviceRGB, an array specifying a valid CalRGB color space (see 8.6.5.3 "CalRGB colour spaces"), or an array specifying a valid RGB-based ICCBased color space (see 8.6.5.5 "ICCBased colour spaces"). If this key is not present, the colour space for the 3D artwork colour values are considered undefined and a PDF processor may choose any appropriate RGB-based colour space, such as sRGB.

It is not clear from other parts of the text whether a DefaultRGB present on the page where the Annotation referencing the stream is used, should be used "in place" of the DeviceRGB (as would be the case for other uses of DeviceRGB). I believe that it should.

@lrosenthol lrosenthol added the bug Something isn't working label Jan 11, 2021
@petervwyatt
Copy link
Member

Proposed solution: add a new 2nd sentence:

If the name is DeviceRGB and the page where the annotation referencing the 3D stream is used has a DefaultRGB color space, then the DefaultRGB color space shall be used (see 8.6.5.6 Default colour spaces).

@petervwyatt petervwyatt added the proposed solution Proposed solution is ready for review label Jan 19, 2021
@petervwyatt
Copy link
Member

PDF TWG also identified typo "If this key is not present, the colour space for the 3D artwork colour values are considered undefined..." --> "... is considered..."

@lrosenthol
Copy link
Collaborator Author

This is also related to #34

@petervwyatt petervwyatt added ISO submitted Resolved issue submitted to ISO for approval and removed bug Something isn't working proposed solution Proposed solution is ready for review labels Dec 6, 2021
@petervwyatt petervwyatt added this to the ISO Submission Feb 2022 milestone Dec 6, 2021
@petervwyatt petervwyatt added ISO approved Resolved issue approved by ISO and removed ISO submitted Resolved issue submitted to ISO for approval labels Apr 27, 2022
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