Hello,
I have a specific problem with GS1 barcode type. One of our customers wants to print GS1 barcodes, but in some cases the output is not OK. We are using Aspose.Barcode library version 6.4.0.0. I cannot upgrade to the latest version because our subscription lasts only until August 2014.
I did the test with the following value:
(02)07610848242406(37)1000(400)7023596184
The Aspose.Barcode.dll library from July this year produces an image which is different from the one that was sent to us from the GS1 department in Switzerland (http://www.gs1.ch/). I attached both images. Do you have an idea why they are different? Or am I doing something wrong with Aspose library? Here is my source code:
var barCodeControl1 = new BarCodeBuilder();
barCodeControl1.SymbologyType = Symbology.GS1Code128;
barCodeControl1.CodeText = "(02)07610848242406(37)1000(400)7023596184";
barCodeControl1.Save(@"C:\work\backup\barcode_not_ok.bmp", ImageFormat.Bmp);
There is also a freeware online barcode generator which is producing the same result as the one suggested by the GS1 Switzerland:
http://generator.onbarcode.com/online-gs1-128-barcode-generator.aspx
Do you have any idea what might be the problem? Thank you in advance for your help.
Oliver
Hi Oliver,
Thank you for contacting support. First off, please note that each new release contains many improvements, bug fixes and new features. So we always recommend our customers use the latest version of Aspose APIs. We don’t provide fixes in the old code base.
Based on your inquiry, we have tested your given code text against the latest build of Aspose.BarCode for .NET 6.5.0. We can generate and recognize GS1Code128 code using your sample code text. However, we can notice printed GS1Code128 bars pattern and widths are not same as of GS1 department in Switzerland. We have logged an investigation under ticket id BARCODENET-34021 in our issue tracking system. Your request has also been linked to this issue. We’ll keep you informed regarding any available updates. We’re sorry for the inconvenience caused.
Hello,
thank you for the answer. Do you have a rough estimation when this issue might be solved? Our customer is waiting for a solution and of course we would like to fix the problem as soon as possible. Thank you in advance,
Oliver
Hi Oliver,
Thank you for asking about the update. Our development team is in-progress to fix the defect. We have asked our development team to share more details. We’ll let you know once an update is available. Please spare us a little time.
Hi Oliver,
Thank you for being patient. We have received a response from our development team. The issue id BARCODENET-34021 has been marked as resolved and will be included in the next release of Aspose.BarCode for .NET 6.6.0. It is expected in a couple of days.
Hi Imran,
thank you for the answer, I am glad that your team was able to fix the problem.
Boris
Hi Boris,
Thank you for the precious feedback. Please feel free to post any other query about Aspose APIs, in which you require our assistance.
The issues you have found earlier (filed as BARCODENET-34021) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
Hello once again,
we tested the latest patch which should resolve the BARCODENET-34021 ticket. I can confirm that it indeed works with that example, but there is another case which is still wrong. Here are the links to the correct image files and their values:
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_ok_01.png
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_ok_01_value.txt
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_ok_02.png
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_ok_02_value.txt
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_ok_03.png
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_ok_03_value.txt
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_ok_04.png
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_ok_04_value.txt
The Swiss GS1 department is telling us that all these samples are valid and they meet the needs of our customer. They were generated the following online GS1 barcode generator:
http://generator.onbarcode.com/online-gs1-128-barcode-generator.aspx
With your latest patch I am able to produce exactly the same results in cases 2, 3 and 4. Only the case 1 is problematic, here is a graphical comparison:
https://dl.dropboxusercontent.com/u/4022229/barcode_samples/barcode_01_comparison.png
The lower barcode was produced with Aspose, the upper with the online generator. As you can see there is a slight difference somewhere in the middle of the barcode. Can you please have a look at this detail and fix it? Thank you in advance,
Oliver
Hi Oliver,
Thank you for your inquiry. We’re working over your query and will get back to you soon.
Hi Oliver,
Thank you for being patient. We managed to replicate the said issue. We would like to clarify that this is not the real problem, because GS1Code128 can be encoded in different ways. However, we have logged your scenario under ticket id BARCODENET-34030 in our issue tracking system. Your post has also been linked to this issue. We’ll keep you informed regarding any available updates. We’re sorry for the inconvenience caused.
Hello,
is there any news related to this issue? Maybe you are right about the fact that the GS1Code128 barcode can be encoded in different ways, but our customer is still complaining that your output is not correct. I guess he is right. Do you have any news from the development team - if they are working on the problem and how long would it take to fix it? Our customer is waiting for a solution. Thanks,
Oliver
Hi Oliver,
Thank you for being patient. Our development team has fixed the issue id BARCODENET-34030. We’ve attached its output barcode image for your reference. Please take a look and let us know your feedback if any.
The issues you have found earlier (filed as BARCODENET-34030) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.