QuantEcon / QuantEcon/lecture-python-programming.fr
Terminology: seven glossary rulings (from action-translation#78 + cours/chapitre)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- Avg merge
- 41m
- Merged PRs (30d)
- 3
Description
Part of #40 (Phase 0). Decision item for @Honaminto.
Question. Six glossary questions were proposed in action-translation#78 and merged 2026-07-22 marked review needed; none has had a native speaker's ruling. Answering them improves all 27 lectures at once, including the 25 nobody has read yet, so this is the highest-leverage item in the project.
The terms. Please reply here with agree / prefer X for each (verbatim from #78, plus one deferred since):
Standard normal→loi normale centrée réduite(the conventional French statistical term). Neither model produced it — both said "loi normale standard". Is the conventional term what we want?f-string— keep in English (proposed), orchaînes f?Broadcasting— keep in English (proposed), or gloss asdiffusion (broadcasting)?Index→Indice— confirm? Matches the existingTail index → Indice de queue, thoughindexis common in French tech writing.Tuple unpacking—déballage de tuple(proposed) ordécompression de tuples?frame— not pinned; the models splittrame/cadreand it is probably context-dependent (stack frame vs dataframe). Pin it at all, and if so to what?lecture—glossary/fr.jsonv1.1 pinsCours;chapitrewas raised and deliberately left to you in action-translation#241.
What happens with the answer. Each ruling is pinned in glossary/fr.json (a PR in action-translation, which we will open and link here), and the terminology flows into every future translation automatically.
Done when
- each of the seven has a ruling on this issue
- the glossary PR is merged and linked
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the seven terminology questions in this issue, then review the linked action-translation PRs #78 and #241 and the glossary/fr.json reference. The work is done when each term has a ruling and the resulting glossary PR is merged and linked here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- localization
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100