Daniel Gredler

Re the default square bracket mode, the same logic applies. Right square brackets are allowed (with a warning as being non-CSET82) but left square brackets aren't as they introduce AI parsing. Are brackets actually used (as data) in GS1 content in the wild? They're illegal per the GS1 spec, which is why I think they were chosen as the AI delimiter over the more traditional parentheses (which are legal in GS1 content, and therefore would introduce an ambiguity).

An interesting use case that I ran across recently which blurs the line between "standard" and "non-standard" is the Swiss QR Code, which requires that a Swiss cross be placed over the QR Code: https://www.six-group.com/dam/download/banking-services/standardization/qr-bill/ig-qr-bill-v2.2-en.pdf

QR code add_version_info possible bug

Cool, thanks for the quick confirmation!

QR code add_version_info possible bug

5 years later, I realize I never responded here! :-) I've been reviewing the QR Code source recently, and ran into this again. From what I can tell (please correct me if I'm wrong), each element in the grid array contains two pieces of information: whether it is ON or OFF (in the least significant 4 bits, or nibble), and whether it should be masked (in the most significant 4 bits, or nibble). The mask info is added in qr_setup_grid(), where we reserve space in the grid for the version info (among...

Thanks, that seemed to fix it. I'll run a few iterations of ZCheck on it over the next few days to triple check it.

GS1 DataBar Expanded Stacked with mostly empty last row