The same numbers, said so they mean something
Carrying a colour profile inside a document costs a few hundred kilobytes, on every copy, and there are documents that cannot afford it: a statement sent to a million people, a form pulled down over a poor connection. It looks like a choice between colour that means something and a file that stays small, and it is not one.
You are looking at one row of colours and one grey ramp, each painted three times over with the very same numbers. The first time the numbers are handed over as they are: the shortest thing to write, and every screen and every printer then settles for itself what they look like. The second time they are said against a stated white and a stated set of base colours, which pins down what they mean, whoever opens the document. The third time the base colours are a wider set, and the same numbers reach deeper, more vivid tones. The greys follow the same three steps, once spread out evenly by measurement and once spread out evenly to the eye — which is why the two ramps do not look alike even though the ten numbers behind them are identical. All of it travels in a handful of numbers, and there is no profile to carry.
What this example shows
- Six colours in three bands, the same three numbers behind each.
- A ten-step grey ramp in three bands, the same ten numbers behind each.
- Under every band, the white and the base colours it was said against.
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