Translator review of lectures/pandas.md — Pandas — for the Japanese edition, by @xuanguang-li.
|
|
| English source |
lectures/pandas.md · published page |
| Japanese draft |
the pull request that closes this issue, opened by Matt when this lecture's round starts (with a preview link) |
How the round works. When this lecture's turn comes, Matt drafts it with the current version of the translation engine and opens one pull request for it. You review it there, with a suggestion block on any line you would change or commits to the branch, and say on the pull request when your review is complete. Matt then reviews the suggestions and updates the lecture and the engine (glossary, rules, lints) before the next lecture is drafted, and merges the pull request. The merged lecture is kept as a reference for measuring later versions of the engine; REVIEWING.md has the details.
What matters most: meaning errors; terms that are wrong or disagree with the glossary; register and punctuation that depart from the house style; Japanese that reads unnaturally; code comments, if the draft translates them. Please skip errors in the English, which belong upstream in QuantEcon/lecture-python-programming, and the translation: block at the top of the file.
About this lecture. The English runs to about 1,900 words of prose and 70 code cells. As your first lecture, it will probably raise more terminology and style questions than later ones, and each answer improves every lecture after it. Much of the output is data downloaded when the page is built (from FRED, the World Bank and Yahoo Finance), so numbers in the preview can differ from the English site.
Done when
- @xuanguang-li has said on this lecture's pull request that the review is complete
- Matt has updated the lecture and the engine from the review and merged the pull request, which closes this issue
Translator review of
lectures/pandas.md— Pandas — for the Japanese edition, by @xuanguang-li.lectures/pandas.md· published pageHow the round works. When this lecture's turn comes, Matt drafts it with the current version of the translation engine and opens one pull request for it. You review it there, with a suggestion block on any line you would change or commits to the branch, and say on the pull request when your review is complete. Matt then reviews the suggestions and updates the lecture and the engine (glossary, rules, lints) before the next lecture is drafted, and merges the pull request. The merged lecture is kept as a reference for measuring later versions of the engine; REVIEWING.md has the details.
What matters most: meaning errors; terms that are wrong or disagree with the glossary; register and punctuation that depart from the house style; Japanese that reads unnaturally; code comments, if the draft translates them. Please skip errors in the English, which belong upstream in QuantEcon/lecture-python-programming, and the
translation:block at the top of the file.About this lecture. The English runs to about 1,900 words of prose and 70 code cells. As your first lecture, it will probably raise more terminology and style questions than later ones, and each answer improves every lecture after it. Much of the output is data downloaded when the page is built (from FRED, the World Bank and Yahoo Finance), so numbers in the preview can differ from the English site.
Done when