Non printable characters in PDF417
Non printable characters in PDF417
We need to be able to encode non-printable characters in the 2D barcode type PDF417.
In my query I insert the on-printable characters and data into 1 field and then I use this field for the barcode data. The problem is that the non printable characters like ASCII decimal 02, 03, 26 and 31 are converted to ; symbol in the barcode.
Is there a function in Stimulsoft that can be used to have those non-printable characters in the PDF417 barcode?
In my query I insert the on-printable characters and data into 1 field and then I use this field for the barcode data. The problem is that the non printable characters like ASCII decimal 02, 03, 26 and 31 are converted to ; symbol in the barcode.
Is there a function in Stimulsoft that can be used to have those non-printable characters in the PDF417 barcode?
Re: Non printable characters in PDF417
Hello.
You could set the Encoding mode to Byte and use any ASCII symbol.
More information you could get from the Stimulsoft User Manual.
Thank you.
You could set the Encoding mode to Byte and use any ASCII symbol.
More information you could get from the Stimulsoft User Manual.
Thank you.
Re: Non printable characters in PDF417
Thanks for your reply Aleksey.
I have tried it and the non-printable characters are there but some characters are lost.
For example I have encoded a barcode with Tom Schleisman and when I scan the barcode I received the following (as you can see some letters are gone):
6
m hleian
TradShoweads
161 S.76thaneoodyr, Z 338niteStat
517008
ms@teadset
I have tried it and the non-printable characters are there but some characters are lost.
For example I have encoded a barcode with Tom Schleisman and when I scan the barcode I received the following (as you can see some letters are gone):
6
m hleian
TradShoweads
161 S.76thaneoodyr, Z 338niteStat
517008
ms@teadset
Re: Non printable characters in PDF417
Hello.
It seems that you use a wrong codepage.
Please, send us a report template which reproduces the issue.
Thank you.
It seems that you use a wrong codepage.
Please, send us a report template which reproduces the issue.
Thank you.
Re: Non printable characters in PDF417
Here is my report file with the 2D barcode encoding that I used.
Thanks for your help.
Thanks for your help.
- Attachments
-
- test1.mrt
- 2D PDF417 with non printable characters
- (257.95 KiB) Downloaded 441 times
Re: Non printable characters in PDF417
Hello.
As we see you use MySQL database. Usually data are stores not in ASCII encoding.
Unfortunately, we cannot reproduce the issue because there is no data for the report.
Please, send us a sample report template with one barcode and static text in it.
Thank you.
As we see you use MySQL database. Usually data are stores not in ASCII encoding.
Unfortunately, we cannot reproduce the issue because there is no data for the report.
Please, send us a sample report template with one barcode and static text in it.
Thank you.
Re: Non printable characters in PDF417
Here is a template with some static code in the 2D barcode including the non-printable characters.
- Attachments
-
- Test1.mrt
- (11.42 KiB) Downloaded 488 times
Re: Non printable characters in PDF417
Hello.
We have made an improvement.
Please, check our next prerelease build that will be available on May 22.
Thank you.
We have made an improvement.
Please, check our next prerelease build that will be available on May 22.
Thank you.
Re: Non printable characters in PDF417
Hi,
I have tried the latest prebuild version and the non-printable characters are now appearing in the 2D barcode when using Byte Encoding Mode except that the carriage returns and line feeds are lost.
I have tried the latest prebuild version and the non-printable characters are now appearing in the 2D barcode when using Byte Encoding Mode except that the carriage returns and line feeds are lost.
Re: Non printable characters in PDF417
Hello.
There was a little issue with carriage return and line feed.
We have made an improvement.
Please, check our next prerelease build.
Thank you.
There was a little issue with carriage return and line feed.
We have made an improvement.
Please, check our next prerelease build.
Thank you.