How to export translated messages from Launchpad? (Re: i18n test environment on Lauchpad staging.

[INADA Naoki]

> Launchpad can export into a bzr branch, which seems like a good fit. I
> think we should let it commit the .po files into a branch that gets
> merged into bzr trunk, and then compile them into .mo files at
> distribution / package build time.
>
> https://help.launchpad.net/Translations/YourProject/Exports

On that URL,

> Directory layout
> In the branch, each translation file will have a normalised name (de.po for a German translation, zh_CN.po > for Simplified Chinese, eo.po for Esperanto, and so on). Each translation sits in the same directory where > its template was located on import.

That's what I wanted to know. It's very nice.

>> If build_mo command is needed, I'll copy it from bzr-explorer.

I've sent merge request adding build_mo command.
https://code.launchpad.net/~songofacandy/bzr/i18n-msgfmt/+merge/61082


On Mon, May 16, 2011 at 7:30 PM, Martin Pool <mbp at canonical.com> wrote:
> On 12 May 2011 14:33, INADA Naoki <songofacandy at gmail.com> wrote:
>> Extracting messages from commands and errors looks fine now.
>> I'll add more tests and then request review.
>>
>> Then, next problem is: how to export translated messages?
>>
>> TortoiseBZR, bzr-explorer and qbzr adds "import_po" and "build_mo"
>> command.
>> But Launchpad can export translated messages as mo format.
>> Should we use mo files directly?
>>
>> If build_mo command is needed, I'll copy it from bzr-explorer.
>
> Launchpad can export into a bzr branch, which seems like a good fit. I
> think we should let it commit the .po files into a branch that gets
> merged into bzr trunk, and then compile them into .mo files at
> distribution / package build time.
>
> https://help.launchpad.net/Translations/YourProject/Exports
>
> Martin
>



-- 
INADA Naoki  <songofacandy at gmail.com>