Malayalam

At a glance

Edition

QuantEcon/lecture-python-programming.ml, translated from Python Programming for Economics and Finance.

Website

The Malayalam site shows the lectures merged so far.

Phase

Initial translation, one lecture per round. See How a review round works.

Editor of record

Adisankar Manoj Thanuja (@adisankarmt) reviews each lecture and settles terms and style with @mmcky. @mmcky drafts each lecture and merges every pull request.

Rounds

Round 1, python_by_example (ml#1). Round 2, functions (ml#7). Round 3, matplotlib (ml#13). Round 4, numpy (ml#23). Round 5, pandas (ml#26). Round 6, intro (ml#58, open).

Follow-up issues

The questions from each round: ml#12 (round 2), ml#22 (round 3), ml#25 (round 4) and ml#57 (round 5, open).

Follow-up pull requests

ml#14 returned the exercise blocks of the first two lectures to the English. ml#24 applies two of the answers from ml#22 to lectures already merged.

Glossary

glossary/ml.json in the action-translation repository. Many entries note the ruling behind them.

Term policy: keep English

Technical terms stay in English, in Latin script. Malayalam supplies the grammar. A case ending joins the English word with a hyphen: economy-യിലെ, relationships-ൽ, concepts-ന്റെ (action-translation#250).

• An English verb that stays in English takes a Malayalam light verb after it: recommend ചെയ്യുന്നു, not ശുപാർശ ചെയ്യുന്നു (ml#1).
• Headings stay identical to the English (action-translation#250).
• An English term is never spelt out in Malayalam letters. The engine applies this rule to every draft.
• An everyday English word can stay in English if a student in Kerala would say it in everyday conversation. The test is a permission only. Where both forms are fine, leave the word as it is (ml#22, ml#25).

The mistake to watch for in this edition is over-translation: Malayalam where the policy keeps English. Automated reviews by GitHub Copilot do not know this policy, and often suggest translating terms that stay in English (ml#1). They need no attention from you.

Worked examples

From the editor's answers to questions and from the round reviews. Each row links to its source.

Exercises

Every exercise block stays in English, exactly as in the English lecture. This covers the exercise statement, its hints and its solution. The rule holds until the editor rules on each exercise, one at a time (ml#12, 2026-09-01).

When the editor is ready to rule on an exercise, a new issue or a comment on any lecture pull request is enough (ml#12).

Register and style

• Use the classroom teacher's voice: നമുക്ക് … -ആം (“let us …”) in place of നമ്മൾ … -ും (ml#7).
• Point to what follows, as in “Here is …”, with താഴെ കാണാം (ml#1, ml#7).
• End every paragraph with a full stop. End a sentence that introduces a code cell or a list with a colon (ml#7).
• Capitalise an English word that opens a sentence: Functions-നെ (ml#7).
• In a list, capitalise the first word of each item. An item that begins with a technical term keeps the term's own case (ml#25).
• Split two clauses joined by a comma into two sentences, whether or not a pronoun (ഇത്, ഇവ, അത്, അതിനാൽ) follows the comma. Keep the comma before a joining word such as കൂടാതെ or പക്ഷേ, and in a list of parallel predicates: … ആകാം, … ആകാം, അല്ലെങ്കിൽ … ആകാം (ml#23, ml#26).
• Sometimes the English ends the lead-in to a bullet list with a pronoun, and each bullet completes the sentence. Leave out ഇത് at the end of such a lead-in by default. For example, “this is a good thing: It”, followed by “forces …” and “removes …”, becomes ഇത് ഒരു നല്ല കാര്യമാണ്, and each bullet stands on its own. Keep ഇത് where the sentence reads more naturally with it (the editor, by email, 2026-10-14).
• Translate an English phrase by its meaning, not word for word (ml#1).

Lines kept in English

A line that stays in English, such as an exercise or a Further Reading entry, stays exactly as in the English lecture, character for character. Do not add a colon or a full stop to it, and do not change its apostrophes. The punctuation rules apply only to Malayalam lines (ml#7, ml#12). Keeping these lines identical lets later changes to the English be matched exactly.

The Further Reading section stays in English. It points to material outside the lecture, which readers follow into English anyway (ml#22).

What to skip

Skip what every reviewer skips: see What to look for. In this edition, the headings, the code cells and the Exercises section are checked against the English before each pull request opens, so you can skip them too (ml#26).

Rendering and input

• The edition's website shows Malayalam in Noto Sans Malayalam for body text and Noto Serif Malayalam for headings. English text and code keep the site's usual fonts.
• In some fonts, -ുകൾ after a hyphen shows a dotted circle. This is one more reason to give an English noun the English plural: objects, not object-ുകൾ (ml#22).
• If you receive questions as a file, return the file itself, as plain text. Malayalam text can contain zero-width joiners, invisible characters that Word and Google Docs can remove. See Terms and house style.

Open questions

• Exercises. Which parts of each exercise, if any, to translate. The editor decides one exercise at a time (ml#12).
• Short bullets and lead-ins. In the pandas review the editor returned five short bullets (“reading in data”, “adjusting indices”, …) and a note's lead-in to the English. Whether a short, label-like bullet stays in English as a rule, as exercises do, is open (ml#57).
• Commas between case-marked -ഉം items. Two items that carry a case ending as well as -ഉം, such as US-ന്റെയും, Australia-യുടെയും: always a comma, as for plain -ഉം items, or optional (ml#57).

Rulings log

Newest first. The log lists the editor's answers to questions, and the style taught to the engine from each round's review.