> > In language diverse communities or organizations, having to install (or > request installation) of a new translation plugin every month, because now > a > French/German/Italian/Russian/Portuguese/Spanish/Chinese/Turkish/Polish/Czech/… > speaking person wants their Jenkins localized in their own language seems > cumbersome.
I do not know any organization which actually does that. Usually Jenkins is managed via various shared services teams if it gets to such scale, and having different localizations makes the system generally unsupportable. Imagine you get a support tickets with screenshots in Russian.. oh wait, it happens in JIRA sometimes. Usually Jenkins admins end up enforcing a single locale using the Locale Plugin. I do not anticipate large-scale instances to require many localization plugins, and I do not see a particular need in an aggregator plugin, especially taking our experience with maintaining them. For example, the current version of Pipeline aggregator just contains obsolete plugins with known incompatibilities like JEP-200. BR, Oleg On Tue, Aug 28, 2018 at 2:36 PM arch <[email protected]> wrote: > Thanks for your checklist and suggestion. That's really great. > > On Tue, Aug 28, 2018 at 6:57 PM Jesse Glick <[email protected]> wrote: > >> On Tue, Aug 28, 2018 at 2:34 AM arch <[email protected]> wrote: >> > Agree with this solution. And I give a prototype plugin. >> https://github.com/LinuxSuRen/localization-plugin >> >> Nice, did you get this to work already? There are a few things to check: >> >> · core vs. plugin localization >> · `Messages_zh_CN.properties` (so `Messages.some_key()` Java calls) >> · `*_zh_CN.properties` (localization from Jelly views like `index`) >> · `help*_zh_CN.html` if these are even supported (I cannot remember >> offhand) >> · `mvn hpi:run` incl. live reloading after saving a resource in the >> source tree >> · effectiveness in a `$JENKINS_HOME/plugins/*.jpi` (this is a >> different class loading mode) >> >> > Do I need to create a ticket on JIRA or just everyone take a look at >> this project? >> >> I think this would make a good JEP describing what you propose to do >> and making sure other localizers are ready to coöperate, since this >> clearly goes beyond a usual plugin HOSTING request: it would involve >> _removing_ localization resources from lots of existing repositories, >> adjusting the default plugin list in the Setup wizard, and maybe some >> infrastructure tasks. And there are some details that need to be >> settled such as the plugin code names (which cannot be changed after >> publishing): rather than, say, `chinese-localization` I might suggest >> something more regular like `localization-zh_CN`. >> >> -- >> 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/CANfRfr1YJ0BuDZ6mXAKO%2BUFkG0tFiun6W-9GpWSfxVyUr5%2BZPw%40mail.gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/jeKVskUwE8M/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFX5My%3D1ADt_tb0ySVVO254cF%3DhE0SfKOxXMLfvHYytNg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFX5My%3D1ADt_tb0ySVVO254cF%3DhE0SfKOxXMLfvHYytNg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPfivLBodAg-HbuhCZkc%3DoJbnditUt8uyaW-Jf-pqPpTVA0P4g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
