On Tue, 17 Jul 2012, Paul Lesniewski wrote:
> On Tue, Jul 17, 2012 at 4:53 AM, Federico Bianchi
> <f.bianchi@...> wrote:
>> On Tue, 17 Jul 2012, Federico Bianchi wrote:
>> We have a vintage SquirrelMail setup still defaulting to ISO-8859-1; after inserting imapproxy
>> some filters stopped working because of its UTF-8 default.
>> While our specific problem was tamed and fixed in a matter of minutes by means of iconv, I
>> assume other people might stumble into it (much more so, because their contexts might not
>> be so trivial to handle): do you think it may be worth a specific workaround? If so, can you
>> think of a reliable one since the simple solution (streaming to iconv via a configuration
>> setting) is likely a bad one?
> You don't say what your "solution" was, and I can't say as I
> understand exactly what your problem was. You can also change the
> default character set in SquirrelMail webmail by making a single
> change in its configuration file.
The trivial fix for us was converting to UTF-8 all the SquirrelMail user
preferences files from ISO-8859-1; much in a similar way, the simple (and,
IMHO, wrong) general solution I could think of would be a configuration
> More generally speaking, one of my primary goals for SquirrelMail
> webmail right now is to encourage all the translators to resubmit
> their translations converted to UTF-8, so we can ship it with its
> character set defaulting to UTF-8. I've not had the time I thought I
> would in the past 6 months to work on this, but it's coming....
OK. Generally speaking, however, I think everything coming from imapproxy
should be normalised to a common encoding.
Dipartimento di Storia delle Arti
Universita` di Pisa
via Trieste, 38 - I-56126 Pisa (Italy)
tel.(+39) 050 221 6 024; fax (+39) 050 221 6 001
!DISCLAIMER!: my e-mail reflects _my_own_ opinions!