Profile extension handling (.icm on Windows / .icc on Linux) #69

Closed
opened 2026-08-25 09:54:48 +01:00 by gronod · 0 comments
Owner

Problem

ArgyllCMS colprof outputs .icm profile files on Windows by default, but .icc on Unix (Linux/macOS). Currently, the frontend and backend hardcode ${basename}.icc, which causes profcheck and iccgamut to fail to find the generated profile on Windows.

Acceptance Criteria

  1. Platform-Aware Extension Resolver:
    • Detect profile extension based on platform (.icm on Windows, .icc on Linux/macOS) or check for existence of both <basename>.icc and <basename>.icm.
    • Update colprof.js, profcheck.js, and backend commands to locate the correct profile file regardless of platform.
  2. Impact:
    • Blocks #57 (3D gamut extraction) and Stage 5 profile verification on Windows.
### Problem ArgyllCMS `colprof` outputs `.icm` profile files on Windows by default, but `.icc` on Unix (Linux/macOS). Currently, the frontend and backend hardcode `${basename}.icc`, which causes `profcheck` and `iccgamut` to fail to find the generated profile on Windows. ### Acceptance Criteria 1. **Platform-Aware Extension Resolver**: - Detect profile extension based on platform (`.icm` on Windows, `.icc` on Linux/macOS) or check for existence of both `<basename>.icc` and `<basename>.icm`. - Update `colprof.js`, `profcheck.js`, and backend commands to locate the correct profile file regardless of platform. 2. **Impact**: - Blocks #57 (3D gamut extraction) and Stage 5 profile verification on Windows.
gronod added this to the Milestone 7: v0.2 ship milestone 2026-08-25 09:54:48 +01:00
gronod added the Kind/Bug
Priority
High
2
labels 2026-08-25 09:54:48 +01:00
Sign in to join this conversation.