Repository navigation
Import and update locales from upstream qBittorrent #2299
Replies: 1 comment
Agent BriefCategory: enhancement Current behavior: Where both projects ship the same language, wording drifts, and the French locale also drifts from itself: Desired behavior:
Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Whether qui adopts another project's translation data, commits to an ongoing sync with it, and how much machine-mapped text may ship without a native speaker's review are maintainer calls, as is the terminology question of whether qui should match qBittorrent wording or keep its own. |
Uh oh!
There was an error while loading. Please reload this page.
qBittorrent currently supports a couple dozen more languages than qui. If these were to be mapped to their equivalent qui lines and imported, a lot of locales would immediately be mostly functional and only the qui specific lines would need to be added.
Moreover, I've noticed a few discrepancies in the French locale of qBittorrent and qui, which is a bit jarring when switching between the two UIs (e.g. qBittorrent: "Dormant" & "Étiquettes" VS. qui: "Bloqué" & "Tags"). There's no reason to use different translations for those.
Getting and regularly updating these translations from upstream would reduce the workload for localizing qui and ensure better consistency between the two tools.
I'm guessing that since qui is already borrowing a lot from the qBittorrent upstream and both project are using a GPLv2 licence, this would not cause issues.
https://github.com/qbittorrent/qBittorrent/tree/master/src/webui/www/translations
https://github.com/qbittorrent/qBittorrent/tree/master/src/lang
All reactions