Address #43 Rare bug in PDF417 barcode generator #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This implements suggested fix for bug reported to SourceForge project. If a value to be enceded as PDF417 contains a run of 45 digits (0-9) and invalid barcode is generated. The issue is rare in that it happens only when there are exactly 45 consequtive digits. For example, error happens with 45 digits but not with 44 or 46. Original bug report: https://sourceforge.net/p/barcode4j/bugs/43/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements suggested fix for bug reported to SourceForge project.
If a value to be enceded as PDF417 contains a run of 45 digits (0-9) and invalid barcode is generated. The issue is rare in that it happens only when there are exactly 45 consequtive digits. For example, error happens with 45 digits but not with 44 or 46.
Original bug report:
https://sourceforge.net/p/barcode4j/bugs/43/