ZINT_WARN_INVALID_OPTION instead of 0 on ignored option;
more barcode synonyms
manual: append man page zint.1.pmd instead of CLI help;
various tweaks and fiddlings;
rMQR add ISO 23941 (released the other day but haven't got yet)
man page: expand and tweak
doc/Makefile: add HTML demo
HANXIN/QRCODE: use Hanzi/Kanji modes when compatible ECIs given
manual: one true source now manual.pmd from which manual.txt is generated
CLI: man page moved from frontend/zint.1.gz to docs/zint.1.gz, now
generated from docs/zint.1.pmd
add README.linux to root dir
UPNQR: fix required binary mode using mode_preset
UPNQR: allow mask to be manually specified
GUI: use non-native QColorDialog on Unix also; no noEXE for CLI equivalent;
add shortcuts for copy-to-clipboard and CLI equivalent
CLI: new --version option to print Zint version
GRIDMATRIX, HANXIN, MAXICODE, MICROPDF417, PDF417, QRCODE, RMQR, ULTRA
RMQR: fix ECI encoding (wrong bit length for indicator)
MICROQR: check versions M1 and M2 for allowed characters so as to give
better error messages
DOTCODE: some small optimizations
common.c: add is_chr(), segs_length(), segs_cpy()
CODEONE/CODE128/DOTCODE/GRIDMATRIX/HANXIN/MAXICODE/QRCODE/ULTRA: add
namespace prefixes to static funcs/data
includes: use Z_ prefix, unuse double underscore prefixes (guard defines)
manual.txt: compress some tables using double/treble column sets
UTF-16LE, GBK, separate GB18030, UTF-32BE, UTF-32LE
add examples to tests for DATAMATRIX, HANXIN, QRCODE
HANXIN: Remove alternating filler in function information;
GB 18030 now ECI 32 (previously used ECI 29);
fix gate-posts on codeword limits
use new ZXing-C++ HanXin detector (diagnostics2 branch) for tests
check against ISO/IEC 20830:2021 (no substantive changes)
backend_tcl: update ECIs; NOTE: changed names "unicode" -> "utf-16be",
"euc-cn" -> "gb2312"
GRIDMATRIX/HANXIN/QRCODE/RMQR: warn if auto-conversion (i.e. no ECI given)
occurs to resp. specialized char sets (GB 2312/GB 18030/Shift JIS)
vertical whitespace, as they're decorative rather than functional (#247)
Allow for dot overspill in height of vertical box sides (dotty mode)
Move is_dotty(), is_fixed_ratio() from library.c to common.c
Add FAST_MODE input_mode flag and --fast CLI/Tcl option that selects older
faster ISO algorithm (may be used by other symbologies in the future)
and "Fast Encoding" checkbox to Data Matrix GUI
GUI: adds Zint version numbers to DATAMATRIX sizes.
DMATAMATRIX: fix look ahead BASE256 use of dm_text_sp_cnt() on switching;
simplify dm_add_tail()
GUI: check suffixes on save so don't go into error state;
use native path for Save As clipboard message
CODE128: use gs1_check_digit() for NVE18 and EAN14
generated by libzint. Whether or not those barcodes are correct should be
validated in the test suite for libzint, for qZint it's good enough to
produce the same printouts that libzint does, which isn't trivial, especially
as some API names have different meanings, such as qZint ```text```
is libzint ```data```. Props Alonso Schaich <alonso@freebsd.org>
and set Escaped flag; fix tooltip that they're converted to spaces;
sequence dialog: re-organize to put Create Sequence stuff only in groupbox
and put Import -> From File and Clear at bottom, similar to data dialog;
mainwindow: use new Escaped flag from data dialog and set checkbox and
statusbar message accordingly
and restrict sequence to max 10,000, add button icons;
make Export dialog sizable and show every 100 results, add button icon;
fix saving CHANNEL option, fix Export painting main window (Windows), fix
guard descent not-resetting
qzint: add getAsCLI(), warnLevel(), extra isStackable()/isComposite() etc
Add ZBarcode_BarcodeName()
manual: doc above, some fixes, tweaks
The ```configuration``` is required by the visual studio generator to determine
whether to use a Debug or a Release setup (or a user customized one). It's
required by whatever uses that generator rather then just the GUI code.
Add instructions for the Visual Studio Project File generator to the README
and enable the test on Windows.
The ```addon_row_height``` variable is conditionally initialized in some
branches, which also set ```addon_latch``` to one(true). Later in the loop's
body, ```addon_row_height``` is accessed if ```addon_latch``` is true.
Unlike ```addon_row_height```, ```addon_latch``` is defined outside of the
loop's body, and as it is never reset to zero, keeps it's value of one once
it has been assigned. Future iterations of the loop can therefore not branch
into the code that initializes ```addon_row_height``` and (re)assigns
```addon_latch```, and ```addon_latch``` will be true, which causes
```addon_row_height``` to be accessed without having been initialized.
On most platforms, the ```addon_row_height``` variable will always be
allocated on the same memory, while skipping the initialization causes
the value that was previously assigned to ```addon_row_height``` to
remain on that memory.
Pull the variable declaration out of the for loop's body to assure the
previous iteration's value remains there independend of compiler or
platform specific behaviour.
other than for digits (worse for TEX 7-11 embedded in extended) and for
returning X12/EDI at EOD - will cause changes in encodation;
allow for GS1 GS in B256 (should never happen);
some re-jigging of dm200encode and fiddling with dm_isXXX;
remove some DM_DEBUG from dm_placementbit
The `__has_feature` macro is a clang extension that works like a macro. If
zint is being compiled using a compiler other then clang, `__has_feature`
is not defined. As it is not defined, it cannot be used as a function call
expression. Any environment that doesn't have `__has_feature` should prevent
the preprocessor from "seeing" the invokation of the macro, as invoking
undefined macros is not supported by the C language.
The usual procedure to assure this would be a construction like
\#if defined(__has_feature)
\# if __has_feature(...)
\# endif
\#endif
which, combined with the GCC check we have here, would result in a
3 level nesting of if and elseif expressions .. and that's without
covering microsoft's compiler.
For this purpose, Qt >= 5.13 has been defining the `__has_feature`
macro on non-clang environments, while defining all (clang) features
to not be available. This allows to write feature checks with "less"
nesting, as we have here.
Mimic Qt-5.13's behavior and provide the `__has_feature` macro if
it's not provided otherwise (either by clang or by Qt), allowing the
function-call-like expression to be parsed on those systems.
PDF417 & CODABLOCKF due to height/scale rounding by changing
out_large_bar_height() to return scaled int values for raster,
props codemonkey82 (#204)
raster/vector.c: const some vars
vector.c: rect_count, last_start_row UPC/EAN only
library.c: check for stacking symbols >= 200
add specify rows option (option_3) (#204);
warn if cols increased from specified (back-incompatible);
move table definitions from "pdf417.h" to new "pdf417_tabs.h" and
make INTERNAL_DATA and share with composite.c (saves ~10K);
prefix routines and tables with "pdf_";
some small performance improvements through if/elses, pdf_textprocess()
& pdf_numbprocess() loop simplifications
MICROQR: fix debug access crash on printing non-NUL-terminating binary
DATAMATRIX: fix missing ++ from "[tp]" at C40/TEXT EOD processing of GS1
(though probably never reached); use "[tp++]" throughout
Add const to static tables missing it and also to some variables
Change "debug" -> "debug_print" throughout
