Re: [SM-I18N] Translations

[Fredrik J. <sqm...@fi...>]

> I'd like to know more about hebrew translation and how i can get
> involved. thanks, Cyndi rand


Hi Cyndi.

Here's what I'm able to find about the Hebrew translation.

* Hebrew - he_IL - iso-8859-8
(SM uses cp1255, locale's header is in iso-8859-8)
    <yo...@za...>

I suggest that you try to contact <yo...@za...> to get his/hers
approval, but since only 57% of SquirrelMail is currently translated, and
that was done 2002-05-03, I don't think there should be any problem if yo=
u
continue the work.

If you want your translation to be really compatible with all kinds of
languages, like if you want to read mails in Japanese using an UI in
Hebrew, it should be coded in UTF-8, but other encodings are OK as well.
In fact, only four translations are in UTF-8 right now.

You can find statistics for the translations at
<http://smstats.topolis.lt>. As you can see there are three different
branches, which differs slightly.

HEAD is all strings used in the CVS versions, both STABLE and DEVEL, and =
I
suggest you start translating that branch.

SM-1_4_3 is the the translation for the current STABLE release of
SquirrelMail. It contains some strings that's not in HEAD. My suggestion
is that when you're done with HEAD, you merge it with SM-1_4_3 and then
complete the empty and fuzzy strings.

SM-1_5_0 is the the translation for the current DEVEL release of
SquirrelMail. It contains some strings that's not in HEAD. My suggestion
is that when you're done with HEAD, you merge it with SM-1_5_0 and then
complete the empty and fuzzy strings.

There's a lot more information about translating SquirrelMail at
<http://www.squirrelmail.org/wiki/en_US/LanguageTranslation>.

It could be helpful to get a more advanced tool than a plain text editor.
There are lots of them out there, both open source and commercial. And
always check your translation before submitting it to the i18n mailing
list.

Good luck, and thank you for contributing to SquirrelMail.

Sincerly,
Fredrik.