[Python-Dev] Translated Python documentation

INADA Naoki songofacandy at gmail.com
Fri Feb 24 08:05:12 EST 2017

On Fri, Feb 24, 2017 at 9:20 PM, Berker Peksağ <berker.peksag at gmail.com> wrote:
> On Thu, Feb 23, 2017 at 12:01 AM, Victor Stinner
> <victor.stinner at gmail.com> wrote:
>> 2017-02-22 19:04 GMT+01:00 Serhiy Storchaka <storchaka at gmail.com>:
>>> What percent of lines is changed between bugfix releases? Feature releases?
>>> My largest apprehension is that the documentation can be outdated and
>>> quickly become degraded if main contributors left it.
>> If the original text (english) changes, untranslated text is
>> displayed, not outdated text.
> I think that's much worse than showing the outdated text. I don't see
> any point on showing half English and half French text if the reader
> can't understand the other half of it.

In Japan, everyone learn English at school, but most people is not
good at English.
So 80% translated text helps us very much.

Especially, Sphinx split document by paragraph.  It's best granularity
for translation.

For example, there are some English paragraph remains in pathlib document
But it's very useful for Japanese not good at English.

> As someone who have spent a lot of time reviewing and committing
> documentation patches, I'm strongly against on marking documentation
> translations as official.

I totally agree with you.  Our QA is not good as commit review of CPython.
So what I want is (un|semi) official place for we share our efforts with other
language translators.  (e.g. automated build, hosting translated documentation,
and downstream customizations like adding link to official English document).

> The Python documentation updates frequently
> and it's simply not possible to keep them sync with the official
> documentation. See
> https://github.com/python/cpython/commits/master/Doc for the commit
> history of the official documentation. You can easily compare it with
> the translations by looking their GitHub repositories.

While we don't translate mastar branch, I admit we behind several weeks or
months from upstream.
But since we moved most work on Travis, we can make it weekly or even daily.
And we can share the automation with other Languages if we have a team.

I can do it without official agreement, but I don't want to do it until I get
consensus about domain name or github organization name.

> Also, there are a lot of better educational materials (e.g. Django
> Girls Tutorial) for people who don't speak English and have no
> previous programming experience. Even the tutorial contains several
> references to different programming concepts and programming languages
> such as C++.

Sadly, there are many medium level programmers who are not good
at English in Japan.  So translated library reference is very helpful too.


More information about the Python-Dev mailing list