Skip to content

chore: translations 202602 follow-up#7142

Merged
PastaPastaPasta merged 1 commit intodashpay:developfrom
UdjinM6:translate_202602_2
Feb 13, 2026
Merged

chore: translations 202602 follow-up#7142
PastaPastaPasta merged 1 commit intodashpay:developfrom
UdjinM6:translate_202602_2

Conversation

@UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Feb 13, 2026

Issue being fixed or feature implemented

Apply some of @coderabbitai suggestions from #7141

What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

@UdjinM6 UdjinM6 added this to the 23.1 milestone Feb 13, 2026
@coderabbitai
Copy link

coderabbitai bot commented Feb 13, 2026

Walkthrough

This pull request updates translation strings in seven Qt locale files (Arabic, Bulgarian, German, French, Italian, Dutch, and Polish). Changes are textual: adjusting directionality text, improving tooltip and context menu wording, fixing grammatical agreement and pluralization, and refining several UI labels. No public APIs, method signatures, or runtime control flow are modified; the changes affect only localization resources.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly describes the changeset as a translation follow-up update for February 2026, which accurately reflects the multiple translation file corrections across multiple locales.
Description check ✅ Passed The description references applying CodeRabbit suggestions from PR #7141 and directly relates to the translation updates present in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into develop

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

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

No actionable comments were generated in the recent review. 🎉


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: 1

🤖 Fix all issues with AI agents
In `@src/qt/locale/dash_pl.ts`:
- Around line 177-179: The translation for the source string "Font in the
Overview tab: " currently uses "Podsumowanie" ("Czcionka w zakładce
Podsumowanie: "); change it to use the consistent term "Przegląd" (e.g.,
"Czcionka w zakładce Przegląd: ") so it matches other Overview translations in
this file and across the UI.

@github-actions
Copy link

github-actions bot commented Feb 13, 2026

✅ No Merge Conflicts Detected

This PR currently has no conflicts with other open PRs.

@UdjinM6
Copy link
Author

UdjinM6 commented Feb 13, 2026

should be ready to merge

@PastaPastaPasta PastaPastaPasta merged commit 95f2f29 into dashpay:develop Feb 13, 2026
20 of 21 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.

2 participants