Hello, I confirm that Russian translation is quite confusing (we enforce English localization for all users, but...).
In my opinion, the approach should be quite simple: All localization changes should be reviewed by people, who know the target language. It would be also useful to have automatic generation of per-language pull requests (e.g. on weekly basis). Best regards, Oleg Nenashev среда, 13 ноября 2013 г., 11:48:40 UTC+4 пользователь Роман Каган написал: > > Hi, > > I've upgraded to 1.539 and discovered that russian localization is > seriously spoiled. > > Some labels contain offensive words (!), some don't match the original, > some are plain garbage. > > They were introduced by > > commit 7828dcb46d9a18f88cc8e71046edc9ee91ed95e6 > Author: Kohsuke Kawaguchi <[email protected] <javascript:>> > Date: Sun Oct 20 22:10:02 2013 -0700 > > Community-contributed localization for Russian (ru) > > > So the problem is actually the quality of localization contributions > submitted via the translation plugin (which comes bundled and enabled with > the main jenkins package). > > AFAICS http://l10n.jenkins-ci.org/ accepts anonymous submissions so > nothing prevents an irresponsible user from submitting whatever crap they > like. > > What can be done about it? > > I guess the option of proofreading by a trusted editor before committing > into the main tree may not be available for a number of languages. > > Perhaps forcing authentication (e.g. via github or jenkins' jira) in the > translation plugin will make the contributions accountable and thus prevent > junk submissions? > > Thanks, > Roman. > > P.S. I'll go through that commit and submit a patch fixing the obvious > issues today or tomorrow. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
