I have modified some parts of squirrelmail 1.4.4 1. in function/mime.php, there's a line $filename=rawurlencode($filename); this would make the chinese filename encoded into something unwanted. so I've comment it out. 2. the squirrelmail cannot wrap line as it does in English. It's because chinese characters doesn't have spaces in between a sentence, so a whole paragraph would also be seen as a single word, and stay in the same line. (I've questioned about this issue in the mailing list before) I've removed the <pre></pre> tag, so that the browser would know to make it swap line when it reach the frame end. 3. some chinese characters will be seen as illegal characters in the addressbook's nickname. It's because some chinese characters contain this "\" symbol, which is seen to be illegal. I've just comment out the checking for illegal characters. This may have some risk, but up till now, no problem is discovered.
I've also modified some other aspects for customization which are not related to chinese problem. Instead of upgrading to 1.4.5, I think I would rather install it into a new directory to test whether the problem can be solved. Actually, I've also installed 1.5.0 for testing. I have used mbstring in other part of my system to convert utf-8 into big5 and gb2312. so, it should support Chinese encoding. Angela --- Tomas Kuliavas <[EMAIL PROTECTED]> 說： > Japanese translation was written to make it work in > Japanese language > environment, because generic SquirrelMail functions > did not support > options that were needed for translation. Current > SquirrelMail support is > improving and developers are solving some issues in > a way that does not > depend on translation. Implementation depends on php > mbstring extension > and character set selected by translation. > > Are you running standard squirrelmail 1.4.4 install > or modified one? Can > you upgrade to 1.4.5? Are Chinese encodings > supported by your php mbstring > extension? > > > My php support mbstring and iconv, but not support > > recode. (php said recode is not available on > Windows > > platforms) > > > > Was Japanese translation has similar problem > before > > and has re-written the functions? > > > > Thanks for your help! > > > > Angela > > > >> rfc2822 "2.1.1. Line Length Limits" > >> http://www.faqs.org/rfcs/rfc2822.html > >> -------------- > >> There are two limits that this standard places on > > the number of > >> characters in a line. Each line of characters > MUST > > be no more than > >> 998 characters, and SHOULD be no more than 78 > > characters, excluding > >> the CRLF. > >> -------------- > >> > >> > >> SquirrelMail can be set to use B encoding in > > messages headers when message > >> is written in multibyte character set. Current > > 1.5.1cvs implementation > >> requires mbstring support in php and multibyte > > character set supported by > >> mbstring extension. Big5 charset is supported > since > > php 4.3.0, if packager > >> compiles php mbstring extension with Chinese > > support. Implementation of B > >> encoding uses three functions unavailable in > 1.4.x > > and modifies standard > >> header encoding function. > >> > >> Other option - write custom handling functions > for > > XTRA_CODE extension in > >> $languages. See Japanese translation for example. > > You must write all > >> functions in 1.4.x or only required functions in > > 1.5.1cvs. > >> > >> Chinese translation must solve other issues too. > > Some changes require php > >> installation with full mbstring and recode or > iconv > > support. I think > >> Windows php packages are limited and don't have > > required extensions. If > >> php install does not have recode or iconv > support, > > you must use basic php > >> functions for character set decoding and > conversion. > > These basic functions > >> are slow in big5 and gb2312 character sets. > Imagine > > how similar functions > >> process all gb18030 characters or handle > > iso-2022-cn. It is possible that > >> gb18030 can be optimized. I haven't tried to find > > any mathematical > >> patterns in character set mapping table. > >> > >> I might try porting 1.5.1cvs code to 1.4.x and > > provide patch that fixes > >> some issues, but I need to know if your php > > installation can handle all > >> modifications. > >> > >> -- > >> Tomas > >> > > > > _______________________________________ > > 想即時收到新 email 通知？ > > 下載 Yahoo! Messenger > http://messenger.yahoo.com.hk > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software > Conference & EXPO > September 19-22, 2005 * San Francisco, CA * > Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects > & Teams * Testing & QA > Security * Process Improvement & Measurement * > http://www.sqe.com/bsce5sf > -- > 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=2995 > List Info: > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > _______________________________________ 想即時收到新 email 通知？ 下載 Yahoo! Messenger http://messenger.yahoo.com.hk ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf -- 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=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
