>>Turn on lossy encoding in SquirrelMail configuration. ISO-8859-2 does not >>cover all UTF-8 characters. By default SquirrelMail does not do charset >>conversions when target charset is subset of source charset. >> >>If you have policy of using utf-8 in all outgoing emails, convert >>SquirrelMail to utf-8 and it will start using utf-8. > > Thanks for the advice, I tried with lossy encoding and it works fine now. > > But: this way I fixed our local squirrelmail installation. Still, there > are many > installations not using this setting and from them we're getting corrupted > replies to our utf-8 mails. > > With lossy encoding set, squirrelmail behaves exactly like mutt - converts > every slovak text properly regardles of charset used and replaces unknown > chars with '?' Try replying to Russian or Chinese emails. That's why I haven't set to true, when setting was introduced. Both lossy encoding ways are broken. SquirrelMail is set to act same way as it acted before setting was introduced. > Thus I wonder why is this behaviour not the default, IMHO > it has several important advantages: > > 1. user selecting Slovak translation can be sure he can correctly reply to > any slovak text > 2. if he receives email in another language, he can simply switch the > translation > to that language and again reply correctly regardles of charset > 3. this behaviour is "industry standard", no other email client is > changing charset without converting the text wanna bet? Any client without proper charset support will do. > 4. without this setting, also windows-1250 emails get broken, as 1/3 of > slovak > national characters are at different positions than in iso-8859-2 > 5. by some googling I found that squirrelmail rpm's for Linux are already > converted > to utf-8 - but this means there's huge interoperability issue between > those versions > and standard version which is using iso-8859-2 for slovak translation and > does not convert from utf-8 into it by default. Interoperability issues will happen only if you run both of them on same set of user preferences. If they don't share preferences, there is no interoperability and only original version remains broken. lossy encoding does not apply to utf-8 translations. Scripts assume that utf-8 is superset of all other charsets and convert replies and forwarded emails. -- Tomas ------------------------------------------------------------------------- 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-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
