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 translation the newline was not
present:
https://github.com/jenkinsci/jenkins/commit/7918698#commitcomment-4384999
I don't know whether this was user error, or whether it indicates a
problem with the translation tool or import process.
Regards,
Chris
On 21/10/13 07:18, 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!)
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
