Skip to content

Finish the Chinese terminology and register fixes: 注解 everywhere, seven phrases rewritten - #26

Merged
renrenmimi merged 2 commits into
masterfrom
fix/zh-annotation-term
Oct 10, 2026
Merged

renrenmimi merged 2 commits into
masterfrom
fix/zh-annotation-term

Conversation

@renrenmimi

@renrenmimi renrenmimi commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

Summary

Finishes two content findings from the 2026-10-09 audit that the chapter PRs (#17–#22) left partly done:

  • B23: one Chinese term for annotation, 注解;
  • B22: written prose instead of colloquial phrases.

Both apply to Chinese only; the English is unchanged. CLAUDE.md states the terms since #23.

Changes

B23: five places that said 标注 for a type annotation

  • Chapter 03 (app/narrowing/page.tsx): the two comments in the assertion-function sample, and the sentence that follows them.
  • Chapter 04 (app/structural/page.tsx): 「才能被 TypeScript 标注」 becomes 「TypeScript 才能为它们写出类型」. This follows the English ("before TypeScript could type it") and the next sentence, which says TypeScript 描述 JavaScript.
  • Chapter 06 (lib/utility-data.tsx): a quiz explanation.

The one 标注 left under app/ and lib/ is a stylesheet comment in app/home.css. There it means "marks", not a type annotation.

B22: seven colloquial phrases the fix record listed as left over

Where Before After
Prologue 反复捣乱 反复干扰理解
Chapter 03 撞上 违反
Chapter 04 没人会这么干 这在现实中行不通
Chapter 10 会踩的那个坑 容易落入的陷阱
Chapter 10 好几年没人敢改。而你干活的时候,系统不能停。 多年来没有人敢修改。而迁移期间,系统必须照常运行。
Chapter 10 债还清了也不吭声 即使底下的错误已经修好,它也不会提示
Finale 项目扛得住时 项目条件成熟时

Verification

  • git grep 标注 -- app lib finds only the stylesheet comment. None of the seven phrases is left anywhere under app/ or lib/.
  • These checks pass:
    • test/zh-copy-spacing.test.ts;
    • npx tsc --noEmit --incremental false;
    • npm test (14 files, 89 tests).

🤖 Generated with Claude Code

Content finding B23 asked for one Chinese term for annotation. The chapter
PRs changed most uses, but five that mean a type annotation were left:

- chapter 03: two comments in the assertion-function sample and the
  sentence after it;
- chapter 04: the sentence on rewriting every JS file before TypeScript
  could type it, which now reads 才能为它们写出类型 to match the English
  ("before TypeScript could type it");
- chapter 06: a quiz explanation.

The one remaining 标注 is a stylesheet comment in app/home.css, where it
means "marks", not a type annotation.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copilot AI balanced review requested due to automatic review settings October 10, 2026 07:06
@vercel

vercel Bot commented Oct 10, 2026

Copy link
Copy Markdown

Deployment failed for project tser with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/renrenmimis-projects?upgradeToPro=build-rate-limit

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-10T07:08:03.121154Z edde18b PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

renrenmimi added a commit that referenced this pull request Oct 10, 2026
#26 changes the last five uses of 标注 to 注解, so the changelog's claim of
one term per concept now holds; it is listed with the chapter PRs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The fix record listed seven informal phrases that the chapter PRs did not
reach (content finding B22). Two sit in sentences this PR already edits.
Each now reads as written prose; the English is unchanged:

- prologue: 反复捣乱 -> 反复干扰理解;
- chapter 03: 撞上 -> 违反;
- chapter 04: 没人会这么干 -> 这在现实中行不通;
- chapter 10: 会踩的那个坑 -> 容易落入的陷阱; 好几年没人敢改 ... 你干活的
  时候,系统不能停 -> 多年来没有人敢修改 ... 迁移期间,系统必须照常运行;
  债还清了也不吭声 -> 即使底下的错误已经修好,它也不会提示;
- finale: 项目扛得住时 -> 项目条件成熟时.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@renrenmimi renrenmimi changed the title Use 注解 for annotation in the last five places that said 标注 Finish the Chinese terminology and register fixes: 注解 everywhere, seven phrases rewritten Oct 10, 2026
@renrenmimi
renrenmimi merged commit 0a51e5c into master Oct 10, 2026
1 of 2 checks passed
@renrenmimi
renrenmimi deleted the fix/zh-annotation-term branch October 10, 2026 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants