> hi, > > 1. have problem with with Reply and Reply All commands. > Reply and Reply All insert text original mail with original encoding(!). > as result getting garbage in compose window. > Who? > > sample: > original mail in windows-1251 (or koi8-r) encoding. > i am using utf-8 encoding (test this some with many others encodings). > user click Reply and getting garbage in compose window. > how-to release this?
SquirrelMail 1.4.x does not support charset conversion in reply or forward. It is being tested in squirrelmail 1.5.x. See http://www.topolis.lt/squirrelmail/patches/pending/encode/squirrelmail-1.4.3a.encode.diff.gz Patch adds newer decoding system (already present in 1.4.4cvs) and charset conversion in compose patches (1.5.1cvs). It removes big5, gb2313 and x-mac-* charset support. If you want to separate decoding system changes and ported charset conversion fixes - compare patched squirrelmail 1.4.3a with squirrelmail 1.4.4cvs (functions/i18n.php v.1.129.2.21) Please understand that patch is experimental. Test it, provide feedback, keep both pieces if it breaks. Some code has to be added to functions/encode/. I might have missed some decodeHeader calls. If you have problems with patching, I can provide patched files. > 2. some users using stupid mail clients why not insert Content-type > Content-transfer-encoding fields. > how-to select encoding for this mails in read window? If content-transfer-encoding is not set, email has to be in 7bit. Email client or web form is broken and violates rfc2045. I would rather inform web form developer, that his/her message is corrupted by some email servers. http://www.topolis.lt/screen-shots/squirrelmail/rfc2045/rfc2045.jpg Problem can be fixed by creating special plugin that fixes this email problem and some other webmail related problems. I am working on such plugin, when I have free time and enough motivation to dig through squirrelmail code. I can't give any final plugin creation date and I will ignore any message, that bugs me to work on it. > 3. many users using old mail clients who not support utf-8. > my users need select custom encoding for compose mail. > how-to release this without switching Options/Display > Preferences/Language? You can't change encoding in webmail pages. If you use browser's menu to change it, you won't inform squirrelmail scripts about it. If you add "change charset" button in web form, such feature would break translations and squirrelmail does not have code, that allows to have such button. Create separate translation, that uses koi8-r, windows-1251 or iso-8859-5. If you need patch for 1.4.3a, just ask. Please note that these changes won't be added to squirrelmail. koi8-r and windows-1251 translations might break Russian folder names, if you don't increase squirrelmail php requirements to 4.3+ with mbstring support. If you use non-Unicode charset in webmail, you might create incorrectly encoded emails in some cases. Different charset options can be included if patch 611298 is implemented. Major problem - original patch does not cover all language+charset variations. It can break translations and some other parts of sm. Changes have to be implemented in different way. https://sourceforge.net/tracker/?func=detail&aid=611298&group_id=311&atid=300311 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
