zhouwenbonwpu@mail.nwpu.edu.cn writes:
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 translation@python.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. Steve