docs: add Japanese README #4028
Conversation
I created Japanese translated README.
|
WalkthroughThe recent updates to the Vue Vben Admin project documentation enhance accessibility for Japanese users by introducing a dedicated Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Outside diff range, codebase verification and nitpick comments (1)
README.ja-JP.md (1)
128-128: Consider simplifying the expression.The phrase "ことができる" can be redundant in Japanese.
- 作者にコーヒーを一杯おごってサポートを示すことができます！ + 作者にコーヒーを一杯おごってサポートを示せます！Tools
LanguageTool
[uncategorized] ~128-~128: 「ことができる」という表現は冗長な可能性があります。
Context: ...プロジェクトが役に立つと思われた場合、作者にコーヒーを一杯おごってサポートを示すことができます！ 
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (3)
- README.ja-JP.md (1 hunks)
- README.md (1 hunks)
- README.zh-CN.md (1 hunks)
Files skipped from review due to trivial changes (2)
- README.md
- README.zh-CN.md
Additional context used
LanguageTool
README.ja-JP.md
[uncategorized] ~128-~128: 「ことができる」という表現は冗長な可能性があります。
Context: ...プロジェクトが役に立つと思われた場合、作者にコーヒーを一杯おごってサポートを示すことができます！ 
Markdownlint
README.ja-JP.md
137-137: null
Images should have alternate text (alt text)(MD045, no-alt-text)
Additional comments not posted (10)
README.ja-JP.md (10)
12-12: Correct translation and clear introduction.The introduction accurately conveys the purpose and technology stack of the project.
16-16: Clear upgrade notice.The upgrade notice clearly informs users about the latest version and its incompatibility with previous versions.
20-24: Accurate feature list.The features section accurately lists the key features of the project.
28-30: Clear preview section.The preview section provides a link to the full version of the project and test account details.
38-42: Clear Gitpod instructions.The Gitpod section provides clear instructions on how to use Gitpod for the project.
46-46: Clear documentation link.The documentation section provides a clear link to the project's documentation.
48-77: Clear installation and usage instructions.The installation and usage section provides clear instructions on how to install and use the project.
83-93: Clear contribution guidelines.The contribution guidelines section provides clear instructions on how to contribute to the project.
95-110: Clear commit message guidelines.The commit message guidelines section provides clear instructions on how to format commit messages.
114-116: Clear browser support information.The browser support section provides clear information about browser compatibility.
I created Japanese translated README.
Summary by CodeRabbit