Hi, This is just a celebration email!! To tell you docs.python.org/fr/3.6/ is online since the recent merge of https://github.com/python/docsbuild-scripts/pull/11 a few hours ago!!! This mean that for all of us having synchronized your translation to the python organization repository you can now add your language to https://github.com/python/docsbuild-scripts/blob/master/build_docs.py#L48 and have your translation on docs.python.org too (this list use the PEP 545 language tag notation, so: lowercased with dashes). And for all other translation, this mean that you should push to github.com/python/python-docs-{your_language} soon :) The next step is https://www.python.org/dev/peps/pep-0545/#create-sphinx-doc-language-switche... if someone want to work on it I'll be welcome. I'm trying to keep an overview about which language are at which step here https://mdk.fr/blog/python-documentation-translation.html as there's numerous translations (11 now !!). Bests, -- Julien Palard https://mdk.fr
Well done :-) 2017-06-28 23:10 GMT+02:00 Julien Palard via Doc-SIG <doc-sig@python.org>:
Hi,
This is just a celebration email!! To tell you docs.python.org/fr/3.6/ is online since the recent merge of https://github.com/python/docsbuild-scripts/pull/11 a few hours ago!!!
This mean that for all of us having synchronized your translation to the python organization repository you can now add your language to https://github.com/python/docsbuild-scripts/blob/master/build_docs.py#L48 and have your translation on docs.python.org too (this list use the PEP 545 language tag notation, so: lowercased with dashes).
And for all other translation, this mean that you should push to github.com/python/python-docs-{your_language} soon :)
The next step is https://www.python.org/dev/peps/pep-0545/#create-sphinx-doc-language-switche... if someone want to work on it I'll be welcome.
I'm trying to keep an overview about which language are at which step here https://mdk.fr/blog/python-documentation-translation.html as there's numerous translations (11 now !!).
Bests, -- Julien Palard https://mdk.fr
_______________________________________________ Doc-SIG maillist - Doc-SIG@python.org https://mail.python.org/mailman/listinfo/doc-sig
Hi! The language switch has been merged in python 3.7, so it's now visible here : https://docs.python.org/3.7/ and here [https://docs.python.org/fr/3.7/](https://docs.python.org/3.7/) Bests, -- Julien Palard https://mdk.fr
Congrats, Julien! But I can't see language switcher on Python 3.6 document. We (Japanese translators) translates latest stable release, not development branch. Is it possible to publish Japanese only for 3.6 branch? INADA Naoki <songofacandy@gmail.com> On Tue, Aug 8, 2017 at 6:39 PM, Julien Palard via Doc-SIG <doc-sig@python.org> wrote:
Hi!
The language switch has been merged in python 3.7, so it's now visible here : https://docs.python.org/3.7/ and here https://docs.python.org/fr/3.7/
Bests, -- Julien Palard https://mdk.fr
_______________________________________________ Doc-SIG maillist - Doc-SIG@python.org https://mail.python.org/mailman/listinfo/doc-sig
Hi Inada,
But I can"t see language switcher on Python 3.6 document.
Yes I'm currently backporting it to older branches (3.6 and 2.7 at least).
We (Japanese translators) translates latest stable release, not development branch.
Is it possible to publish Japanese only for 3.6 branch?
Current implementation of the switcher can't do it, see: https://github.com/python/cpython/blob/dff9b5f9d62aa0b23f8a255867d09d11890ef... but if it make sense, it may be enhanced. We're also limited by the fact that switchers are versionned in cpython itself, so they will follow the freez (security only) cycles, typically blocking us to add/remove a translations to a frozen versions, which may or may not be a problem as old versions documentation are built without switchers (see: https://docs.python.org/3.4/). Last comment about this is that the current script building the documentation will automatically find the nearest branch for translations, see: https://github.com/python/docsbuild-scripts/blob/master/build_docs.py#L132 meaning that if you're working on the 3.6 branch, the ja/3.7 directory will be built using your 3.6 po files, which may (or may not) be desirable. Advantages are: - If a translation team want to translate 3.7 only, then can and 3.6 will be partially build using it - If a translation team is late adding a new branch, the new branch will still be built for them using their old translations, which for an unknown timespan will not diverge a lot - Crawlers can start discovering / indexing new branches before translators start working on them Disadvantages are more obvious: Translations are only partials. So, currently, if you push a 3.6 branch to python-docs-ja, ja/{2.7,3.5,3.6,3.7} will be built using it. -- Julien Palard https://mdk.fr
Last comment about this is that the current script building the documentation will automatically find the nearest branch for translations, see: https://github.com/python/docsbuild-scripts/blob/master/build_docs.py#L132 meaning that if you're working on the 3.6 branch, the ja/3.7 directory will be built using your 3.6 po files, which may (or may not) be desirable. Advantages are:
- If a translation team want to translate 3.7 only, then can and 3.6 will be partially build using it - If a translation team is late adding a new branch, the new branch will still be built for them using their old translations, which for an unknown timespan will not diverge a lot - Crawlers can start discovering / indexing new branches before translators start working on them
Disadvantages are more obvious: Translations are only partials.
Make sense.
So, currently, if you push a 3.6 branch to python-docs-ja, ja/{2.7,3.5,3.6,3.7} will be built using it.
OK, I pushed 2.7 and 3.6 branch. I won't push 3.5 branch because we haven't maintenanced it for months.
-- Julien Palard https://mdk.fr
Thanks
o/
OK, I pushed 2.7 and 3.6 branch. I won"t push 3.5 branch because we haven"t maintenanced it for months.
I added it to docsbuild-scripts: https://github.com/python/docsbuild-scripts/commit/00dbec7f463ba8c06091d0514... So it will be built, you'll be able to check if everything is OK and if it's OK we'll add it to the language pickers too. While I'm thinking, even if we're currently unable to skip building a given version in a given language, we can just not add 'ja' for a given release in the language picker (language pickers are versionned), so it will be built but not publicly, what do you think? -- Julien Palard https://mdk.fr
participants (3)
-
INADA Naoki -
Julien Palard -
Victor Stinner