mirror of
https://git.code.sf.net/p/zint/code
synced 2025-12-17 09:57:02 +00:00
RAW_TEXT: change source to be unconverted, i.e. UTF-8 (unless
`DATA_MODE`); allows ZXing-C++ to be built in writer-only mode without needing "libzueci" library: in GS1 mode check that ECI if any is ASCII compatible general: some code fiddling, `mode` -> `modes`
This commit is contained in:
@@ -333,7 +333,7 @@
|
||||
<h1 class="title">Zint Barcode Generator and Zint Barcode Studio User
|
||||
Manual</h1>
|
||||
<p class="author">Version 2.15.0.9</p>
|
||||
<p class="date">August 2025</p>
|
||||
<p class="date">September 2025</p>
|
||||
</header>
|
||||
<nav id="TOC" role="doc-toc">
|
||||
<ul>
|
||||
@@ -4369,9 +4369,9 @@ Segments</a> for the format), one for each segment specified, the size
|
||||
of the array being set in <code>raw_seg_count</code> - which will always
|
||||
be at least one.</p>
|
||||
<p>The <code>source</code>, <code>length</code> and <code>eci</code>
|
||||
members of <code>zint_seg</code> will be set accordingly - the data in
|
||||
<code>source</code>, the data length in <code>length</code>, and the
|
||||
character set the data is in (UTF-8 data will be converted) in
|
||||
members of <code>zint_seg</code> will be set accordingly - the
|
||||
unconverted data in <code>source</code>, the data length in
|
||||
<code>length</code>, and the character set the data was converted to in
|
||||
<code>eci</code>. Any check characters encoded will be included,<a
|
||||
href="#fn16" class="footnote-ref" id="fnref16"
|
||||
role="doc-noteref"><sup>16</sup></a> and for GS1 data any
|
||||
@@ -4382,6 +4382,11 @@ as will EAN-8 but only if it has an add-on (otherwise it will remain at
|
||||
separator). GS1 Composite data if any will be separated from the primary
|
||||
data (including any EAN/UPC add-ons) by a pipe (<code>|</code>)
|
||||
character.</p>
|
||||
<p>The <code>source</code> member is not NUL-terminated, and is not
|
||||
converted: if <code>input_mode</code> is <code>DATA_MODE</code>, it
|
||||
remains in binary; otherwise it will be in UTF-8. The UTF-8 source may
|
||||
be converted to the character set of the corresponding <code>eci</code>
|
||||
member using the two helper functions discussed next.</p>
|
||||
<h2 id="utf-8-to-eci-convenience-functions">5.17 UTF-8 to ECI
|
||||
convenience functions</h2>
|
||||
<p>As a convenience the conversion done by Zint from UTF-8 to ECIs is
|
||||
@@ -8359,7 +8364,7 @@ bcsample source code</li>
|
||||
<li>PNG: The Definitive Guide and wpng source code by Greg Reolofs</li>
|
||||
<li>PDF417 specification and pdf417 source code by Grand Zebu</li>
|
||||
<li>Barcode Reference, TBarCode/X User Documentation and TBarCode/X
|
||||
demonstration program from Tec-It</li>
|
||||
demonstration program from TEC-IT</li>
|
||||
<li>IEC16022 source code by Stefan Schmidt et al</li>
|
||||
<li>United States Postal Service Specification USPS-B-3200</li>
|
||||
<li>Adobe Systems Incorporated Encapsulated PostScript File Format
|
||||
@@ -9737,7 +9742,7 @@ class="footnote-back" role="doc-backlink">↩︎</a></p></li>
|
||||
characters undefined: <code>#</code>, <code>$</code>, <code>@</code>,
|
||||
<code>[</code>, <code>\</code>, <code>]</code>, <code>^</code>,
|
||||
<code>`</code>, <code>{</code>, <code>|</code>, <code>}</code>,
|
||||
<code>~</code>.<a href="#fnref7" class="footnote-back"
|
||||
<code>~</code> (tilde).<a href="#fnref7" class="footnote-back"
|
||||
role="doc-backlink">↩︎</a></p></li>
|
||||
<li id="fn8"><p>BARCODE_MEMORY_FILE textual formats EPS and SVG will
|
||||
have Unix newlines (LF) on both Windows and Unix, i.e. not CR+LF on
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
% Zint Barcode Generator and Zint Barcode Studio User Manual
|
||||
% Version 2.15.0.9
|
||||
% August 2025
|
||||
% September 2025
|
||||
|
||||
# 1. Introduction
|
||||
|
||||
@@ -1364,7 +1364,7 @@ ECI Code Character Encoding Scheme (ISO/IEC 8859 schemes include ASCII)
|
||||
Table: {#tbl:eci_codes tag=": ECI Codes"}
|
||||
|
||||
[^7]: ISO/IEC 646 Invariant is a subset of ASCII with 12 characters undefined:
|
||||
`#`, `$`, `@`, `[`, `\`, `]`, `^`, `` ` ``, `{`, `|`, `}`, `~`.
|
||||
`#`, `$`, `@`, `[`, `\`, `]`, `^`, `` ` ``, `{`, `|`, `}`, `~` (tilde).
|
||||
|
||||
An ECI value of 0 does not encode any ECI information in the code symbol (unless
|
||||
the data contains non-default character set characters). In this case, the
|
||||
@@ -2696,14 +2696,19 @@ Segments] for the format), one for each segment specified, the size of the array
|
||||
being set in `raw_seg_count` - which will always be at least one.
|
||||
|
||||
The `source`, `length` and `eci` members of `zint_seg` will be set accordingly -
|
||||
the data in `source`, the data length in `length`, and the character set the
|
||||
data is in (UTF-8 data will be converted) in `eci`. Any check characters encoded
|
||||
will be included,[^16] and for GS1 data any `FNC1` separators will be
|
||||
represented as `GS` (ASCII 29) characters. UPC-A and UPC-E data will be expanded
|
||||
to EAN-13, as will EAN-8 but only if it has an add-on (otherwise it will remain
|
||||
at 8 digits), and any add-ons will follow the 13 digits directly (no separator).
|
||||
GS1 Composite data if any will be separated from the primary data (including any
|
||||
EAN/UPC add-ons) by a pipe (`|`) character.
|
||||
the unconverted data in `source`, the data length in `length`, and the character
|
||||
set the data was converted to in `eci`. Any check characters encoded will be
|
||||
included,[^16] and for GS1 data any `FNC1` separators will be represented as
|
||||
`GS` (ASCII 29) characters. UPC-A and UPC-E data will be expanded to EAN-13, as
|
||||
will EAN-8 but only if it has an add-on (otherwise it will remain at 8 digits),
|
||||
and any add-ons will follow the 13 digits directly (no separator). GS1 Composite
|
||||
data if any will be separated from the primary data (including any EAN/UPC
|
||||
add-ons) by a pipe (`|`) character.
|
||||
|
||||
The `source` member is not NUL-terminated, and is not converted: if `input_mode`
|
||||
is `DATA_MODE`, it remains in binary; otherwise it will be in UTF-8. The UTF-8
|
||||
source may be converted to the character set of the corresponding `eci` member
|
||||
using the two helper functions discussed next.
|
||||
|
||||
[^15]: DotCode, Han Xin, Micro QR Code, QR Code and UPNQR have variable masks.
|
||||
Rectangular Micro QR Code has a fixed mask (4).
|
||||
@@ -4992,7 +4997,7 @@ Below is a list of some of the sources used in rough chronological order:
|
||||
- PNG: The Definitive Guide and wpng source code by Greg Reolofs
|
||||
- PDF417 specification and pdf417 source code by Grand Zebu
|
||||
- Barcode Reference, TBarCode/X User Documentation and TBarCode/X demonstration
|
||||
program from Tec-It
|
||||
program from TEC-IT
|
||||
- IEC16022 source code by Stefan Schmidt et al
|
||||
- United States Postal Service Specification USPS-B-3200
|
||||
- Adobe Systems Incorporated Encapsulated PostScript File Format Specification
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
Zint Barcode Generator and Zint Barcode Studio User Manual
|
||||
Version 2.15.0.9
|
||||
August 2025
|
||||
September 2025
|
||||
|
||||
*******************************************************************************
|
||||
* For reference the following is a text-only version of the Zint manual, *
|
||||
@@ -2643,14 +2643,19 @@ for the format), one for each segment specified, the size of the array being set
|
||||
in raw_seg_count - which will always be at least one.
|
||||
|
||||
The source, length and eci members of zint_seg will be set accordingly - the
|
||||
data in source, the data length in length, and the character set the data is in
|
||||
(UTF-8 data will be converted) in eci. Any check characters encoded will be
|
||||
included,[16] and for GS1 data any FNC1 separators will be represented as GS
|
||||
(ASCII 29) characters. UPC-A and UPC-E data will be expanded to EAN-13, as will
|
||||
EAN-8 but only if it has an add-on (otherwise it will remain at 8 digits), and
|
||||
any add-ons will follow the 13 digits directly (no separator). GS1 Composite
|
||||
data if any will be separated from the primary data (including any EAN/UPC
|
||||
add-ons) by a pipe (|) character.
|
||||
unconverted data in source, the data length in length, and the character set the
|
||||
data was converted to in eci. Any check characters encoded will be included,[16]
|
||||
and for GS1 data any FNC1 separators will be represented as GS (ASCII 29)
|
||||
characters. UPC-A and UPC-E data will be expanded to EAN-13, as will EAN-8 but
|
||||
only if it has an add-on (otherwise it will remain at 8 digits), and any add-ons
|
||||
will follow the 13 digits directly (no separator). GS1 Composite data if any
|
||||
will be separated from the primary data (including any EAN/UPC add-ons) by a
|
||||
pipe (|) character.
|
||||
|
||||
The source member is not NUL-terminated, and is not converted: if input_mode is
|
||||
DATA_MODE, it remains in binary; otherwise it will be in UTF-8. The UTF-8 source
|
||||
may be converted to the character set of the corresponding eci member using the
|
||||
two helper functions discussed next.
|
||||
|
||||
5.17 UTF-8 to ECI convenience functions
|
||||
|
||||
@@ -4784,7 +4789,7 @@ Below is a list of some of the sources used in rough chronological order:
|
||||
- PNG: The Definitive Guide and wpng source code by Greg Reolofs
|
||||
- PDF417 specification and pdf417 source code by Grand Zebu
|
||||
- Barcode Reference, TBarCode/X User Documentation and TBarCode/X demonstration
|
||||
program from Tec-It
|
||||
program from TEC-IT
|
||||
- IEC16022 source code by Stefan Schmidt et al
|
||||
- United States Postal Service Specification USPS-B-3200
|
||||
- Adobe Systems Incorporated Encapsulated PostScript File Format Specification
|
||||
@@ -5755,7 +5760,7 @@ matrix barcodes.
|
||||
the yen sign (¥), and tilde (~) to overline (U+203E).
|
||||
|
||||
[7] ISO/IEC 646 Invariant is a subset of ASCII with 12 characters undefined: #,
|
||||
$, @, [, \, ], ^, `, {, |, }, ~.
|
||||
$, @, [, \, ], ^, `, {, |, }, ~ (tilde).
|
||||
|
||||
[8] BARCODE_MEMORY_FILE textual formats EPS and SVG will have Unix newlines (LF)
|
||||
on both Windows and Unix, i.e. not CR+LF on Windows.
|
||||
|
||||
Reference in New Issue
Block a user