wordpress-mobile / wordpress-mobile/WordPress-Android
Use Arabic numerals consistently
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Expected behavior
Arabic numerals (1 2 3 4 5 6 7 8 9 0) should be used everywhere all the time.
Actual behavior
When Arabic is the selected app language, in a number of places, but not consistently, we use Indo-Arabic numerals instead of normal Arabic numerals. We would do better to consistently use Arabic numerals (the regular ones we’re used to) rather than Eastern Arabic (Indo-Arabic) numerals – (٠ ١ ٢ ٣ ٤ ٥ ٦ ٧ ٨ ٩) – because everyone who reads Arabic knows the Arabic numerals, but not all know the Indo-Arabic numerals.
This looks especially strange on screens where we use both types of numerals:

Steps to reproduce the behavior
- Head to Me > App Settings > Interface Language and select Arabic.
- Explore the app and find the Eastern Arabic numerals displayed in various places.
I've seen them in the Stats Card and Screens, Blogging Prompts Card, while selecting Media, and in Reader (dates)
Tested on Samsung Galaxy S21, Android 12, WPAndroid 20.4-rc-2
Internal reference: p5T066-3jv-p2#comment-12698
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Select Arabic under Me > App Settings > Interface Language and reproduce the inconsistent numerals in the Stats Card, Screens, Blogging Prompts Card, Media selection, and Reader dates. Trace each affected screen or entry point, then verify that displayed numbers consistently use Arabic numerals rather than Eastern Arabic numerals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- internationalization, localization, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100