hiciefte opened a new issue, #6719: URL: https://github.com/apache/jmeter/issues/6719
The localisation guide says the coverage gaps are "due to lack of contributions," and the numbers back that up. I cloned `master` and counted the core `messages` bundle (1,522 keys, 11 languages): only French (96%) and Korean (93%) are close. The rest lag — German 35%, Traditional Chinese 38%, Japanese 29%, Norwegian 9% — and that's before the ~289 component bundles, which add a lot more untranslated strings. These land as hand-written PRs a component at a time, so they drift as English strings change. I maintain Bisq's localization tooling ([localize-pipeline](https://github.com/bisq-network/localize-pipeline)) and could set up a job that translates the changed keys and opens a PR to review. It stays off until someone sets a model key, never merges by itself, keeps the `{0}` placeholders intact, and handles the ISO-8859-1/`native2ascii` encoding these bundles use. It can run against a local model too. Worth pursuing? Happy to move this to `dev@` if that's the better place. And if AI-drafted translations are a no in principle, that's a fine answer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
