> Hello,
> 24.08.2016 02:19, Tatsuo Ishii пишет:
>>> We at Postgres Pro using the gettext technologies for this. And we
>>> have complete working toolchain (including modified Makefile) for
>>> translation the docs.
>> Sounds great but I am not sure if the technique can be applied to any
>> language including Japanese.
> I don't think that gettext is Russian-focused. At
> https://babel.postgresql.org/ I see a number of languages, including
> Japanese.
Yes, I know gettext can be used for Japanese messages translation in
PostgreSQL. I just couldn't imagine how the technique can be expanded
to docs.
> Please look at the attached .pot for one of the doc files. You can use
> any translation software (which supports .po (e.g. poedit, Lokalize,
> ...)) to translate it to any language.
> And you can look at all the docs converted to .po for translation:
> http://oc.postgrespro.ru/index.php/s/puEJKoUwbZ3dia5/download
Ok, the idea is, each sentence in the doc are regarded as "very long
message". Interesting. Looks better than "replacing SGML contents with
translated contents" (which Japanese doc project is doing for now).
>>> (If someone is interested in, we can share our results and provide
>>> everything needed to get started).
>>> Those who translated sgmls/xml before are moving to gettext/po (The
>>> FreeBSD Documentation Project is most remarkable example) or similar
>>> approaches.
>> As far as I know, FreeBSD's Japanese document project does not use
>> the gettext technologies.
> Unfortunately I can't read Japanese and don't understand how Japanese
> FreeBSD team works (and why cant it use the gettext technologies) ,
> but the main FreeBSD Documentation team is moving to PO (see
> https://www.bsdcan.org/2016/schedule/track/Hacking/680.en.html).
>
> Best regards,
> Alexander Lakhin
> https://postgrespro.com/
>
>
