-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Data Matrix - selectable encoding #41
Comments
Plan is to create a dedicated encoder for the Royal Mail Mailmark application of non-standard DataMatrix which mandates the use of C40 encoding except for the customer detail field where a latch to any other encoding can be used. Too specific a specialisation to pollute the datamatrix encoder with this. Requires introducing a raw mode to the datamatrix encoder so that the encoded codewords can be passed directly. |
For anyone in need of enforcing a c40 encoding before that is done, the earlier version here https://github.com/bwipp/postscriptbarcode/blob/5dfc33e823c582a1ffa47e9d6c768095c637203e/src/datamatrix.ps allows passing the encoding=c40 flag, which will give you a compliant barcode (if not one that allows the freedom of any encoding for the last bit). |
Is there a way to use a base256 encoding, which is used by Deutsche Post? When I try libdmtx with the -e8 option for base256, the resulting Data Matrix code is 100% the same as the matrix code generated by Deutsche Post. So it looks like they use a pure base256 encoding, for their completely HEX encoded stamps. |
To have a control over encoding would be a good feature (e.g., auto, ascii, text, base256,..). |
Coming, but stuck behind some tricky rendering enhancements... |
Option added to support Royal Mail Mailmark encoding requirements. |
There are cases where selecting a fixed encoding method is preferable over automatic selection for minimum barcode size. (some systems are fixed to read only certain types)
I'd suggest reintroducing the "encoding=???" options so the default can be overridden.
The text was updated successfully, but these errors were encountered: