From i at wi24rd.ml Mon Jul 2 09:43:22 2018 From: i at wi24rd.ml (Zephyr Waitzman) Date: Mon, 2 Jul 2018 21:43:22 +0800 Subject: [Doc-SIG] Question for Simplified Chinese translation Message-ID: Hello, everyone. I'm glad to join this list today, and I'm interested in translating the docmentation into Simplified Chinese. I look through some information about how to work with you [1][2]. I read just a little history mail list message like this [3], and congratulation to zh-tw group's effort, and I think the Simplified Chinese version should use zh-cn tag, because of the existing naming convention. >From historic talk I see Xiang Zhang[4] doesn't have free time, however, I want to konw more about the current state about zh-cn, is everyone can help me?Another question is how dose transifex's [7] Chinese process work? [10] is a talk from python-cn's googlegroups about zh-cn's translation, where someone say that his application for transifex doesn't receive reponse. My idea including: 1. Use some library such as opencc[5] to interact zh-tw with zh-cn, and use zhwiki's regional word convertor [6] to combinate Chinese translation. 2. Base some works like [8](for tutorial part) [9](which is synced with transifex). BTW, I think I can be the coordinator with the responsibilty, and I wish there is someone can mentor me, and I'm a novice, if there is any problem, please pick up. Maybe, I don't have much free time in these 20 days for the preparation of final exam, but later, I will have much time for such work during my holiday. [1] https://www.python.org/dev/peps/pep-0545/ [2] https://mdk.fr/blog/python-documentation-translation.html [3] https://mail.python.org/pipermail/doc-sig/2018-June/004041.html [4] https://bugs.python.org/user21530 [5] https://github.com/BYVoid/OpenCC [6] https://zh.wikipedia.org/wiki/%E6%A8%A1%E5%9D%97:CGroup/IT [7] https://www.transifex.com/python-doc/public/ [8] https://github.com/sixu05202004/pythontutorial3 [9] https://github.com/zhsj/python-docs-zh-cn [10] https://groups.google.com/forum/#!topic/python-cn/8H4qhhI6khw -------------- next part -------------- An HTML attachment was scrubbed... URL: From zsj950618 at gmail.com Mon Jul 2 12:20:20 2018 From: zsj950618 at gmail.com (Shengjing Zhu) Date: Tue, 3 Jul 2018 00:20:20 +0800 Subject: [Doc-SIG] Question for Simplified Chinese translation In-Reply-To: References: Message-ID: On Mon, Jul 2, 2018 at 11:36 PM Zephyr Waitzman wrote: > > Hello, everyone. > From historic talk I see Xiang Zhang[4] doesn't have free time, however, I want to konw more about the current state about zh-cn, is everyone can help me?Another question is how dose transifex's [7] Chinese process work? transifex is easy to use, you just need to sign up and join the Chinese(China) team, which is for Simplified Chinese translation. > [10] is a talk from python-cn's googlegroups about zh-cn's translation, where someone say that his application for transifex doesn't receive reponse. I think the admin of the transifex project is very responsive for the join request. For example my join request got replied within 24 hours. But it's said to say, I didn't see any activity for the current Chinese coordinator of the transifex project. And there's no reviewer. > > My idea including: > 1. Use some library such as opencc[5] to interact zh-tw with zh-cn, and use zhwiki's regional word convertor [6] to combinate Chinese translation. opencc is great tool. But I don't think you can _just_ relay on it. You still need review every words, and adjust the sentences in a preferred way. For example, I usually use google translation when I translate, but I won't just copy and paste. I think it's same for opencc. The current problem for Simplified Chinese translation is, we don't have many people evolved in. I started the thread on python-cn mailing list and the Telegram group, but there're very few people doing the work. -- Regards, Shengjing Zhu From zsj950618 at gmail.com Mon Jul 2 12:45:19 2018 From: zsj950618 at gmail.com (Shengjing Zhu) Date: Tue, 3 Jul 2018 00:45:19 +0800 Subject: [Doc-SIG] Question for Simplified Chinese translation In-Reply-To: References: Message-ID: On Mon, Jul 2, 2018 at 11:36 PM Zephyr Waitzman wrote: > My idea including: > 1. Use some library such as opencc[5] to interact zh-tw with zh-cn, and use zhwiki's regional word convertor [6] to combinate Chinese translation. > 2. Base some works like [8](for tutorial part) [9](which is synced with transifex). I just looked at the current status for zh_CN/zh_TW translation coverage. For python-newest, zh_CN is 3.06%, zh_TW is 0.95%; for python-36, zh_CN is 0.93%, zh_TW is 1%. Both are far behind :( ,so opencc won't help much here. And link in [8] https://github.com/sixu05202004/pythontutorial3, there's no license. Be sure to contact the author before you copy that into the official translation. As noted in PEP-0545, the translations need to be licensed under CC0. -- Regards, Shengjing Zhu From arj.python at gmail.com Tue Jul 10 13:47:54 2018 From: arj.python at gmail.com (Abdur-Rahmaan Janhangeer) Date: Tue, 10 Jul 2018 21:47:54 +0400 Subject: [Doc-SIG] appinv - intro Message-ID: greetings everybody, i'm Abdur-Rahmaan Janhangeer from Mauritius i volunteer to help with french translation and arabic (coordinator maybe?) i'm available for one hour per day for translation languages i know : creole (native) english (native) french (native) arabic (written and spoken) urdu (reading and spoken) others are not of significance, else i also program in py, which helps with contextual translations i have only a vague idea of the translation procedure, help appreciated yours, Abdur-Rahmaan Janhangeer https://github.com/Abdur-rahmaanJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From julien at palard.fr Wed Jul 11 11:39:50 2018 From: julien at palard.fr (Julien Palard) Date: Wed, 11 Jul 2018 11:39:50 -0400 Subject: [Doc-SIG] appinv - intro In-Reply-To: References: Message-ID: Hi and welcome to the mailing list! > i volunteer to help with french translation and arabic (coordinator maybe?) Looks like you already started some PR on the french translation which are very welcome. For arabic you may follow the PEP 545. In a nutshell: start to translate the tutorial in any repo. When translated we'll create you a repository to host it on the Python organisation on github. Also, as a coordinator, start to gather people to help you (translating the whole documentation alone (let alone translating two versions of it) is not possible). Currently, in france we're creating sprints to make the effort known: at pycon fr (https://www.pycon.fr/2017/programme.html#sprints), in Paris, France (https://www.meetup.com/fr-FR/Python-NUMA/events/245789981/, https://www.meetup.com/fr-FR/Python-NUMA/events/251983533/) and in Lyon, France. Bests, ?--? Julien Palard https://mdk.fr? From arj.python at gmail.com Wed Jul 11 11:55:39 2018 From: arj.python at gmail.com (Abdur-Rahmaan Janhangeer) Date: Wed, 11 Jul 2018 19:55:39 +0400 Subject: [Doc-SIG] appinv - intro In-Reply-To: References: Message-ID: for the french ok! got it! for arabic i'll look for some friends! for the meetups as i'm from mauritius island, i'll not be physically present *snif* but i'll help as far as i can! else for .fr i'll try to push something daily ! thanks for support guys, very much appreciated! Abdur-Rahmaan Janhangeer https://github.com/Abdur-rahmaanJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From arj.python at gmail.com Thu Jul 12 04:42:33 2018 From: arj.python at gmail.com (Abdur-Rahmaan Janhangeer) Date: Thu, 12 Jul 2018 12:42:33 +0400 Subject: [Doc-SIG] where is the empty .po en repo? Message-ID: where is an original .po repo found? (containing only english?) Abdur-Rahmaan Janhangeer https://github.com/Abdur-rahmaanJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From arj.python at gmail.com Thu Jul 12 07:04:29 2018 From: arj.python at gmail.com (Abdur-Rahmaan Janhangeer) Date: Thu, 12 Jul 2018 15:04:29 +0400 Subject: [Doc-SIG] Arabic Translations Repo Message-ID: i created a repo at https://github.com/Abdur-rahmaanJ/py-docs-ar and modified the readme since i could not find where i could not find untranslated .po files i've copied the french folder for now (ar contribs will just erase the french) i have also pinged some friends to contribute, planning a meeting tonight to disscuss terms and pr process i request a community review of the readme if possible that's all for now yours, Abdur-Rahmaan Janhangeer https://github.com/Abdur-rahmaanJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From julien at palard.fr Thu Jul 12 08:45:28 2018 From: julien at palard.fr (Julien Palard) Date: Thu, 12 Jul 2018 08:45:28 -0400 Subject: [Doc-SIG] where is the empty .po en repo? In-Reply-To: References: Message-ID: Those are typically ".pot" files, but we do not have a repository for them, we're building them when needed, using the cpython repo using: $ sphinx-build -Q -b gettext -D gettext_compact=0 Doc pot/ while being at the root of a cpython clone on the right branch (I mean if you want pot for 3.7, git checkout 3.7 right before running sphinx-build). Also see: https://github.com/python/python-docs-fr/blob/61b4b28ab86c42b274621663277d1b2cc7abccc9/Makefile#L68 ?--? Julien Palard https://mdk.fr? From adrianliaw2000 at gmail.com Mon Jul 16 06:45:45 2018 From: adrianliaw2000 at gmail.com (Adrian Liaw) Date: Mon, 16 Jul 2018 18:45:45 +0800 Subject: [Doc-SIG] Question for Simplified Chinese translation In-Reply-To: References: Message-ID: On Tue, 3 Jul 2018 at 00:45 Shengjing Zhu wrote: > > I just looked at the current status for zh_CN/zh_TW translation > coverage. For python-newest, zh_CN is 3.06%, zh_TW is 0.95%; for > python-36, zh_CN is 0.93%, zh_TW is 1%. Both are far behind :( ,so > opencc won't help much here. > > Agree. For zh_TW translations, we're still working on tutorials, glossary and builtin functions, they're not that much compared to other parts of the documentations. But once we both reach the first phase goal, I think we can start collaborating with opencc, e.g. the zh_TW team work on the translations for Library Reference and the zh_CN team work on Language Reference, then both teams will have someone periodically take each other's translations, process them using opencc, and then adjust them as Shengjing mentioned, and eventually merge them. This can definitely work out, we'll just have to make sure we're working on different parts of the documentation, we can do that through a shared project board or something like that. Actually, right now I think library/functions is a great chance for us to experiment on opencc as our team have barely translated the page, but I saw the zh_CN translations have that translated about 2/3 of them already. Best Regards, Adrian -- Wey-Han "Adrian" Liaw (@adrianliaw2000) https://linkedin.com/in/adrianliaw https://github.com/adrianliaw -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrianliaw2000 at gmail.com Mon Jul 16 07:48:49 2018 From: adrianliaw2000 at gmail.com (Adrian Liaw) Date: Mon, 16 Jul 2018 19:48:49 +0800 Subject: [Doc-SIG] Setting python-docs-zh-tw's Default Branch to 3.7 Message-ID: Hi, This is Adrian from the zh_TW translation team, for the sake of simplicity for newcomers who wants to contribute to the translation through GitHub but not that skilled at git nor GitHub, the process could be easier if our default branch is set to 3.7. Asking for someone with permission (maybe Julien) to help us change our default branch to 3.7. Thanks so much! Best, Adrian -- Wey-Han "Adrian" Liaw (@adrianliaw2000) https://linkedin.com/in/adrianliaw https://github.com/adrianliaw -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrianliaw2000 at gmail.com Mon Jul 16 07:54:42 2018 From: adrianliaw2000 at gmail.com (Adrian Liaw) Date: Mon, 16 Jul 2018 19:54:42 +0800 Subject: [Doc-SIG] Question for Simplified Chinese translation In-Reply-To: References: Message-ID: By the way, for zh_CN team, I'm not sure if you have something similar already, but we have a translation guideline [1] for our Traditional Chinese translations (although I think there's more to add), and I think most of them can apply on Simplified Chinese, please feel free to copy them and make them into Simplified Chinese if they make sense to you. > [1] https://github.com/python/python-docs-zh-tw#id7 -- Wey-Han "Adrian" Liaw (@adrianliaw2000) https://linkedin.com/in/adrianliaw https://github.com/adrianliaw -------------- next part -------------- An HTML attachment was scrubbed... URL: From zsj950618 at gmail.com Mon Jul 16 10:30:56 2018 From: zsj950618 at gmail.com (Shengjing Zhu) Date: Mon, 16 Jul 2018 22:30:56 +0800 Subject: [Doc-SIG] Question for Simplified Chinese translation In-Reply-To: References: Message-ID: On Mon, Jul 16, 2018 at 7:54 PM Adrian Liaw wrote: > > By the way, for zh_CN team, I'm not sure if you have something similar already, but we have a translation guideline [1] for our Traditional Chinese translations (although I think there's more to add), and I think most of them can apply on Simplified Chinese, please feel free to copy them and make them into Simplified Chinese if they make sense to you. There's one guide[1] for zh_CN translation, (maybe)widely used in other open source projects, like GNOME. I added it in my personal repo, but I'm not coordinator, so this is not an enforcement. But if someone wants to step in as coordinator, I hope he can enforce this. This guide also has a zh_Hant version[2], but I'm not sure whether it's been adopted by other projects. [1] https://repo.aosc.io/misc/l10n/zh_CN_l10n.pdf [2] https://docs.google.com/document/d/1Zs4CS_ZjN-imnImq4aEsiVYih8zkIkVZTSQim13_kYg/edit -- Regards, Shengjing Zhu From julien at palard.fr Mon Jul 16 11:59:26 2018 From: julien at palard.fr (Julien Palard) Date: Mon, 16 Jul 2018 11:59:26 -0400 Subject: [Doc-SIG] Setting python-docs-zh-tw's Default Branch to 3.7 In-Reply-To: References: Message-ID: Hi, > Asking for someone with permission (maybe Julien) to help us change our default branch to 3.7. Done ! ?-- Julien Palard https://mdk.fr? From julien at palard.fr Sat Jul 28 07:10:23 2018 From: julien at palard.fr (Julien Palard) Date: Sat, 28 Jul 2018 07:10:23 -0400 Subject: [Doc-SIG] Spell check in reStructuredText inside po files Message-ID: Hi doc-sig, For the needs of the french translation I created a tool, pospell [1], which checks spelling errors in our translations. It uses hunspell, so if you're also translating the Python documentaiton and hunspell has a dictionary in your language, you may use it too. [1]: https://pypi.org/project/pospell/ ?--? Julien Palard https://mdk.fr? From cocoatomo77 at gmail.com Mon Jul 30 20:39:41 2018 From: cocoatomo77 at gmail.com (tomo cocoa) Date: Tue, 31 Jul 2018 09:39:41 +0900 Subject: [Doc-SIG] Migrating translations to 3.7 In-Reply-To: References: Message-ID: Hi, Julien > - 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 Would you like to have the version of Japanese documentation defaults to 3.7? Thanks, cocoatomo On Thu, 28 Jun 2018 at 23:03, Julien Palard via Doc-SIG wrote: > 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 > -- 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 Jul 31 03:14:46 2018 From: julien at palard.fr (Julien Palard) Date: Tue, 31 Jul 2018 03:14:46 -0400 Subject: [Doc-SIG] Migrating translations to 3.7 In-Reply-To: References: Message-ID: <-Nrjsaa10jpkTBJQToNNVkLKDkPmV6tTPa19O-QfJhtEcXmFBVb6EYftG78GEKxm36YTTvA-VjKCqd9XAK8hmGVjm3WmbHePvr0gEagLt7c=@palard.fr> o/ > Would you like to have the version of Japanese documentation defaults to 3.7? I don't really care when each language is doing its transition, just tell me and I'll switch, it's a manual operation for the moment, but a simple one (more or less just a symlink to change). -- Julien Palard https://mdk.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: