Thijs Kinkhorst wrote:
> Hello All,
>
> It's a pleasure to be able to announce the availability of the first Release
> Candidate of SquirrelMail 1.4.15. A release candidate is intended as the
> final public verification that a version is all right before it's
> declared "stable". Please try it
>-Pôvodná správa-
>> 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 in
>-Pôvodná správa-
>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, co
>-Pôvodná správa-
>If standard SquirrelMail is used in Czech translation, it sends emails in
>ISO-8859-2. Standard SquirrelMail does not try to change composed email
>charset to utf-8. If you expect emails to be converted to other charset and
>they are corrupted during conversion, you have
Hi list,
I'd like to ask for help with the problem with broken national characters like
"čťľš".
All our outgoing email uses utf-8 and the replies from almost all email clients
are OK.
However, Squirrelmail seems to be one of the exceptions - the replies from it
always have
partially corrupted n
