Hi folk: Once we done with separate localization resource files, the end user will get a pure English version of Jenkins and plugins. This proposal has some benefits, e.g. more native language people could join the process of localization. But there is no need to give many people the commit permission. But there are some issues we need to consider.
First, it's not very friendly for someone is not familiar with English. Maybe a lot of people even don't know the exists of the language plugin(e.g. https://github.com/jenkinsci/localization-zh-cn-plugin). My proposal is here. Add a setting option in System Configuration of Jenkins core. This option allows users to choose their language. I think it's a common way to do this job like other many software. Another idea is that put the localization plugin into suggestion list. So we could detect browse user-agent setting then give the end users a friendly suggestion. I create a PR to implements the idea. Any opinion is welcomed. https://github.com/jenkinsci/jenkins/pull/3626 Background information ref: https://github.com/jenkinsci/jep/blob/master/jep/216/README.adoc Thanks in advance Rick -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1dcdb85f-1cdc-4ae2-a9d4-751412776f94%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
