Re: [SM-I18N] Japanese language .po encoding

[Tomas K. <to...@us...>]

> Hi there,
> im using the latest squirrelmail,
> I need to know what encoding the Japanes translation in the .po file are
> and
> how I can change them to UTF-8 for a customer.
> I believe i have modified the php language functions enough for this to be
> plausible as the browser now auto detects utf8 and shows the utf 8 encoded
> (japanese) email perfectly but the squirrelmail webpages are just garbled.
> From what i can see this is just an encoding at the file lvl problem and i
> just think i need to know howto convert the translations in the msgstr:
> fields to utf-8.
> What i have tried so far is enciding the whole file as utf-8 form an
> editor
> but the editor pukes,
>
>
> I have also tried selcting the "encode all as utf-8 uppn save" option in
> Kbabel this throws up errors:

Quick (untested) guide:

1. convert .po
msgconv -t utf-8 squirrelmail.po -o squirrelmail-utf8.po

you can also use charconv or recode (http://www.freshmeat.net)

2. recompile .mo
msgfmt -v -c -o squirrelmail-utf8.mo squirrelmail-utf8.po

3. convert help files.
charconv, iconv or recode.

4. change charset in functions/i18n.php and move squirrelmail-utf8.* files
to squirrelmail.*

5. Please note that SquirrelMail Japanese translation uses some extra
functions:
a) in some places it might assume that you are using euc-jp.
b) it tries to compose messages in shift-jis
c) there are Japanese fixes, that are not available in 1.4.2

It might be better if you don't change currect $languages['ja_JP'] entries
in functions/i18n.php and just create new ja_JP.UTF-8 translation. But new
translation won't be able to read all Japanese encodings.

-- 
Tomas