mirror of
https://git.code.sf.net/p/zint/code
synced 2026-05-11 16:43:51 +00:00
GS1: new GS1RAW_MODE (CLI "--gs1raw") and GS1 Syntax Engine
"Unbracketed AI" (caret) options for specifying GS1 input (ticket #350, props Mario Verbruggen) DBAR_EXP_CC/DBAR_EXPSTK_CC: fix separator over finder patterns when linear part is greater than 4 codeblocks general: left-over raw_text -> content_segs in comments; update & expand some GS1 General Specs refs; some minor code fiddling test suite: suppress some additional ZINT_SANITIZEM false positives (& add new ZINT_TESTUTIL_SANITIZEM_INIT helpers)
This commit is contained in:
10
docs/zint.1
10
docs/zint.1
@@ -248,6 +248,16 @@ square brackets \f[CR]\(dq[]\(dq\f[R].
|
||||
If the AI data contains opening parentheses, they must be backslashed
|
||||
(\f[CR]\(dq\(rs(\(dq\f[R]).
|
||||
.TP
|
||||
\f[CR]\-\-gs1raw\f[R]
|
||||
Treat input as GS1 compatible data (as \f[CR]\-\-gs1\f[R]), but process
|
||||
literally, with any required \f[CR]FNC1\f[R]s represented by
|
||||
\f[CR]GS\f[R] (0x1D).
|
||||
AIs are not delimited by brackets (\f[CR]\(dq[]\(dq\f[R] or
|
||||
\f[CR]\(dq()\(dq\f[R]).
|
||||
(Similar to the GS1 Syntax Engine \(lqUnbracketed AI\(rq entry mode
|
||||
except using \f[CR]GS\f[R]s instead of carets, and without any initial
|
||||
\f[CR]GS\f[R].)
|
||||
.TP
|
||||
\f[CR]\-\-gs1strict\f[R]
|
||||
Treat input as GS1 compatible data (as \f[CR]\-\-gs1\f[R]) and use the
|
||||
GS1 Syntax Engine (if available) to strictly verify the GS1 data,
|
||||
|
||||
Reference in New Issue
Block a user