Please close - not a zint issue. (Good lesson for anyone testing barcodes - try multiple scanners) Thanks
WOW....so I was using "QR Code Scanner" for android which decodes the number with prefix "CR" . So I tried using "Barcode Scanner" for android it it decodes the number with prefix "M". Any chance the ascii value is 13 which is control-M, or interpreted character "CR" (carriage return). Just looking for how a scanner can make such an obvious mistake. I suppose this underscores the importance of using a good scanner! (Staying on topic). Thanks for finding that!
I actually opened a ticket, but on Git Hub. I wasn't sure if one/both sites are used for bug tracking. I didn't want to double post in case that annoyed someone. It would be great to find a good android scanner (since I sometimes scan a user's badge at remote site). I tried 3 different Android scanners and they're OK, but don't show developer level details.
I realize that :) In order to diagnose what I think is a Zint problem (with PDF417) I need a barcode reader that shows a lot of detail (most just decode and show the symbology and maybe compaction mode). I'm hoping someone in this project can recommend a great decoder...
Just to clarify, content type is actually "compaction mode", and check digits is ECC. Trying to use the right words :)
Android app to fully decode PDF417 or other barcodes
I can't seem to reproduce the problem at will. Once in a while I just see the output barcode of all zero's, and my program log does suggests all steps executed without error. If I can figure out how to reproduce I'll post more info. For now, maybe this post will just help someone else who experiences the same symptom
Barcode string all zero's