> If we were to have standardized font that had distinct characters In addition you'll need checksums to detect folds or scratches on the print. E.g. when the

> If we were to have standardized font that had distinct characters In addition you'll need checksums to detect folds or scratches on the print. E.g. when the "m" in pets.com is scratched. QR codes have that. You'll want fallbacks for such wear and tear. QR codes can have that (depending on settings when creating, it will repeat the pattern multiple times). You'll need unicode support for all languages in the world (QR is just bits). You'll need to handle (bi)direction (Again: QR is just bits and bytes). And when you have all that, the solution suffers from the exact same problems as what QR "suffers" from. I, human, cannot read an arab unicode URL that is repeated for redundancy (and one of the three is malicious) or understand the checksums.