On 21 Oct 2013 at 10:10, Kohsuke Kawaguchi wrote:
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.
There seemed to come in no more
Thanks! Now that RC for 1.538 is created, I'm merging them into
1.539-SNAPSHOT.
2013/10/28 Harald Albers jenkins-...@folk.de
**
On 21 Oct 2013 at 10:10, Kohsuke Kawaguchi wrote:
I really appreciate everyone reviewing the locales they understand.
However, the lack of commit access for
This submitted localization has a lot of contributions to plugins, too.
What's the best way to do this? I'm thinking about:
- Create a branch like the one we created for the core in all the affected
plugins, committing one locale at a time
- Generate a separate set of files that show all the
Hi,
I've added some comments to the Spanish commit:
https://github.com/jenkinsci/jenkins/commit/68890bb641cb587b7b73b032310b2a725a05c3ec
.
Regards.
Marcelo Rebasti
On Mon, Oct 21, 2013 at 2:18 AM, Kohsuke Kawaguchi k...@kohsuke.org wrote:
I've re-run the l10n applications and force-updated
I went through the en_GB translations.
Most translations are either empty files, or files which do not differ
at all from en_US. So it would be nice if we could filter that out.
I did find one issue, where a string in the original file was split over
two lines, with a backslash. But in the
On 10/21/2013 09:34 AM, Christopher Orr wrote:
I went through the en_GB translations.
Most translations are either empty files, or files which do not differ
at all from en_US. So it would be nice if we could filter that out.
I did filter out the case where a key and a value are the same.
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
Thanks for doing this Kohsuke!
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
There are spelling differences between en_US and en_GB, but that
translation has some jokes in it, too, which probably should not be used:
login=Ascend
Back\ to\ Project=open thy kingdom
+Changes=change is inevitable. See it happen?+Console\ Output=stuff
+Edit\ Build\ Information=Edit Build
open thy kingdom :-)
If the key and the value are the same, they shouldn't be added, so I think
the program that generates diff needs some improvements, too.
2013/10/20 Marc MacIntyre marc...@purestorage.com
There are spelling differences between en_US and en_GB, but that
translation has
BTW, the program that applies the submitted changes is in
https://github.com/jenkinsci/backend-l10n-applier
2013/10/20 Christoph Kutzinski ku...@gmx.de
Thanks for doing this Kohsuke!
However, after looking at the German translation updates (
https://github.com/jenkinsci/**jenkins/commit/**
On 20 October 2013 22:45, Christoph Kutzinski ku...@gmx.de wrote:
Thanks for doing this Kohsuke!
However, after looking at the German translation updates (
https://github.com/jenkinsci/**jenkins/commit/**
On 20.10.2013, at 23:45, Christoph Kutzinski ku...@gmx.de 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
I've re-run the l10n applications and force-updated the
localization-20131020https://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
14 matches
Mail list logo
