Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upRemove partial (less than 5% complete) translations #2813
Conversation
|
CC @KostyaSha regarding Belarusian. Maybe there are people who want to contribute to this area |
|
I would say the usefulness threshold is rather close to 50% than to 5%, but I agree with deletion of the translations. Alternative option would be to just comment the entries and then let translation contributors uncomment them if they feel the strings are useful |
|
I agree, but I think this should be a fairly uncontroversial change. And in some of the ~20-30% translations may be enough to make it reasonable to continue working on. FTR, localizations by % done right now:
|
|
Agreed. |
No-no-no) |
|
It's ok on my side. I sent the pull-request to remove wrong translations, otherwise the Jenkins interface was completely useless in basque. So if you completely remove the basque translation it's OK. I have no plans to maintain the basque translation. |
|
I'm also fine with deleting these localizations. |
|
Ready to go then |
…tial-translations
|
Merged master in after conflicts due to merging #2812. |
|
https://ci.jenkins.io/job/Core/job/jenkins/job/PR-2813/2/console
GHBS seems to be lying. The build is stable. |
daniel-beck commentedMar 19, 2017
•
edited
Proposed changelog entry:
Remove the following translations:
All of these localizations have less than 100 keys translated (the best translated of these is Indonesian with 73 keys, or 4.17%), and no localized HTML help files.
Don't get me wrong -- It would be great if Jenkins were translated into these languages, but the current state of these localizations is just not useful to anyone: Users don't have enough to allow them to use even the common functionality of Jenkins in their own language, and anyone wishing to translate into these languages gets unnecessarily constrained by previous decisions without a substantial part of the work already done.
And it's not like they're in progress either: All of these translations have been contributed in 2013 or earlier, with the exception of @erral's #2731. (@erral If you decide to do some more work on this localization I'd be happy to restore these, and explain our tooling to get you started.) Otherwise, the few changes since then were some cleanup by @albers in 2014, and adaptations to changed code structure.
I don't think 100 keys/5% is the threshold after which a localization suddenly becomes useful, but this at least gets rid of the translations that never even tried to have reasonable coverage, often probably one person translating just a single screen (at most) via Translation Assistance.