I cloned master and counted how complete each translation is against messages.properties (329 keys, 17 languages). Turkish is the most complete at 90%, but a lot are well behind — Estonian 6%, Japanese 21%, Lithuanian 43%, Russian 57% — and German and Spanish sit around 78%. The app already ships preferences.language.someIncomplete for exactly this, so it's a known thing.
Since translations come in as hand-written PRs, the older languages drift as English strings change and mostly don't catch back up.
I maintain Bisq's localization tooling (localize-pipeline) and could set up a workflow that translates the changed keys and opens a PR to review. It stays off until someone adds a model key, never merges by itself, keeps the {0} placeholders intact, and can run against a local model if you'd rather keep strings local.
Before I put up a PR: is this worth having here? If AI-drafted translations are a no for you, that's fine — just say so and I'll leave it.
cc @angryziber
I cloned
masterand counted how complete each translation is againstmessages.properties(329 keys, 17 languages). Turkish is the most complete at 90%, but a lot are well behind — Estonian 6%, Japanese 21%, Lithuanian 43%, Russian 57% — and German and Spanish sit around 78%. The app already shipspreferences.language.someIncompletefor exactly this, so it's a known thing.Since translations come in as hand-written PRs, the older languages drift as English strings change and mostly don't catch back up.
I maintain Bisq's localization tooling (localize-pipeline) and could set up a workflow that translates the changed keys and opens a PR to review. It stays off until someone adds a model key, never merges by itself, keeps the
{0}placeholders intact, and can run against a local model if you'd rather keep strings local.Before I put up a PR: is this worth having here? If AI-drafted translations are a no for you, that's fine — just say so and I'll leave it.
cc @angryziber