Repository navigation
docs: translate the Japanese locale - #182
Merged
Merged
Conversation
Translate the remaining English pages under content/ja into technical Japanese, record the locale terminology, and point internal links at /ja/. Co-authored-by: hector <majinghe@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
rustfs-docs | 0c5749d | Commit Preview URL Branch Preview URL |
Oct 19 2026, 11:23 AM |
This branch was successfully deployed
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.
Summary
Translates the Japanese locale (
content/ja) from English stubs into technical Japanese (です・ます), usingcontent/enas the source of truth. Other locales are unchanged.The audit in
ja-language-audit.mdwas taken against8814682. On currentmain, the already-translated pages had already picked up those fixes (Chinese leftovers结果/插入, restic “trusted network”, the doubledにin prerequisites, mixed pages such as Iceberg, IAM policies, and Keycloak, and the terminology in section 4). This PR finishes the remaining English copies and records the glossary.Terminology
Locked in
.agents/skills/localize-rustfs-docs/references/ja.mdand applied in the new pages:Product names (DuckDB, Keycloak, Apache Flink, AWS CLI, and similar) stay in English. Code fences, CLI flags, API names, and URL slugs are unchanged. Absolute internal links use
/ja/....Files
176 files changed: the Japanese pages that were still English or mixed, link prefixes on pages that were already Japanese, and the Japanese terminology reference.
Coverage includes installation, administration, security and compliance, operations, troubleshooting, reference, developer entry points, SDKs, and the integration guides.
Remaining gaps
/en/(docs.ray.io,docs.vllm.ai, Elastic docs). The URLs match English; rewriting them would fail the external-URL check.Apache Flink,S3 Tables,AWS CLI,DevOps,Operator,Golang) plus a homepageclassNameline counted as untranslated prose. The same product-name titles are kept in the German locale.content/japage is left as a raw English copy.Verification
npm run docs:check— pass (orphans, relative links, fences, banned strings, locale parity, technical code blocks)npm run build— pass (3785 static files, including/ja/installation/linux/quick-start/withlang="ja"and the title クイックスタート)node .agents/skills/localize-rustfs-docs/scripts/audit-locales.mjs --locales ja— 0 missing/extra files; 3 external-URL false positives and the product-name warnings above