>> Yes, "functions/i18n.php" is updated. See:
>> <
http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM>> -1_
>> 4-STABLE/squirrelmail/functions/i18n.php?view=patch&r1=13619&r2=13618&pa
>> thre v=13619>
>>
>> Download "functions/i18n.php" from 1.4.18, replace the one in 1.4.17
>> (don't forget to back up) with it, and see if it solves the problem.
>> <
http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM>> -1_
>> 4-STABLE/squirrelmail/functions/i18n.php>
>>
>
> OK, I was able to make a workaround behind doors:
> I changed the encoding from iso-8859-2 to utf-8 in functions/i18n.php like
> this:
>
> < $languages['hu_HU']['CHARSET'] = 'utf-8';
> < $languages['hu_HU']['LOCALE'] = array('hu_HU.UTF-8', 'hu_HU.UTF8',
> 'hu_HU');
> ---
>
>> $languages['hu_HU']['CHARSET'] = 'iso-8859-2';
>> $languages['hu_HU']['LOCALE'] =
>> array('hu_HU.ISO8859-2','hu_HU.ISO-8859-2','hu_HU');
>
> This is similar to
>
http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1> _4-STABLE/squirrelmail/functions/i18n.php
> but I also changed the 'CHARSET' to utf-8, not only the locale as it was
> in your development version.
My bad. What you did is what I was supposed to do. I've fixed it in the
repository now. Thank you for spotting it.
http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1_4-STABLE/squirrelmail/functions/i18n.php?r1=13599&r2=13623&view=patch> So, my SquirrelMail started to work entirely
> in utf-8, I mean it sends utf-8 encoded pages to the browser, and I can
> answer both iso8859-2 and utf-8 messages properly now. However, I have
> some more questions:
>
> -How could SM work when all my .mo files were already in utf-8, but the
> 'LOCALE' in my i18n.php was
> still iso-8859-2? Does it some charset detection and on the fly
> conversion?
No, it won't work.
> -Why does SM convert iso8859-2 messages to utf-8 while inserting as
> quote, but not in the opposite direction?
I think this has to do with the decoding functions in SquirrelMail. Since
UTF-8 can contain characters from any writing system, let's say Chinese,
it's hard to convert that to ISO-8859-2 which doesn't have Chinese
characters. Should be possible to do, but I think that we're moving
towards making SquirrelMail UTF-8 only (UI and outgoing mail). Incoming
mail has to be converted to UTF-8 when displaying and answering them in
SquirrelMail.
> -What if my page encounters some old browsers not supporting utf-8?
I don't know any such browser, but I guess there might be such cases. If
the browser doesn't handle UTF-8, which I think is about 30 years old,
then the reading experience might not be pleasant.
Sincerely,
Fredrik
------------------------------------------------------------------------------
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