This issue makes use of DeepL translation.
Description
I am the current lead for the Japanese localization of the "bridge. v2" project and an active member of the Japanese Minecraft add-on community.
I am reopening the discussion from #47 (opened by
toka7290 in 2021). Although this issue was closed as "completed" in 2022, the actual state of the Japanese documentation is a failure.
The Reality of "ja-JP" Support
Contrary to the statement that ja-JP is a supported language, almost every crucial page in the Script API documentation currently displays the following message:
"This content is not available in your language. Here is the English version."
Japanese creators are being systematically excluded from the latest technical information. The "limited localization" mentioned by maintainers in other issues is effectively zero for the core Script API content.
Why this matters now
The 5-Year Gap: It has been 5 years since the community first requested multilingual support. The "official" solution has failed to deliver.
Community Impact: As a maintainer of community tools like bridge. v2, I see firsthand how this lack of documentation hinders new creators in Japan.
Broken Links: Clicking "Japanese" often leads to a dead-end or a fallback to English, creating a frustrating loop for users.
Request
If Microsoft does not have the resources to translate these pages, please stop blocking the community. * Allow us to submit PRs for ja-JP content directly.
Or, provide a transparent reason why community-led translation (via Crowdin or similar) is being rejected despite the official failure to maintain these docs.
We are ready to help. We have the knowledge and the will. Please give us the access.
"This content is not available in your language. Here is the English version."
Images:
This issue makes use of DeepL translation.
Description
I am the current lead for the Japanese localization of the "bridge. v2" project and an active member of the Japanese Minecraft add-on community.
I am reopening the discussion from #47 (opened by
toka7290 in 2021). Although this issue was closed as "completed" in 2022, the actual state of the Japanese documentation is a failure.
The Reality of "ja-JP" Support
Contrary to the statement that ja-JP is a supported language, almost every crucial page in the Script API documentation currently displays the following message:
"This content is not available in your language. Here is the English version."
Japanese creators are being systematically excluded from the latest technical information. The "limited localization" mentioned by maintainers in other issues is effectively zero for the core Script API content.
Why this matters now
The 5-Year Gap: It has been 5 years since the community first requested multilingual support. The "official" solution has failed to deliver.
Community Impact: As a maintainer of community tools like bridge. v2, I see firsthand how this lack of documentation hinders new creators in Japan.
Broken Links: Clicking "Japanese" often leads to a dead-end or a fallback to English, creating a frustrating loop for users.
Request
If Microsoft does not have the resources to translate these pages, please stop blocking the community. * Allow us to submit PRs for ja-JP content directly.
Or, provide a transparent reason why community-led translation (via Crowdin or similar) is being rejected despite the official failure to maintain these docs.
We are ready to help. We have the knowledge and the will. Please give us the access.
"This content is not available in your language. Here is the English version."
Images:
