From esr at thyrsus.com Tue Jun 12 15:16:14 2018 From: esr at thyrsus.com (esr at thyrsus.com) Date: Tue, 12 Jun 2018 15:16:14 -0400 (EDT) Subject: [Doc-SIG] Problems in pytest.1 Message-ID: <20180612191614.250343A4F4F@snark.thyrsus.com> 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 -------------- next part -------------- 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 From julien at palard.fr Wed Jun 13 18:11:30 2018 From: julien at palard.fr (Julien Palard) Date: Wed, 13 Jun 2018 18:11:30 -0400 Subject: [Doc-SIG] Problems in pytest.1 In-Reply-To: <20180612191614.250343A4F4F@snark.thyrsus.com> References: <20180612191614.250343A4F4F@snark.thyrsus.com> Message-ID: <-8DmnKifSOUoqlx3B0HXu6OXnZ4Ywaf1JdM5_FNlS28T-MznuPxDMf8-J0QgjooTqlTgHWgFnrS-g8qMUmP80vuDIqbbGOU_pYcK5VwWeL8=@palard.fr> Hi, Thanks for caring about documentations and taking time to write scripts to report bugs. I checked and spotted two python-related projects: - pylint.1 which has been fixed (differently) here: https://github.com/pycqa/pylint/commit/6e2c366ff8752a3d98cab9acbd8221868c69f820 - pytest.1, in which package did you find it? I was unable to find the same issue on various pytest.1 manpages. I cloned pytest and tried and I don't see the section your patch tries to fix. For the record here's how I build locally the manpage of pytest : git clone https://github.com/pytest-dev/pytest.git cd pytest python3 -m venv /tmp/pytest . /tmp/pytest/bin/activate python3 -m pip install sphinx sphinxcontrib-trio python3 -m pip install . make -C doc/en/ man less doc/en/_build/man/pytest.1 Also please note those two projects have their own bugtrackers on github, and you may have more success there than here. Bests, ?--? Julien Palard https://mdk.fr? From esr at thyrsus.com Wed Jun 13 20:57:54 2018 From: esr at thyrsus.com (Eric S. Raymond) Date: Wed, 13 Jun 2018 20:57:54 -0400 Subject: [Doc-SIG] Problems in pytest.1 In-Reply-To: <-8DmnKifSOUoqlx3B0HXu6OXnZ4Ywaf1JdM5_FNlS28T-MznuPxDMf8-J0QgjooTqlTgHWgFnrS-g8qMUmP80vuDIqbbGOU_pYcK5VwWeL8=@palard.fr> References: <20180612191614.250343A4F4F@snark.thyrsus.com> <-8DmnKifSOUoqlx3B0HXu6OXnZ4Ywaf1JdM5_FNlS28T-MznuPxDMf8-J0QgjooTqlTgHWgFnrS-g8qMUmP80vuDIqbbGOU_pYcK5VwWeL8=@palard.fr> Message-ID: <20180614005754.GC23233@thyrsus.com> Julien Palard : > Hi, > > Thanks for caring about documentations and taking time to write scripts to report bugs. > > I checked and spotted two python-related projects: > > - pylint.1 which has been fixed (differently) here: https://github.com/pycqa/pylint/commit/6e2c366ff8752a3d98cab9acbd8221868c69f820 I will investigate. > - pytest.1, in which package did you find it? I was unable to find the same issue on various pytest.1 manpages. I'm no longer sure where that page came from. I'll drop it out of my patch list and see if anything with the same name comes up in testing. -- Eric S. Raymond My work is funded by the Internet Civil Engineering Institute: https://icei.org Please visit their site and donate: the civilization you save might be your own. From adrianliaw2000 at gmail.com Fri Jun 22 15:18:07 2018 From: adrianliaw2000 at gmail.com (Adrian Liaw) Date: Sat, 23 Jun 2018 03:18:07 +0800 Subject: [Doc-SIG] Coordinating zh_TW (Taiwanese Mandarin) Translations In-Reply-To: References: Message-ID: Hi all, I think we're ready to migrate our repository as we've set up all the requirements for docsbuild-scripts to work, it has currently only 3.6 branch which has the same hierarchy as other translation repos, and master branch for informations for translators. The current repo is at https://github.com/python-doc-tw/python-docs-zh-tw, I've requested a repository transfer to Python's GitHub organisation, please approve if it's appropriate. Thank you! Best Regards, Adrian On Sun, 27 May 2018 at 20:38 Adrian Liaw wrote: > Thanks everyone for your great comments and all the useful informations. > > I'd say I'm agreeing with using zh-tw language tag. And I personally > believe adding "Hant" or "Hans" tag is somehow redundant, the reason is > that you can usually assume its writing system by region. e.g. you can > assume zh-cn to be written in Simplified Chinese, zh-tw to be in > Traditional Chinese, zh-hk (Hong Kong Cantonese) to be in Traditional > Chinese, zh-sg (Singaporean Mandarin) to be in Simplified Chinese, etc. > > Regarding the repository setup that Julien mentioned earlier, big thanks > to Julien for providing lots of inspirations, I'll stay with our own > Transifex project, and I'll setup the project and a proper contribution > workflow, I'll get back to you as soon as I done it! > > Best Regards, > Adrian > > On Sun, 27 May 2018 at 02:08 Julien Palard via Doc-SIG > wrote: > >> > So I'd like to keep using zh-cn and zh-tw as I didn't see there's much >> translation effort in other varieties. >> >> OK, works for me. And if in the future they start translating we'll still >> be able to affect them specific tags as needed, like zh-Hant-HK, we're not >> locking them out by choosing zh-cn and zh-tw. >> >> > BTW, for zh_CN translations, we are slow at reaching the coverage. >> However I've contacted Xiang Zhang(The only person I known using Chinese >> and also a >> > core developer) to get the work organized. >> >> Xiang Zhang told in january 2018 he won't be "as free as before" [1], >> already in a discussion about chinese translations : >> https://mail.python.org/pipermail/doc-sig/2018-January/003991.html. >> >> [1]: https://mail.python.org/pipermail/doc-sig/2018-January/003994.html >> >> ?-- >> Julien Palard >> https://mdk.fr? >> >> _______________________________________________ >> Doc-SIG maillist - Doc-SIG at python.org >> https://mail.python.org/mailman/listinfo/doc-sig >> > -- > Wey-Han "Adrian" Liaw (@adrianliaw) > http://linkedin.com/in/adrianliaw > -- Wey-Han "Adrian" Liaw (@adrianliaw) http://linkedin.com/in/adrianliaw -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrianliaw2000 at gmail.com Fri Jun 22 15:20:37 2018 From: adrianliaw2000 at gmail.com (Adrian Liaw) Date: Sat, 23 Jun 2018 03:20:37 +0800 Subject: [Doc-SIG] Coordinating zh_TW (Taiwanese Mandarin) Translations In-Reply-To: References: Message-ID: Sorry, let me correct my previous message, I failed to request a transfer, seems like we'll need a repository in Python's GitHub organisation. Thanks! Best Regards, Adrian On Sat, 23 Jun 2018 at 03:18 Adrian Liaw wrote: > Hi all, > > I think we're ready to migrate our repository as we've set up all the > requirements for docsbuild-scripts to work, it has currently only 3.6 > branch which has the same hierarchy as other translation repos, and master > branch for informations for translators. The current repo is at > https://github.com/python-doc-tw/python-docs-zh-tw, I've requested a > repository transfer to Python's GitHub organisation, please approve if it's > appropriate. Thank you! > > Best Regards, > Adrian > > On Sun, 27 May 2018 at 20:38 Adrian Liaw wrote: > >> Thanks everyone for your great comments and all the useful informations. >> >> I'd say I'm agreeing with using zh-tw language tag. And I personally >> believe adding "Hant" or "Hans" tag is somehow redundant, the reason is >> that you can usually assume its writing system by region. e.g. you can >> assume zh-cn to be written in Simplified Chinese, zh-tw to be in >> Traditional Chinese, zh-hk (Hong Kong Cantonese) to be in Traditional >> Chinese, zh-sg (Singaporean Mandarin) to be in Simplified Chinese, etc. >> >> Regarding the repository setup that Julien mentioned earlier, big thanks >> to Julien for providing lots of inspirations, I'll stay with our own >> Transifex project, and I'll setup the project and a proper contribution >> workflow, I'll get back to you as soon as I done it! >> >> Best Regards, >> Adrian >> >> On Sun, 27 May 2018 at 02:08 Julien Palard via Doc-SIG < >> doc-sig at python.org> wrote: >> >>> > So I'd like to keep using zh-cn and zh-tw as I didn't see there's >>> much translation effort in other varieties. >>> >>> OK, works for me. And if in the future they start translating we'll >>> still be able to affect them specific tags as needed, like zh-Hant-HK, >>> we're not locking them out by choosing zh-cn and zh-tw. >>> >>> > BTW, for zh_CN translations, we are slow at reaching the coverage. >>> However I've contacted Xiang Zhang(The only person I known using Chinese >>> and also a >>> > core developer) to get the work organized. >>> >>> Xiang Zhang told in january 2018 he won't be "as free as before" [1], >>> already in a discussion about chinese translations : >>> https://mail.python.org/pipermail/doc-sig/2018-January/003991.html. >>> >>> [1]: https://mail.python.org/pipermail/doc-sig/2018-January/003994.html >>> >>> ?-- >>> Julien Palard >>> https://mdk.fr? >>> >>> _______________________________________________ >>> Doc-SIG maillist - Doc-SIG at python.org >>> https://mail.python.org/mailman/listinfo/doc-sig >>> >> -- >> Wey-Han "Adrian" Liaw (@adrianliaw) >> http://linkedin.com/in/adrianliaw >> > -- > Wey-Han "Adrian" Liaw (@adrianliaw) > http://linkedin.com/in/adrianliaw > -- Wey-Han "Adrian" Liaw (@adrianliaw) http://linkedin.com/in/adrianliaw -------------- next part -------------- An HTML attachment was scrubbed... URL: From julien at palard.fr Sun Jun 24 02:22:26 2018 From: julien at palard.fr (Julien Palard) Date: Sun, 24 Jun 2018 02:22:26 -0400 Subject: [Doc-SIG] Coordinating zh_TW (Taiwanese Mandarin) Translations In-Reply-To: References: Message-ID: <4gAcL6Pt4PdiIPVZgpeH8GW5gDJdmgDdHYE8JOyRAYBNwlne59EUh9Eh2Lj12f8dy_iV9O7CQxiTf2toLxECermfFzOZBsPkh6gXl83PEjo=@palard.fr> Hi Adrian, I created the repository https://github.com/python/python-docs-zh-tw and invited you with commit rights on it. -- Julien Palard https://mdk.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrianliaw2000 at gmail.com Mon Jun 25 14:57:28 2018 From: adrianliaw2000 at gmail.com (Adrian Liaw) Date: Tue, 26 Jun 2018 02:57:28 +0800 Subject: [Doc-SIG] Coordinating zh_TW (Taiwanese Mandarin) Translations In-Reply-To: <4gAcL6Pt4PdiIPVZgpeH8GW5gDJdmgDdHYE8JOyRAYBNwlne59EUh9Eh2Lj12f8dy_iV9O7CQxiTf2toLxECermfFzOZBsPkh6gXl83PEjo=@palard.fr> References: <4gAcL6Pt4PdiIPVZgpeH8GW5gDJdmgDdHYE8JOyRAYBNwlne59EUh9Eh2Lj12f8dy_iV9O7CQxiTf2toLxECermfFzOZBsPkh6gXl83PEjo=@palard.fr> Message-ID: Hi Julien, Thanks a lot! I've moved our repository there. Cheers! On Sun, 24 Jun 2018 at 14:22 Julien Palard wrote: > Hi Adrian, > > I created the repository https://github.com/python/python-docs-zh-tw and > invited you with commit rights on it. > > -- > Julien Palard > https://mdk.fr > > > -- Wey-Han "Adrian" Liaw (@adrianliaw) http://linkedin.com/in/adrianliaw -------------- next part -------------- An HTML attachment was scrubbed... URL: From cocoatomo77 at gmail.com Mon Jun 25 14:01:20 2018 From: cocoatomo77 at gmail.com (tomo cocoa) Date: Tue, 26 Jun 2018 03:01:20 +0900 Subject: [Doc-SIG] About restructuring Transifex projects Message-ID: 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 at gmail.com' twitter_id = '@cocoatomo' -------------- next part -------------- An HTML attachment was scrubbed... URL: From julien at palard.fr Tue Jun 26 01:23:13 2018 From: julien at palard.fr (Julien Palard) Date: Tue, 26 Jun 2018 01:23:13 -0400 Subject: [Doc-SIG] About restructuring Transifex projects In-Reply-To: References: Message-ID: Hi, > Please let me know if you have some opinions or questions. > If this plan sounds good, I will operate the restructuring of Transifex projects. LGTM but I don't know Transifex well so I may miss something. ?--? Julien Palard https://mdk.fr? From adrianliaw2000 at gmail.com Tue Jun 26 04:28:24 2018 From: adrianliaw2000 at gmail.com (Adrian Liaw) Date: Tue, 26 Jun 2018 16:28:24 +0800 Subject: [Doc-SIG] About restructuring Transifex projects In-Reply-To: References: Message-ID: Hi cocoatomo, I think keeping the translation history is a perfect idea. However, will the previous version lose its translation history? e.g. For this scenario you mentioned: > 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) Technically this is creating a new project on Transifex called "Python 3.7", that way the "Python 3.7" project might lose its translation history for the same reason that creating a new project for newer Python version is going to lose the previous translation history. I'm not sure how Transifex works in this scenario as I'm also not very familiar with Transifex and I may be wrong. Thanks so much! On Tue, 26 Jun 2018 at 13:38 Julien Palard via Doc-SIG wrote: > Hi, > > > Please let me know if you have some opinions or questions. > > If this plan sounds good, I will operate the restructuring of Transifex > projects. > > LGTM but I don't know Transifex well so I may miss something. > > ?-- > Julien Palard > https://mdk.fr? > > > > _______________________________________________ > Doc-SIG maillist - Doc-SIG at python.org > https://mail.python.org/mailman/listinfo/doc-sig > -- Wey-Han "Adrian" Liaw (@adrianliaw) http://linkedin.com/in/adrianliaw -------------- next part -------------- An HTML attachment was scrubbed... URL: From songofacandy at gmail.com Tue Jun 26 04:38:55 2018 From: songofacandy at gmail.com (INADA Naoki) Date: Tue, 26 Jun 2018 17:38:55 +0900 Subject: [Doc-SIG] About restructuring Transifex projects In-Reply-To: References: Message-ID: On Tue, Jun 26, 2018 at 5:28 PM Adrian Liaw wrote: > Hi cocoatomo, > > I think keeping the translation history is a perfect idea. However, will > the previous > version lose its translation history? > ?Yes. It's not easy to track "who / when this paragraph is translated?" > e.g. For this scenario you mentioned: > > > 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) > > Technically this is creating a new project on Transifex called "Python > 3.7", that way > the "Python 3.7" project might lose its translation history for the same > reason that > creating a new project for newer Python version is going to lose the > previous > translation history. > ?Yes, you're right.? Transifex doesn't support branching. We need to drop history from 3.7 or master. Since master branch is maintained for long time in the future, I think history of master branch is more important. > I'm not sure how Transifex works in this scenario as I'm also not > very familiar with Transifex and I may be wrong. > > Thanks so much! > > On Tue, 26 Jun 2018 at 13:38 Julien Palard via Doc-SIG > wrote: > >> Hi, >> >> > Please let me know if you have some opinions or questions. >> > If this plan sounds good, I will operate the restructuring of Transifex >> projects. >> >> LGTM but I don't know Transifex well so I may miss something. >> >> ?-- >> Julien Palard >> https://mdk.fr? >> >> >> >> _______________________________________________ >> Doc-SIG maillist - Doc-SIG at python.org >> https://mail.python.org/mailman/listinfo/doc-sig >> > -- > Wey-Han "Adrian" Liaw (@adrianliaw) > http://linkedin.com/in/adrianliaw > _______________________________________________ > Doc-SIG maillist - Doc-SIG at python.org > https://mail.python.org/mailman/listinfo/doc-sig > -- INADA Naoki -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrianliaw2000 at gmail.com Tue Jun 26 04:49:10 2018 From: adrianliaw2000 at gmail.com (Adrian Liaw) Date: Tue, 26 Jun 2018 16:49:10 +0800 Subject: [Doc-SIG] About restructuring Transifex projects In-Reply-To: References: Message-ID: On Tue, 26 Jun 2018 at 16:39 INADA Naoki wrote: > Since master branch is maintained for long time in the future, I think > history of master branch is more important. > Agree. Thanks Naoki! -- Wey-Han "Adrian" Liaw (@adrianliaw2000) https://linkedin.com/in/adrianliaw https://github.com/adrianliaw -------------- next part -------------- An HTML attachment was scrubbed... URL: From cocoatomo77 at gmail.com Wed Jun 27 22:57:32 2018 From: cocoatomo77 at gmail.com (tomo cocoa) Date: Thu, 28 Jun 2018 11:57:32 +0900 Subject: [Doc-SIG] About restructuring Transifex projects In-Reply-To: References: Message-ID: Thank you for your helpful comments. It seems that the restructuring plan is acceptable. I will announce this restructuring and necessary works on document builds to all translators of the Transifex team using Transifex announcement feature ( https://docs.transifex.com/teams/announcements-and-discussions). After announcement, I will start restructuring Transifex projects. Best Regards, cocoatomo On Tue, 26 Jun 2018 at 17:50, Adrian Liaw wrote: > On Tue, 26 Jun 2018 at 16:39 INADA Naoki wrote: > >> Since master branch is maintained for long time in the future, I think >> history of master branch is more important. >> > > Agree. Thanks Naoki! > -- > Wey-Han "Adrian" Liaw (@adrianliaw2000) > https://linkedin.com/in/adrianliaw > https://github.com/adrianliaw > _______________________________________________ > Doc-SIG maillist - Doc-SIG at python.org > https://mail.python.org/mailman/listinfo/doc-sig > -- class Cocoatomo: name = 'cocoatomo' email_address = 'cocoatomo77 at gmail.com' twitter_id = '@cocoatomo' -------------- next part -------------- An HTML attachment was scrubbed... URL: From julien at palard.fr Thu Jun 28 10:03:11 2018 From: julien at palard.fr (Julien Palard) Date: Thu, 28 Jun 2018 10:03:11 -0400 Subject: [Doc-SIG] Migrating translations to 3.7 Message-ID: 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? From flowdas at gmail.com Thu Jun 28 15:43:25 2018 From: flowdas at gmail.com (=?utf-8?B?IkZsb3dkYXMgKOyYpOuPmeq2jCki?=) Date: Fri, 29 Jun 2018 04:43:25 +0900 Subject: [Doc-SIG] Migrating translations to 3.7 In-Reply-To: References: Message-ID: Hi, Python-docs-ko have also prepared 3.7 branch. Please, change links to finish 3.7 migration. > 2018. 6. 28. ?? 11:03, Julien Palard via Doc-SIG ??: > > 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? > > _______________________________________________ > Doc-SIG maillist - Doc-SIG at python.org > https://mail.python.org/mailman/listinfo/doc-sig From cocoatomo77 at gmail.com Fri Jun 29 17:57:09 2018 From: cocoatomo77 at gmail.com (tomo cocoa) Date: Sat, 30 Jun 2018 06:57:09 +0900 Subject: [Doc-SIG] About restructuring Transifex projects In-Reply-To: References: Message-ID: Hi all, I have just finished setting up the Transifex project for Python 3.6 and 3.7. Configuration for these project is as follows: Python - project for Python 3.7 - URL: https://www.transifex.com/python-doc/python-newest/ Python 3.6 - project for Python 3.6 - URL: https://www.transifex.com/python-doc/python-36/ For both projects, source strings are already updated, and some translation strings are registered from Translation Memory. So you can start translating at this very moment! Best Regards, cocoatomo On Thu, 28 Jun 2018 at 11:57, tomo cocoa wrote: > Thank you for your helpful comments. > > It seems that the restructuring plan is acceptable. > I will announce this restructuring and necessary works on document builds > to all translators of the Transifex team > using Transifex announcement feature ( > https://docs.transifex.com/teams/announcements-and-discussions). > > After announcement, I will start restructuring Transifex projects. > > Best Regards, > cocoatomo > > > On Tue, 26 Jun 2018 at 17:50, Adrian Liaw > wrote: > >> On Tue, 26 Jun 2018 at 16:39 INADA Naoki wrote: >> >>> Since master branch is maintained for long time in the future, I think >>> history of master branch is more important. >>> >> >> Agree. Thanks Naoki! >> -- >> Wey-Han "Adrian" Liaw (@adrianliaw2000) >> https://linkedin.com/in/adrianliaw >> https://github.com/adrianliaw >> _______________________________________________ >> Doc-SIG maillist - Doc-SIG at python.org >> https://mail.python.org/mailman/listinfo/doc-sig >> > > > -- > class Cocoatomo: > name = 'cocoatomo' > email_address = 'cocoatomo77 at gmail.com' > twitter_id = '@cocoatomo' > -- class Cocoatomo: name = 'cocoatomo' email_address = 'cocoatomo77 at gmail.com' twitter_id = '@cocoatomo' -------------- next part -------------- An HTML attachment was scrubbed... URL: