QuantEcon / QuantEcon/lecture-python-programming.fr

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

オープン
#40 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

audit maintenance
主要言語
Python
スター
0
フォーク
1
平均マージ
41分
マージ済み PR(30日)
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. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

調査の方向性

.translate/config.yml と Phase 0 のサブ issue #41 および #42 から始めて、アクセスと用語に関する決定を理解してください。レビュー作業では、オープンな lecture のサブ issue を 1 つ選び、指定されている .md ファイルを読み、記載されたレビューの優先順位に従ってください。完了とは、その lecture を編集する PR がマージされるか、レビュアーが変更なしで承認することを意味します。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
python
領域
documentation
issue の種類
ドキュメント
難易度
4/5
見積もり時間
3〜5日
活発さ
活発
明瞭さ
明確に書かれている
初心者へのやさしさ
38/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。