Code 128 and retail barcodes
A page of barcodes, drawn as bars: Code 128 and the retail family, EAN-13, UPC-A, EAN-8.
A page of QR codes, drawn as squares.
A page of QR codes drawn as squares, each captioned with what it carries. QR is the code most documents end up wanting: a payment request on an invoice, a boarding pass, a link to a case file, a serial number on a label.
Whether a code works is not a question the page can answer, and not one a human eye can. A code reader is run over the finished page and what it reads back is compared with what went in, which is how the sample below is checked. The white margin the standard asks for is kept, because a code without one is a code some scanners will not see.
The same document is written twice, once in each language. Both files are shown in full, with the code coloured on the server, and can be copied in one click.
The same document is written in each of these languages. Open the one you want to look at.
This document weighs 44,412 bytes.
The team has since put a heading and two lines at the top of this page saying what the codes are for, so the earlier figure was taken on a document this one is no longer. See every document measured.
A page of barcodes, drawn as bars: Code 128 and the retail family, EAN-13, UPC-A, EAN-8.
A page of Data Matrix codes, drawn as squares.
A page of PDF417 codes, drawn as stacked bars.
A page of Aztec codes, drawn as squares.
Every picture the tests ship with, on one page, each captioned with what its own file declares.
One picture fitted into a box of one size eight ways: brought to four different sizes, stood against an edge, turned by a quarter and by an angle of its own, and mirrored — every panel drawn from the placement the rule worked out.