[Bf-docboard] New Blender user manual translation (for Japanese)

Cheng-Chia Tseng pswo10680 at gmail.com
Wed Mar 18 16:09:50 CET 2015


On Thu, Nov 13, 2014 at 10:14 PM, Tetsuo Mitsuda <lab1092 at gmail.com> wrote:

>
> > Which approach would you recommend?
>
> My recommend is 'Use Sphinx I18n'.
> Because it is new and simple for editing .po file.
> the translators just care about reST inline markup.
>

HI, I am a traditional Chinese translator.
I am testing the method proposed by Tetsuo Mitsuda today.
The workflow of translation just works fine.

I prefer to "use Sphinx I18n" too.
It makes writers put more focus/love on English documentation, and that's
what we want.

Separating doc projects for each language might fragmentize/disunite the
work,
and might be more difficult to update the content to date.
It is better for us to have one mainline doc (en doc) to maintain and to
translate from.

It seems that "use Sphinx I18n " is the better solution for us so far.



>
> But some case,  it have some limitation:
>
>    (1) additional 'translators note'
>
>          additional paragraph is (or need) only available for non-english
> page.
>          no original paragraph, it can't add po file for the
> paragraph. (msgid is empty)
>
>    (2) image
>
>          .po file is message text, it contains only text.
>          if you need to use different picture on every language,
> another solution may be needed.
>

This might be a problem...
We might have to figure it out or to find some help from Sphnix developers.


>
>    (3) Mark up (for english author)
>
>          (Need to test)
>          some reST markup seems that it does not support for gettext.
>
>
> Thanks,
>
>

-- 
Cheers,
by Cheng-Chia Tseng
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20150318/6318839f/attachment.htm 


More information about the Bf-docboard mailing list