maxicode uszeropad

[gitlost]

• code128: Avoid extraneous CodeC switch Avoid extraneous CodeC switch (with immediate switch back to CodeA/B) by re-checking digit runlength >= 4 after enca/encb push
• maxicode: Zero-pad US postcodes that lack "+4" (Annex B.1.4a) Adapted from OkapiBarcode, with stricter interpretation (only pad if "+4" totally absent), props Daniel Gredler

[terryburton]

@gitlost Was this closed in error, or are you reworking it?

[gitlost]

My local master was out of sync so just fixed it up (I think) and pushed again!

…

On Wed, Oct 9, 2024 at 5:53 PM Terry Burton ***@***.***> wrote: @gitlost <https://github.com/gitlost> Was this closed in error, or are you reworking it? — Reply to this email directly, view it on GitHub <#273 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADVVPTS7DKTBFAR5LIDXUTZ2VNO5AVCNFSM6AAAAABPU6AGNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBSHAZTGMRVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[terryburton]

Thanks!

I'm not sure whether you spotted the opportunities for further optimisation of Code 128 in #272

If you start to look then just let me know. Otherwise I'll poke it next week when I'm at the WG1 meeting in London.

[gitlost]

I hadn't no, just checked them out now.

Good cases, zint fails on the 1st one (FNC4), same as bwipp, as both use 5 chars as the non-terminal cut-off. A simple fix for that could be lower the cut-off to 4 - will check it out.

zint passes the 2 middle cases which bwipp fails, and both pass the last one.

Will have a look and let you know if I make headway (hopefully avoiding the usual whack-a-mole issues).