Git Lost

Hi, yes it would be possible to restore the previous algorithm behind FAST_MODE - it was mainly removed to reduce code length; also it was hard to reason about. It may be a while though before it's restored. Could you give an example (or two) that's affected? Regards, Martin

- MAXICODE: do not span segments when counting digits/alphas even

Hi Andre, interesting one, the small amount of data means that the GS1 Databar Expanded Stacked barcode hasn't enough data for 2 rows, so "demotes" to a single row, which is the same as a GS1 Databar Expanded barcode. (BWIPP does the same). To answer your questions: 1) Depends on one's definition of "valid". Without getting too philosophical I would say it's a valid GS1 Databar Expanded barcode (not Stacked) as I don't see any requirement for GS1 General Specifications conformance in the standard,...

Hi Andre, interesting one, the small amount of data means that the GS1 Databar Expanded Stacked barcode hasn't enough data for 2 rows, so "demotes" to a single row, which is the same as a GS1 Databar Expanded barcode. (BWIPP does the same). To answer your questions: Depends on one's definition of "valid". Without getting too philosophical I would say it's a valid GS1 Databar Expanded barcode (not Stacked) as I don't see any requirement for GS1 General Specifications conformance in the standard, although...

Thanks Andre, that should be fixed with commits [edaa21] & [4aec8d] (no validation was being done on warn_level - it now resets it silently to WARN_DEFAULT if invalid), best regards, Martin

library: fix `warn_level` check from last commit

composite: validate `warn_level` using new `WARN_LEVEL_MASK` mask,

pandoc: latest