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
RSS-14 / DataBar Stacked: incorrect separator pattern
Possible Data Matrix buffer overflow bug
Hi Robin, Thanks for looking at this! Your logic sounds right to me, and it's compelling that other tools generate the same output. I'm going to leave the implicit mode change out in Okapi for now in order to achieve wider compatibility (with e.g. ZXing), but hopefully it can be added back in at some point. Daniel
Possible DataBar (RSS) bug (FNC1 handling)
Never mind, the latest version of the spec matches the code -- my version of the spec was a couple of years old.
Bug in GS1 validation for AI 8017, 8018 data length
Bug in GS1 validation for AI 425 data length
Bug in GS1 validation for AI 253 (max length)
Bug in GS1 validation for "length 70 max" AIs
I think some of the new code is expanding % to %% even when GS1 mode is not enabled; I think the extra space should only be allocated when in GS1 mode, no?
QR code add_version_info possible bug
By extension, the same should probably happen in the cwbit function (for the name of the first parameter).
QR code populate_grid parameter naming issue (minor)
QR code possible bug: format info grid initialization
QR code error correction capacity optimization bug
QR code mode optimization possible bug
Data Matrix ECI broken
Crash with QR Code + GS1 + % chars
Invalid Code128 barcodes: reader init + code set C
UPC/EAN: Make printing of check digit in human-readable text configurable
This check would be nice, if it weren't so buggy...
PositionLiteralsFirstInComparisons false positive
UseUtilityClass false positive