glossary(fr): v1.2 — Namespace, Heads, standard-normal context from the second editor round

[mmcky]

Encodes the terminology rulings from the French editor's second native-review round — QuantEcon/lecture-python-programming.fr#77 (functions) and QuantEcon/lecture-python-programming.fr#80 (names), both merged 2026-09-23 — that meet the glossary bar (explicit native ruling plus measured variation). Glossary v1.1 → v1.2, 367 → 369 terms.

Entry	Change	Evidence
Namespace → Espace de nommage	new	The official French Python docs use « espace de nommage » (tutorial §9.2: 37 « nommage », 0 « noms »). Fresh init draws at v0.29.2 wrote « espace de noms » 206/206. UPDATE mode already preserves the editor's term; a NEW section brought « noms » back 3/3 without the pin and 0/3 with it (full document 2/2).
Heads (coin toss) → Face	new	The seed wrote « une face (pile) », a contradiction. Fresh draws of the exercise got the side wrong in 6/12 without the pin, 0/12 with it (24/24 lines); a python_oop time-series "tail" stays « queue » / « fin ».
Standard normal	context refined	Keeps « Loi normale centrée réduite » for the distribution; the context now steers draws and random variables to « variable normale centrée réduite ». Fresh translation called the draws « lois » in 8/32 renderings with the old context, 0/28 with the new one (Fisher p = 0.005); the distribution sense is unchanged 16/16. Consistent with the editor's 2026-07-16 ruling on #78.

Deliberately not pinned: Tails → Pile (no source occurrence; it would sit beside four « queue » entries); Random device → Expérience aléatoire (polysemous — lecture-python.myst uses "random device" for a physical spinner, where « dispositif » is right); Built-in function (the editor's own PRs disagree — asked on fr#80); Garbage collection → Ramasse-miettes and Return (a value) → Renvoyer (meet the bar, held for a small pinned A/B).

Order of operations. The French edition's names.md already says « espace de nommage » (fr#80); four other lines in three fr lectures still say « espace de noms » and are being aligned in an edition PR so the release does not leave the edition inconsistent with its own glossary. The reviewer sees the glossary too (terminology gates), so this should reach @v0 after that edition PR merges.

Validation: npm test 1590/1590, lint and format clean; the glossary is read at runtime beside the bundle, so dist-action is unchanged. Measurements are from the round-2 review (QuantEcon/project-translation reports/2026-09-23-fr-round2-editor-review-disposition.md, §5 S6–S8); it rides the normal §4a release gate.

🤖 Generated with Claude Code

[Copilot]

Copilot review overview

🟡 Changes recommended

The documentation’s Malayalam glossary term count/version is inconsistent with the actual glossary/ml.json contents and should be corrected while these glossary summary tables are being updated.

Get a fresh assessment by requesting another Copilot review.

Review effort: Lite
Findings: 2

Open (2)

• Update Malayalam glossary count in status line · New
• Sync Malayalam glossary table count and version · New

What changed in this PR

Updates the French translation glossary to incorporate decisions from the editor’s second review round, and propagates the new French glossary version/term counts into user-facing documentation and the changelog.

Changes:

• Bumps glossary/fr.json to v1.2 and adds/refines three terminology entries (Namespace, Heads (coin toss), Standard normal context).
• Updates French glossary term counts in docs/README-style status surfaces.
• Records the French glossary update in CHANGELOG.md under Unreleased.

File	Description
glossary/​README.md	Updates French glossary status line to 369 terms and v1.2.
glossary/​fr.json	Bumps glossary version and adds/adjusts French terminology entries per editor rulings.
docs/​user/​glossary.md	Updates the French glossary row (term count/date).
docs/​index.md	Updates the headline French glossary term count in the “Current status” block.
CHANGELOG.md	Adds an Unreleased “Changed” entry documenting the French glossary v1.2 update and rationale.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.