Closed gitkathryn closed 9 years ago
Got it, thanks.
The change would be more genetic as I might also apply the same to EAN-14, ITF-14 and possibly EAN/UCC/GS1-128.
The only decision would be whether to make the spacing arbitrary as provided by the user or to enforce some kind of structure.
Good point. Is there some kind of convention for spacing? I'll look around.
On Thu, Mar 19, 2015 at 12:49 PM, Terry Burton notifications@github.com wrote:
Got it, thanks.
The change would be more genetic as I might also apply the same to EAN-14, ITF-14 and possibly EAN/UCC/GS1-128.
The only decision would be whether to make the spacing arbitrary as provided by the user or to enforce some kind of structure.
For SSCC as follows:
(00) E P S C
E = Extension - Can be thought of as packaging level. P = GS1 Prefix - 0+EAN/UPC prefix S = Serial identifier |P| + |S| = 16 C = Check digit
Looks like I need the text to echo the user input, but you don't necessarily need to worry about that, as that's the easy part.
Support for arbitrary spacing in the human readable text of SSCC-18 and EAN-14 has been added to version 2015-03-23.
Support also added to ITF-14.
To clarify, allow spaces in the input text, and print it out that way, too.