🌐 [translation-sync] Improve clarity and fix typos in need_for_speed lecture

[mmcky]

Automated Translation Sync

This PR contains automated translations from QuantEcon/lecture-python-programming.

Source PR

#523 - Improve clarity and fix typos in need_for_speed lecture

Files Updated

• ✏️ lectures/need_for_speed.md
• ✏️ .translate/state/need_for_speed.md.yml

Details

• Source Language: en
• Target Language: zh-cn
• Model: claude-sonnet-4-6

---

This PR was created automatically by the translation action.

[github-actions]

⚠️ Translation Quality Review

Verdict: WARN | Model: claude-sonnet-4-6 | Date: 2026-04-13

---

📝 Translation Quality

Criterion	Score
Accuracy	7/10
Fluency	8/10
Terminology	8/10
Formatting	6/10
Overall	7.4/10

Summary: The translation is generally of good quality with accurate technical terminology and fluent Chinese prose. However, there is a critical structural error in the Multithreading/Multiprocessing subsections: the first subsection is incorrectly labeled '#### 多进程' instead of '#### 多线程', and its content conflates material from both sections in a confusing order. This is a significant accuracy and formatting issue in the changed sections that must be corrected. The rest of the changed content—including Why is Pure Python Slow?, Type Checking, Summing with Compiled Code, Summary, Vectorization vs pure Python loops, Hardware Accelerators, and Accessing GPU Resources—is translated accurately and fluently. The 'Why is Pure Python Slow?' and 'Type Checking' sections are accurately and fluently translated, with correct technical terminology for dynamic typing and static types. The 'Vectorization vs pure Python loops' section is well-translated, clearly conveying the performance comparison and the batch operation concept. Hardware Accelerators and Accessing GPU Resources sections are accurately translated with correct terminology (GPU→图形处理单元, TPU→张量处理单元, core→核心). The note blocks and code comments are appropriately translated without disrupting the MyST directive syntax. The 'Which Should We Use?' section accurately conveys the preference for multithreading on single machines and multiprocessing for scaling, matching the source well.

⚠️ Markdown Syntax Errors (CRITICAL)

• 🔴 In '#### 多进程' section (first occurrence): The translation duplicates the '#### 多进程' heading and mixes content from '#### Multithreading' and '#### Multiprocessing' under the wrong headings. The first '#### 多进程' heading should be '#### 多线程' to match the English source '#### Multithreading'.

Suggestions:

• Multithreading section heading and content mismatch: The first subsection under '### CPU 上的并行化' is labeled '#### 多进程' but should be '#### 多线程' (Multithreading). Furthermore, the content under this heading incorrectly combines text from both Multithreading and Multiprocessing sections, with '所有线程共享同一内存空间...' (shared memory content) appearing under what should be the Multithreading section but after text that belongs to Multiprocessing ('多进程是指使用多个处理器并发执行多条逻辑线程...'). This is a significant accuracy error.

• Multiprocessing section: The translation of '多进程是指使用多个处理器并发执行多条逻辑线程' is inaccurate. The English source says 'Multithreading means running multiple threads of execution within a single process' — 'within a single process' (在单个进程内) is omitted in the first occurrence. The second '#### 多进程' section correctly translates Multiprocessing but the first occurrence conflates the two sections.

• Why do we need them? — '向量化：提供已编译的机器码以及使该代码可访问的接口': The English source reads 'Vectorization: providing compiled machine code and interfaces that make this code accessible' — this is accurately translated, no issue here. However, the list item numbering uses '1.' twice (items 1 and 1) matching source, which is fine.

• Summary — '代码加速在本质上已经与并行化画上了等号': The phrase '画上了等号' (literally 'drawn an equals sign') is a reasonable colloquial rendering of 'synonymous with', but a more precise academic phrasing would be '代码加速在本质上已与并行化同义' or '代码加速已基本等同于并行化'.

---

🔍 Diff Quality

Check	Status
Scope Correct	✅
Position Correct	❌
Structure Preserved	❌
Heading-map Correct	✅
Overall	5/10

Summary: The heading map is correctly updated, but the document body has structural corruption in the Parallelization section where multithreading content is misplaced under a Multiprocessing heading and the Multiprocessing heading appears twice.

Issues:

• In the Parallelization > Parallelization on CPUs section, the target body incorrectly duplicates the '#### 多进程' (Multiprocessing) heading twice, and multithreading content (shared memory explanation and the {note} block about GIL) is misplaced inside the first Multiprocessing subsection instead of appearing under a Multithreading heading
• The source restructured the CPU parallelization subsection order to Multithreading first, then Multiprocessing, then 'Which Should We Use?' — but the target body does not reflect this new ordering correctly, mixing content from both sections under the wrong headings

---

This review was generated automatically by action-translation review mode.

[Copilot]

Pull request overview

Automated translation sync for the zh-cn version of the need_for_speed lecture, incorporating upstream clarity improvements and typo fixes from the English source.

Changes:

• Updated the lecture’s translation frontmatter heading map to match revised section structure/titles.
• Rewrote and reorganized multiple zh-cn sections for improved clarity (pure Python performance reasons, parallelization, GPU/TPU discussion).
• Updated translation sync state metadata (source SHA, sync date, mode, tool version).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 7 comments.

File	Description
lectures/need_for_speed.md	Syncs zh-cn lecture content and heading mappings with updated upstream structure and wording.
.translate/state/need_for_speed.md.yml	Updates translation-sync bookkeeping (source SHA/date/mode/tool version).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

这里说“通过三种主要策略…”，但有序列表的标号是“1., 1., 2.”（最后一项不同）。本文件其他有序列表统一使用“1.”让 Markdown 自动编号；建议把最后一项也改为“1.”以保持一致并避免读者误以为缺了一项。

Suggested change

	2. 并行化：将任务分配到多个线程/CPU/GPU/TPU 上
	1. 并行化：将任务分配到多个线程/CPU/GPU/TPU 上

[Copilot]

“考虑以下 Python 操作”后面紧跟代码块，当前缺少结尾标点（通常用“：”引出示例）。建议补上“：”以符合上下文的行文和排版习惯。

Suggested change

	考虑以下 Python 操作
	考虑以下 Python 操作：

[Copilot]

“例如，考虑以下 C 代码，它计算从 1 到 10 的整数之和”后面直接进入代码块，建议在句末补上“：”以引出示例。

Suggested change

	例如，考虑以下 C 代码，它计算从 1 到 10 的整数之和
	例如，考虑以下 C 代码，它计算从 1 到 10 的整数之和：

[Copilot]

该句作为独立段落结尾缺少句号，建议补全中文标点以保持全文一致的书面表达。

Suggested change

	NumPy 使用类似的模型，灵感来源于 MATLAB
	NumPy 使用类似的模型，灵感来源于 MATLAB。

[Copilot]

该行后面紧跟代码块，建议在句末补上用于引出示例的“：”，避免读起来像未完句。

Suggested change

	如果 `a` 和 `b` 是字符串，那么 `a + b` 需要执行字符串拼接
	如果 `a` 和 `b` 是字符串，那么 `a + b` 需要执行字符串拼接：

[Copilot]

该行后面紧跟代码块，建议在句末补上用于引出示例的“：”，避免读起来像未完句。

Suggested change

	如果 `a` 和 `b` 是列表，那么 `a + b` 需要执行列表拼接
	如果 `a` 和 `b` 是列表，那么 `a + b` 需要执行列表拼接：

[Copilot]

该句后面接项目符号列表，建议在句末加“：”以引出下方要点，避免句子悬空。

Suggested change

	在 C 或 Fortran 中，整数数组存储在一块连续的内存空间中
	在 C 或 Fortran 中，整数数组存储在一块连续的内存空间中：