TeamAmaze / TeamAmaze/AmazeFileManager
In the language selector, the language names should be in that language, not current locale
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
In the language selector, the language names should be in that language, not current locale. Doing this simplifies problems with translations, where not all languages have translations to all locales (bqi for example). This is tagged as bug because some languages (such as Luri dialect), have no language names defined and only show the raw codes, which are illegible.
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
No file or test is named; locate the Android language-selector entry point and inspect how language names are resolved for the current locale. Reproduce the issue with Luri and bqi, then verify that each language displays its own name rather than a missing translation or raw code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- localization, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100