Re: [core-workflow] Where to host documentation? (was: Voting on possible subdomains for the devguide)
As another note, PEP 545 (https://www.python.org/dev/peps/pep-0545/) requires a lot of changes to how Python generates its documentation. RTD already has support for this (http://docs.readthedocs.io/en/latest/localization.html) and I'd argue this is another classic case of duplicating effort, instead of working together to make the solution that the entire community uses better. I'd love to have the work going towards making Python's i18n story better also help make the community's i18n story better. Cheers, Eric -- Eric Holscher Maker of the internet residing in Portland, Oregon http://ericholscher.com
Eric Holscher wrote:
As another note, PEP 545 (https://www.python.org/dev/peps/pep-0545/) requires a lot of changes to how Python generates its documentation. RTD already has support for this (http://docs.readthedocs.io/en/latest/localization.html) and I'd argue this is another classic case of duplicating effort, instead of working together to make the solution that the entire community uses better. I'd love to have the work going towards making Python's i18n story better also help make the community's i18n story better.
Cheers, Eric
I think it is wonderful that there is energy and enthusiasm behind translation of documentation. The Django documentation (https://docs.djangoproject.com/ja/1.11/) provides a very nice user experience for different languages. I have to agree with Eric that it would be great to leverage the effort already done by RTD and the Django community. Warmly, Carol
participants (2)
-
Carol Willing -
Eric Holscher