Android RTL Rendering Mathematical Symbols and Number Groups Backwards
Nessuno ha ancora preso questa issue.
- Lingua principale
- C++
- Stelle
- 127k
- Fork
- 25.3k
- Merge medio
- 1g 23h
- PR unite (30g)
- 4
Descrizione
Description
Since upgrading to Expo 53/54, we are seeing a big change in how numbers are rendered in Arabic mode (RTL) on Android.
Here are some examples of differences we're seeing (tested on both Expo 53 and Expo 54 using 0.79.5 and 0.81.5 respectively)
Expo 52 (RN 0.76.9): -123.456
Expo 53 (RN 0.79.5): 123.456-
Expo 54 (RN 0.81.5): 123.456-
Expo 52 (RN 0.76.9): +455.234
Expo 53 (RN 0.79.5): 455.234+
Expo 54 (RN 0.81.5): 455.234+
Expo 52 (RN 0.76.9): 12 - 13 = 25
Expo 53 (RN 0.79.5): 25 = 13 - 12
Expo 54 (RN 0.81.5): 25 = 13 - 12
I'm unable to find any documentation regarding this change which is not being applied on iOS (causing a lot of differences between the two devices). Please see the attached screenshots for more details.
Expo 52 repo: https://github.com/steinalex/expo-52-arabic-numbers
Expo 54 repo: https://github.com/steinalex/expo-54-arabic-numbers
Is there a way to opt out of this on Android and always render numbers with mathematical symbols in LTR mode?
The only way around it so far is to manually inject the LRT unicode character '\u200E' everywhere, but that's not a viable solution for our very large project.
Whilst I'm using Expo templates to help generate a minimal example, I do not believe this is an Expo specific issue.
Steps to reproduce
- Install the minimal retro
- Observe the difference in the numbers being rendered between React Native versions
React Native Version
0.79.5+
Affected Platforms
Runtime - Android
Output of npx @react-native-community/cli info
System:
OS: macOS 15.7.1
CPU: (10) arm64 Apple M1 Pro
Memory: 156.45 MB / 32.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.17.1
path: /Users/alex.stein/.asdf/installs/nodejs/22.17.1/bin/node
Yarn:
version: 1.22.19
path: /Users/alex.stein/.asdf/shims/yarn
npm:
version: 10.9.2
path: /Users/alex.stein/.asdf/plugins/nodejs/shims/npm
Watchman:
version: 2025.03.10.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 25.1
- iOS 26.1
- macOS 26.1
- tvOS 26.1
- visionOS 26.1
- watchOS 26.1
Android SDK: Not Found
IDEs:
Android Studio: 2024.3 AI-243.24978.46.2431.13208083
Xcode:
version: 26.1.1/17B100
path: /usr/bin/xcodebuild
Languages:
Java:
version: 11.0.16.1
path: /Users/alex.stein/.asdf/shims/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 19.1.0
wanted: 19.1.0
react-native:
installed: 0.81.5
wanted: 0.81.5
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Stacktrace or Logs
N/A
MANDATORY Reproducer
https://github.com/steinalex/expo-54-arabic-numbers
Screenshots and Videos
| Expo 52 (Android) | Expo 54 (Android) |
|---|---|
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Esegui il riproduttore obbligatorio di Expo 54 e confronta il suo output RTL su Android con l’esempio di Expo 52, concentrandoti su React Native 0.76.9 rispetto a 0.79.5/0.81.5. Il lavoro è completato quando viene determinato se Android può eguagliare la precedente gestione LTR dei simboli matematici e dei gruppi di numeri oppure esporre un’opzione di esclusione documentata senza richiedere caratteri \u200E per ogni valore.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- android, react-native
- Ambito
- internationalization, mobile-dev
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100