forty bits to a quantum: five bytes, eight characters and five padding cases
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.
The "=" carries no data: it fills the last quantum out to eight characters. Base32hex differs in the alphabet alone — the same bit scheme, the same padding.
The byte 0x00 is smaller than 0x07, yet its encoding is larger: AA====== against A4======. From value 26 on, the base32 alphabet switches from letters to digits, and in ASCII the digits come before the letters — so any five-bit group that crosses that line reverses the comparison.
Base32hex puts the digits first, and the order survives the encoding: sorted data stays sorted. Checked on all 256 one-byte and all 65,536 two-byte inputs. It is what NSEC3 in DNSSEC uses to encode hashed owner names (RFC 5155), not plain base32.
Why the numbers can be trusted. Every countable number here is computed from data rather than typed in, and the sheet must pass 9 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
three bytes become four characters: the alphabet, the tail, and what the "=" at the end is for
two scales · 1000 and 1024 · why a drive looks smaller