Skip to content

zh: improve translation fidelity and consistency across newsletters #0-#202 - #2930

Open
bittomhan wants to merge 6 commits into
bitcoinops:masterfrom
bittomhan:2026-10-20-newsletter-zh-fidelity
Open

bittomhan wants to merge 6 commits into
bitcoinops:masterfrom
bittomhan:2026-10-20-newsletter-zh-fidelity

Conversation

@bittomhan

Copy link
Copy Markdown
Contributor

Summary

This PR is a maintenance pass over the existing Chinese translations of the Optech Newsletter, covering #0–#202 (203 articles). It does not add new translations and does not change the English source.

The goal is to preserve and raise the quality of the work that is already in the archive. With an AI-assisted review workflow, I was able to check all 203 articles as one corpus instead of article by article, which made it practical to align terminology, restore structure that had drifted over time, and fix meaning-changing mistranslations.

This is intended to make the Chinese archive reliable enough to keep building on.

Why this is useful

The Chinese archive has grown over several years and many contributors. As a result:

  • the same term is translated in several ways (e.g. anchor outputs, incoming capacity, multisig, coin selection, coinbase, eclipse attacks);
  • some sections use Taiwan/HK wording or literal translations that are not standard in mainland technical Chinese;
  • a few edits merged or split paragraphs and lists, so the Chinese page no longer has the same structure as the English page;
  • a small number of sentences changed the meaning (negation, conditions, quantifiers, actor/object order, tense, numbers).

This PR fixes those classes of problems without rewriting the translations or changing their voice.

Size

  • 203 articles, 205 files (203 newsletters + 2 Taproot special-page anchor updates)
  • +4,382 / −4,361
  • 5 commits, split so they can be reviewed independently

What changed

1. Meaning-changing mistranslations

Only clear cases were changed. Representative examples:

2. Terminology consistency (mainland technical Chinese)

Preferred Occurrences Removed variant
锚定输出 90 锚点输出 (0)
入站容量 / 入站通道 8 / 9 入向 (0)
多重签名 169 多签 (0)
选币 44 币选择 (0)
币基交易 21 coinbase 交易 (0)
日食攻击 56 eclipse 攻击 (0)
讨论帖 64 讨论串 (0)
offers 76 报价 (0)
硬件钱包接口(HWI) 50 files mixed Chinese/English (0)
付款方 / 收款方 — 支付方 / 接收方 in payment contexts (0)

Also:

  • relay → 中继; forward → 转发 (the two were mixed before).
  • Section names unified to 栏目 (previously 版块 / 板块 / 专栏).
  • 值得注意的变更 — added the missing 的 in 112 places.
  • 其它 → 其他; 帐号 → 账号.
  • Straight quotes 「」 → Chinese curly quotes “” (38 places).

3. Structure restored to match the English page

These were not style changes; they restore visible structure that had drifted:

4. Links and anchors

5. Formatting

  • 42 remaining check_zh.py P2 items are format-only (zero-width characters, half-width punctuation, [...], code/alt false positives). They are intentionally left for a separate formatting pass.
  • No front matter, permalink, lang, layout, ``, {:#id}, {% include %}, code block, or link-reference style was changed.

What was deliberately not changed

  • The English source.
  • Front matter, permalinks, slugs, anchors, includes, code blocks.
  • Link reference style ([X][X] vs [X][]).
  • English source typos such as NVE, Cory Field, 3.072 bytes — the Chinese follows the source or the correct technical name, but does not “fix” English in this PR.
  • Terms that look inconsistent but are not:
    • 区块奖励 vs 区块补贴 (reward = subsidy + fees)
    • 存取款 (mainland banking term, not “access”)
    • 看门狗 (watchdog) vs 瞭望塔 (watchtower)
    • 拥堵控制交易 (CTV context)
    • 草图 (sketch, algorithm context)

Validation

  • 203/203 articles reviewed against the English source in three passes.
  • check_zh.py:
    • P0 = 0 (was 2)
    • P1 = 0 (was 20)
    • P2 = 42 (was 254; all format-only)
  • Structure parity:
  • Internal anchors: 0 broken heading anchors; issue-number anchors are generated by linkers/issues.md.
  • Local build passed: bundle exec jekyll build --future --drafts --unpublished with Ruby 3.4.11 (65.58s, exit 0). Rendered pages for Layout: add default opengraph image #134 and Compatibility data: coinbase conio copay edge #180 were checked (quote inside <li>, id="signet" / id="quantum" present).

Review guide

Suggested order:

  1. af5ee955 — main 203-article pass (the bulk).
  2. d6c8c13b — Website occasionally fails to load #7 blank line.
  3. b93f76cf — Add Marcin to the about page #6 / Add Compatibility Section to the site #168 / Style guide updates #171 / Compatibility data: coinbase conio copay edge #180 structure alignment.
  4. 841cb50c — Style guide updates #171 include spacing.
  5. c6558b55 — Layout: add default opengraph image #134 blockquote indentation.

If you want to spot-check, start with:

Risk

  • Only Chinese newsletter bodies and two Taproot special-page anchor references are touched.
  • No build configuration, permalink, anchor, include or code change.
  • Every commit can be reverted independently.

…#202

- fix mistranslations affecting negation, conditions, quantifiers, actor/object order, causality, numbers and version numbers
- unify section headings, lead-ins and core terminology per mainland usage
- restore paragraph/bullet structure and missing links/captures
- preserve front matter, permalinks, anchors, includes and code blocks

Validation:
- check_zh.py: P0=0, P1=0, P2=42 (was P0=2, P1=20, P2=254)
- 203/203 articles reviewed in three passes
- structure parity: 0 articles with count difference >= 3
- 0 link-style regressions
- bitcoinops#6: move [Newsletter bitcoinops#3] definition to the end-of-file definitions block
- bitcoinops#168: restore the English editor comment above the ghost43 item
- bitcoinops#171: restore the English editor comment above Bitcoin Core #22863
- bitcoinops#180: add blank lines before {:#signet} and {:#quantum}

No translated prose changed; only block structure, link definition placement and non-rendering comments.
Preserve translated link text while keeping the original English reference label:
- [CPFP 豁免(carve-out)][CPFP carve out]
- [Bitcoin Core PR 审查俱乐部][Bitcoin Core PR Review Club]
- [Rust Bitcoin 0.28][Rust-Bitcoin 0.28]

Update four cross-newsletter links to the actual Chinese heading ids, and add stable ids for the bitcoinops#180 taproot timeline TOC.

Validation: 0 literal ][, 0 broken internal anchors, htmlproofer passes.
@bittomhan
bittomhan force-pushed the 2026-10-20-newsletter-zh-fidelity branch from 1314e62 to f533f08 Compare October 20, 2026 09:27
@bitschmidty

Copy link
Copy Markdown
Contributor

@hulatown if you have a moment and interest to check a few of these AI-assisted suggestions for older newsletter translations (made previously by @bittomhan) Let me know

@bitschmidty bitschmidty left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

One suggestion below and this feedback as a whole:

The PR preserves some links with trick, but other anchors will break for external links and bookmarks.

FR PR #2929 preserved old ids with IALs and spans.

Up to you and @hulatown if break the links or trying to preserve is the plan.


- [C-Lightning #3490][] 增加了一个 `getsharedsecret` RPC,它将通过本地节点的私钥和用户指定的公钥组合来导出共享密钥。该共享密钥与 LN 协议中导出的其他共享密钥相同(ECDH 结果的 SHA256 摘要),这可能与其他程序使用椭圆曲线密码学(如 [ECIES][])导出的共享密钥不同。这个 RPC 对于希望与其他 LN 节点加密通信的插件很有用。
- [C-Lightning #3490][] 新增一个 `getsharedsecret` RPC,它用本地节点的私钥与用户指定的公钥组合,导出一个共享密钥。这个共享密钥的导出方式与 LN 协议中其他共享密钥一致(对 ECDH 结果取 SHA256 摘要),这可能不同于其他程序用椭圆曲线密码学导出共享密钥的方式(例如 ECIES)。对于希望与其他 LN 节点加密通信的插件,这个 RPC 很有用。

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
- [C-Lightning #3490][] 新增一个 `getsharedsecret` RPC,它用本地节点的私钥与用户指定的公钥组合,导出一个共享密钥。这个共享密钥的导出方式与 LN 协议中其他共享密钥一致(对 ECDH 结果取 SHA256 摘要),这可能不同于其他程序用椭圆曲线密码学导出共享密钥的方式(例如 ECIES)。对于希望与其他 LN 节点加密通信的插件,这个 RPC 很有用。
- [C-Lightning #3490][] 新增一个 `getsharedsecret` RPC,它用本地节点的私钥与用户指定的公钥组合,导出一个共享密钥。这个共享密钥的导出方式与 LN 协议中其他共享密钥一致(对 ECDH 结果取 SHA256 摘要),这可能不同于其他程序用椭圆曲线密码学导出共享密钥的方式(例如 [ECIES][])。对于希望与其他 LN 节点加密通信的插件,这个 RPC 很有用。

This branch has not been deployed

No deployments
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