Orange-OpenSource / Orange-OpenSource/ouds-android
Investigate how to support unit display in text inputs when RTL
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 22
- Forks
- 5
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 30
Description
Did you double check with Arabic people that this is how this should work? It seems strange to keep LTR orientation for the whole component (especially if there is another text input, which is not the case here) but on the other hand, I don't know what else we can do.
Originally posted by @florentmaitre in https://github.com/Orange-OpenSource/ouds-android/pull/1322#discussion_r3378293341
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
Start with the discussion in PR #1322 and inspect the current text-input behavior for unit display in RTL contexts. Clarify the expected behavior with Arabic users and define the component-level outcome before identifying the relevant implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- internationalization, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100