You have changed different squirrelmail install or RH changed something in squirrelmail i18n. Your changes should have set US English translation to utf-8 charset. Which charsets are used in your emails? iso-2022-jp, euc-jp, some other charset. Which extensions are supported by your php install? I need information about iconv and recode support. Which php version is used? Can you check if you can write in Japanese when Lithuanian or Russian translations are used. If lt_LT and ru_RU locales are not installed, interface will remain in English. Don't try to reply to other Japanese email. Only write in Japanese and check if others can read it. Can you create utf-8 encoded html page with all Kanji, Hirigana and Katakana characters and check if your browser displays them correctly?Message: 10 Date: Tue, 22 Mar 2005 20:51:22 +0200 (EET) Subject: Re: [SM-USERS] Sending Japanese Characters From: "Tomas Kuliavas" <[EMAIL PROTECTED]> To: [email protected]>
I am experiencing a problem sending Japanese characters from Squirrelmail using the English interface.
They end up in the users mailbox as テツ
if I send through my mail server via mail client like Thunderbird. The text is received correctly. Also if I send via Squirrel Mail with the Japanese interface the characters are printed correctly as well.
Is there a way to switch the encoding to something like UTF-8 so it will send Japanese from the English version of Squirrel Mail?
edit functions/i18n.php and set utf-8 charset for en_US translation in $languages array or check custom_charset plugin.
Tomas
-- __--__--
Tomas thanks for your suggestion but I that did not work for me... most of the text Kanji, Hirigana and Katakana is moji baki (unreadable) regardless of what I change the en_US encoding to. I have tried utf-8 and ja-utf-8 (saw this in phpmyadmin). Also I noticed what ever I changed the encoding to this is what appeared in the header <snip> User-Agent: SquirrelMail/1.4.4-1.FC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit <snip>
I changed these lines in i18n.php <code> $languages['en_US']['NAME'] = 'English'; $languages['en_US']['CHARSET'] = 'utf-8'; $languages['en_US']['LOCALE'] = 'en_US.utf-8'; $languages['en']['ALIAS'] = 'en_US'; </code> Was I changing the wrong lines or is there something else I need to change? My problem is I have a number of bi-lingual users who's first language is English but have to communicate with customers in Japanese they would rather see a English interface even though they read/write Japanese. Thanks Again, Erin
-- Tomas
Tomas-
First let me apologize for the delay in my response I was dragged away to work on a Windows project for a week or so.
PHP Version php-4.3.10-2.4
I am sorry I do not know what you mean by iconv and recode I searched for them on my system and in a the code sent back from my php info page and did not see them.
I sent a mail from the Lithuanian interface of my Squirrelmail and it appears fine like and uses UTF-8 here is the header:
User-Agent: SquirrelMail/1.4.4-1.FC2 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on localhost X-Virus-Status: Clean
When I tried to change the English to UTF-8 it gives me broken text again. It is still including this header which has charset=iso-8859-1. If I manually change the encoding to UTF-8 in the users mail program and the text appears correctly in (Thunderbird or OE) (After it is sent from SquirrelMail)
User-Agent: SquirrelMail/1.4.4-1.FC2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: ClamAV version 0.83, clamav-milter version 0.83 on localhost
X-Virus-Status: Clean
Status:
æ
ãããã
ããã
æåæ
ããããããããããã
I can create UTF-8 pages and post them on the server and they read correctly.
Japanese mail is ussually encoded in iso-2022-jp and that will handle all Kanji, Hirigana, and Katakana.
But UTF-8 will work for most everything as well.
2 points of interest ***I am sure others know this file much better than I do but here goes***
I found this in while searching for en_US
// Catch removed translation
if (!isset($languages[$my_language])) {
$my_language="en_US";
}
while (isset($languages[$my_language]['ALIAS'])) {
$my_language = $languages[$my_language]['ALIAS'];
}
$my_charset = $languages[$my_language]['CHARSET'];
if ($my_language!='en_US') {
$default_charset = $my_charset;And I also note there was a extra line associated with Japanese XTRA_CODE
$languages['ja_JP']['NAME'] = 'Japanese'; $languages['ja_JP']['CHARSET'] = 'iso-2022-jp'; $languages['ja_JP']['XTRA_CODE'] = 'japanese_charset_xtra'; $languages['ja']['ALIAS'] = 'ja_JP';
Does anyone have any other thoughts on this?
Thanks for your help, Erin
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click -- squirrelmail-users mailing list Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines List Address: [email protected] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id)95 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
