Hi Brett, On Wed, 29 Mar 2017 at 13:13 Julien Palard <julien at palard.fr> wrote: What kind of support does Read the Docs have for translations? I have no active plans to push for this but it has been idea in the back of my head for a while so it would be good to know if such a move would make this easier or harder. [...] Their language tags are simplified too (redundency removed (fr-FR → fr)) but not lowercased, and they use underscore "instead of" dashes as a separator, see for example: - https://docs.phpmyadmin.net/fr/latest/ - https://docs.phpmyadmin.net/pt_BR/latest/ while the PEP proposes /pt-br/ instead. .. [1] Project with multiple translations (https://docs.readthedocs.io/en/latest/localization.html#project-with-multiple-translations) Should we just match what Read the Docs does then? As I prefer our notation (/pt-br/) over Read the Docs one (/pt_BR/), I'd prefer if we stick on our notation. They are not against changing and looks like they're OK with our notation: https://github.com/rtfd/readthedocs.org/issues/2763 -- Julien Palard https://mdk.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170514/13d1b9b3/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4