-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Binary data changed after encoding in azteccode #354
Comments
Hi @terryburton, Can you take a look at the two "bad" examples? They are generating a rangecheck error in ghostscript. Verified against BWIPP 2024-11-16. This is the dump from the first bad example:
PostScript calls:
|
Yes. It won't be immediate though as I'm recovering from flu. Thanks for the triage. |
This ensures that the bitstream is properly truncated: bwipp/postscriptbarcode@d7c9cec Please also let me know whether it resolves the original issue. |
Thank you for the great library!
We are encountering a very seldom but huge Issue where some binary data is wrongly encoded in the barcode.
Usually we are taking binary data as base64 and render it into an azteccode. Very seldomly those barcodes return the wrong data back after scanning. (Tested by multiple different barcode-scanners used in public transit. For my testing I use the QRbot App but the result is the same on every scanner.)
Putting the same data into Apple-Wallet PKPass works.
I was able to find two examples. In HEX the following happens (Only the part and a few bytes around the part that breaks)
I built you an example that directly takes the binary from hex. Tested on latest commit (ec9c2c8).
The text was updated successfully, but these errors were encountered: