QuantEcon / QuantEcon/lecture-python-programming.fr
Terminology: seven glossary rulings (from action-translation#78 + cours/chapitre)
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Python
- Estrellas
- 0
- Forks
- 1
- Merge medio
- 41 min
- PR fusionados (30 d)
- 3
Descripción
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
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza con las siete preguntas terminológicas de este issue, luego revisa los PRs de action-translation enlazados #78 y #241 y la referencia glossary/fr.json. El trabajo estará terminado cuando cada término tenga una resolución y el PR del glosario resultante se haya mergeado y enlazado aquí.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- localization
- Tipo de issue
- Documentación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Activo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100