128 ASCII positions: 66 unreserved, 18 delimiters, 43 that must always be encoded — and the "%" itself
Built as a memo rather than a table: the thing worth hanging it up for reads across the room, with the full reference in smaller type below it.
Three sizes in one archive — from a sheet on the fridge to a poster on the wall.
Encode every position outside the unreserved set, and a delimiter too whenever it stands as data inside a component.
The built-in encodeURIComponent leaves 71 positions untouched — exactly what RFC 2396 called unreserved: alphanum and mark. RFC 3986 took "!" "'" "(" ")" "*" out of that set and moved them to sub-delims, calling them "typically unsafe to decode" (Appendix D.2).
So 5 delimiters ride through it as data, and a scheme is free to read them as boundaries. The difference was measured over all 128 positions: on every other one the engine gives the same triplet as this sheet.
Why the numbers can be trusted. Every countable number here is computed from data rather than typed in, and the sheet must pass 11 independent checks before it is allowed to build — how many items there are, the order they come in, and the claim in the highlighted box itself. If one fails, there is no file.
ten tasks, the year of each, the system, the figure — and the human it was measured against
who published each standard, when, what it does to the sound, and how many bits per second it allows
forty bits to a quantum: five bytes, eight characters and five padding cases
three bytes become four characters: the alphabet, the tail, and what the "=" at the end is for