84669 person learning
152542 person learning
20005 person learning
5487 person learning
7821 person learning
359900 person learning
3350 person learning
180660 person learning
48569 person learning
18603 person learning
40936 person learning
1549 person learning
1183 person learning
32909 person learning
Pyhton项目的文档有好多种风格,例如Scrapy这种,比较干净简洁;也比如Flask这种更加素雅、简单;当然还有Python的官方文档
最近想翻译的一个项目文档dota2api,他们的项目开源在Github
我的想法是fork一下,增加相应的中文文档,然后提个pull request。问题是不知道这种文档的组织结构,这种类似Scrapy的文档风格是否用了一些框架。
请教各位,该如何下手?
光阴似箭催人老,日月如移越少年。
After looking at their code, the document uses the Sphinx engine. I don’t know if the poster has used it. If not, you can
pip install sphinx sphinx-quickstart xxx
Try it.
The translation order is:
Translate first
After completion, open an issue to communicate with the author and agree on document specifications
If the author wants to merge into the main project, fork, modify, and submit a PR
The author hopes to open a new document repo, fork, rename, replace the document content, and deploy it to RTD
The author doesn’t want you to translate, well, there shouldn’t be such an arrogant author...
After looking at their code, the document uses the Sphinx engine. I don’t know if the poster has used it. If not, you can
Try it.
The translation order is:
Translate first
After completion, open an issue to communicate with the author and agree on document specifications
If the author wants to merge into the main project, fork, modify, and submit a PR
The author hopes to open a new document repo, fork, rename, replace the document content, and deploy it to RTD
The author doesn’t want you to translate, well, there shouldn’t be such an arrogant author...