From albertasgim at gmail.com Sun Jul 7 07:15:17 2019 From: albertasgim at gmail.com (niekas) Date: Sun, 7 Jul 2019 14:15:17 +0300 Subject: [Doc-SIG] Python docs translation to Lithuanian language Message-ID: Hi, ? I want to set up a team of translators to translate Python documentation to Lithuanian language. I am a little bit confused about the first steps I have to do as a team coordinator. I think Trasifex would be enough for Lithuanian team for the beginning. The steps I have already done: ?- I have requested for Lithuanian language to be added to Python translations at https://www.transifex.com/python-doc/public/? and it was approved. ?- I have requested to be added to the Lithuanian language translation team. ?- I have signed the Contributors Agreement (https://www.python.org/psf/contrib/contrib-form/). However I am still not added to Lithuanian translation team. I wonder what do I have to do next: wait more time or do I have to create `python-docs-lt` repository at my GitHub account? Best regards, Albertas Gimbutas From julien at palard.fr Sun Jul 7 11:12:32 2019 From: julien at palard.fr (Julien Palard) Date: Sun, 07 Jul 2019 15:12:32 +0000 Subject: [Doc-SIG] Python docs translation to Lithuanian language In-Reply-To: References: Message-ID: Hi Albertas Gimbutas! > I want to set up a team of translators to translate Python > documentation to Lithuanian language. That's a very good news! Welcome on board! > I am a little bit confused about the first steps I have to do as a team coordinator. That's huge, and if you read PEP 545 I'm not sure it make it easier. There's https://devguide.python.org/documenting/#translating that is a bit more readable. But in a nutshell: as a coordinator, you have to find and gather translators around the project. In France here we're organizing meetups to translate, it help spreading the word and finding new people, since we're doing workshops translations goes really faster: We started with events around mid 2018, but we are doing them regularily every month since jan 2019: https://julienpalard.frama.io/write-the-docs-paris-19/#/2/5 See between 2015 and 2016 this almost flat but not flat line? That's me translating alone. (ignore huge bumps in 2016, that's me dropping sections I won't translate, so it "artificially" bumps the progression). > I think Trasifex would be enough for Lithuanian team for the beginning. As PEP 545 say and devguide say: you're free to choose (and to change as needed). > However I am still not added to Lithuanian translation team. That's done now. > do I have to create `python-docs-lt` repository at my GitHub account? That will be usefull only when you'll decide you need a preview on docs.python.org/lt/, as long as you don't need a preview there, you don't really need a github repo. Don't hesitate to ask questions (yes we're on #python-doc, I'm mdk, don't hesitate to highlight me). Bests, --? Julien Palard https://mdk.fr From arj.python at gmail.com Sun Jul 7 14:25:41 2019 From: arj.python at gmail.com (Abdur-Rahmaan Janhangeer) Date: Sun, 7 Jul 2019 22:25:41 +0400 Subject: [Doc-SIG] Separate Org Message-ID: Greetings All I was thinking if we could set up a separate github org repo dedicated for translations where we can regroup all translations, infos and tools The aim is focus and freeing up the main Cpython org (not cluttering it up) ! -- Abdur-Rahmaan Janhangeer Mauritius -------------- next part -------------- An HTML attachment was scrubbed... URL: From julien at palard.fr Sun Jul 7 16:13:20 2019 From: julien at palard.fr (Julien Palard) Date: Sun, 07 Jul 2019 20:13:20 +0000 Subject: [Doc-SIG] Separate Org In-Reply-To: References: Message-ID: > I was thinking if we could set up a separate github org repo dedicated for translations where we can regroup all translations, infos and tools Do you mean a separate org or a separate repo? I have hard times to parse "org repo", I will assome "a separate organization". I don't think scattering things is a good thing, mainly It makes out-of-main-organization repos hard to discover. As long as there is not a big gain of moving things, I prefer the status quo of not moving things. > The aim is focus Can you elaborate? I don't get it. > and freeing up the main Cpython org (not cluttering it up) ! I don't feel we're cluttering the /python/ org: translation represents 9/74 repos. At worse it shows there's activity on translations which can bring more translators. If the org starts to be "hard to browse" it's a github UI/UX issue they have to fix (Sub-orgs? Directories? Namespaces? Namespaces are one honking great idea -- let's do more of those!). --? Julien Palard https://mdk.fr From arj.python at gmail.com Sun Jul 7 22:02:23 2019 From: arj.python at gmail.com (Abdur-Rahmaan Janhangeer) Date: Mon, 8 Jul 2019 06:02:23 +0400 Subject: [Doc-SIG] Separate Org In-Reply-To: References: Message-ID: Abdur-Rahmaan Janhangeer Mauritius On Mon, 8 Jul 2019, 00:13 Julien Palard, wrote: > > I was thinking if we could set up a separate github org repo dedicated > for translations where we can regroup all translations, infos and tools > Do you mean a separate org or a separate repo? I have hard times to parse > "org repo", I will assome "a separate organization". > My mistake, organisation. A separate organisation > The aim is focus > > Can you elaborate? I don't get it. > People contributing to translations have a clear space > and freeing up the main Cpython org (not cluttering it up) ! > > I don't feel we're cluttering the /python/ org: translation represents > 9/74 repos. Imagine it for 90 languages? We can then also host beginner translations. Someone who wants to contribute can browse and see. Associated helping tools/scripts on the CPython org are for facilitating CPython dev, not for translations. -------------- next part -------------- An HTML attachment was scrubbed... URL: From engelbert.gruber at gmail.com Sun Jul 21 05:39:58 2019 From: engelbert.gruber at gmail.com (engelbert gruber) Date: Sun, 21 Jul 2019 11:39:58 +0200 Subject: [Doc-SIG] docutils release 0.15 Message-ID: Note Docutils 0.15.x is compatible with Python versions 2.6, 2.7 and 3.3 to 3.5 * reStructuredText: - Allow embedded colons in field list field names (before, tokens like ``:this:example:`` were considered ordinary text). - Fixed a bug with the "trim" options of the "unicode" directive. * languages: Added Korean (ko) mappings and latin. * Several fixes to keep mor information on source in parsed elements, isolate documents roles from other documents parsed, smartquotes, table gets width and latex table multicolumn cells, ... all the best engelbert -------------- next part -------------- An HTML attachment was scrubbed... URL: From rgammans at gammascience.co.uk Sun Jul 21 12:57:58 2019 From: rgammans at gammascience.co.uk (Roger Gammans) Date: Sun, 21 Jul 2019 17:57:58 +0100 Subject: [Doc-SIG] docutils release 0.15 In-Reply-To: References: Message-ID: <8EC23C11-74A8-4C61-BF4F-1674E6B1ECC8@gammascience.co.uk> On 21 July 2019 10:39:58 BST, engelbert gruber wrote: >Note > Docutils 0.15.x is compatible with Python versions 2.6, 2.7 and 3.3 to >3.5 Is there a problem with 3.6, 3.7 and 3.8 betas? Or is this an oversight in the announcement text -- Sent from my Android device with K-9 Mail. Please excuse my brevity.