The device a file's colours are meant for
Two people can open the same file, disagree about what colour it is, and both be right, because nothing inside it says what the numbers were meant to look like. A printing works will not take that risk: before running a job they want to know which press, which paper and which set of inks the colours were chosen for.
So the answer travels inside the file, and it is also printed in plain words on the page it applies to: the device the colours were chosen for, and the name its setting goes by. Beside those words stand a ramp and one patch for each of the base colours that device works in, all painted through the very description the page names — so whoever opens the document can compare the words with the colours, and nobody has to telephone to ask. The document below is stated for an ordinary screen, which is what a file settles on when nothing else is said; the engine takes your own printing works' description just as readily, and the same page then comes out in that press's inks. A document meant to be kept for decades carries such a statement as a matter of course, which is why it turns up on every archived file.
What this example shows
- The device's own colour profile, carried inside the file itself.
- The device and the name its setting goes by, printed on the page they apply to.
- A ramp and one patch per base colour, painted through that same profile.
The source code, complete
Nothing is left out and nothing is simplified: this is the program exactly as it runs, for the developer who uses this library.
The third is the description itself: a plain list of what the page has to say, which is what the service is sent.
Read the Rust source
Read the Python source
Read the JSON source
The document itself
Open the document in English
Open the document in French