nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

callServer perl and UTF-8

vahu

Hi,
Scenario:
We have a DCT that uses FormAPI to call an *.ipl script. The script then uses TeamSite::XMLnode to read values from a DCR. The issue here is that the DCR's contain Danish characters (æ, ø , å) and when used in perl the values extracted looks as follows:
VaHu Test µ°σ (= print "VaHu Test æøå")
VaHu Test ├ª├╕├Ñ (= value extracted from the DCR)
VaHu Test ├â┬ª├â┬╕├â┬Ñ (= UTF-16 encoded in the script)
VaHu Test ├ª├╕├Ñ (= TeamSite::I18N_utils::utf8_to_other_encoding("UTF-8", "VaHu Test æøå");
VaHu Test ├ª├╕├Ñ (= encoded using Unicode::Map and String).

The above encoded values as you can see get translated ?. Look at the attached file to view the variable values.
The weird thing is that I made a testing script which reads a file containing the text ("VaHu Test æøå"). The script when holding the $line writes it to a txt file and the values in that file are correct. The script is attached as well ( copy it out of the txt file and change the output file and utf.txt path).

Does any have experience with this. How do I get perl to properly encode (decode ???) the values. I need to set these values on the DCR that invoked the script, so that the user sees (æøå).
I am working on a short deadline, so any help will be greatly appreciated.

Find more posts tagged with

Comments

Xilu

I also found this problem when I read a DCR that contains French character, which I need to populate by inline.

I would like to know if you have found any solution, thanks.

marcussteiner

same here. I have a selectbox in the dcr which is displaying german characters. When I do my callserver to a perl script there is only weird stuff arriving there. Is there a setting for this?

m

kaalraa

Usage of

 [CDATA[SpecialChars]]

might help. Has to use in a bit tricky way.

Please add angle braces as per the CDATA syntax.

same here. I have a selectbox in the dcr which is displaying german characters. When I do my callserver to a perl script there is only weird stuff arriving there. Is there a setting for this?

m

marcussteiner

thanks for that. but it doesnt seem to like the syntax and I could not find anything in either the docs nor the devnet. is
[CDATA[SpecialChars
more formapi
]]

or
[CDATA[[SpecialChars]
more formapi
]]

neither of those worked.

m

ravio

same here. I have a selectbox in the dcr which is displaying german characters. When I do my callserver to a perl script there is only weird stuff arriving there. Is there a setting for this?

m

How are you transcoding your data?
are you using TeamSite::I18N_utils, TeamSite::Uniscape?

Johnny

The best way to make sure you can read utf-8 now that we use PERL 5.8 is to have this at the top of your script

use open ':utf8';

That will make newly opened file handles default to utf8 encoding.

Also - to fix the the three standard file handles do this

binmode (STDOUT, ':utf8');
binmode (STDIN, ':utf8');
binmode (STDERR, ':utf8');

That's important if you're using teamsite command line tools - most CLT's work with utf-8 encoding but PERL defaults to iso..... for standard in/out etc.

We actually had this in a common module so that we could reuse it, but later learnt that use open ':utf8'; did not import into the current namespace - any ideas?

By the way - we use TeamSite: Smiley Very Happy

CRnode without any problems - works well.

marcussteiner

thanks for all your help. but it's still not working. In the dct everything is fine. I have a function in formapi which is taking some argument and one of them is in german umlaute var test="Töne"; e.g. Then I do a alert(test); and the output is fine. Then I create a new params Object (var params = new Object Smiley Wink

and assign the variable to the Object (params.filter=test Smiley Wink

Then I ran a IWDatacapture.callServer("http://localhost:8081/iw-bin/filename.ipl", params, true);

When I get to filename.ipl I create a new CGI object and take the parameters (my $var = $in-> ('filter') Smiley Wink

. But I also open a configurationfile also with umlauten und print both params and the input from the configurationfile into another logfile and just the stuff from the callserver is messed up. The stuff from the configurationfile is fine.

Is there a setting in the httpd.conf which I need to set? There is a AddCharset UTF-8 .utf8 setting.

m

Johnny

Did you put this at the top of your script before doing anything else (including using the CGI module)?

use open ':utf8';
binmode (STDOUT, ':utf8');
binmode (STDIN, ':utf8');
binmode (STDERR, ':utf8');

marcussteiner

yep

#!E:\iw-home/iw-perl/bin/perl
use open ':utf8';
binmode (STDOUT, ':utf8');
binmode (STDIN, ':utf8');
binmode (STDERR, ':utf8');

use TeamSite::Config;
use File::Copy;
use CGI;
use TeamSite: Smiley Very Happy

CRnode;
use strict;

$| = 1;

Johnny

Sorry I couldn't help - I guess you're right - it's not the PERL script itself, could be the webserver.

neeraj_forever

Have you got the solution for this?
Please help to find out the solution as i m facing the same problem.

Thanks
Neeraj