Whitepaper v0.4.1: privacy wording fix and all eight locale translations - #50
Merged
Conversation
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
2 participants
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.
Rewrites the Privacy Properties section of the English v0.4.1 whitepaper to state the concrete privacy model of encrypted sends, replacing the "probabilistic rather than absolute" framing.
Adds v0.4.1 to every other locale (zh-CN, ja-JP, ko-KR, de-DE, es-ES, ru-RU, id-ID, hi-IN). Those locales were still serving v0.3.3; v0.4.1 is a major restructure, so each is a full translation of the current English, reusing v0.3.3 terminology where the text was unchanged. One commit per locale.
Verified: component, heading, URL, and reference counts match English in every locale; TOC keys resolve to the translated headings; prettier and
bun run buildpass; each built locale page serves v0.4.1.Not included: v0.4.1 PDFs (none exist for any locale yet, including en-US; they need
bun run build:pdf).Please have someone other than the author review and merge.