Repository navigation
Conversation
…#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
force-pushed
the
2026-10-20-newsletter-zh-fidelity
branch
from
October 20, 2026 09:27
1314e62 to
f533f08
Compare
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
reviewed
Oct 30, 2026
|
|
||
| - [C-Lightning #3490][] 增加了一个 `getsharedsecret` RPC,它将通过本地节点的私钥和用户指定的公钥组合来导出共享密钥。该共享密钥与 LN 协议中导出的其他共享密钥相同(ECDH 结果的 SHA256 摘要),这可能与其他程序使用椭圆曲线密码学(如 [ECIES][])导出的共享密钥不同。这个 RPC 对于希望与其他 LN 节点加密通信的插件很有用。 | ||
| - [C-Lightning #3490][] 新增一个 `getsharedsecret` RPC,它用本地节点的私钥与用户指定的公钥组合,导出一个共享密钥。这个共享密钥的导出方式与 LN 协议中其他共享密钥一致(对 ECDH 结果取 SHA256 摘要),这可能不同于其他程序用椭圆曲线密码学导出共享密钥的方式(例如 ECIES)。对于希望与其他 LN 节点加密通信的插件,这个 RPC 很有用。 |
Contributor
There was a problem hiding this comment.
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
This PR fixes those classes of problems without rewriting the translations or changing their voice.
Size
What changed
1. Meaning-changing mistranslations
Only clear cases were changed. Representative examples:
hard to misuse in ways that could result in loss of fundswas translated as if the design intended to avoid loss, reversing the causality. Fixed to “难以被误用,以免造成资金损失”.48%was attached to the wrong scope (“还能再提升 48%”); the English says the overall improvement is 48%. Removed the extra “再”.has also likely made it harderwas translated as “或能增加……难度” (future possibility), weakening both tense and modality. Fixed to “也很可能增加了……难度”.for perpetuitywas attached to “每一笔交易” instead of “必须永久满足”. Fixed the modifier scope.Rust-Bitcoinchanged toRust Bitcoin, matching the project’s own spelling and the term list.2. Terminology consistency (mainland technical Chinese)
Also:
relay→ 中继;forward→ 转发 (the two were mixed before).值得注意的变更— added the missing的in 112 places.其它→其他;帐号→账号.「」→ 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:
{% capture %}blocks were missing, so footnote table variables rendered empty; restored.{% include references.md %}.alttexts were still English; translated.4. Links and anchors
Bitcoin Core #9484inline link.eltoolink and its definition.BOLTs #880pointed to the wrong Newsletter (House style guide #165); fixed.time/putinline links had been moved into a “see also” parenthesis; restored in-sentence links.[topic generic signmessage]link.5. Formatting
check_zh.pyP2 items are format-only (zero-width characters, half-width punctuation,[...], code/alt false positives). They are intentionally left for a separate formatting pass.lang,layout, ``,{:#id},{% include %}, code block, or link-reference style was changed.What was deliberately not changed
[X][X]vs[X][]).NVE,Cory Field,3.072 bytes— the Chinese follows the source or the correct technical name, but does not “fix” English in this PR.Validation
check_zh.py:32=32,31=31); this is a parser classification artifact, not missing content.linkers/issues.md.bundle exec jekyll build --future --drafts --unpublishedwith 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:
af5ee955— main 203-article pass (the bulk).d6c8c13b— Website occasionally fails to load #7 blank line.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.841cb50c— Style guide updates #171 include spacing.c6558b55— Layout: add default opengraph image #134 blockquote indentation.If you want to spot-check, start with:
Risk