TeamAmaze / TeamAmaze/AmazeFileManager
Add context to string.xml for better translation
Open
Nobody has claimed this yet.
Area-CodeHealth
Area-Internationalization
Issue-Task (low)
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
Describe the bug
Stuff like:
- character limits
- what view it will go on
- if it should be a verb, adjective or noun
- what the %s should will contain with examples
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 by locating the Android string.xml resources and reviewing entries where translators need character limits, UI placement, grammatical role, or %s placeholder details. Add translator-facing context for the affected strings, including placeholder examples where applicable, and verify that the resource files remain valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- localization
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100