Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Translations#144

Merged
shub39 merged 9 commits intomasterfrom
translations
Jul 1, 2025
Merged

Translations#144
shub39 merged 9 commits intomasterfrom
translations

Conversation

@shub39
Copy link
Owner

@shub39 shub39 commented Jul 1, 2025

Summary by CodeRabbit

  • New Features

    • Added new Estonian and Hebrew translations for various UI elements and messages.
    • Expanded Italian localization with new strings for error messages, UI customization, and app features.
  • Bug Fixes

    • Improved clarity and consistency in existing Italian and Hebrew translations.
  • Documentation

    • Updated Italian app metadata, including the app title, full description, and short description, to reflect new features and improved language.

elid and others added 8 commits June 22, 2025 07:01
Currently translated at 100.0% (125 of 125 strings)

Translation: Rush/strings
Translate-URL: https://hosted.weblate.org/projects/rush/strings/he/
Currently translated at 14.4% (18 of 125 strings)

Translation: Rush/strings
Translate-URL: https://hosted.weblate.org/projects/rush/strings/et/
Currently translated at 59.2% (74 of 125 strings)

Translation: Rush/strings
Translate-URL: https://hosted.weblate.org/projects/rush/strings/it/
Currently translated at 59.2% (74 of 125 strings)

Translation: Rush/strings
Translate-URL: https://hosted.weblate.org/projects/rush/strings/it/
Currently translated at 59.2% (74 of 125 strings)

Translation: Rush/strings
Translate-URL: https://hosted.weblate.org/projects/rush/strings/it/
Currently translated at 59.2% (74 of 125 strings)

Translation: Rush/strings
Translate-URL: https://hosted.weblate.org/projects/rush/strings/it/
Currently translated at 66.6% (2 of 3 strings)

Translation: Rush/metadata
Translate-URL: https://hosted.weblate.org/projects/rush/metadata/it/
Updated by "Remove blank strings" add-on in Weblate.

Translation: Rush/strings
Translate-URL: https://hosted.weblate.org/projects/rush/strings/
@coderabbitai
Copy link

coderabbitai bot commented Jul 1, 2025

Walkthrough

This update expands and refines localization support for Estonian, Hebrew, and Italian languages by adding and modifying string resources. Additionally, the Italian app metadata—including the app title, full description, and short description—has been updated for improved clarity and feature coverage. No code or structural changes were made.

Changes

File(s) Change Summary
app/src/commonMain/composeResources/values-et/strings.xml Added 10 new Estonian string resources for UI elements and messages.
app/src/commonMain/composeResources/values-he/strings.xml Added 3 new Hebrew strings; updated the value of "rush_branding".
app/src/commonMain/composeResources/values-it/strings.xml Modified and added numerous Italian strings for clarity, features, and error states; 1 removed.
fastlane/metadata/android/it-IT/full_description.txt Updated Italian app description: improved wording, added feature, and fixed formatting.
fastlane/metadata/android/it-IT/short_description.txt Updated Italian short description: added article and changed verb for consistency.
fastlane/metadata/android/it-IT/title.txt Changed Italian app title to include descriptive suffix.

Poem

In a warren of words, new phrases appear,
Estonian, Hebrew, Italian—now crystal clear!
Descriptions refined, app names extended,
With every translation, the user experience mended.
🐰 Hopping through languages, I’m happy to see
Our app now speaks with more clarity!


📜 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 f5b6383 and 9ac94a7.

📒 Files selected for processing (1)
  • app/src/commonMain/composeResources/values-it/strings.xml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • app/src/commonMain/composeResources/values-it/strings.xml

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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

🧹 Nitpick comments (3)
fastlane/metadata/android/it-IT/title.txt (1)

1-1: Check terminology – “lyrics” vs “testi”.
Using the English word “lyrics” in the Italian store-title may slightly hurt local discoverability (users tend to search “testi canzoni”). Consider “Rush – App testi canzoni” or similar, unless “lyrics” is a deliberate branding choice.

fastlane/metadata/android/it-IT/full_description.txt (1)

9-9: Typo: “perfomance” → “performance”.

- (Funzione sperimentale) Immagini "ipnotiche" per la pagina dei testi. Potrebbe impattare sulle perfomance
+ (Funzione sperimentale) Immagini "ipnotiche" per la pagina dei testi. Potrebbe impattare sulle performance
app/src/commonMain/composeResources/values-it/strings.xml (1)

81-81: Same typo as metadata – “perfomance”.

- Potrebbe impattare sulle perfomance
+ Potrebbe impattare sulle performance
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6d71f59 and f5b6383.

📒 Files selected for processing (6)
  • app/src/commonMain/composeResources/values-et/strings.xml (1 hunks)
  • app/src/commonMain/composeResources/values-he/strings.xml (2 hunks)
  • app/src/commonMain/composeResources/values-it/strings.xml (2 hunks)
  • fastlane/metadata/android/it-IT/full_description.txt (1 hunks)
  • fastlane/metadata/android/it-IT/short_description.txt (1 hunks)
  • fastlane/metadata/android/it-IT/title.txt (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: GitGuardian Security Checks
🔇 Additional comments (5)
app/src/commonMain/composeResources/values-et/strings.xml (2)

13-13: IO-error translation appears network-specific

Võrguühenduse viga narrows the scope to networking issues, whereas the original key io_error is a generic input/output failure. Consider a broader phrasing such as:

-    <string name="io_error">Võrguühenduse viga</string>
+    <string name="io_error">I/O viga</string>

or
<string name="io_error">Sisendi/väljundi viga</string>

to better preserve intent across non-network contexts.


11-20: New Estonian strings look consistent & complete

Keys, naming style, and capitalization align with existing resources; no placeholder mismatches detected.

app/src/commonMain/composeResources/values-he/strings.xml (2)

89-89: Consider marking brand strings as translatable="false"

“Rush” is now left in English, which is usually correct for a brand.
To avoid future accidental localisation across all languages, you may want to declare the key in the base values/strings.xml with translatable="false" and delete the per-locale overrides.


125-127: Minor wording / branding tweaks for new Hebrew strings

  1. rate_on_play – “חנות של גוגל” is uncommon; the standard Hebrew term is “Google Play”.
  2. bmc – If this refers to the “Buy Me a Coffee” service, keeping the English brand name usually improves recognition and avoids mistranslation.
  3. For both keys, consider adding a comment attribute (e.g. <!-- Google Play brand – do not translate -->) to guide future translators.

Example diff:

-    <string name="rate_on_play">דרג בחנות של גוגל</string>
+    <!-- Google Play brand – do not translate -->
+    <string name="rate_on_play">דרג ב-Google Play</string>
-    <string name="bmc">קנה לי קפה</string>
+    <!-- “Buy Me a Coffee” is a brand – keep English -->
+    <string name="bmc">Buy Me a Coffee</string>

[ suggest_nitpick ]

fastlane/metadata/android/it-IT/short_description.txt (1)

1-1: Looks good – within Play-Store length limits (≤80 chars).

@shub39 shub39 merged commit 56fd4b7 into master Jul 1, 2025
2 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Jul 27, 2025
@coderabbitai coderabbitai bot mentioned this pull request Aug 21, 2025
@coderabbitai coderabbitai bot mentioned this pull request Sep 2, 2025
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