Re: Updated hungarian translations for SquirrelMail 1.4.18

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