🌐 [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: PASS | Model: claude-sonnet-4-6 | Date: 2026-04-12

---

📝 Translation Quality

Criterion	Score
Accuracy	9/10
Fluency	9/10
Terminology	9/10
Formatting	9/10
Overall	9/10

Summary: The translation of the changed sections is of high quality, accurately conveying technical content with natural Chinese phrasing and consistent terminology. The new sections on GPU resources, parallelization strategies, and Python's slowness are well-handled. Minor issues include a slightly informal idiom in the Summary section and a subtle weakening of 'shifting' to '分配', but these do not materially affect comprehension. No syntax errors were found. The new sections ('## Why is Pure Python Slow?', '### Type Checking', '### Vectorization vs pure Python loops', '#### Which Should We Use?', '### Accessing GPU Resources') are all accurately and fluently translated with appropriate technical terminology. Technical terms such as '多线程' (multithreading), '多进程' (multiprocessing), '向量化' (vectorization), 'JIT 编译器', and '硬件加速器' are consistently and correctly used throughout the modified sections. The note blocks and code-cell comments in the modified sections are properly translated and formatted, preserving the MyST directive structure. The translation of the '#### Summing with Compiled Code' and '### Summary' sections accurately conveys the nuanced technical explanation about memory layout and the argument against switching entirely to C/Fortran. The YAML frontmatter translation metadata is correctly structured with all new and modified headings properly mapped.

Suggestions:

• Summary section: '代码加速在本质上已经与并行化画上了等号' → '代码加速在本质上已与并行化同义' — The phrase '画上了等号' is slightly informal; '同义' or '等同' would be more precise and academic in register.

• Why do we need them? section: '将任务分配到多个线程/CPU/GPU/TPU 上' → the English uses 'Shifting tasks across multiple threads/ CPUs / GPUs /TPUs'; '分配' (distribute/assign) is slightly weaker than the original 'shifting'; consider '转移任务至多个线程/CPU/GPU/TPU' to better match the source.

• Which Should We Use? section: '对于单台机器上的数值工作，通常首选多线程——它更加轻量' → '轻量' is acceptable but '轻量级' is the more established Chinese computing term for 'lightweight'; consider '更为轻量级' for better terminological precision.

• Accessing GPU Resources section: 'Modern Python libraries like JAX, discussed extensively in this lecture series' is translated as '现代 Python 库（如本系列讲座中广泛讨论的 JAX）'; this is accurate but slightly restructured — acceptable, no change needed. However, '以最少的代码改动' for 'with minimal code changes' is correct and natural.

---

🔍 Diff Quality

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

Summary: The translation target document correctly mirrors all structural changes from the English source, with the heading map accurately updated to reflect new/removed/renamed sections.

---

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 中，整数数组存储在一块连续的内存空间中：