« Return to Thread: Change of SM default_charset to UTF-8
Re: Change of SM default_charset to UTF-8
by Bugzilla from petr.hroudny@gmail.com
::
Rate this Message:
2009/5/4 Németh Tamás <nice@...>:
> According to my observations, locale files contain charset information, so
> SquirrelMail (or php behind the scenes) can do a charset translation on the
> fly. For example, I created utf-8 .mo files, and simply copied them into a
> plain ISO-8859-2 SM 1.4.17 installation, and all the messages were diplayed
> correctly.
Have you also recompiled the .po files? If not, your SM was still using .po
files from the ISO-8859-2 installation. Also have you copied the utf-8 help
files and tried to click on Help?
> The only problem I observed was, that I was
> unable to answer other messages than the ones composed in the same charset as
> mine
Yes, pure display is possible, but all operations (Reply, Forward)
fail. So indeed,
you can see everyone's message correctly, but your outgoing messages are broken.
> Yes, I know, but you would be able to correctly reply mails which are utf-8
> encoded, but doesn't contain any character not in you charset, and this wold
> be a big advantage.
Still not a decent solution. You get a mail from outside of CE
(latin-2) region and
your reply gets broken. It's really not nice to call your email recipient Bj?rn.
> You're right but It can be painful to change charset on an existing
> installation, as I've explained before.
It's still not clear whether this is not just your local problem. And if
it proves to be true, then it's one more argument for switching to UTF-8.
Imagine a user chooses English initially and then decides to change
to Hungarian - if you're right, his password will get broken as well as
all prefs, addressbooks etc.
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/postingguidelines
Information about translations: http://squirrelmail.org/wiki/LanguageTranslation
Statistics for translations: http://l10n-stats.squirrelmail.org/
List address: squirrelmail-i18n@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n
> According to my observations, locale files contain charset information, so
> SquirrelMail (or php behind the scenes) can do a charset translation on the
> fly. For example, I created utf-8 .mo files, and simply copied them into a
> plain ISO-8859-2 SM 1.4.17 installation, and all the messages were diplayed
> correctly.
Have you also recompiled the .po files? If not, your SM was still using .po
files from the ISO-8859-2 installation. Also have you copied the utf-8 help
files and tried to click on Help?
> The only problem I observed was, that I was
> unable to answer other messages than the ones composed in the same charset as
> mine
Yes, pure display is possible, but all operations (Reply, Forward)
fail. So indeed,
you can see everyone's message correctly, but your outgoing messages are broken.
> Yes, I know, but you would be able to correctly reply mails which are utf-8
> encoded, but doesn't contain any character not in you charset, and this wold
> be a big advantage.
Still not a decent solution. You get a mail from outside of CE
(latin-2) region and
your reply gets broken. It's really not nice to call your email recipient Bj?rn.
> You're right but It can be painful to change charset on an existing
> installation, as I've explained before.
It's still not clear whether this is not just your local problem. And if
it proves to be true, then it's one more argument for switching to UTF-8.
Imagine a user chooses English initially and then decides to change
to Hungarian - if you're right, his password will get broken as well as
all prefs, addressbooks etc.
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/postingguidelines
Information about translations: http://squirrelmail.org/wiki/LanguageTranslation
Statistics for translations: http://l10n-stats.squirrelmail.org/
List address: squirrelmail-i18n@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n
« Return to Thread: Change of SM default_charset to UTF-8
| Free embeddable forum powered by Nabble | Forum Help |
