Repository navigation
Add Persian localization - #1122
Open
aliafshany wants to merge 1 commit into
Open
aliafshany wants to merge 1 commit into
aliafshany wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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:
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: |
Nain57
requested changes
Nov 2, 2026
Nain57
left a comment
Owner
There was a problem hiding this comment.
Requested changes: provide missing translations
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Description of the pull request, what, why and where
Adds Persian (fa): a
values-fa/strings.xmlnext to each of the 14 Englishstrings.xmlfiles (app, core and feature modules, including the playStore revenue flavor), 638 strings and plural forms in all. Strings markedtranslatable="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
oneandotherplural forms often share the same text. Product names (Klick'r, Smart AutoClicker, Google Play, F-Droid) stay in English.Checks:
xmllintpasses 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
📹 Demo
Not applicable: string resources only.
🤖 Generated with Claude Code