Added Group Separator #26
Open
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
Added Group Separator character to Code 128 and DataMatrix barcodes for separation of variable length GS1 Application Identifiers.
Added the ability to generate GS1 QR codes including the ability to terminate variable length GS1 Application Identifiers using Group Separator.
|
Hi, today I have added the support to generate GS1 QR barcodes. |
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.
Hi, I have added the Group Separator character to Code 128 and DataMatrix barcodes for separation of variable length GS1 Application Identifiers. It is used by using a keyword
\FNC1anywhere in thedData string.I like your library, it's easy to use and implement. The only thing I missed here was the separation of variable length GS1 AIs, so I decided to implement it myself. The chosen keyword may cause conflicts and confusion. The confusion is addressed in README. The conflicts are solvable by just changing the keyword
\FNC1tosomethingNotInConflict.