On Mon, Aug 27, 2018 at 5:33 AM arch <[email protected]> wrote: > We could create a Chinese Localization plugin for Jenkins core. But we can't > create every localization for other plugins. Right? Because there are lots of > them.
I do not see a problem here. If you are working on the Chinese localization, or Albanian or whatever, you get to decide how much you wish to localize. If you have time to localize every plugin listed in the Setup wizard and then some others, great. If you can only manage some of the most commonly seen screens (and maybe only part of core), so be it. You need to balance the desire for completeness with available resources, and keep in mind that as code is changed and refactored over time there will be some new message keys and some obsolete ones, so there is an ongoing cost proportional to the size of the localization. -- 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/CANfRfr3DoWyNdO%2BoacHxNx7vO%3DqpUV-xj8XjbFZM6fuTKCvj_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
