Updated hungarian translations for SquirrelMail 1.4.18

This archive contains hungarian .po files for squirrelmail 1.4.18 and some
plugins (note that the plugin "change_pass" reads its translations from a
different place!). All files are updated with .pot files from
http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1_4_18/locales/po/ 
and converted to UTF-8. Every fuzzy and untranslated messages are fixed, and
some more bugfixes are applied.

Regards,

Tamás


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
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

[Fredrik Jervfors-4]

> This archive contains hungarian .po files for squirrelmail 1.4.18 and
> some plugins (note that the plugin "change_pass" reads its translations
> from a different place!). All files are updated with .pot files from
> http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1
> _4_18/locales/po/
> and converted to UTF-8. Every fuzzy and untranslated messages are fixed,
> and some more bugfixes are applied.

Thank you, Tamás. I'll commit it later tonight. I also have a question:
which is your given name and which is your family name? I've seen it as
both "Németh Tamás" and "Tamás Németh", so now I'm confused. I usually
list translators as [given name] [family name] and want to make sure that
I do the same with your name.

Sincerely,
Fredrik

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
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

Hi,

> Thank you, TamĂĄs. I'll commit it later tonight. I also have a question:
> which is your given name and which is your family name? I've seen it as
> both "NĂŠmeth TamĂĄs" and "TamĂĄs NĂŠmeth", so now I'm confused. I usually
> list translators as [given name] [family name] and want to make sure that
> I do the same with your name.

Mi given name is Tamás, so my family name is Németh. The confusion is
caused by this: http://en.wikipedia.org/wiki/Personal_name#Name_order

But can you see your quoted text above? You've sent me the mail in the
utf-8 encoding, and I use SquirrelMail in iso8859-2. Every time when I try
to answer to a mail in different encoding than my SquirrelMail setup
(iso8859-2 for now) the quotex text gets garbaged. This is because
SquirrelMail "forgets" to convert the quoted text from the original mail's
codepage to its own codepage. (I can answer iso8859-2 mails without a
problem.)

I consider this a bug. How can we get the developers to fix it (and
askuserinfo's unawareness of the translations) before releasing SM 1.4.18?

Regards,

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: 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

[Fredrik Jervfors-4]

>> Thank you, TamĂĄs. I'll commit it later tonight. I also have a
>> question:
>> which is your given name and which is your family name? I've seen it as
>> both "NĂŠmeth TamĂĄs" and "TamĂĄs NĂŠmeth", so now I'm confused. I
>> usually list translators as [given name] [family name] and want to make
>> sure that I do the same with your name.
>
> Mi given name is Tamás, so my family name is Németh. The confusion is
> caused by this: http://en.wikipedia.org/wiki/Personal_name#Name_order

Thank you, Tamás.

> But can you see your quoted text above? You've sent me the mail in the
> utf-8 encoding, and I use SquirrelMail in iso8859-2. Every time when I try
>  to answer to a mail in different encoding than my SquirrelMail setup
> (iso8859-2 for now) the quotex text gets garbaged. This is because
> SquirrelMail "forgets" to convert the quoted text from the original mail's
>  codepage to its own codepage. (I can answer iso8859-2 mails without a
> problem.)

As you can see above, your name got garbled when quoting me (i.e.
converting from UTF-8 to ISO-8859-2). It comes through all right in the
text you wrote.

> I consider this a bug. How can we get the developers to fix it (and
> askuserinfo's unawareness of the translations) before releasing SM 1.4.18?

I've converted Hungarian to UTF-8 this morning, which will solve this
problem for 1.4.18. I haven't committed your latest update yet, but I will
as soon as I can. As for askusersinfo I have to check.

Sincerly,
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/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

On 2009. április 28. 09.51.30 Fredrik Jervfors wrote:
> As you can see above, your name got garbled when quoting me (i.e.
> converting from UTF-8 to ISO-8859-2). It comes through all right in the
> text you wrote.

Yes, yes, that's what I'm talking about. The problem is that the conversion
DID NOT happen!

> > I consider this a bug. How can we get the developers to fix it (and
> > askuserinfo's unawareness of the translations) before releasing SM
> > 1.4.18?
>
> I've converted Hungarian to UTF-8 this morning, which will solve this
> problem for 1.4.18. I haven't committed your latest update yet, but I will
> as soon as I can. As for askusersinfo I have to check.

I'm already using utf-8 encoded .mo files but that doesn't solve the problem
in 1.4.17. Is 1.4.18 different? SquirrelMail is configured to work in
iso8859-2 (in config.php):

$squirrelmail_default_language = 'hu_HU';
$default_charset       = 'iso-8859-2';

And it is definitely able to convert the utf-8 messages to iso8859-2 before
displaying them. Of course it even converts every message to iso8859-2 before
displaying. However it doesn't convert the messages before inserting them as
quoted text when replying!

> Sincerly,
> 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/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

------------------------------------------------------------------------------
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

[Fredrik Jervfors-4]

>> As you can see above, your name got garbled when quoting me (i.e.
>> converting from UTF-8 to ISO-8859-2). It comes through all right in the
>> text you wrote.
>
> Yes, yes, that's what I'm talking about. The problem is that the
> conversion DID NOT happen!
>
>>> I consider this a bug. How can we get the developers to fix it (and
>>> askuserinfo's unawareness of the translations) before releasing SM
>>> 1.4.18?
>>
>> I've converted Hungarian to UTF-8 this morning, which will solve this
>> problem for 1.4.18. I haven't committed your latest update yet, but I
>> will as soon as I can. As for askusersinfo I have to check.
>
> I'm already using utf-8 encoded .mo files but that doesn't solve the
> problem in 1.4.17. Is 1.4.18 different?

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&pathrev=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>

> SquirrelMail is configured to work
> in iso8859-2 (in config.php):
>
> $squirrelmail_default_language = 'hu_HU';
> $default_charset       = 'iso-8859-2';

$default_charsed is only used for English, so it doesn't matter what you
put there when using Hungarian.

> And it is definitely able to convert the utf-8 messages to iso8859-2
> before displaying them. Of course it even converts every message to
> iso8859-2 before displaying. However it doesn't convert the messages
> before inserting them as quoted text when replying!

I see. Maybe someone who knows the SquirrelMail internals better can take
a look at this.

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/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

[Fredrik Jervfors-4]

> This archive contains hungarian .po files for squirrelmail 1.4.18 and
> some plugins (note that the plugin "change_pass" reads its translations
> from a different place!). All files are updated with .pot files from
> http://squirrelmail.svn.sourceforge.net/viewvc/squirrelmail/branches/SM-1
> _4_18/locales/po/
> and converted to UTF-8. Every fuzzy and untranslated messages are fixed,
> and some more bugfixes are applied.

Committed! Thank you for your contribution, Tamás.

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/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

On 2009. április 28. 11.01.05 Fredrik Jervfors wrote:
> 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&pathre
>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>

Sorry, but it didn't solve the problem (in addition it make SquirrelMail
1.4.17 unable to display some folder name, so the frame of the folder view
contains only warning messages). Take a look at the attached images. I sent
myself two identical messages but one of the was encoded in utf-8 and the
other in iso8859-2. Then I attempted to answer both messages, and you can see
what happened. (This happend using the new version of i18n.php, but also
happens with a standard 1.4.17 setup, as well as all previous versions (or at
least 1.4.4.)

Regards,

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: 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

> 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&pathre
>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. 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?

-Why does SM convert iso8859-2 messages to utf-8 while inserting as quote, but not
in the opposite direction?

-What if my page encounters some old browsers not supporting utf-8?

Regards,
Tamás

PS: I've found a seemingly true solution:

Setting the $lossy_encoding in config .php make SM able to convert utf-8 text to iso-8859-2
when quoting. However, I don't understand why it is necessary, since these utf-8 messages
can be displayed in iso-8859-2 without character loss.

PS2: Do I need to edit locale/hu_HU/setup.php when changing functions/i18n.php
converting .po and .mo files to utf-8?
and

------------------------------------------------------------------------------
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

[Fredrik Jervfors-4]

>> 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/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

>> 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.

locale/LANGUAGECODE/setup.php files may be also affected, arent they?



>> -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.

But it worked for me that way!

>> -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.

OK, finally I found the solution: If I want to make SM to convert utf-8
text to iso-8859-2 when replying (thus, using SM in iso-8859-2 and being
able to reply to utf-8 messages) then I have to enable the lossy_encoding
option in config.php. Here's the explanation from conf.pl:

Enable this option if you want to allow lossy charset encoding in message
composition pages. This option allows charset conversions when output
charset does not support all symbols used in original charset. Symbols
unsupported by output charset will be replaced with question marks.

But I was such and idiot that i misinterpreted this text so far. Going to
utf-8 will totally eliminate this problem, but I'll stay with iso-8859-2 &
lossy_incoding until SM 1.4.18 (in spite of the fact that it doesn't make
it possible to answer chinese mails :).

Regards,

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: 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

[Fredrik Jervfors-4]

>>> 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.
>
> locale/LANGUAGECODE/setup.php files may be also affected, arent they?

That file is only used in 1.5, not 1.4. I just ported the file from HEAD
to 1.4.18 anyway, so now it looks the same in both HEAD and 1.4.18.

>>> -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.
>
> But it worked for me that way!

Did you remember to restart the web server after installing new mo-files,
to make sure that your web server didn't use cached translations? Or maybe
I misunderstood the question. Anyway, I don't know the i18n code in
SquirrelMail by heart, so I can't easily answer questions about who it
works. If anyone else on the list know the answer, please help out.

>>> -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.
>
> OK, finally I found the solution: If I want to make SM to convert utf-8
> text to iso-8859-2 when replying (thus, using SM in iso-8859-2 and being
> able to reply to utf-8 messages) then I have to enable the lossy_encoding
>  option in config.php. Here's the explanation from conf.pl:
>
> Enable this option if you want to allow lossy charset encoding in message
>  composition pages. This option allows charset conversions when output
> charset does not support all symbols used in original charset. Symbols
> unsupported by output charset will be replaced with question marks.
>
> But I was such and idiot that i misinterpreted this text so far. Going to
>  utf-8 will totally eliminate this problem, but I'll stay with iso-8859-2
> &
> lossy_incoding until SM 1.4.18 (in spite of the fact that it doesn't make
> it possible to answer chinese mails :).

Ah, that's right. I had forgotten about this configuration option. I still
have a lot to learn about the i18n code in SquirrelMail.

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/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

On 2009. április 29. 02.55.15 Fredrik Jervfors wrote:

> >>> -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.
> >
> > But it worked for me that way!
>
> Did you remember to restart the web server after installing new mo-files,
> to make sure that your web server didn't use cached translations? Or maybe
> I misunderstood the question. Anyway, I don't know the i18n code in
> SquirrelMail by heart, so I can't easily answer questions about who it
> works. If anyone else on the list know the answer, please help out.

I did this just now:

titanic:/home/squirrelmail/1.4.17/htdocs/functions # vi i18n.php
titanic:/home/squirrelmail/1.4.17/htdocs/functions # /etc/init.d/apache restart
Shutting down httpd                                                                                   done
Starting httpd [ PHP4 ]
titanic:/home/squirrelmail/1.4.17/htdocs/functions # grep 'hu_' i18n.php
$languages['hu_HU']['NAME']    = 'Hungarian';
$languages['hu_HU']['CHARSET'] = 'iso-8859-2';
$languages['hu_HU']['LOCALE']  = array('hu_HU.ISO8859-2','hu_HU.ISO-8859-2','hu_HU');
$languages['hu']['ALIAS']      = 'hu_HU';

But then:

titanic:/home/squirrelmail/1.4.17/htdocs/functions # fgrep -i 'utf-8' ../locale/hu_HU/LC_MESSAGES/squirrelmail.mo
Binary file ../locale/hu_HU/LC_MESSAGES/squirrelmail.mo matches

(All .mo files are utf-8 encoded.) And squirrelmail displays all messages correctly.
However I don't consider it a problem and you don't have to worry about it.


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: 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

On 2009. április 28. 16.51.39 Fredrik Jervfors wrote:
> > 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.

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)!

Regards,

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: 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

[Fredrik Jervfors-4]

>>> 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?

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/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

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: 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