The page now leads with adding a picture, then its answer: how wide to print it to scan from a table, for every picture whose code's version a scanner reported or the checks estimate. Below, as the evidence, all 6,499 codes sit on one scale from easy to hard.
The pixel check now takes its limits from the grid behind the print widths, in its good-light scene, by the same rule as the other checks: Fine from 4.45 camera pixels per square at every version, and a Problem limit that rises with the version.
At a slant, or on a can or bottle, the width grows so that the squares the phone sees narrowest keep the need. No width is given turned past 55°, for a code wider than the diameter over 1.2, or where the code and its margin, turned, would no longer fit the camera's view.
Behind the + under the answer, What a phone sees draws your picture as a phone's scanner would get it, printed at the width worked out and seen from its distance. It is an illustration, not a scan.
A test sheet, to pri…
3 days ago
Fix styled-file hints, and add inches, copies and the many-codes rule
Styled files now get the 'looks like a file' hint, and flat files no longer get the 'looks like a photo' one. Every width and distance is also given in inches, and a printed width can be typed in inches. A picture that repeats one code gives each code's width and says how many copies zxing-cpp read. A file whose version no scanner reported is planned from the checks' estimate, and says so. The margin check reads small files better, and a margin the picture's edge may have cut is left out of the code's facts. On a picture where zxing-cpp reads 100 codes or more at one size, OpenCV's newer detector isn't run at that size or smaller, and the confidence is at most medium. OpenCV's reads of contents that aren't UTF-8 text now count. /api/measure adds copies, not_run, quiet.capped and content.sha256s.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HykRoFZnnb98KRf6Xxomka
A file marked The original graphic now gets its code's facts as made: its version, error correction and margin, how much of its error correction it already uses, and whether its content fits a smaller version, with where these come from behind "+". /api/measure adds ec_level, mask, squares, raw_sha256 and raw_bytes, and on a picture that repeats a code, uec is now the lowest figure among its copies.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HykRoFZnnb98KRf6Xxomka
5 days ago
Add print widths for a scanning distance, pairing, and a flag for styled files
Each read picture now leads with how wide to print its code, or a file itself, to scan from a chosen distance, worked out in the browser from the measured scanner needs and an assumed phone camera. Pictures of one code are paired in the browser by a digest of their content, and a file that already uses some of its error correction is flagged. /api/measure adds uec, uec_frame and content.sha256.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HykRoFZnnb98KRf6Xxomka