Repository navigation
docs: separate English and Japanese READMEs - #5
Merged
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
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.
Mixed Japanese/English prose makes the default README harder to scan. Keep README.md in English, add the complete Japanese README.ja.md, and link both directions. Include the Japanese file in distribution lists; Cargo continues to select the English README.
Scope: 3 files (package.json, README.ja.md, README.md). Current main implementation, scripts, exports, dependencies, workflows, versions, registry policy and license files are preserved.
Validation: independently reviewed documentation proposal; current-main/hash and docs-only separation checks; git apply --check; npm11.15 English README selection, real archives and source/archive links. Existing validated runtime payload and license bytes are unchanged. Cargo archive checks, where applicable, used --no-verify and do not claim compilation.
Already published 0.1.0 remains unchanged. Registry README changes require a separately approved future version; this PR does not publish or republish it.