-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-02-26 at 11:00 +0100, Olav P. wrote:
Torsdag 26. februar 2009 10:05:04 skrev Jannick Kuhr:
2009/2/23 Karl Eichwalder <ke@suse.de>:
To avoid a fork-like product, it is desirable to align translations as close as possible. =A0It would be great if you could make use of SLE 11 translations, as vice versa SLE translators are encouraged to make use of openSUSE translations.
Could you tell me when and why these SLE translations have been created? In many files, especially files we (the german team) have proof read before the 11.1 release are very different (70%?). Many changes/improvements (conformity with Gnome/KDE!) are reverted, other strings are just translated differently - not better not worse. Of course some typos have been fixed, others been introduced. But in general I would say that at least our files recently proofread before the 11.1 release are better. I have the impression that for at least some files SLE did not make any use of our translations or real fork happened a long time ago. For example the installation.de.po from openSUSE is almost an other translation. There are only few strings the same and our openSUSE translations are absolutely ok. There was no reason to change almost every string and/or revert improvements made by the openSUSE team in the past. I am a bit angry about this situation and I don't understand why openSUSE should have a community based team, if there also payed translators working independently from us. I don't really understand why I should spend rare time in translating and improving translations for openSUSE, if S.u.S.E. has it's own teams... Sorry.
Kind regards, Jannick Kuhr (German OpenSUSE and KDE translation team)
I have not checked my language very recently, but I can relate to this from past experiences.
It is indeed quite annoying to fix bad translations (which I suspect comes from the SLES/SLED process), only to have the the same bad translations reintroduced before the next translation round.
I still haven't had time to do any verification, the script seems very arduous to use; and as I can't use 11.1, I can't try the "lokalize" trick, which I think would be neat. I'm not aware that any of the Spanish team has been able to do any checking yet. But from past experiences I fear I will not like the SLE translation. And I must say that if I can finally do any review, I'm 95% sure I will prefer the openSUSE translation to the SLE translation. Why? Because we took our time to do it, to dicusse terminology on our mail list, to check what other upstream translators use, etc. We are not professionals, but we took a lot of care. And we haven't seen the SLE translators asking us why we decided to translate that way and not the other, participating, or offering conseil. No, I will not take their changes unless argued that their choice is more correct than ours. Not unless I see clearly that we made a mistake. I don't speak for my entire team (Spanish), of course, but I have the feeling they think around these lines, too. Sorry. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmmkPYACgkQtTMYHG2NR9UR4wCcCHjsA/rG7W7cz46dUesxKLMH LHwAn1vDjRbZ3XLB0NlFKN0uXpPHh+PD =CNwl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org