Skip to content

Translations update from Hosted Weblate#100

Merged
OlaProeis merged 1 commit intoOlaProeis:masterfrom
weblate:weblate-ferrite-ferrite-ui
Mar 11, 2026
Merged

Translations update from Hosted Weblate#100
OlaProeis merged 1 commit intoOlaProeis:masterfrom
weblate:weblate-ferrite-ferrite-ui

Conversation

@weblate
Copy link
Contributor

@weblate weblate commented Mar 9, 2026

Translations update from Hosted Weblate for Ferrite/Ferrite UI.

Current translation status:

Weblate translation status

Summary by CodeRabbit

  • Localization
    • Updated Japanese language translations for improved clarity and consistency throughout the application.
    • Added new Japanese translations for expanded editor configuration options, including complex script support, default language selection, and header spacing settings.

Currently translated at 99.5% (733 of 736 strings)

Translation: Ferrite/Ferrite UI
Translate-URL: https://hosted.weblate.org/projects/ferrite/ferrite-ui/ja/
@coderabbitai
Copy link

coderabbitai bot commented Mar 9, 2026

📝 Walkthrough

Walkthrough

Updated Japanese localization strings in a single configuration file, adding new editor setting labels for complex scripts, default language, and header spacing, while modifying existing tooltip and notification text formatting.

Changes

Cohort / File(s) Summary
Japanese Localization Updates
locales/ja.yaml
Added 8 new editor settings keys (complex_scripts, default_language, header_spacing variants) and modified 3 existing keys (vim_mode_tooltip, settings_reset, pipeline.hint) with updated string values and formatting.

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly Related PRs

Poem

🐰 Hop through the locales, adding words with care,
Complex scripts, languages, spacing most fair!
Japanese strings in their proper place—
Settings now clearer, with improved grace! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: Japanese localization updates from Hosted Weblate, matching the file modified (locales/ja.yaml) and automated translation source.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@locales/ja.yaml`:
- Around line 181-183: The translation for the key complex_scripts is
misleadingly "追加スクリプト"; update the value for complex_scripts in locales/ja.yaml
to a phrase that conveys script/font categories (e.g., "複雑な文字体系" or "複雑なスクリプト")
so it correctly reflects the UI intent listing script families like Arabic,
Bengali, Devanagari, etc.; leave complex_scripts_hint unchanged.
- Around line 151-152: Replace the quoted, folded scalar value for the
vim_mode_tooltip key with a literal block scalar (use "|-" followed by the
tooltip lines) so the newline is preserved; update the value for
vim_mode_tooltip to a |- literal block, keep the same indentation level as the
key, place the two lines inside the block exactly as intended, and ensure
spacing/indentation matches the surrounding YAML to avoid parsing errors.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2863fa65-2a80-415e-996d-4b5bf933b83e

📥 Commits

Reviewing files that changed from the base of the PR and between aaed024 and 9335e34.

📒 Files selected for processing (1)
  • locales/ja.yaml

Comment on lines +151 to +152
vim_mode_tooltip: "Vimスタイルのモーダル編集を、通常モード、挿入モード、ビジュアルモードで有効にします。ナビゲーションには hjkl、挿入には
i、通常モードには Escを使用します。"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
python - <<'PY'
import sys, subprocess, pkgutil

if pkgutil.find_loader("yaml") is None:
    subprocess.check_call([sys.executable, "-m", "pip", "install", "-q", "PyYAML"])

import yaml

with open("locales/ja.yaml", encoding="utf-8") as f:
    data = yaml.safe_load(f)

value = data["settings"]["editor"]["vim_mode_tooltip"]
print(repr(value))
print("contains_newline =", "\n" in value)
PY

Repository: OlaProeis/Ferrite

Length of output: 172


Replace the wrapped quoted scalar with a literal block scalar to preserve newlines.

The YAML parser folds the double-quoted scalar into a single line, removing the intended line break. Use |- (literal block scalar, stripped final newline) to ensure the tooltip renders correctly with the line break intact.

Suggested fix
-    vim_mode_tooltip: "Vimスタイルのモーダル編集を、通常モード、挿入モード、ビジュアルモードで有効にします。ナビゲーションには hjkl、挿入には
-      i、通常モードには Escを使用します。"
+    vim_mode_tooltip: |-
+      Vimスタイルのモーダル編集を、通常モード、挿入モード、ビジュアルモードで有効にします。ナビゲーションには hjkl、挿入には
+      i、通常モードには Esc を使用します。
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
vim_mode_tooltip: "Vimスタイルのモーダル編集を、通常モード、挿入モード、ビジュアルモードで有効にします。ナビゲーションには hjkl、挿入には
i、通常モードには Escを使用します。"
vim_mode_tooltip: |-
Vimスタイルのモーダル編集を、通常モード、挿入モード、ビジュアルモードで有効にします。ナビゲーションには hjkl、挿入には
i、通常モードには Esc を使用します。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@locales/ja.yaml` around lines 151 - 152, Replace the quoted, folded scalar
value for the vim_mode_tooltip key with a literal block scalar (use "|-"
followed by the tooltip lines) so the newline is preserved; update the value for
vim_mode_tooltip to a |- literal block, keep the same indentation level as the
key, place the two lines inside the block exactly as intended, and ensure
spacing/indentation matches the surrounding YAML to avoid parsing errors.

Comment on lines +181 to +183
complex_scripts: 追加スクリプト
complex_scripts_hint:
アラビア語、ベンガル語、デーバナーガリー語、タイ語、ヘブライ語、タミル語、グルジア語、アルメニア語、エチオピア語などの文字体系のフォントを事前に選択できます。これらの文字体系を含むファイルを開くと、フォントがオンデマンドで読み込まれます。
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

complex_scripts is mistranslated here.

追加スクリプト reads like add-on scripts, but this section is about script/font categories such as Arabic, Bengali, and Devanagari. A label closer to 複雑な文字体系 or 複雑なスクリプト would match the UI intent better.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@locales/ja.yaml` around lines 181 - 183, The translation for the key
complex_scripts is misleadingly "追加スクリプト"; update the value for complex_scripts
in locales/ja.yaml to a phrase that conveys script/font categories (e.g.,
"複雑な文字体系" or "複雑なスクリプト") so it correctly reflects the UI intent listing script
families like Arabic, Bengali, Devanagari, etc.; leave complex_scripts_hint
unchanged.

@OlaProeis OlaProeis merged commit 1c5392a into OlaProeis:master Mar 11, 2026
2 checks passed
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.

3 participants