MerginMaps / MerginMaps/mobile
Check for correct argument expansion in translated strings
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
We often use constructions like these when creating translatable strings:
`showMessage( qsTr( "GPS currently unavailable.%1Try to allow GPS Location in your device settings." ).arg( "\n" ) )`
However, percentage signs can be tricky for translators. I have seen translations where there is a space between `%` and `1` which breaks the argument expansion and resulting string is without added arguments. In order to fix this, we could create additional CI workflow to automatically check whether the expansions are broken. Do you see other options?
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
The issue provides a translated-string example but names no source file, test, or workflow. Review the repository's translation handling and CI configuration, then determine an agreed way to detect malformed %n expansions. Done means the approach is defined and automated validation covers this failure mode.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, internationalization, mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100