Problem of Traditional Chinese & Simplified Chinese with UTF8
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
Problem of Traditional Chinese & Simplified Chinese with UTF8
by Frankie Wong
::
Rate this Message:
Hi List,
After I changed functions/i18n.php as follows: $languages['zh_TW']['NAME'] = 'Chinese Trad'; $languages['zh_TW']['CHARSET'] = 'utf-8'; $languages['zh_TW']['LOCALE'] = 'zh_TW.UTF-8'; $languages['tw']['ALIAS'] = 'zh_TW'; $languages['zh_CN']['NAME'] = 'Chinese Simp'; $languages['zh_CN']['CHARSET'] = 'utf-8'; $languages['zh_CN']['LOCALE'] = 'zh_CN.UTF-8'; $languages['cn']['ALIAS'] = 'zh_CN'; All chinese characters can be converted and displayed with UTF-8 charset when I received email with big5 or gb2312 charset. However, when I forward and reply such an email, all original content resume original charset and can't be displayed well. Any idea? Best Regards, Frankie Wong ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ----- squirrelmail-i18n mailing list Posting guidelines: http://squirrelmail.org/postingguidelines Information about translations: http://squirrelmail.org/wiki/LanguageTranslation List address: squirrelmail-i18n@... List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n |
|
|
Re: Problem of Traditional Chinese & Simplified Chinese with UTF8
by Tomas Kuliavas
::
Rate this Message:
Used SquirrelMail version? Extra decoding library version? results of configtest.php iconv, recode and mbstring extension tests? PHP version and mbstring compilation options? type of chinese email? plain text or html? 8bit, quoted printable or base64? Can you provide sample email for testing? -- Tomas |
|
|
Re: Problem of Traditional Chinese & Simplified Chinese with UTF8
by Frankie Wong
::
Rate this Message:
sm version: 1.4.13
extra decode lib: 1.2 php: 5.1.4 with mbstring Actually, either big5 or gb2312 can be displayed when reply by sm-1.4.8-utf8. Because I am not good at PHP, I have no idea about how to amend 1.4.13 version to be fully support utf-8 even after taking a look to the squirrelmail-1.4.8.utf8-1.diff. I tried to follow the difference in 1.4.13 but it didn't work after testing by the plugin of test_charset that you sent me before. Charset turned from utf-8 to big5 if I selected traditional chinese language and to gb2312 if I selected simplified chinese language. Apparently, sm-1.4.13 doesn't convert original charset to utf-8 when reply or forward. It only converts original message when viewing it. Any hints or highlight about it? Frankie > > > Frankie-10 wrote: >> >> >> >> Hi List, >> >> After I changed functions/i18n.php as follows: >> >> $languages['zh_TW']['NAME'] = 'Chinese Trad'; >> $languages['zh_TW']['CHARSET'] = 'utf-8'; >> $languages['zh_TW']['LOCALE']= 'zh_TW.UTF-8'; >> $languages['tw']['ALIAS'] ='zh_TW'; >> >> $languages['zh_CN']['NAME'] = 'Chinese Simp'; >> $languages['zh_CN']['CHARSET'] = 'utf-8'; >> $languages['zh_CN']['LOCALE'] = 'zh_CN.UTF-8'; >> $languages['cn']['ALIAS'] = 'zh_CN'; >> >> All chinese characters can be converted and displayed with UTF-8 charset >> when I received >> email with big5 or gb2312 charset. However, when I forward and reply such >> an email, >> all original content resume original charset and can't be displayed well. >> Any >> idea? >> > > Used SquirrelMail version? > Extra decoding library version? > results of configtest.php iconv, recode and mbstring extension tests? > PHP version and mbstring compilation options? > type of chinese email? plain text or html? 8bit, quoted printable or base64? > Can you provide sample email for testing? > > -- > Tomas > -- > View this message in context: > http://www.nabble.com/Problem-of-Traditional-Chinese---Simplified-Chinese-with-UTF8-tp16011794p16012564.html > Sent from the squirrelmail-i18n mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ----- > squirrelmail-i18n mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > Information about translations: http://squirrelmail.org/wiki/LanguageTranslation > List address: squirrelmail-i18n@... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ----- squirrelmail-i18n mailing list Posting guidelines: http://squirrelmail.org/postingguidelines Information about translations: http://squirrelmail.org/wiki/LanguageTranslation List address: squirrelmail-i18n@... List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n |
|
|
Re: Problem of Traditional Chinese & Simplified Chinese with UTF8
by Tomas Kuliavas
::
Rate this Message:
Can you show your "diff -uwrN squirrelmail-1.4.13.orig squirrelmail-1.4.13 > squirrelmail-1.4.13.diff". If translation is switched to utf-8 the way you said, charset conversion is working. There is nothing specific to Chinese in such switch. If conversion is broken, then existing utf-8 translations would be broken too and Russians would complain about it. SquirrelMail 1.4.8 utf-8 has additional fixes for PHP recode. These fixes are not used in CJK text conversion. Other utf8 changes are not related to Chinese charset conversion. They only drop Japanese XTRA_CODE support and add address book updates. -- Tomas |
|
|
Re: Problem of Traditional Chinese & Simplified Chinese with UTF8
by Frankie Wong
::
Rate this Message:
I only changed i18n.php as follows:
$languages['zh_TW']['NAME'] = 'Chinese Trad'; $languages['zh_TW']['CHARSET'] = 'utf-8'; $languages['zh_TW']['LOCALE'] = 'zh_TW.UTF-8'; $languages['tw']['ALIAS'] = 'zh_TW'; $languages['zh_CN']['NAME'] = 'Chinese Simp'; $languages['zh_CN']['CHARSET'] = 'utf-8'; $languages['zh_CN']['LOCALE'] = 'zh_CN.UTF-8'; $languages['cn']['ALIAS'] = 'zh_CN'; Maybe I accidentally changed something that I didn't know. I will download a fresh one to try again. Thank you Frankie > > > Frankie-10 wrote: >> >> >> sm version: 1.4.13 >> extra decode lib: 1.2 >> php: 5.1.4 with mbstring >> >> Actually, either big5 or gb2312 can be displayed when reply by >> sm-1.4.8-utf8. Because I am not good at PHP, I have no idea about how to >> amend 1.4.13 version to be fully support utf-8 even after taking a look to >> the squirrelmail-1.4.8.utf8-1.diff. >> >> I tried to follow the >> difference in 1.4.13 but it didn't work after testing by the plugin of >> test_charset that you sent me before. Charset turned from utf-8 to big5 if >> I >> selected traditional chinese language and to gb2312 if I selected >> simplified >> chinese language. >> >> Apparently, sm-1.4.13 doesn't convert original >> charset to utf-8 when reply or forward. It only converts original message >> when >> viewing it. Any hints or highlight about it? >> > > Can you show your "diff -uwrN squirrelmail-1.4.13.orig squirrelmail-1.4.13 > > squirrelmail-1.4.13.diff". If translation is switched to utf-8 the way you > said, charset conversion is working. There is nothing specific to Chinese in > such switch. If conversion is broken, then existing utf-8 translations would > be broken too and Russians would complain about it. > > SquirrelMail 1.4.8 utf-8 has additional fixes for PHP recode. These fixes > are not used in CJK text conversion. Other utf8 changes are not related to > Chinese charset conversion. They only drop Japanese XTRA_CODE support and > add address book updates. > > -- > Tomas > -- > View this message in context: > http://www.nabble.com/Problem-of-Traditional-Chinese---Simplified-Chinese-with-UTF8-tp16011794p16022116.html > Sent from the squirrelmail-i18n mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ----- > squirrelmail-i18n mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > Information about translations: http://squirrelmail.org/wiki/LanguageTranslation > List address: squirrelmail-i18n@... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n > This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ----- squirrelmail-i18n mailing list Posting guidelines: http://squirrelmail.org/postingguidelines Information about translations: http://squirrelmail.org/wiki/LanguageTranslation List address: squirrelmail-i18n@... List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n |
|
|
Re: Problem of Traditional Chinese & Simplified Chinese with UTF8
by James Li
::
Rate this Message:
Hi,
I have a similar problem and need help. I have a server side python script that emails user submitted content to email accounts. The content is normally Simplified Chinese and when I view it from Squirrelmail it appears corrupted. However, emails sent by the same script to my other accounts (yahoo, hotmail) are fine. I changed my script to set charset=utf-8 to make it work for Squirrelmail but when I try to reply the message the quoted message is again corrupted. The following is the email headers. From: myname@hotmail.com To: "['myname@yahoo.ca', 'admin@mydomain.com']"@mail.mydomain.com Subject: Feedback MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Message-Id: <20080406194601.644D6C8FB@mail.mydomain.com> Date: Sun, 6 Apr 2008 15:46:01 -0400 (EDT) It's interesting that if I change charset to gb2312 the message will be corrupted, even if the content is gb2312. Emails sent from Squirrelmail's web interface can be viewed and replied OK. Mails sent from yahoo/hotmail can be viewed and replied OK. It's just the script ... My setup is Squirrelmail 1.4.10a, php5, firefox&ie7. I used the conf.pl script to set langauage and charset to zh_CN and gb2312 respectively. The display option is set to Simp Chinese for the client. Thanks!
|
|
|
Re: Problem of Traditional Chinese & Simplified Chinese with UTF8
by Tomas Kuliavas
::
Rate this Message:
Your sample message is not in Chinese or Content-Transfer-Encoding header is missing. gb2312 and utf-8 are 8bit character sets and Chinese characters use full 8bit bytes. Only ASCII characters are in 7bit. RFC2045 states that default Content-Transfer-Encoding value is 7bit. Default value can't be correct, if you have "Content-Type: text/plain;charset=utf-8" or "Content-Type: text/plain;charset=gb2312" with Chinese characters. In SquirrelMail default charset option is applied only to US English translation. I think it is clearly stated in conf.pl. I recommend switching SquirrelMail Chinese translations to utf-8 the way Frankie did and installing extra decoding library. Use of recode extension is recommended. Iconv can break or fail to decode things. mbstring is only third option and it might be less tested. Aggressive decoding will increase memory usage. If you keep CJK translations in big5, euc-kr and gb2312 charsets, SquirrelMail compose won't work correctly with utf-8 emails, because code does not have big5, euc-kr, gb2312 encoding functions. -- Tomas |
| Free Forum Powered by Nabble | Forum Help |