Re: Updated hungarian translations for SquirrelMail 1.4.18

On 2009. április 30. 20.14.46 Fredrik Jervfors wrote:
> >>> This is similar to
> >>> http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/S
> >>> M-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.
> >
> > One more important information: changing to
> > $languages['hu_HU']['CHARSET'] = 'utf-8';
> > will render all the data files (.pref files etc.) and even user passwords
> > with accentuated/special characters UNUSABLE. Everyone changing the
> > codepage from iso-8859-2 to utf-8 (this is implied in updating from
> > 1.4.17 to 1.4.18 AFAIK) will have to convert his/her data files (with
> > iconv) or database and even the user passwords (cooperating with the
> > affected users)!
>
> I've seen no such complaints for other languages converted to UTF-8. Could
> it be that you have some plugin installed that might affect this? Can you
> please try a SVN version of 1.4.18 (there are snapshots at the download
> page) without plugins and see if you can re-create the problem? Can you
> please give more information about the IMAP server you're using and its
> configuration?

Sorry, I don't have the time to test 1.4.18 now, but there is no problem with the IMAP server. The problem is that in my existing SquirrelMail installation, 
all .pref (and .abook etc.) files were stored in ISO-8859-2 charset, since it was my charset defined by functions/i18n.php ( $languages['hu_HU']
['CHARSET'] = 'iso-8859-2'; ) so far. Now, when I've changed to UTF-8, I had to convert all the data files from iso-8859-2 to utf-8 by the iconv 
command. Moreover, user passwords with accentuatd characters had to be changed (user cooperation was necessary of course), since the browser 
sends the passwords in the charset dictated by SquirrelMail.

However, this is only caused by the line
$languages['hu_HU']['CHARSET'] = 'utf-8';
in functions/i18n.php, and is totally unaffected by the encoding of .po and .mo files, since those files contain charset information in themselves, so 
SquirrelMail can do message charset conversions on the fly  without needing any additional configuration info. Also, Squirrelmail can easily find the new 
traslation files, since they are in the same place as the old ones, and functions/i18n.php already instructs it to search for message translation in this 
directory (local/hu_HU):
$languages['hu_HU']['LOCALE']  = array('hu_HU.UTF-8', 'hu_HU.UTF8', 'hu_HU');
or
$languages['hu_HU']['LOCALE']  = array('hu_HU.ISO8859-2','hu_HU.ISO-8859-2','hu_HU');
it doesn't matter (in theory, however, it confuses the change_pass plugin).

Sincerely,

Tamás

------------------------------------------------------------------------------
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: [email protected]
List archives: http://news.gmane.org/gmane.mail.squirrelmail.internationalization
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-i18n