French translation review — native-speaker read-through (project tracker)

Tracker for the native-speaker review of the French edition by @Honaminto. It replaces #3, whose 26-box checklist could not be ticked by its reviewer (read access only) and which is closed in favour of this project — see the decision on project-translation#19.

Background

This repository is a machine-generated first draft of the QuantEcon Python Programming lectures in French (Claude Opus 4.8, one pass, 364-term glossary, no human edits). The precedent that matters: the Persian review found meaning-inverting mistranslations that read perfectly fluently. A native reading is the only thing that catches those. There is no deadline — one lecture a month is genuinely useful.

Where we stand (verified 2026-08-21)

How the review works

One sub-issue per lecture, below. Each is complete when a PR editing that lecture by @Honaminto is merged, or when he approves the lecture as needing no change — nothing is ticked by hand; the PR is the record. Edit the French directly (a branch in this repo, one PR per lecture), or leave line comments / suggestion blocks on a PR if that is easier. Priorities, in order: meaning errors; wrong technical terms; inconsistent terminology; unnatural French (academic register); anything in code comments that looks wrong. Please ignore spacing before : ; ! ? (fixed automatically, action-translation#81), errors in the English (raise upstream), and the translation: header block. A term that is wrong is probably wrong in several lectures — say so on the terminology sub-issue and it goes into the glossary once, for every lecture.

Work plan

Phase 0 gates nothing technically — Emile can already open PRs from a fork, as #24/#25 show — but accepting the invitation is what makes in-repo branches and one-click suggestions work, and the terminology decision improves every unreviewed lecture at once, so both come first. Phase 1 runs in any order; intro.md and about_py.md are the most-read after the two already done. The two reviewed lectures are filed as sub-issues and closed immediately so the progress bar reflects work that has actually happened.

What does not need to change

The translations are not re-generated during the review. Glossary changes from Phase 0 flow into future syncs automatically; they are not back-applied to reviewed lectures by machine.

Sources

#3 (superseded), project-translation#19 (decision, 2026-08-21), plans/human-reviews.md WS5 (nominated audits, derived status). Repo state verified at main on 2026-08-21.

Merci beaucoup, Emile — questions and disagreement are very welcome.

Empieza por .translate/config.yml y las subissues de la Fase 0 #41 y #42 para entender las decisiones sobre acceso y terminología. Para el trabajo de revisión, elige una subissue abierta de una lecture y lee su archivo .md indicado, siguiendo las prioridades de revisión especificadas. Se considera completado cuando se hace merge de un PR que edita esa lecture o el reviewer lo aprueba sin cambios.