Mailman 3 June 2018 - Doc-SIG

Migrating translations to 3.7
by Julien Palard Sept. 8, 2018

Sept. 8, 2018

Hi, We (France) migrated our translations to 3.7, if one want to follow here are the steps we used, here they are: - We "tx pull"ed transifex first. - We created the 3.7 git branch based on the 3.6 git branch - Used our "make merge" [1] to pull upstream pot files to our 3.7 branch (basically `sphinx-build -Q -b gettext` + `msgmerge`). - Configured 3.7 as a default branch on github - Changed the symlink 3 → 3.6 to 3 → 3.7 on docs.iad1.psf.io, so the viewers of docs.python.org/fr/3/ see 3.7 instead of 3.6.6 - Invalidated manually https://docs.python.org/fr/3/_static/documentation_options.js and https://docs.python.org/fr/3/ from fastly so the page and the version switcher display "3.7". The last two steps I can do them for you, (and yes we should automate them in docsbuild-scripts) don't hesitate to ask me to do them, by email or via IRC (I'm mdk on #python-doc on freenode). We're fixing fuzzy strings, and will wait for the ja team to update transifex projects so we can "tx push" on it (almost no french are working on tx, we're all working on github). -- Julien Palard https://mdk.fr

3 6

Brazilian Portuguese translation coordinate
by Marco Rougeth Aug. 2, 2018

Aug. 2, 2018

Hi, I'm Marco Rougeth <https://rgth.co>, member of the Brazilian Python community. I'm volunteering to coordinate the pt_BR translation of the Python documentation. We already have some strings translated on Transifex and we just merge efforts with our local Django community to speed up the translations. We're talking at a Telegram group (@pythonbr_i18n <https://telegram.me/joinchat/CjIqFj4UVvCtPnCwxUDJLA>). Bests, Marco.

5 11

About restructuring Transifex projects
by tomo cocoa June 29, 2018

June 29, 2018

Hi all, I am a member of Japanese translation team, and administrating documents along with INADA Naoki. I send this mail to Doc-SIG in order to have a talk about the Transifex projects of the organization "Python document translators" ( https://www.transifex.com/python-doc/) with members of translation teams. We, Naoki and I, are now preparing a Transifex project for Python 3.7 documentation. To avoid losing translation history, we will give the project for the newest version of Python a fixed name such like 'Python' or 'Python-newest', etc. This restructuring enables to keep translation history, but requests some work to edit Transifex project configuration. Diagram: On release of Python 3.8 Before: Python (for Python 3.7) Python 3.6 (for Python 3.6) After: Python (for Python 3.8) Python 3.7 (for Python 3.7) Python 3.6 (for Python 3.6) Please let me know if you have some opinions or questions. If this plan sounds good, I will operate the restructuring of Transifex projects. Best Regards, cocoatomo -- class Cocoatomo: name = 'cocoatomo' email_address = 'cocoatomo77(a)gmail.com' twitter_id = '@cocoatomo'

4 6

Coordinating zh_TW (Taiwanese Mandarin) Translations
by Adrian Liaw June 25, 2018

June 25, 2018

Hi all, This is Adrian from Taiwan, I'm currently a core organising staff at PyCon TW, and I would like to volunteer as the coordinator of zh_TW (Taiwanese Mandarin) translations! The current translations (although it's not complete enough to add it to the language switcher) are hosted on our own GitHub repository ( https://github.com/python-doc-tw/cpython-tw/tree/tw-3.6/Doc/locale/zh_TW/LC…) and on our own Transifex project ( https://www.transifex.com/python-tw-doc/python-36-tw), and I would like to migrate them into the PEP 545 workflow. However, I have a concern here, if I migrate the translations to the official Transifex project for Python documentation translations, that way it may completely lost the metadata of each string including history and translator, which I think is probably a bad thing to happen. I'm wondering if anyone knows whether there's some way to solve this problem or it's currently an unsupported feature (migrating translation metadata along with the translations) on Transifex? Thank you for taking time reading this, thank you for your contributions, and I'm super excited about making more contributions to the Python community! Best Regards, Wey-Han "Adrian" Liaw -- Wey-Han "Adrian" Liaw (@adrianliaw) http://linkedin.com/in/adrianliaw

4 10

Problems in pytest.1
by esr＠thyrsus.com June 14, 2018

June 14, 2018

This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database. See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand. I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template. -- Eric S. Raymond Problems with pytest.1: Broken command synopsis syntax. This may mean you're using a construction in the command synopsis other than the standard [ ] | { }, or it may mean you have running text in the command synopsis section (the latter is not technically an error, but most cases of it are impossible to translate into DocBook markup), or it may mean the command syntax fails to match the description. Running text cannot occur in Synopsis sections; this make lifting to XML impossible. This page was rather ill-formed, I have re-sectioned it. --- pytest.1-unpatched 2010-07-23 03:28:44.000000000 -0400 +++ pytest.1 2010-07-23 03:30:00.000000000 -0400 @@ -5,8 +5,7 @@ .SH SYNOPSIS usage: pytest [OPTIONS] [testfile [testpattern]] -.PP -examples: +.SH EXAMPLES .PP pytest path/to/mytests.py pytest path/to/mytests.py TheseTests @@ -18,7 +17,7 @@ pytest \fB\-\-coverage\fR test_foo.py .IP (only if logilab.devtools is available) -.SS "options:" +.SH OPTIONS .TP \fB\-h\fR, \fB\-\-help\fR show this help message and exit

3 2