Update Japanese translations for new strings and fix fragment handling#4050
Merged
dgtlmoon merged 1 commit intodgtlmoon:masterfrom Apr 14, 2026
Merged
Update Japanese translations for new strings and fix fragment handling#4050dgtlmoon merged 1 commit intodgtlmoon:masterfrom
dgtlmoon merged 1 commit intodgtlmoon:masterfrom
Conversation
- Translate newly added English strings - Use single-space msgstr for fragments redundant in Japanese (e.g. "Set to", "There are", "Use", "Accepts the") to prevent gettext from falling back to English source strings, which would break sentence flow - Add translator comments explaining space-as-translation technique - Fix unnatural translations - Redistribute fragment translations for natural Japanese word order
skkzsh
force-pushed
the
translation-ja-260414
branch
from
c2b3372 to
b09566a
Compare
Owner
|
Thanks so much! |
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.
This PR is a follow-up to #4019 and provides further updates to the Japanese localization.
Changes
# 訳注:).Redistribution of Fragmented Strings
Japanese and English have quite different word orders (SVO vs. SOV).
so for some UI strings that are split across multiple msgid fragments in the templates,
a direct 1:1 mapping would produce unnatural or broken Japanese.
To address this, I have intentionally redistributed the translations across the adjacent fragments to make the joined output read naturally.
The reasoning for each redistribution is documented in the code with
# 訳注: comments.Single Space Technique
As a result of redistribution, some fragments become redundant in Japanese (e.g., "Use", "There are", "Set to").
Since gettext treats
msgstr ""as untranslated and falls back to the English source,I have set these to
msgstr " "(a single half-width space).This effectively hides the text without triggering the fallback, and since it is rendered in HTML,
the extra whitespace is collapsed and does not affect the UI layout.
Side Note
Consolidating some of these fragmented strings into a single
msgidin the future would greatly simplify translation maintenance across all locales.