2009/5/4 Németh Tamás <
nice@...>:
> Instead of switching every language to utf-8, I would suggest to enable system
> admins to set the charset for the currently used language, not just the
> default_charset,
This is totally impossible - you need to convert all locales, all
helpfiles and modify
functions/i18n.php for that. Translated strings in e.g. latin-2 charset can't be
properly displayed in latin-1 and vice versa. That's why default_charset can
only be configured with English, where all strings are plain 7-bit ASCII.
Your only choices are:
1. broken emails, or
2. UTF-8.
There's no third option, sorry. Even lossy_encoding won't help - try replying to
russian email and you'll get a screen full of ?????????.
To sum up - the sooner we switch to UTF-8, the better. Any modern webmail
is doing exactly that. BTW, Fedora SM packages are converted to UTF-8 for years
and known to work fine.
My suggestion for 1.4.18: let's try to release two versions: legacy and utf-8
This way anyone could choose. No extra work is required, utf-8 version could be
autogenerated by a script.
Petr
------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3.
http://p.sf.net/sfu/velocityconf-----
squirrelmail-i18n mailing list
Posting guidelines:
http://squirrelmail.org/postingguidelinesInformation about translations:
http://squirrelmail.org/wiki/LanguageTranslationStatistics for translations:
http://l10n-stats.squirrelmail.org/List address:
squirrelmail-i18n@...
List archives:
http://news.gmane.org/gmane.mail.squirrelmail.internationalizationList info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n