Re: Turkish translation; encoding problem

Martin Edenhofer <[email protected]>
Newsgroups gmane.comp.otrs.internationalization
Message-ID <[email protected]>
Hi Necmettin,

that's cool. It's working fine for me. :)

If the file encoding is utf8, you only need to use utf8 in the charset  
definding:

  #  $Self->{Charset} = [ 'utf8', 'iso-8859-9', ];
     $Self->{Charset} = [ 'utf8' ];

Remove the iso-x and it will work fine (I hope, the only turkish word  
I know is "arkadas" :) )!

See also http://users.otrs.com/~me/tr.png

PS: Can we put it into upcoming OTRS 2.2.6?

Many thanks for feedback! :)

  -Martin

-- 
((otrs)) :: OTRS AG :: Europaring 4 :: D - 94315 Straubing
   Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18
     http://www.otrs.com/ :: Communication with success!

Address of record: Bad Homburg
Local Court: Bad Homburg, HRB 10751
Tax number: 003/240/97505

Chairman: Burchard Steinbild
Chief Executive Officer: André Mindermann

On Mar 13, 2008, at 15:36 , Necmettin Begiter wrote:

> Haven't seen any activity in this mailing list since maybe months, but
> I'll give it a try.
>
> I have finished translating the main file (Kernel/Language/x.pm), read
> in the manuals to send it here, so attached it is.
>
> But we have a problem with OTRS's interface, I have used UTF-8 in
> translating the file, so (I suppose) that should make the strings in
> the interface display correctly, but they don't. No matter what
> encoding we choose, we can't get the characters specific to Turkish
> (like 'ş', 'ğ') display correctly. Searched the archives, but no  
> luck
> of finding a solution to this issue. System locale is tr-TR.UTF-8. Any
> ideas on what might be wrong, what can be done about it?
> <tr.pm.zip>_______________________________________________
> OTRS mailing list: i18n
> Archiv: http://lists.otrs.org/cgi-bin/listinfo/i18n

_______________________________________________
OTRS mailing list: i18n 
Archiv: http://lists.otrs.org/cgi-bin/listinfo/i18n
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.