News for hackers. Stuff that matters.
Re:Libre Barcode Project by eqvinox on Tuesday December 22, 2020 @12:24PM (#25508712)
Barcodes are easier and more reliably scanned by dedicated devices; QR codes are easier and more reliably scanned by general-purpose devices like phones.
Re:Libre Barcode Project by edoceo on Tuesday December 22, 2020 @02:11PM (#25509927)
I've used scores of different hardware readers (zebra, motorola, star, el-cheapo, etc). All of them read 2d faster than they read 1d. And we get a higher first-try success on 2d. IIRC 1d was like 80% and 2d was over 95%
Re:Libre Barcode Project by mark-r on Tuesday December 22, 2020 @04:08PM (#25511269)
There are many 1d standards. How many did you try?
Re:Libre Barcode Project by edoceo on Tuesday December 22, 2020 @05:17PM (#25511985)
C128(ABC) and 39 got the most testing (other players in my space like C128). I'd also like to add that the fail rate on C128 increased as the encoded values got complex. That is to say 15 numeric chars was "very reliable" but 17 alpha-numeric+1 symbol had was "very unreliable"

And if you're in the <12 digits only space C128 is still a safe choice

Re:Libre Barcode Project by mark-r on Tuesday December 22, 2020 @06:06PM (#25512505)
That's an interesting observation. I'd expect C128 to be good because the checksum character should reject most bad scans.
Re:Libre Barcode Project by edoceo on Tuesday December 22, 2020 @09:37PM (#25513809)
Yessir, that's my (perhaps unclear) point. Give it the trigger on the "complex" C128 and we get a read fail. But scan success on attempt 3 or 4. QR scans with high success on first bread.
Re:Libre Barcode Project by mark-r on Thursday December 24, 2020 @02:20AM (#25525663)
Does QR include some kind of error correction code? That would be far more sophisticated than a checksum, and lead to more salvageable results from bad scans.