docs(color): Use color interop IDs and new views instead of legacy names - #5388
Merged
lgritz merged 2 commits intoAug 11, 2026
Merged
Conversation
Some of the color space and view names were still from older SPI and ACES configs. Signed-off-by: Brecht Van Lommel <brecht@blender.org>
lgritz
reviewed
Aug 10, 2026
Signed-off-by: Brecht Van Lommel <brecht@blender.org>
brechtvl
force-pushed
the
color-interop-docs
branch
from
August 10, 2026 18:31
a4f3566 to
7f28ee5
Compare
34 tasks
lgritz
approved these changes
Aug 10, 2026
lgritz
left a comment
lgritz
left a comment
Collaborator
There was a problem hiding this comment.
LGTM, but I'd like to get a second ok from @zachlewis before I merge.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Some of the color space, display and view names were still from older SPI and ACES configs.
Ref #4980
Tests
N/A
Checklist:
and if I used AI coding assistants, I have an
Assisted-by: TOOL / MODELline in the pull request description above.
behavior.
PR, by pushing the changes to my fork and seeing that the automated CI
passed there. (Exceptions: If most tests pass and you can't figure out why
the remaining ones fail, it's ok to submit the PR and ask for help. Or if
any failures seem entirely unrelated to your change; sometimes things break
on the GitHub runners.)
fixed any problems reported by the clang-format CI test.
corresponding Python bindings. If altering ImageBufAlgo functions, I also
exposed the new functionality as oiiotool options.