
Hello, I'm not sure if posting to dev is the right place, but considering it's not a localization specific problem. So, I want to add some fields in the CustomerLogin.tdl to categorize clients after account create. But if I use for example: <select name="X"> <option value="X">Czech language chars ěščřžýáíé</option> </select> Then the "combobox" display garbage in the language specific characters. But complete OTRS system play fine with Czech translation, emails and so. I have a DefaultCharset utf-8 in Config.pm. I try to save edited DTL in ISO8859-2 and UTF-8, but have no luck. FreeBSD 5.4 Apache 2.0.54 MySQL 4.1.11 Perl 5.8.6 OTRS 2.0.4 as CGI (will switch to mod_ after testing) -- Vladimir Benc PS: Sorry for possible bad English, not my native lang.

Hi Vladimir, On Fr, Aug 11, 2006 at 11:06:46 +0200, Vladimír Benc wrote:
I'm not sure if posting to dev is the right place, but considering it's not a localization specific problem.
So, I want to add some fields in the CustomerLogin.tdl to categorize clients after account create. But if I use for example:
<select name="X"> <option value="X">Czech language chars ?????ýáíé</option> </select>
Then the "combobox" display garbage in the language specific characters. But complete OTRS system play fine with Czech translation, emails and so.
I have a DefaultCharset utf-8 in Config.pm. I try to save edited DTL in ISO8859-2 and UTF-8, but have no luck.
Saving the file in utf-8 should work. You should see also the correct letters in an editor that supports utf-8. Regards, Christian -- ((otrs)) :: OTRS GmbH :: Europaring 4 :: D - 94315 Straubing Fon: +49 (0) 9421 1862 760 :: Fax: +49 (0) 9421 1862 769 http://www.otrs.com/ :: Communication with success!

On Mon, 14 Aug 2006 15:50:10 +0200
Christian Schoepplein
Then the "combobox" display garbage in the language specific characters. But complete OTRS system play fine with Czech translation, emails and so.
I have a DefaultCharset utf-8 in Config.pm. I try to save edited DTL in ISO8859-2 and UTF-8, but have no luck.
Saving the file in utf-8 should work. You should see also the correct letters in an editor that supports utf-8.
Yes, I've saving in utf-8 and I see correct letters in editor (Bluefish but this doesn't matter). The tricky thing is that if I save the desired text values in translation file (Kernel/Language/cz.pm) and use a e.g. $Text{"USR_COMPANY1"} in the DTL file, then the utf-8 characters are displayed correctly. I use this workaround now. But this point me that the encoding problem is in "parsing" the DTL template. Seems the core DTL is internaly parsed as ISO8859-1(5) and then broke the multibyte chars into two singlebyte and then the encoding "back" to utf-8 doesn't work.
Regards,
Christian Thank's for reply, Vladimir Benc
participants (2)
-
Christian Schoepplein
-
Vladimír Benc