mirrors/zint-barcode-generator
1
0
Fork 0
mirror of https://git.code.sf.net/p/zint/code synced 2025-05-27 13:34:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Release 2.11.1

Browse source
This commit is contained in:
gitlost 2022-08-22 16:28:22 +01:00
parent 25c9582ae2
commit 8310a4b938
36 changed files with 106 additions and 98 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/manual.pmd
View file

@ -1,5 +1,5 @@
% Zint Barcode Generator and Zint Barcode Studio User Manual
% Version 2.11.0.9
% Version 2.11.1
% August 2022
# 1. Introduction
@ -1280,7 +1280,7 @@ zint -b 84 --direct --filetype=pcx -d "Data to encode"
```
This command will output the symbol as a PCX file to stdout. The currently
supported output file formats are shown in the following table:
supported output file formats are shown in the following table.
Abbreviation File format
------------ ---------------------------
@ -3175,7 +3175,7 @@ information on mail items. Valid data characters are 0-9, A-Z, a-z, space and
hash (#). A Format Control Code (FCC) is added by Zint and should not be
included in the input data. Reed-Solomon error correction data is generated by
Zint. Encoding behaviour is determined by the length of the input data according
to the formula shown in the following table:
to the formula shown in the following table.
-------------------------------------------------------------
Input Required Input Format Symbol FCC Encoding
@ -3590,7 +3590,7 @@ MaxiCode symbols are composed of two parts named the primary and secondary
messages. The primary message consists of a Structured Carrier Message which
includes various data about the package being sent and the secondary message
usually consists of address data in a data structure. The format of the primary
message required by Zint is given in the following table:
message required by Zint is given in the following table.
Characters Meaning
---------- -----------------------------------------------------------------
@ -3716,7 +3716,7 @@ is dependent on the length of the data input and Zint will allow error
correction capacities as low as 3 codewords.
Alternatively the amount of error correction data can be specified by setting
the `--secure` option (API `option_1`) to a value from the following table:
the `--secure` option (API `option_1`) to a value from the following table.
Mode Error Correction Capacity
---- -------------------------
@ -3810,7 +3810,7 @@ The size of the symbol and the error correction capacity can be specified. If
you specify both of these values then Zint will make a 'best-fit' attempt to
satisfy both conditions. The symbol size can be specified using the `--vers`
option (API `option_2`), and the error correction capacity can be specified by
using the `--secure` option (API `option_1`), according to the following tables:
using the `--secure` option (API `option_1`), according to the following tables.
Input Symbol Size Input Symbol Size
----- ----------- - ----- -----------
@ -3915,7 +3915,7 @@ Table: {#tbl:hanxin_sizes tag=": Han Xin Sizes"}
There are four levels of error correction capacity available for Han Xin Code
which can be set by using the `--secure` option (API `option_1`) to a value from
the following table:
the following table.
Mode Recovery Capacity
---- -----------------
@ -3944,7 +3944,7 @@ option_3 = ZINT_FULL_MULTIBYTE | (N + 1) << 8
This symbology uses a grid of coloured elements to encode data. ECI and GS1
modes are supported. The amount of error correction can be set using the
`--secure` option (API `option_1`) to a value as shown in the following table:
`--secure` option (API `option_1`) to a value as shown in the following table.
Value EC Level Amount of symbol holding error correction data
----- -------- ----------------------------------------------
@ -4054,7 +4054,7 @@ those owners, companies or organisations.
## 7.3 Version Information
The current stable version of Zint is 2.11.0, released on 24th May 2022.
The current stable version of Zint is 2.11.1, released on 22nd August 2022.
See `"ChangeLog"` in the project root directory for information on all releases.