Skip to content

Add Persian localization - #1122

Open
aliafshany wants to merge 1 commit into
Nain57:masterfrom
aliafshany:add-persian-localization
Open

aliafshany wants to merge 1 commit into
Nain57:masterfrom
aliafshany:add-persian-localization

Conversation

@aliafshany

Copy link
Copy Markdown

📝 Description of the pull request, what, why and where

Adds Persian (fa): a values-fa/strings.xml next to each of the 14 English strings.xml files (app, core and feature modules, including the playStore revenue flavor), 638 strings and plural forms in all. Strings marked translatable="false" are left out. Android picks the locale up from the resource folders, so nothing else needs registering.

Persian nouns stay singular after a number, so the one and other plural forms often share the same text. Product names (Klick'r, Smart AutoClicker, Google Play, F-Droid) stay in English.

Checks: xmllint passes on every new file, every translatable key matches the English file with nothing missing or extra, format specifiers (%s, %d, %1$s) match per string, and apostrophes are escaped. I could not build the app locally (no Android SDK on this machine).

AI disclosure: the translation was drafted with AI (Gemini 3.8 Flash in Antigravity, with Claude Code for building the files) and checked with automated validation: every key present, format specifiers and escapes, and no Arabic-only letter forms (ي, ك). I am a native Persian speaker.

✅ How to test

  • Set the device language to Persian (فارسی).
  • Open the app and go through the scenario list, the event and action editors, and the tutorial.

📹 Demo

Not applicable: string resources only.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Nain57

Nain57 commented Nov 2, 2026 •

Copy link
Copy Markdown
Owner

Hi and thank you for your contribution.

I see you only translated strings.xml files, but there is multiple localization files that are not named like that:

  • In feature/tutorials: all tutorials, categories and slideshows are localized in their respective file, they are all located under values folder, prefixed with strings_
  • In feature/smart-config: event_default_config.xml contains the default names for all edtiable values (Same thing with feature/dumb, deumb_actions_default_config"

There might be more missing. I see you use IA to help you, you can use the following prompt to get a list of the missing translations:

I'm adding a new translation to this Android project in the `values-fa` resource folders. So far I've only translated the `strings.xml` files, but other XML files under `res/values/` also contain translatable strings.

Please list every file I still need to translate. Don't change any files.

1. Find every XML file under `*/src/*/res/values/` (skip `build/` directories) that contains `<string>`, `<plurals>` or `<string-array>` elements.
2. Ignore any file where every string is marked `translatable="false"`, and ignore any element marked that way when counting.
3. For each remaining file, check whether the same file exists in the matching `res/values-fa/` folder of the same module and source set.
4. Show the result as a table with these columns: module path, file name, and status ("missing", or "partial" with the number of untranslated keys). Group the rows by module.
5. Also report any `strings.xml` in `values-fa` that is missing keys that exist in the default `values/strings.xml`. List those missing key names.

Finish with the total number of files and strings that still need translating.

@Nain57 Nain57 self-assigned this Nov 2, 2026

@Nain57 Nain57 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Requested changes: provide missing translations

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