QuantEcon / QuantEcon/lecture-python-programming.fr

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

未关闭
#40 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

audit maintenance
主要语言
Python
星标
0
派生
1
平均合并
41 分钟
30 天内合并 PR
3

描述

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)

Fact State
Lectures in the ToC 27 (polars.md was added after #3 was opened, which listed 26)
Reviewed so far 2numpy.md (#24) and python_by_example.md (#25), Emile's edits merged 2026-08-04
Reviewer's access write pending — added to translation-team-french (push) on 2026-08-21, awaiting his acceptance of the invitation; was read before, contrary to what #3 said
Roster .translate/config.yml names editors.primary: Honaminto
Glossary questions the six in action-translation#78 (merged 2026-07-22 "review needed") are unanswered; Cours vs chapitre deliberately deferred in action-translation#241

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 Issue Work item
0 — access #41 @Honaminto accepts the team invitation (write) and acknowledges the editor agreement
0 — terminology #42 Decision: the seven open glossary questions (six from QuantEcon/action-translation#78 + Cours vs chapitre)
1 — lectures #43 Review intro.md
1 — lectures #44 Review about_py.md
1 — lectures #45 Review getting_started.md
1 — lectures #46 Review python_by_example.mddone: fr#25 merged 2026-08-04
1 — lectures #47 Review functions.md
1 — lectures #48 Review python_essentials.md
1 — lectures #49 Review oop_intro.md
1 — lectures #50 Review names.md
1 — lectures #51 Review python_oop.md
1 — lectures #52 Review need_for_speed.md
1 — lectures #53 Review numpy.mddone: fr#24 merged 2026-08-04
1 — lectures #54 Review matplotlib.md
1 — lectures #55 Review scipy.md
1 — lectures #56 Review numba.md
1 — lectures #57 Review jax_intro.md
1 — lectures #58 Review numpy_vs_numba_vs_jax.md
1 — lectures #59 Review autodiff.md
1 — lectures #60 Review pandas.md
1 — lectures #61 Review pandas_panel.md
1 — lectures #62 Review polars.md
1 — lectures #63 Review writing_good_code.md
1 — lectures #64 Review workspace.md
1 — lectures #65 Review python_advanced_features.md
1 — lectures #66 Review debugging.md
1 — lectures #67 Review sympy.md
1 — lectures #68 Review troubleshooting.md
1 — lectures #69 Review status.md

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.

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从 .translate/config.yml 以及 Phase 0 的子 issue #41 和 #42 开始,以了解访问权限和术语方面的决定。对于 review 工作,选择一个处于开放状态的 lecture 子 issue,并阅读其中指定的 .md 文件,遵循所述的 review 优先级。完成的标准是:编辑该 lecture 的 PR 被合并,或 reviewer 无需修改即可批准它。

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
documentation
Issue 类型
文档
难度
4/5
预计耗时
3-5 天
活跃度
活跃
描述清晰度
描述清楚
新手友好度
38/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。