mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-10-24 09:46:59 -06:00
japbcoelhoandClaude Opus 5.5
92a801a04f
A document assigned a CMYK profile (Edit > Assign Profile) keeps it when it is saved, but the working spaces are the app's, and a new session starts with the defaults. Opened again, such a document exported its CMYK colours tagged with the working CMYK space (VectorCraft Generic CMYK (SWOP-like)) instead of its own profile, made that profile the PDF/X output intent, and separated its RGB colours through it; print separations did the same. edit.assignProfile still reported the assigned profile, and document.exportPdf's documentation says CMYK colours are tagged with "the document's CMYK profile". Found on a book cover assigned FOGRA39L Coated: built in several vectorcraft-cli runs, each reopening the saved document, its PDF/X-4 came out tagged with the SWOP-like profile unless every run set FOGRA39 as the working CMYK space again. Export and print now work in the document's colour spaces: the active settings with the assigned profiles in their place (document_cms). An assigned profile that isn't available leaves the working space, with a warning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>