Release v3.14.1: correct Measurement Report reference colours, clip-border text fit, and an ArgyllCMS fallback when the engine can't drive an instrument

Measurement Report (Knut): the .ti2 design reference was read as D50 although
printtarg records RGB charts under D65, so every expected colour was skewed
(paper white as Lab 100/-2.3/-19.3). A .ti2 storing XYZ normalised 0..1 was
also taken at face value, making expected colours 100x too dark. Both are now
detected and normalised; REPORT_SCHEMA 5 -> 6 rebuilds saved reports.

Clip border (Knut): stacked lines were justified across the strip, pushing the
last line into the patch area and making deleted blank lines look ineffective.
Lines now keep natural spacing from the outer text edge.

Measuring (mavtop): with the engine on by default since 3.14.0, an instrument
it cannot drive left the user unable to measure at all. A failed start now
restarts on stock chartread automatically -- only before the first reading,
never after a strip, never on user abort, never twice. The calibration prompt
carries the instrument's own request, and the helper no longer serialises an
uninitialised identifier buffer (verified against a real ColorMunki).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: itsab1989

CHANGELOG.md

@@ -1,5 +1,52 @@
 # Changelog
 
+## v3.14.1
+
+- **Measurement Report — the cube corners are the chart's real ideals again
+  (Knut).** Expected values were being read out of the chart's `.ti2` in the
+  wrong colour space: printtarg records an RGB chart's design colours under D65,
+  but the report compared them in D50. Paper white came out as a bluish
+  Lab 100/-2.3/-19.3 instead of a neutral 100/0/0, and every corner looked
+  invented rather than the textbook ideal. The design reference is now adapted to
+  D50 first, so the corners match the sRGB primaries exactly and every ΔE in the
+  report is correct — this affected **all** reports built against a chart, not
+  just imported ones.
+- **Measurement Report — charts whose `.ti2` stores XYZ 0..1 are read correctly
+  (Knut).** printtarg writes the design colours either 0..100 or normalised
+  0..1, with nothing in the header to tell them apart. The normalised form was
+  taken at face value, making every expected colour 100× too dark (a chart's
+  white read as L\* 9) and its ΔE meaningless. The scale is now detected and
+  normalised.
+- **Measuring falls back to ArgyllCMS when ChromIQ's engine can't use your
+  instrument (mavtop).** v3.14.0 turned the ChromIQ chart-reading engine on by
+  default. If it could not drive a particular meter, measuring simply stopped
+  there — even when ArgyllCMS's own chartread would have worked. ChromIQ now
+  notices a failed start and quietly restarts the run on stock chartread, so you
+  can carry on measuring. It only ever does this before the first reading is
+  taken, never after a strip has been read, and never when you stopped the run
+  yourself.
+- **The calibration prompt now shows what your instrument actually asked for
+  (mavtop).** The engine reports the exact calibration step, but ChromIQ threw
+  that away and showed one generic message for every case. It now passes the
+  instrument's own instruction through, and offers a "Skip this step" button
+  when the instrument says the step is optional.
+- **Fixed unreadable characters in the calibration prompt.** For calibration
+  steps that carry no message of their own — an X-Rite ColorMunki asking for its
+  calibration position, for instance — the measuring engine sent uninitialised
+  data instead of an empty message, which would have appeared as random
+  characters in the dialog.
+- **Clip border — the text no longer runs into the patch area (Knut).** The
+  stacked lines were justified across the full strip width, which pushed the last
+  line's ink past the inner edge and over the patches. Lines now keep their
+  natural spacing and start at the outer text-edge distance, so the block always
+  stays inside the strip. Only the font size grows — until the longest line
+  reaches the text-edge along the strip, or the stack reaches it across.
+- **Clip border — deleting the blank lines between records now visibly tightens
+  the text (Knut).** Because the lines were stretched to fill the strip whatever
+  their number, removing the blank lines between them changed nothing on screen.
+- **Clip border — "Example custom table" is now called "Custom text example"
+  (Knut).**
+
 ## v3.14.0
 
 The chart-reading engine, the Measurement Report and the i1Profiler import

README.md

@@ -5,7 +5,7 @@
 </p>
 
 <p align="center">
-  <img alt="Version" src="https://img.shields.io/badge/version-3.14.0-7c5cff">
+  <img alt="Version" src="https://img.shields.io/badge/version-3.14.1-7c5cff">
   <img alt="Downloads" src="https://img.shields.io/endpoint?url=https://itsab1989.github.io/github-traffic-downloads-dashboard/assets/badges/itsab1989_ChromIQ-downloads.json">
   <img alt="Platforms" src="https://img.shields.io/badge/platforms-macOS%20%C2%B7%20Windows%20%C2%B7%20Linux-2a9d8f">
   <img alt="License" src="https://img.shields.io/badge/license-GPLv3-blue">

core/version.py

@@ -1 +1 @@
-APP_VERSION = "3.14.0"
+APP_VERSION = "3.14.1"