Translation of Trac to Japanese/日本語 [ja_JP]

[asmodai@…]

This ticket should be used to coordinate the translation to Japanese/日本語.

[asmodai@…]

See also TracTermsJa.

[jruigrok]

Please see source:sandbox/i18n/trac/locale/ja_JP/LC_MESSAGES/messages.po for the first version of the translation file.

[Shun-ichi Goto <shunichi.goto@…>]

Wow, wanderful! I'll check and fix words soon.

[Shun-ichi Goto <shunichi.goto@…>]

Now I'm translating ja_JP .po file (current state is 50%) and I'm bothered by some msgid and have requests of message extraction in .pot file.

Some msgid in .pot file is not good to translate becuase single sentence are splitted into some parts.

For example, msgid="(added by" and msgid="ago)" should be merged as one id and parameterized. I want msgid="(added by $1 $2 ago)" and translated to msgstr="$1により$2前に追加".

I don't know how .pot is generated (auto generated by extractor?), But Change of msgid (in .pot) may bother other translations already started... Any plan?

[jruigrok]

Yes, right now this is a problem that is still open to fix, please see http://genshi.edgewall.org/ticket/129 for more details as they become available.

So please, concentrate on those parts of the messages.po file that can be translated and leave the broken sentences for now. We will get there, step by step.

The .pot is generated through

./setup.py extract_messages

and the file misses a lot of information. This will be fixed up in the coming days now that cmlenz implemented some new feature for me.

[Shun-ichi Goto <shunichi.goto@…>]

Thanks. I'll go with current messages. And watch genshi/babel tickets also.

[Shun-ichi Goto <shunichi.goto@…>]

Japanese translation against i18n branch r5942

[Shun-ichi Goto <shunichi.goto@…>]

I added the Japanese translation against i18n branch (r5942). All the msgids are translted.

BTW, there's many non-extracted words and badly fragmented phrases in i18n branch code due to lack of i18n:msg attributes although with latest babel/genshi. Current view is not good to use. How do I contribute it? By making a patch and attaching onto this ticket? or send patch to trac-dev? Or go ahead with this extraction and wait improvement of genshi?

[eblot]

Replying to Shun-ichi Goto <shunichi.goto@gmail.com>:

BTW, there's many non-extracted words and badly fragmented phrases in i18n branch code due to lack of i18n:msg attributes although with latest babel/genshi. Current view is not good to use.

This issue is common to all translated language (i.e. the messages.pot file needs some improvements). Maybe it's time to start a thread on this topic on the trac-dev ML.

[jruigrok]

See #G129 for more details on what needs to be fixed.

[Kyosuke Takayama <support@…>]

I translated message.po of the i18n branch(r6950) from a file attached here.

However, a part of non-translation is still left a lot. I can go ahead little by little.

[Kyosuke Takayama <support@…>]

Japanese translation i18n branch r6950

[jruigrok]

高山さんのファイルありがとうございました。

I have committed it in r6956.

[Kyosuke Takayama <support@…>]

Japanese translation from trunk r7087

[jruigrok]

Applied in r7138.

ありがとうございます。