Closed terryburton closed 1 year ago
@gitlost Hi. From now on, anything that causes the PS interpreter to fail without calling the BWIPP raiseerror
routine should be considered to be a bug.
Hi, thanks, just a few things I noticed on running the Zint tests with BWIPP enabled:
msi
, the check when badmod11
is set should allow any checktype
that contains a mod11
I think, i.e. mod11
or ncrmod11
or mod1110
or ncrmod1110
code49
, the option concat
clashes with the built-in concat
operator - maybe rename to append
?pdf417
, the check of eclevel
should be from 0 to 8, not 1 to 5datamatrix
, the doly
/dmre
logic needs to be done in the second metrics
loop alsoIf you like, I can do PRs for these....
- in
msi
, the check whenbadmod11
is set should allow anychecktype
that contains amod11
I think, i.e.mod11
orncrmod11
ormod1110
orncrmod1110
I think you're right.
- in
code49
, the optionconcat
clashes with the built-inconcat
operator - maybe rename toappend
?
Agreed. Note the workaround I put in BWIPP for this, but I agree we should rename it to append
if it causes trouble downstream.
- in
pdf417
, the check ofeclevel
should be from 0 to 8, not 1 to 5
Doh.
- in
datamatrix
, thedoly
/dmre
logic needs to be done in the secondmetrics
loop alsoIf you like, I can do PRs for these....
That would be excellent, thank you.
Cool, will do.
Add proper input validation with detailed error messages to all symbologies: