mirror of
https://github.com/zint/zint
synced 2024-11-16 20:57:25 +13:00
624d40021e
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) |
||
---|---|---|
.. | ||
cmake/Modules | ||
CMakeLists.txt | ||
README | ||
test_args.c |
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.