I really appreciate everyone reviewing the locales they understand.
However, the lack of commit access for many means that they'd have to leave comments and I would have to manually apply these changes. I think it'd be a lot more efficient for everyone if those who are fixing comments would do so as commits.
Let me take advantages of the opportunity that everyone is just one CLA away from the core committership.
But to make the localization edits more easily, what if I create a mirror of the core repository for the sole purpose of receiving localization edits?
We can then bundle up changes and merge them into the core, with a check that it's only editing *.properties
On 10/20/2013 10:18 PM, Kohsuke Kawaguchi wrote:
I've re-run the l10n applications and force-updated the localization-20131020 <https://github.com/jenkinsci/jenkins/commits/localization-20131020> ref. So people should see a different contents than my first attempt several hours ago. This time, I've looked at the changes more carefully and tightened up automatic checks, reject suspicious text, blacklisted some instances. As we discussed I've added the "addition only no edit" mode for German. If other locales want the same flag, let me know. I'll also most likely have to just throw away the entire Afrikaans translation. This locale is unfortunately selected as the default locale, so it ended up getting lots of translations to other languages where the submitter wasn't careful enough to select the right locale. I've seen some Hebrew and Russians, which were quite noticable because of the letters used, but I have to assume that other languages that aren't so easily distinguishable have also crept in. (This is a shame as Google Translate did verify that some of the submissions are legitimate Afrikaans!) 2013/10/20 Daniel Beck <[email protected] <mailto:[email protected]>> On 20.10.2013, at 23:45, Christoph Kutzinski <[email protected] <mailto:[email protected]>> wrote: > However, after looking at the German translation updates (https://github.com/jenkinsci/jenkins/commit/95f1d4b60d11fb0b68230690af708310de3cf07a), I doubt that this is in a state ready to be merged. > The main problem I see is that keys, which were already translated previously, were translated anew, and I often feel that the previously translated text was more 'correct' - i.e. feels more naturally to me. Seconded. "Nur jeweils letztes Bauvorhaben"? Also, the actual password used as the translation of 'Password' would be _very_ confusing. -- 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] <mailto:jenkinsci-dev%[email protected]>. For more options, visit https://groups.google.com/groups/opt_out. -- Kohsuke Kawaguchi -- 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.
-- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Jenkins Enterprise, our professional version of Jenkins -- 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.
