Skip to content

Add Kotoba v1 OCIO config-header binding - #2335

Closed
com-junkawasaki wants to merge 2 commits into
AcademySoftwareFoundation:mainfrom
kotoba-lang:cursor/kotoba-ocio-header-v1-6d25
Closed

Add Kotoba v1 OCIO config-header binding#2335
com-junkawasaki wants to merge 2 commits into
AcademySoftwareFoundation:mainfrom
kotoba-lang:cursor/kotoba-ocio-header-v1-6d25

Conversation

@com-junkawasaki

Copy link
Copy Markdown

Adds a first-class kotoba/ sibling next to src/OpenColorIO and src/bindings/{java,python}.

What this is

v1 parse of the OCIO config header key ocio_profile_version: plus identification of ColorSpace name raw on a 71-byte vendored fixture. Compiles to host-independent wasm32 with kotoba CLI v0.7.2 (no FFI, no IEEE floats).

What this is not

  • Not a color transform pipeline or LUT engine
  • Not a drop-in replacement for the C++ / Python / Java APIs
  • Not robotics-ready

Checks

kotoba/checks.sh compiles the module and compares the packed result to the fixture bytes. Fork workflow is on kotoba-lang#1. This PR does not claim that workflow has already gone green.

Linux Foundation EasyCLA may apply for this contribution. This PR does not file it.

Fork PR: kotoba-lang#1

Parse ocio_profile_version and the raw colorspace name from a 71-byte
fixture. No color transform pipeline, no FFI, i64-v1 wasm32 only.

Co-authored-by: Jun Kawasaki <04.feasts_minded@icloud.com>
@linux-foundation-easycla

linux-foundation-easycla Bot commented Aug 28, 2026

Copy link
Copy Markdown

CLA Not Signed

Skip the VFX/macOS/GPU matrix when only kotoba/** or kotoba*.yml
change. README drops unverified wasm/packed claims; fixture stays 71B.

Co-authored-by: Jun Kawasaki <04.feasts_minded@icloud.com>
@carolalynn

Copy link
Copy Markdown
Collaborator

Hello,

Thank you for attempting to contribute, but this is not a language we are familiar with nor were we able to find much info.

Also, this PR does not follow our contribution guidelines - no DCO, signed CLA, or disclosure of AI tool usage. Going to close this - please feel free to give us more information at a TSC meeting or on our slack, and we can discuss re-opening.

@carolalynn carolalynn closed this Sep 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants