Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

BARCODES 128 ENCODING PROBLEM

487602Feb 2 2006
We are using IDAutomation tools in order to print barcodes in our forms.
We are using the IDautomation barcode font and the special PLL for reports developer.
The system we are using is Oracle 11.5.10.2 and UTF8 as our NLS_LANG.

The problem is that we need BARCODE 128 standard for the reports which means that there is an encoding function which we sent a string to and it prints an encoded barcode string as an output.

When I try to run the report locally on my computer which uses
NLS_LANG="AMERICAN_AMERICA.IW8MSWIN1255" it runs ok and when i try to use the print layout in reports developer it bring the correct barcode.
But, when I try to run the report from the application in the server, the barcode prints invalid.
After some investigations we found:
a. the fonts are installed correctly.
b. the encoding function of the 128 barcode brings different results when run on UTF8 and on AMERICAN_AMERICA.IW8MSWIN1255.

It seems that the problem is not with the barcodes font rather than with the
function that calculates and encodes the 128 barcode.
The same function bring different output when is it running locally and when is
running on the server. The function we are running is the standare one taken
from the IDAutomation PLL for oracle applications and report developer.
Since it is a common PLL used by most of the companies, we think it is a
problem related to the NLS_LANG we are running.
I tried to change the string output of the function and find the ASCII

characters it outputs.
When trying to encode into barcode the string "1234567890" it brings locally
the output:
chr(205)chr(205)chr(44)chr(66)chr(88)chr(110)chr(122)chr(117)chr(206). This is

the right output which was supposed to be.
Butm, when trying to run the encoding function on the server with the UTF-8
NLS_LANG it brings the following INVALID

output:chr(44)chr(44)chr(66)chr(88)chr(110)chr(122)chr(68)
My guess is that some of the ASCII characters in the right output are not
supported in the UTF8 NLS_LANG environment.

Thanks alot,
Please advise
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 2 2006
Added on Feb 2 2006
0 comments
654 views