hi all, I want to know does Python Developer’s Guide have chinese version, If not, i want to do some translation, may i tell to PSF(or other people) to grant authorization? May you also want to do this translation, please contact me. Best, bobozi
I want to know does Python Developer’s Guide have chinese version,
The closest I found is a Taiwanese version of the general doc site which conforms to PEP 545 (see below). I don't read Chinese well enough to be sure, but I do not think the devguide is linked there. https://docs.python.org/zh-tw/3/
This doesn't mean it doesn't exist (see PEP 545 rationale), but I didn't find PEP 545-conformant paths /zh/, /zh-tw/, or /zh-hk/ at devguide.python.org. Try Baidu and friends.
If not, i want to do some translation, may i tell to PSF(or other people) to grant authorization?
The devguide sources come with a Creative Commons CC0 1.0 Universal license. That means that contributors to the devguide disclaim copyright entirely. You do not need any authorization to translate it, and you can do whatever you want with your translation (subject to relevant copyright law which would govern duplications of anybody else's translation). I doubt the PSF needs or wants to be involved.
May you also want to do this translation, please contact me. Best,
PEP 545 -- Python Documentation Translations https://www.python.org/dev/peps/pep-0545 sets up a process for organizing translation teams, which also grants access to have your work distributed by the Python sites. But I don't know if the Developer's Guide participates in PEP 545, it's mentioned only as part of the process.
Further information, I guess you should ask on the translations list https://mail.python.org/mailman3/lists/translation.python.org/ or the PEP authors. There may also be a channel on the discourse server. I looked for python-zh, python-cn, and python-chinese mailing lists, but no luck.
Thanks for bringing this up. I hope you find some good teammates! You don't owe anybody anything for this work, but I hope you will follow the PEP 545 process, which will bring the most benefit to Chinese speakers (like most of my masters students :-).
Hi,Steve. Thank you for your help, there are too much files and i'm just a new contributor for python so that I am confused at the beginning. I really appreciate your help，now i have some directions，it‘s a big project, and I didn't find more infomation in PEP 545 -- Python Documentation Translations. But i find that devguide has its repo in github, can i make a zh branch in this repo? I want to konw if this follows some standards? Thanks again！ bobozi
(Taking the liberty to add Julien Palard in CC; I think you would have to post on doc-sig to connect with people involved in documentation translation.)
The PEP 545 infrastructure is for the main Python documentation. The devguide is separate; I don't think there is anything set up for it. Actually that's probably because people didn't think of it — are you sure you want to translate the devguide? I say this because contributing to CPython unavoidably requires the ability to read some English. The Chinese version of the main documentation is not complete (quite advanced compared to others, but the overall task is huge). Perhaps you would be better off contributing to that? Or maybe you need a quick setup guide in Chinese but not the full devguide with all reST instructions, information on branches and release cycles, technical overview sections, etc.?
Best regards, Jean Abou Samra
Hi Jean, I know what you mean, of course, if someone want to contribute to Cpython, must read some English. My goals is to lower the threshold for new contributor. Aslo, I think you are right, I can only translate some basic page like Quick Start instead of the whole guide. And I also join in main Python documentation's translation in transfex. Thanks for your help! bobozi
But i find that devguide has its repo in github, can i make a zh branch in this repo?
Well, you can't make a branch in *that* repo, but you can make a fork of it in your account on GitHub. That's just a couple of clicks on the GitHub page, and you need to do that to do any translation. And zh won't be a separate branch in the end, because all of the languages need to coexist at the same time. Eventually it has to get merged to 'main' or it won't be published via python.org.
However, before doing anything else, you should read other posts in this thread, and think carefully about whether this is really worth doing now. I'm more supportive than the other posters so far, because Python has a very formal, fairly carefully structured process for development that has proven to provide a very high-quality product, over and over again, and on a pretty reliable schedule at that. I think introducing that to Chinese speakers in their native language, or natives of any non-English language, has some value as "software engineering education" even if they don't become Python core devs. But I agree with the other posters that from Python's point of view, translating the main documentation seems clearly more needed.
Second, you should read the ReadTheDocs information on translations https://docs.readthedocs.io/en/stable/guides/manage-translations-sphinx.html (copied from Julien's post for your convenience, h/t Julien for the URL!) to get a better idea of what kind of process is involved.
Then you should join the firstname.lastname@example.org mailing list, and ask questions there.
I want to konw if this follows some standards?
There is a specific process and format, yes. See the ReadTheDocs info. That will tell you how to set up the new translation so that ReadTheDocs will provide it automatically in the /zh/ subtree.
I want to know does Python Developer’s Guide have chinese version, If not, i want to do some translation, may i tell to PSF(or other people) to grant authorization?
IIRC the idea has already been raised by Stéphane Wirtel a few years back, and IIRC the conclusion was "anyway, to contribute to cpython, one will have to read/write english, so it may not be usefull, let's focus on docs.python.org first, that's already a lot of work.".
(Sorry I can't find the thread, maybe it was durring a sprint.)
But if you really want to translate it (with good arguments on how it can be usefull) the next step is probably to shoot a mail in the translation@ list.
The devguide is hosted on readthedocs (see how they handle translations ), so PEP 545 won't be of any help here.
(Thanks Jean Abou Samra for pinging me on the thread.) -- Julien Palard https://mdk.fr