The proofreading activity of data science on the command line second edition was restarted

Warehouse ：https://github.com/apachecn/ds-cmd-line-2e-zh

Overall progress ：https://github.com/apachecn/ds-cmd-line-2e-zh/issues/1

Contribution Guide ：https://github.com/apachecn/ds-cmd-line-2e-zh/blob/master/CONTRIBUTING.md

Chapter list ：

• order
• Preface
• 1 brief introduction
• 2 Start
• 3 get data
• 4 Create a command line tool
• 5 Clean up the data
• 6 Project management and make
• 7 Explore data
• 8 Parallel pipes
• 9 Modeling data
• 10 Multilingual data science
• 11 summary
• appendix ： List of command line tools

---

Contribution Guide

Please bravely translate and improve your translation . Although we pursue excellence , But we don't want you to be perfect , So don't worry about translation mistakes —— In most cases , Our server has recorded all translations , So you don't have to worry about irreparable damage because of your mistakes .（ Adapted from Wikipedia ）

person in charge ：

• Flying dragon ：562826179

Useful links

• ApacheCN Document navigation
• Google Translate
• ApacheCN Proofreading activity participation manual
• Post editing
• When translation turns into text editing —— Lee smile to
• Translation engine error prone term list （ Welcome to add ）
• Liao Xuefeng Git course

technological process

One 、 Claim

Proofreaders need to master Markdown and Git, And the theme of the document （ Programming ,Web Development , big data ,AI, Safety one ）.

First of all to see Overall progress , Make sure no one claims the chapter you want to claim .

Then reply ISSUE, Indicate the “ chapter + QQ Number ”, Easy to contact and track progress .

Two 、 proofreading

Need proofreading 【 Professional term 】 and 【 Format 】.

【 grammar 】 There is no need to proofread because it has been proofread , And please keep the language style of the original text to the greatest extent .

Translation in docs Under the table of contents , For the original text, please see the link at the beginning of each article .

Be careful ： Do not change the file name of the translation , Because they correspond to chapters ！

Ensure that the translation conforms to the following 【Markdown Typesetting requirements 】 section .

Please refer to 【 Useful regular expressions 】 section , as well as 【 Translation engine error prone term list 】 To improve efficiency .

3、 ... and 、 Submit

• fork Github project
• stay docs Edit the translation under the folder
• add、commit and push
• pull request

Please see Liao Xuefeng Git course .

Markdown Typesetting requirements

1. Code blocks and pictures don't need proofreading , And do not count words .
2. Chinese characters and English letters , There is a space between Chinese characters and numbers . But there is no space between Chinese punctuation and any characters .
3. Bold, italic and link requirements are the same as above , Chinese and English bold , Spaces are also required between English and Chinese bold .
4. Anything that appears in any programming language , For example, variable name , Class name , Function name , Package name , And what appears on the command line , For example, command , file name , route , Extension , All need to be packaged in inline code . Inline code and Chinese characters / There is no space between punctuation , But there is a space between it and English letters or numbers .
5. The format of the table is easy to mess , Make sure they display normally .
6. Titles and short lists need special proofreading .
7. There are a few untranslated paragraphs , Use Google Translate Then proofread .

Useful regular expressions

link ：

(?<!!)\[[^\]]*\]

form ：

^\|

Chinese space ：

The space between Chinese characters is usually the place where the translation engine makes mistakes .

[\u4e00-\u9fff]\s+[\u4e00-\u9fff]

Untranslated paragraph ：

^[a-zA-Z0-9][^\u4e00-\u9fff]+$
^\s*([\+\-\*]\x20{3}|\d+\.\x20{2})[^\u4e00-\u9fff]+$

Inline code ：

stay Markdown in , Inline code needs to be enclosed in backquotes , But some tutorials do not . therefore , Need to check the boundary between Chinese and English , Change inline code that is not enclosed in backquotes .

[\u2018-\u201d\u3001-\u301c\u4e00-\u9fff\uff01-\uff65]\x20*[A-Za-z0-9]|[A-Za-z0-9]\x20*[\u2018-\u201d\u3001-\u301c\u4e00-\u9fff\uff01-\uff65]

bold / Italics ：

\*\*[^\*]+\*\*|(?<!\*)\*[^\*]+\*(?!\*)

title ：

^#+\x20

list （ Within twenty words ）：

Short lists are very error prone because they have no context .

^\s*([\+\-\*]\x20{3}|\d+\.\x20{2}).{1,20}$

Reward

Proofreaders can receive 1000 words after completion 2~4 Yuan reward （ It depends on the difficulty and workload ）, Please contact Fei Long （Q562826179,V:wizardforcel）.

Word count follows word standard ： Every Chinese character and punctuation count as a word , A continuous English letter 、 Numbers and punctuation sequences count as one word .