Yes, once we get more localization plugins then add such page.
On Tue, Oct 2, 2018 at 7:52 PM Oleg Nenashev wrote:
> I am fine with the proposed approach.
> There are some edge cases, but it should work well.
>
> At some point we could add "Localizations" page to the installation
> Wizard, if
I am fine with the proposed approach.
There are some edge cases, but it should work well.
At some point we could add "Localizations" page to the installation Wizard,
if there are many such plugins created.
BR, Oleg
On Monday, October 1, 2018 at 3:26:46 PM UTC+2, Jesse Glick wrote:
>
> On Sat,
On Sat, Sep 29, 2018 at 10:38 PM Rick wrote:
> detect browse user-agent setting
As far as I know this is how locale is normally taken into account in
Jenkins, so this proposal makes sense to me.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers"
I like the setting options for language, this is appreciable for us.
Changing the language easily benefits comparing different version
documentation when getting confusing at reading.
Rick 于2018年9月30日周日 上午10:38写道：
> Hi folk:
>
> Once we done with separate localization resource files, the end
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
