-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discrepancies between this encoder's output and others #2
Comments
Ah, just found this: https://github.com/toretore/semacode/blob/master/ext/semacode.c#L57 Which doesn't entirely account for every difference I'm seeing, but it does seem to give a clear indication that this code is not fit for real world usage. |
Yeah, I'm not sure that the semacode gem is working 100%.. This has already been touched upon here: But as I wrote there, I don't know how to fix it myself, and I don't know of any alternatives to semacode.. |
This seems to be it, and it requires a separate library installation, which makes deployment unnecessarily difficult: |
I don't think that's a big problem.. It's better than something that On Mon, Feb 24, 2014 at 11:51 PM, nathan-munchery
|
This is old news but I came here for the same reason. https://github.com/srijan/ruby-dmtx seems to work a lot better but it unfortunately requires imagemagick and libdmtx. |
I can't quite tell if anyone responsible for the underlying implementation is in any way involved with this particular copy of it, but on the off chance that they are...
I'm using this library along with Barby, and am noticing some big differences between the codes they generate and every other encoder I can find out there. As an example, given the magic initialization string for the scanner I happen to be working with
#FNC IOS ACCEPTOR 000000000000#
results in the output at the left everywhere, while Barby + Semacode spit out something much, much larger as seen here:Is there anything I can or should be doing to influence the output here?
The text was updated successfully, but these errors were encountered: