Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Terminology: seven glossary rulings (from action-translation#78 + cours/chapitre)

Open
#42 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
localization

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.

Description

audit maintenance

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):

  1. 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?
  2. f-string — keep in English (proposed), or chaînes f?
  3. Broadcasting — keep in English (proposed), or gloss as diffusion (broadcasting)?
  4. Index → Indice — confirm? Matches the existing Tail index → Indice de queue, though index is common in French tech writing.
  5. Tuple unpacking — déballage de tuple (proposed) or décompression de tuples?
  6. frame — not pinned; the models split trame / cadre and it is probably context-dependent (stack frame vs dataframe). Pin it at all, and if so to what?
  7. lecture — glossary/fr.json v1.1 pins Cours; chapitre was 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
Dominant language
Python
Stars
0
Forks
1
Avg merge
41m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from QuantEcon/lecture-python-programming.fr

All issues in QuantEcon/lecture-python-programming.fr

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.