Repository navigation
Round-2 review questions for Adisankar (functions): six word choices, the exercise rule, and the web font #12
Description
Activity
1 - 1) ഉദാഹരണത്തിന് means 'for example'. this can be retained in english itself.
2) ഉദാഹരണം means 'example'. this can again be retained in english. if any modifications is required, I will let you know in the upcoming reviews.
3) ഇതിനകം means 'already'. keep in english.
4) Keep it as - work ചെയ്യുന്നുണ്ടോ
5) English for the noun (an identifier's name), Malayalam for the act of naming
6) typo2 - Regarding exercises, I have not made a final decision yet. For now, please retain all exercise-related content in English and keep it byte-for-byte identical to the source. I will review each exercise individually and decide later which parts, if any, should be translated into Malayalam.
3- The Malayalam font is comfortable. No change needed
Thank you @adisankarmt — every row is answered and all of it is being encoded now. A short read-back so you can correct anything I have misunderstood:
Word choices. For example, / example(s) / already stay in English; work keeps the light-verb form
work ചെയ്യുന്നുണ്ടോ; name is English for an identifier's name and Malayalam (പേരിട്ടു,പേരും) for the act of naming; line 159 becomescall ചെയ്ത് നോക്കാം. These go into the engine's Malayalam glossary and rules so the next lectures come out that way without your having to flag them again.Exercises. Understood: until you have ruled on each exercise individually, every exercise block — the exercise statement and its hint and solution text — stays in English, byte-for-byte identical to the source. Because that rule has no judgement in it, we are encoding it as a mechanical copy step rather than an instruction to the model, so it cannot drift. Two consequences I am assuming, please say if either is wrong:
- It applies to the two lectures already merged as well as to new ones.
functionsandpython_by_exampleboth still carry Malayalam inside some exercise blocks (the hybrid sentences infunctionsexercises 1 and 2, and the exercise statements inpython_by_example). I will open one small PR that restores those blocks to the English source, for you to approve — that PR is also a natural place for your per-exercise decisions later, whenever you get to them. matplotlib(Malayalam translation: matplotlib — calibration review round 3 (v0.27.0 engine) #13) already has its single exercise and solution byte-identical to the source, so you can skip those lines when reviewing it.
Font. Noted, no change.
I will leave this issue open until the restoration PR is up, then close it with links to what was encoded.
- It applies to the two lectures already merged as well as to new ones.
- added a commit that references this issue
on Sep 3, 2026 Please go ahead. We are on the same page.
Closing this as done, with thanks, @adisankarmt. Every question here was answered on 2026-09-01 and confirmed on 2026-09-03, and all of it is now in the tool:
- The six word choices (For example, example(s), already, work, name, and the
call ചെയ്ത് നോക്കാംtypo) are in the Malayalam glossary and rules, via feat(ml): exercise-family blocks byte-identical to source, enforced in code; encode the ml#12 answers (glossary v0.5.0, rules 24 → 23, E2E scenario 28) action-translation#303 in release v0.28.0. - The exercise rule is recorded as a decision (every exercise-related block stays byte-identical to the English), and the tool now enforces it in code. Restore exercise blocks to byte-identical English per the editor's ruling on #12 #14 restores the two pages already published.
- The web font stays as it is.
Your per-exercise review — deciding later which parts of each exercise, if any, should be translated — is still yours to raise whenever you are ready; a new issue or a comment on any lecture PR is all it takes.
- The six word choices (For example, example(s), already, work, name, and the
- added a commit that references this issue
on Oct 6, 2026
@adisankarmt — these are the open questions from your round-2 review of
functions(#7), moved here so they do not get lost when that PR merges. All 118 of your suggestions are already applied on the PR; nothing here changes the page — your answers decide what the translation engine learns for the next lectures (tracked in QuantEcon/action-translation#296). No deadline; one word per row is plenty, and a reply comment here is all we need.1. Six places where the same word went both ways. We want to encode the rule you intend rather than guess.
ഉദാഹരണത്തിന്,at 49, 430ഉദാഹരണംat 105, 137, 466ഇതിനകംat 49work ചെയ്യുന്നുണ്ടോ)പ്രവർത്തിക്കുന്നുat 127, 402പേരിട്ടുat 68,പേരുംat 276call ചെയ്ത നോക്കാം— should that becall ചെയ്ത് നോക്കാം?(Line numbers are those of the PR as you reviewed it.)
2. Your exercise retentions — is this the rule? We read the pattern as: an exercise statement whose content is probability or mathematics (the coin-flip device in Exercise 3, the binomial sentence in Exercise 2) stays in English; a mixed sentence keeps its mathematical clause in English and its programming instruction in Malayalam (your line 484:
factorialഎന്ന് പേരുള്ള ഒരു function എഴുതുക, such thatfactorial(n)returns $n!$ …); and a purely programming exercise (Exercise 5) is translated as normal. Matt has adopted this as policy alongside your earlier Hint/Solution rule, so later lectures will follow it — if the boundary is somewhere else, a sentence on where would help. One small thing on our side: lines kept in English stay byte-for-byte identical to the English source (so future updates diff cleanly), which is why we left off the colons you added at 557 and 563 — the punctuation rule applies to the Malayalam lines.3. The Malayalam web font. Whenever you are next on the rendered preview: does the Noto Malayalam font from #9 sit at a comfortable size beside the English? It can be nudged a few percent either way.
Thank you again — this round taught the engine a great deal.