New submission from Julien:

Hi,

The [french translation of the Python 
documentation](https://github.com/afpy/python_doc_fr) just hit a 21% coverage 
in terms of pageviews (According to statistics [nicely provided by 
EWDurbin](https://github.com/AFPy/python_doc_fr/issues/32#issuecomment-195071379)).
 (It's 14% of the total strings to translate).

I think it may be a good time to push the translation to *docs.python.org*, so 
french speaking people will be able to find it naturally, and more translators 
will be aware of it, increasing the translation speed.

Also it will probably motivate other translations (http://docs.python.jp/3/, 
http://docs.python.org.ar/tutorial/3/index.html, others ?) to work in a more 
standardized ways, and make their translations more discoverable.

So there's two discussions to have: The URL, and the "how".

# URL

I think the only reasonable possibility is *docs.python.org/{country_code}/*

Having a CCTLD per translation is near impossible (a LOT or work and highly 
time consuming) as some domains are unavailable like python.fr and some other 
have high restrictions like having a physical presence in the country (like 
python.ca, python.pt.br) or having a commercial relation with a local company 
like for python.com.tr).

Also it allows localization via *docs.python.org/fr_FR/* even if I don't think 
we need it soon.

If you have other ideas, better than *docs.python.org/fr/*, that's why this 
issue is opened.

# How to

We have a 
[Makefile](https://github.com/AFPy/python_doc_fr/blob/master/Makefile) which 
like [docsbuild-scripts](https://github.com/python/docsbuild-scripts) delegates 
naturally most of its work to the sphinx Makefile in *Doc/Makefile*, and is 
capable of building french versions of 2.7, 3.3, 3.4, and 3.5 in a simple 
invocation of `make build_all MODE=autobuild-stable` (cloning itself from the 
github repository, applying various patches (typically to configure sphinx to 
generate french). 3.2 is also possible but not built by default (no 
autobuild-html in its sphinx Makefile). 

I think docsbuild-scripts may delegate the french generation by simply 
cloning/updating our repository and calling our makefile. A patch (attached) 
will be necessary in docsbuild-scripts to copy generated doc to /fr/ and send 
purges to the CDN.

Finally, once all this is running, we'll start a discussion about cross-linking 
both documentations, probably reopening 
https://github.com/sphinx-doc/sphinx/issues/1246.

----------
assignee: docs@python
components: Documentation
files: build_doc_fr.patch
keywords: patch
messages: 261654
nosy: benjamin.peterson, docs@python, sizeof
priority: normal
severity: normal
status: open
title: Provide translated french translation on docs.python.org
type: enhancement
Added file: http://bugs.python.org/file42150/build_doc_fr.patch

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26546>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to