New Crowdin updates

[nicotsx]

Summary by CodeRabbit

• Localization
  • Updated Vietnamese text for the "ignore update" action.
  • Updated Hungarian translations across the UI, including version actions, notes, save/error messages, validation, settings, and various app strings.
  • Updated Italian translations and wording for backups, App Store flows, My Apps actions, settings, domain/errors, and general UI copy.
  • Updated Turkish translations for My Apps batch actions (start/stop/restart) and related labels/subtitles.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated localization string values across four locale JSON files (vi-VN.json, hu-HU.json, it-IT.json, tr-TR.json). Only translation string values were modified; no keys, file structure, exported signatures, or control flow changed.

Changes

Cohort / File(s)	Summary
Vietnamese translation packages/backend/src/modules/i18n/translations/vi-VN.json	Updated APP_ACTION_IGNORE_VERSION value to "Bỏ qua cập nhật này". Only string content changed.
Hungarian translations packages/backend/src/modules/i18n/translations/hu-HU.json	Updated many UI string values to Hungarian (e.g., APP_ACTION_IGNORE_VERSION, APP_ACTION_UNIGNORE_VERSION, APP_ACTION_IGNORE_VERSION_SUCCESS, APP_ACTION_UNIGNORE_VERSION_SUCCESS, APP_DETAILS_NOTES, APP_NOTES_SAVE_SUCCESS, multiple APP_ERROR_*, CUSTOM_APP_*, file validation messages, settings and app-related labels). Only string content changed.
Italian translations packages/backend/src/modules/i18n/translations/it-IT.json	Updated multiple UI strings to Italian (e.g., backup/tab titles, App Store dialog/form labels, MY_APPS actions, settings and domain-related messages). Only string content changed.
Turkish translations packages/backend/src/modules/i18n/translations/tr-TR.json	Updated several MY_APPS_* strings to Turkish (start/stop/restart/batch action labels and subtitles such as MY_APPS_START_ALL_*, MY_APPS_STOP_ALL_*, MY_APPS_RESTART_ALL_*, MY_APPS_BATCH_ACTIONS). Only string content changed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify JSON validity and encoding for the four files.
• Confirm no accidental key renames or structural changes.
• Spot-check translations for escaping, punctuation, and typos.

Possibly related PRs

• New Crowdin updates #2471 — Overlapping i18n edits touching APP_ACTION_IGNORE_VERSION and related keys across locales.
• New Crowdin updates #2489 — Updates MY_APPS_* translation keys across locale files (start/stop/restart/batch actions).
• New Crowdin updates #2474 — Edits to it-IT.json and other locale files with overlapping translation keys.

Suggested labels

size/L

Suggested reviewers

• Onigam

Pre-merge checks and finishing touches

✅ 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 'New Crowdin updates' accurately reflects the main change in the pull request—localization updates across multiple language translation files via Crowdin.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch l10n_develop2

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4a2e109 and 7ea2cea.

📒 Files selected for processing (1)

• packages/backend/src/modules/i18n/translations/tr-TR.json (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: nicotsx
Repo: runtipi/runtipi PR: 0
File: :0-0
Timestamp: 2025-04-06T14:59:45.074Z
Learning: When updating translations from external systems like Crowdin, ensure that proper translations in native languages aren't replaced with English fallbacks. When only a brand name needs to be updated (like "Tipi" to "Runtipi"), preserve the existing translated text and only change the specific brand reference.

Learnt from: nicotsx
Repo: runtipi/runtipi PR: 2371
File: packages/backend/src/modules/i18n/translations/da-DK.json:0-0
Timestamp: 2025-10-14T19:37:24.136Z
Learning: Repository: runtipi/runtipi
Context: i18n translations under packages/backend/src/modules/i18n/translations/**
Preference: It is acceptable to keep English fallback values for newly auto-added keys from Crowdin in non-English locale files (e.g., SYSTEM_ERROR_INVALID_BODY in da-DK.json). Do not flag these as issues or request translations. However, do not overwrite existing proper native translations with English fallbacks when updating from Crowdin.

Learnt from: nicotsx
Repo: runtipi/runtipi PR: 2079
File: packages/backend/src/modules/i18n/translations/de-DE.json:213-213
Timestamp: 2025-05-04T16:53:35.189Z
Learning: For the runtipi repository, don't flag English text in non-English localization files as errors. This is part of their normal localization process where strings are first added in English and then gradually translated.

Learnt from: nicotsx
Repo: runtipi/runtipi PR: 0
File: :0-0
Timestamp: 2025-04-06T14:59:45.074Z
Learning: In translation files, when rebranding from "Tipi" to "Runtipi" is performed, only the brand name should be replaced while preserving the existing translated text in the native language.

Learnt from: nicotsx
Repo: runtipi/runtipi PR: 0
File: :0-0
Timestamp: 2025-04-06T14:59:45.074Z
Learning: When updating branding in translation files (e.g., changing "Tipi" to "Runtipi"), only the brand name should be replaced while preserving the rest of the existing translated text in each native language. Replacing entire translated sentences with English equivalents should be avoided as it reduces localization quality.

📚 Learning: 2025-10-14T19:37:24.136Z

Learnt from: nicotsx
Repo: runtipi/runtipi PR: 2371
File: packages/backend/src/modules/i18n/translations/da-DK.json:0-0
Timestamp: 2025-10-14T19:37:24.136Z
Learning: Repository: runtipi/runtipi
Context: i18n translations under packages/backend/src/modules/i18n/translations/**
Preference: It is acceptable to keep English fallback values for newly auto-added keys from Crowdin in non-English locale files (e.g., SYSTEM_ERROR_INVALID_BODY in da-DK.json). Do not flag these as issues or request translations. However, do not overwrite existing proper native translations with English fallbacks when updating from Crowdin.

Applied to files:

• packages/backend/src/modules/i18n/translations/tr-TR.json

📚 Learning: 2024-10-08T15:38:59.539Z

Learnt from: meienberger
Repo: runtipi/runtipi PR: 1522
File: src/client/messages/pl-PL.json:1-1
Timestamp: 2024-10-08T15:38:59.539Z
Learning: The translations for application messages and actions in the `src/client/messages/pl-PL.json` file are accurate and contextually appropriate.

Applied to files:

• packages/backend/src/modules/i18n/translations/tr-TR.json

🔇 Additional comments (1)

packages/backend/src/modules/i18n/translations/tr-TR.json (1)

420-432: Turkish translations for batch actions look good.

The MY_APPS batch action strings have been properly translated from English fallbacks to Turkish equivalents. The terminology is consistent with existing translations in the file (e.g., "Tümünü" for "all", "Tüm uygulamalar" for "all apps"). The grammatical structure and context-appropriate phrasing align with standard Turkish UI conventions.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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