Hi Shawn, Well, I've checked the Config.pm on a development machine I have, and it's using UTF-8 for DBMS writes. As for the live system, having had checked the Config.pm on there, there is no line specifying a character encoding which strikes me as somewhat weird. However, this live system works fine with English, Japanese, Russian, Chinese, Korean and other such languages.
Having had then updated the 2.1.4 Config.pm to explicitly use utf-8 no problems were encountered from viewing the ticket under 2.1.4. The problems persisted on 2.2.6 though. (2.2.6 has read access to the live system DB, but can't write to it). If 2.2.6 won't be able to read any standard answers, old tickets or any other information (this includes usernames) from our usage via 2.1.4, this proves problematic. - Muz >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of >Shawn Beasley >Sent: 09 April 2008 15:39 >To: User questions and discussions about OTRS.org >Subject: Re: [otrs] Upgrading from 2.1.4 to 2.2.6 seems to havebroken >charencoding > >Hi Mustaqil, >> >> I’d love to hear any feedback on this issue if anyone has any, given >> that I’ve experienced the same issue. >> >> >> >> I’m currently still running 2.1.4 and not updating as this bug makes >> it impossible for us to the OTRS for all of our non-English support. >> >> >> >> Thanks in advance. >> >> >> >> *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On >> Behalf Of *Hiren Joshi >> *Sent:* 03 April 2008 12:54 >> *To:* [email protected] >> *Subject:* [otrs] Upgrading from 2.1.4 to 2.2.6 seems to have broken >> charencoding >> >> >> >> Before: >> >> mysql database (in latin1) shows: Réponse Automatisée >> >> OTRS webpage shows: Réponse Automatisée >> >> >> >> After Upgrade: >> >> mysql database (in latin1) shows: Réponse Automatisée >> >> OTRS webpage shows: Réponse Automatisée >> >> >> >> Any thoughts? >> >> I noticed en.pm was not updated but I tried en.pm.rpmnew as well. >> >> >> >> Thanks. >> >Did you check the Charset default in Kernel/Config.pm to verify it is >using the correct Charset for writing to your DBMS, after the upgrade? >Alternatively it could be configured in your Sysconfig. > >((enjoy)) > >-- >Shawn Beasley >((otrs)) :: OTRS AG :: Norsk-Data-Straße 1 :: 61352 Bad Homburg > Fon: +49 (0) 9421 56818 0 :: Fax: +49 (0) 9421 56818 18 > http://www.otrs.com/ :: Communication with success! > > >Geschäftssitz: Bad Homburg >Amtsgericht Bad Homburg, HRB 10751 >Steuernummer: 003/240/97521 > >Aufsichtsratsvorsitzender: Burchard Steinbild >Vorstandsvorsitzender: André Mindermann >
_______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support or consulting for your OTRS system? => http://www.otrs.com/
