Charset issue in dropdown

[GMunjal]

Hi,
We implement OTRS and we are using external data source to show data in dropdown.

How we implement : we create a file extdata.pl in bin . on browsing this file it shows content as

Code: Select all

<option value="IKO999-99">IKO999-99 Dummy [b]für [/b]EA-Verwaltung (ohne Abrechnung)</option>

Check the für above, which is shown in correct way.

Issue : Now the issue is, when we bind these external data source values with dropdown, the same value will change as shown in attached image(Please find attached image).

Please provide the inputs that how can we show the correct values in dropdown.

[reneeb]

Does your script send the data as utf-8?

[GMunjal]

We tried to open execute the script first in SQL...in SQL it work right.

Then we tried to execute the http://1.1.2.2/otrs/extdata.pl in chrome browser, but in browser it shows us the same issue.

But if we execute the http://1.1.2.2/otrs/extdata.pl in Iternet explorer and save the file, and then open it using text file, in Text file it shows the right results.

So overall - If we check in browser it shows wrong result.
But if we open in using notepad, is shows right result.

any inputs to correct this ?

[reneeb]

Does your script send the data as utf-8?

again...

[GMunjal]

No

[reneeb]

Then you should change that... OTRS output is utf-8 encoded, so you should do that, too.

[GMunjal]

Hi,

We change the script, now our script output data as UTF-8. below is the output of script attached

Output in DB :

DBOut.png

Output of extdata.pl :

fileOut.png

Issue -

But when we bind this file on UI, it looks like as below in dropdown :

dropOut.png

So can you please update us, where is the issue that on GUI the format is not correct seen ?
Also let us know if more description required...

[jojo]

I eally doubt that it has the correct format.

[GMunjal]

One more input to describe the issue:

If I execute the extdata.pl in IE, It popups for save the JSON file. that JSON file shows us the correct format.

But if we execute the extdata.pl in chromeBrowser than it will show us the wrong format as it shows us in dropdown.

I check in SQL server from where we get the data , the collation type is Latin1_General_CI_AS in SQL.

Below is the snapshot of extdata.pl. May be it will help you to get some more information for this issue.

extdata.pl.png

[GMunjal]

Any updates on the above issues ?????

[jojo]

your databse has the wrong charset. If you require commercial support you should consider buying it

[reneeb]

Your "SourceCharset" attribute has no effects. Kernel::System::DB doesn't know anything about that attribute. So you have to write your own layer like Kernel::System::CustomerUser::DB where the encoding/decoding is done. And in that layer you have to use the encoding names the Perl module Encode (http://metapcan.org/pod/Encode) supports.

[cryptoroot]

I know this thread is old, but recently I have resolved this problem doing a little change in the example of extdata.pl.

Code: Select all

use strict;
use warnings;
#Add Encode
use Encode; 

use CGI qw(:standard);
#use JSON; #install JSON via cpan/ppm if you want to use it instead

#Add to the print header -charset => 'utf-8'
print header(-type => 'application/json', -charset => 'utf-8');

The problem is the original code didn't specify the charset. although db has the correct setting