MerginMaps / MerginMaps/mobile
Improve translations workflow
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
Currently we have some setup to support translations in the app. For releasing we use combination of bash scripts (`update_i18n_ts.bash`, `release_i18n_qm.bash`) and incoming PRs from translators.
From Qt 6.7 the bash scripts could be replaced by cmake targets, which would streamline our setup to be more cmake oriented and less "held together by custom scripts". Besides that the developer experience is not the greatest. `update_i18n_ts.bash` requires path to Qt directory as argument, but `release_i18n_qm.bash` is expecting the path to be in `PATH`. The transition to cmake could also help us to use the Qt build with VCPKG instead of custom installation by developer.
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 reading update_i18n_ts.bash and release_i18n_qm.bash to document their current arguments and environment assumptions. Then inspect the existing CMake setup and Qt translation workflow; done means the release and update steps are represented by CMake targets and no longer depend on inconsistent Qt path handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, cmake, cpp
- Domain
- build-system, localization, mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100