Repository navigation
Merged
Conversation
docs/zh-cn/ holds translations of the README through its Status section, docs/cloudflare-settings.md and the runbook part of docs/disaster-recovery.md, each recording the SHA-256 of the English it was made from. mailda.site renders them at their English pages' paths under /zh-cn/ in place of Starlight's fallback. apps/site/test/translations.test.mjs fails when an English source moves, and holds each translation to its source's code blocks, links, inline code, tables and headings, the glossary's NEVER list and the zh-Hans register. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The README changes about twice a day, so a whole-file hash on its translation would have failed every unrelated pull request until somebody re-translated it, and the /zh-cn/ landing page already carries its pitch and status in Chinese. A translation with translated_until now records the hash of the English before that line, so a new drill report under the runbook does not fail it; the whole file stays hashed for cloudflare-settings. `node apps/site/scripts/translations.mjs` prints each current hash. Two README defects the translation found: the delivery-events paragraph said only the Setup screen creates the subscription, while the installer's setup step does (provisionNode posts /api/provider/subscription with wrangler's login, attaching the consumer when none is); it now says so, and names what a button-deployed Node needs. "Alice via <mailbox>" was raw HTML and drew as "Alice via"; escaped in the README and in history.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
# Conflicts: # docs/history.md
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
1 participant
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.
The owner approved translating key operator pages for mailda.site's /zh-cn/.
docs/zh-cn/cloudflare-settings.md(whole file) anddocs/zh-cn/disaster-recovery.md(the runbook part), in the owner-confirmed glossary's words, rendered at their English page's path under /zh-cn/ in place of the "not translated" notice; the English stays authoritative and says so.translated_until);apps/site/test/translations.test.mjsfails, naming both files, when the English changes, so a translation cannot fall behind silently. Edits outside a partial translation's span do not fail it.<mailbox>was swallowed on the site; the delivery-events paragraph now says what the installer actually does (and what a button-deployed Node needs).Verified: site tests 17/17, worker node suite 885/885, lint, typecheck.
🤖 Generated with Claude Code