Skip to content

[CHORE]: Update Japanese translations - #2536

Open
KC-2001MS wants to merge 1 commit into
Dimillian:mainfrom
KC-2001MS:localization/ja
Open

KC-2001MS wants to merge 1 commit into
Dimillian:mainfrom
KC-2001MS:localization/ja

Conversation

@KC-2001MS

@KC-2001MS KC-2001MS commented Nov 9, 2026 •

Copy link
Copy Markdown

Description

This Pull Request fills in missing Japanese (ja) translations and replaces English placeholder values in IceCubesApp/Resources/Localization/Localizable.xcstrings. After this change, every key in the catalog has a Japanese entry (628 → 741 of 741 keys).

Only the Japanese localization is touched. No other locales, keys, or source files are changed.

Why it's needed

Several keys had the English value copied into the Japanese locale and marked as translated (e.g. settings.tabs.*, list.*, notifications.menu-title.quote*). Because they were marked translated, they didn't show up in Xcode's "untranslated" filter or in the SwiftPolyglot check, and Japanese users saw English text in those places. Many newer keys (App Intents / Shortcuts, notification filtering, collections, toasts) also had no Japanese entry at all.

What changed

Category Keys Notes
New Japanese translations 113 Keys that had no ja entry
English placeholders replaced 25 Keys whose ja value was the English source marked translated (e.g. settings.tabs.*, list.*, notifications.content-filter.*, notifications.menu-title.quote*, account.blocked, account.muted)
Existing translations corrected 2 settings.account.cached-posts-%@ (ポスト → 投稿 for consistency), trending-tag-people-talking %lld (was English)
Plural cleanup 8 Removed unused plural.one variants from ja. Japanese only has the other plural category in CLDR, so one is never used at runtime. The displayed other values are unchanged.

Translation decisions

  • Terminology follows the existing Japanese translations. For example, "post" → 投稿, "Visibility" → 可視性 (as in accessibility.editor.privacy.label), "Post visibility" → 投稿の公開範囲 (as in status.editor.visibility), "ALT" → 注釈, "Mention" → 返信.
  • Mastodon's official Japanese strings were used as a reference where this app had no precedent (e.g. collections → コレクション, notification policy wording).
  • Shortcut action titles are worded by behavior so that actions stay distinguishable in the Shortcuts app:
    • Opens the composer (PostIntent, PostImageIntent): 〜を作成する
    • Posts without opening the app (InlinePostIntent, InlinePostImageIntent): 〜を投稿する
  • Proper nouns stay in Latin script (Mastodon, Ice Cubes, TelemetryDeck, DeepL).
  • Visibility options in App Intents (Public, Quiet Public, Followers Only, Private) use the same Japanese wording as the in-app visibility picker (status.visibility.*), since they refer to the same visibility levels.

Things reviewers should be aware of

  • Some Japanese entries are intentionally left in the needs_review state.

Linked Issues

None.

Type of Change

  • Bug Fix
  • New Feature
  • Documentation
  • Localization

Checklist:

  • I have performed a self-review of my own changes.
  • Format specifiers (%lld, %@, %#@…@, %arg) in every changed Japanese string match the English source.
  • No locale other than ja and no key or metadata was changed (diffed against main).
  • The catalog is valid JSON, and all new and updated Japanese translations are in the translated state.
  • My changes generate no new warnings or errors in the compiler or runtime.
  • My code is able to build and run on my machine.

Screenshots (if applicable)

Not applicable. This Pull Request only changes translation strings.

Additional Notes

None.

- Add missing Japanese translations
- Replace English placeholder values in the Japanese locale
- Remove unused plural "one" variants from Japanese
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant