QuantEcon / QuantEcon/lecture-python-programming.ml

Round-3 review questions for Adisankar (matplotlib): which words stay English, five word choices, Further Reading

未关闭
#22 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@adisankarmt 已经在做这个了。

开始于 2026年9月17日。

主要语言
Python
星标
0
派生
0
平均合并
3 天 9 小时
30 天内合并 PR
5

描述

@adisankarmt — these are the open questions from your round-3 review of matplotlib (#13), collected here so they outlive that PR's merge. All 44 of your suggestions are already applied on the PR exactly as you wrote them; nothing here changes the page — your answers decide what the translation tool learns before the next lecture. No deadline, and a short reply comment is all we need: one word per row is plenty.

First, what your review told us. Everything you corrected in round 2 came through clean this time — the colons and full stops, the capitalised sentence openers, നമുക്ക് … -ആം, For example, already, name, useful. You left 22 of the 66 Malayalam lines untouched (it was 5 of 123 last round), and your edits were lighter: six of them add only a comma. What remains is mostly rhythm and grammar — where a comma falls, ചെയ്ത versus ചെയ്തിരിക്കുന്ന, ഉപയോഗിച്ച് versus ഉപയോഗിച്ചാൽ, word order. We plan to teach those by showing the tool your own corrected sentences as examples, rather than by writing more rules.

1. The main question: which everyday English words stay in English? In round 2 you moved many Malayalam words back to English (useful, already, name, example). This round went mostly the other way. Looking across all three lectures:

You keep in English You move to Malayalam
simple, useful, already, name, example, available, remove, draw explicitവ്യക്തമായി, multipleഒന്നിലധികം, treatmentsപാഠങ്ങൾ, dictionary-likedictionary പോലെയുള്ള, straightforwardഎളുപ്പം, contrivedകൃത്രിമം, facilitateസഹായിക്കുക

Our reading: a word that a student in Kerala would actually say in everyday conversation stays in English; a bookish or formal English word goes to Malayalam. Is "would a student say this word when talking?" the right test? If the real boundary is somewhere else, a sentence on where would help us more than any individual word.

2. Five places where the same thing went both ways. We want to encode the rule you intend rather than guess.

# Item One way The other way Our guess
1 provide round 2 (functions, line 47): you changed it to provide ചെയ്യുന്ന this round, line 57: you changed provide ചെയ്യുന്നു to നൽകുന്നു നൽകുന്നു
2 plural of an English noun line 89: object-ുകൾ, function call-കളിൽ (Malayalam plural on the singular) objects (your line 112), plots, styles-ന്റെ, parameters everywhere else English plural + suffix (objects-ൽ) — also because -ുകൾ after a hyphen shows a dotted circle in some fonts
3 prefer line 91: you kept prefer ചെയ്യുന്നത് line 246: you changed it to ഇഷ്ടമാണെന്ന് not sure — your call
4 draw (a plot) line 295: വരയ്ക്കുന്നdraw ചെയ്യുക line 339: graphs വരയ്ക്കാം left as it was draw ചെയ്യുക
5 comma between two -ഉം items added at 147 (… ചെയ്യുന്നതും, … ചേർക്കുന്നതും) and 160 (functions-ഉം, features-ഉം) not added at 87 (simple-ഉം convenient-ഉം) comma between phrases, none between two single words

(Line numbers are those of the PR as you reviewed it.)

3. Further Reading in English — adopted. You returned all four Further Reading bullets to English. Matt has accepted this as policy, so later lectures will keep that list in English. What is the principle, so we draw the line where you would: is it the Further Reading section specifically, any list of links to outside resources, or any bullet that starts with a link?

4. Two small fixes we made to your text — please confirm. Line 244: we changed ഉണ്ടായേകാം to ഉണ്ടായേക്കാം (you wrote ബുദ്ധിമുട്ടായേക്കാം in functions, so we took it for a typo). Line 91: the suggestion box drops formatting, so we put the code formatting back on import this and ended the bracket with a single full stop: … രണ്ടാമത്തെ line നോക്കുക.). Say if either is wrong and we will put it back.

Thank you — three rounds in, the pattern is clear and it is your corrections that made it so.

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。