-
Notifications
You must be signed in to change notification settings - Fork 241
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
Code 128 encoding is broken for some payloads containing "99" #184
Comments
Hi, I have exactly the same issue with version 3.0.3 in .NET 8, generating a Code128 barcode. |
This is interesting. I just tested the java version of this lib and it doesnt have this issue. Let me try the .NET verison. |
I confirm the same problem, and indeed "99" appears to be the key. For the message ^750-993/1 it generated barcode with 750-191517 , although the label read ^750-993/1. This is version 3.1.1 and all previous since 3. Version 2.4.0 generated it correctly. .Net Framework 4.8.1 |
I think this will fix the issue here. The issue was related to when it was trying to switch code types. PR here: #205 |
Closing as fixed. |
Unrelated to this problem, but what about #210 ? |
In v3.0.0 and v3.0.3, Code128 generates incorrect barcodes for certain payloads. In my experience, the payloads that provoke the bug always involve the text
"99"
. I included some examples at the bottom.If I force it to use only code set B, it works fine:
If I downgrade to v2.4.0, it also works fine:
Some bad barcodes
The text was updated successfully, but these errors were encountered: