mirror of
https://github.com/zint/zint
synced 2024-11-16 20:57:25 +13:00
5e2044ff2e
encodation in certain cases (and no pessimizations found so far), props lyngklip (BWIPP); fix extended char latching when exactly 3 extended chars at end; count code set C (not digits) in loop deciding when to shift/latch to extended for better estimate AZTEC: return warning if ECC < 5% (due to bit-stuffing when version given); return error if > 22 layers (Zint 26) for Reader Initialisation symbol requested for better error message AZTEC/HANXIN/QRCODE: consolidate different ECC data size tables into one indexed by ECC DBAR_EXP: check for reduced length <= 77 up front for better error message HANXIN: use `malloc()` rather than `z_alloca()` for large binary array QRCODE: `ecc_level` now 0-based (not 1-based) MICROQR: consolidate different version end routines into one `microqr_end()` and use new `microqr_data` table to simplify code MICROPDF417: use table for max codewords per column library: centralize all error messages using new `errtxt()`, `errtxtf()`, `errtxt_adj()` funcs that protect `symbol->errtxt` from overflow, & try to make error messages more consistent thru-out, adding more feedback info to many, & use positional args "%n$" in prep for l10n (maybe); `is_sane/is_sane_lookup()` -> `not_sane/not_sane_lookup()`, returning 1-based position (zero on failure) instead of bool; `long` ints -> plain `int` (except those dealing with `ftell()`, `fread()` etc) as depend on int being 32-bits already GUI: in "grpDATF.ui" use "PlainText" rather than "RichText" for tracker ratio examples as height of text messing up sometimes manual: clarify Codablock-F length maximum & add examples docs: README: pandoc 3.5, Ubuntu 24.04 CMake: use "-Wpedantic" for Clang only as GNU complains about `errtxtf()` positional args "%n$" |
||
---|---|---|
.. | ||
cmake/Modules | ||
CMakeLists.txt | ||
README | ||
test_args.c |
% frontend/tests/README 2024-01-12 Zint frontend test suite ------------------------ See <project-dir>/backend/tests/README to see how to build the test suite. In addition to the setup for the backend tests, the environment needs to be able to find the `zint` application using that name. In UNIX-like systems this can be configured by prepending the PATH variable with the frontend's directory inside the build directory: cd <build-dir> export PATH=$(pwd)/frontend:${PATH} ------------------------------------------------------------------------------ the frontend test will be automatically run by cmake's ctest, however manual invocation is also possible: cd <build-dir>/frontend/test ./test_args As with the backend tests, individual test functions and single dataset items can be run using '-f <func-name>' and '-i <index>' etc.