-
Notifications
You must be signed in to change notification settings - Fork 310
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
Generating Code128A #102
Comments
BWIPP only supports two encoding methods for code128 - Is there a reason why only subset A can be used? If you can guarantee that the text to encode will always be subset A characters, it is not hard to generate the raw encoding. As a reference, see the code128 wikipedia page. |
The following issue represents the current status of fixed-mode support in the underlying BWIPP library: bwipp/postscriptbarcode#58 (comment) This linked workaround should be sufficient to generate your required Code 128A:
Representing:
|
You guys are awesome!! Thanks for the super quick clarification! |
I have an existing barcode encoded in Code128A with text "12ABC456". I don't think parse or parsefnc is necessary, but even testing with / without those, the barcode does not match my existing one. Is there a way to force a CODE128A barcode to be generated?
For reference, the barcode I have looks like the attached barcode.
The one generated by bwip looks like this:
The text was updated successfully, but these errors were encountered: