On Fri, 24 Feb 2017 at 03:50 INADA Naoki <songofacandy at gmail.com> wrote: > > Where should these translated docs live and how does one make it clear to > > users reading them that doc bugs shouldn't be submitted to the main bug > > tracker/github repo? > > > > We setup github page. See https://python-doc-ja.github.io/py36/ (note > that > version switcher won't work because this html is build for docs.python.jp > .) > > I reserved "python-docs" organization. So we can use URL like > https://python-doc.github.io/<lang>/3.6/ > (Because the organization name looks "something official", I won't use it > until we get consensus about it.) > > For issue tracker, bugs.html must mention about translated document, before > mention to normal issue tracker. > It's getting a little hard to tease out what exactly is being asked at this point. Perhaps it's time to move the discussion over to a translation SIG (which probably needs to be created unless the old https://mail.python.org/mailman/listinfo/i18n-sig makes sense)? That way active translators can figure out exactly what they want to ask of python-dev in terms of support and we can have a more focused discussion. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170225/4eee0b8a/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