Closed neemevool closed 9 months ago
@neemevool : i will merge this. is this the only changes you need for your code to work? changes may come in the future, but don't expect them to be breaking to an application.
Yes, thats it so far. I get with these changes lot of ancient barcodes working with scanners. Thank you a lot!
@neemevool : 0.1.3-preview2 is online on nuget so you can already integrate it into your application. im just going to cleanup code and make an official 0.1.3 release
Created in separate namespace CODE128. Although GS1128 is based technically on Code128, not all GS1 barcodes derive from Code128. This is according to what we discussed.
Modified AimParser to handle ]C0 exclusively by Code128 and not try to apply others.
There is one thing which is significant. Code39 and Code128 parsers do not parse the barcode without explicit symbology prefix, because when it is not explicitly known it would cause too much abiguity. Basically any ASCII string sequence would be Code39 and any extended ASCII string would be Code128. I see there is possibility to assign order to the parsers, but it would still be too fragile to let Code39 or Code128 parsers handle any string.
I did not modify README, but maybe at some day you would mention Code39 and Code128 there too.
Sorry for mess with the second commit. I pushed it without amend and I cannot see how I can stash them on github anymore. It was just temporary add to troubleshoot one problem.