>
> 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
_______________________________________________
Doc-SIG maillist - Doc-SIG@python.org
https://mail.python.org/mailman/listinfo/doc-sig
