docs: add Japanese README translation#1153
Open
sscodeai wants to merge 1 commit into
Open
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
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
Add
README_ja.mdand wire up the language switcher inREADME.md/README_zh.mdso the existing trilingual setup actually includes Japanese.What's included
README_ja.md— full Japanese translation of the README, structurally aligned with the English version and including the mobile section that exists inREADME_zh.mdREADME.mdandREADME_zh.mdto expose the日本語link (the bar previously only linked between EN ↔ ZH)Translation notes
README_zh.mdwas also included so the Japanese version isn't a strict subset of either sourceREADME_zh.md's conventions:super administrator/regular administrator→スーパー管理者/一般管理者multi-agent extensibility→マルチ Agent 拡張アーキテクチャProfile,Provider,Backend,bearer token,Bot token, etc.) since they appear that way in the product UI and platform docsTokenis capitalized when used as a standalone noun (matchingREADME_zh.md); kept lowercase inside fixed phrases likeBot token/Access token/bearer tokenTest plan