RFC: How to translate help topics.

[INADA Naoki]

This problem is not specific to help topics.
User documentation has same problem now.
For example, Japanese documentation is very out of date.

So, I think we should have the way for tracking document
translation even if we select using gettext for help topics.
(Unless we use gettext for document too. Sphinx have gettext
based i18n feature already.)

For example, adding $Revision-Id$ may be simple and enough
solution. Translators can use bzr-keywords plugin to know
revision of original document easily. Then, they copy original
revision id to translate document as a comment or separated
"original_revisions.txt" file.

Getting back to Rosetta vs Plain Text.
I think we can assume that most translators are Bazaar user.
But making branch and sending merge request are hurdles to
many users. I may be able to lead Japanese translators, but
what about other languages?
I think using Rosetta to ease start translating.


On Sun, May 8, 2011 at 4:17 AM, Alexander Belchenko <bialix at ukr.net> wrote:
> INADA Naoki пишет:
>>> If the help topics are translated in text files in the branch,
>>> translators can pretty easily run a diff and fix their translations.
>>
>> If we take this approach, we should provide a way to manage
>> which translate text is based on which version of original text.
>
> That's a very good point against plain txt files. We'll need some sort
> of md5/sha for every translation. That very quickly will go out of
> control.
>
>
>



-- 
INADA Naoki  <songofacandy at gmail.com>