-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.00.0902271710430.20726@nimrodel.valinor> El 2009-02-27 a las 16:27 +0100, Camaleón escribió:
Entonces, efectivamente han despreciado nuestras traducciones? Cómo saberlo finalmente y de manera acertada?
Ya postee la prueba fehaciente anoche. Mira en el src.rpm.
No entiendo nada :-/
SLED/SLES es Novell, y yo no traduzco para Novell. Ni me pagan ni quiero que lo hagan. ¿Qué me importa a mí lo que haga Novell con sus traducciones?. El trabajo que yo he hecho es libre, lo puede usar quien quiera, sea Novell o sea Microsoft.
Lo que no vería correcto es que sus traducciones "eliminen" las nuestras, pero no es eso lo que ha pasado o al menos así lo he entendido.
No veo en este PO a Novell ni a sus traducciones por ninguna parte:
<https://forgesvn1.novell.com/viewsvn/suse-i18n/trunk/lcn/es/po/zypper.es .po>
Y dale. Es que no es ese el .po que han usado en el upgrade del yast. Mira en el zypper-1.0.5-2.1.2.src.rpm. Yo lo hice anoche y postee la cabecera. Te puedo enviar el po entero para que lo compruebes.
Y nosotros vamos a trabajar sobre "ese archivo" y openSUSE va a llevar las traducciones de "ese archivo".
¡No señora! Lleva las traduciones de la rama SLE. Stephan Kulow ha reconocido el problema y dicho que lo van a arreglar. I can at least tell some: the problem was mainly that packages that were meant purely for SLE (i.e. only containting SLE languages, not all openSUSE ones) were checked in into Factory to get the bug fixes within that packages into Factory fast. That this regressed the translations for the moment in Factory was seen as smaller evil. What should not have happened is that the zypper maintainer "merged" SLE and openSUSE translations for an 11.1 online update. Of course Jan did with good intention, taking that SLE translations had more time - but now he knowsbetter ;( But this is tracked in bug 473004 and there is already a new update in testing that is fixing this problem. There isn't and never was an intention to automatically merge the SLE translations. The SLE translators had a different time scale, different requirements and different tools - so it's clear that there is no simple merging. The code11 branch is there and open and you can grab from it what's considered good or file bug reports if you consider something bad (if you care for SLE, of course noone expects you too). Again: We will not throw away any translation work done for 11.1 when going towards 11.2 - the opposite is true. I went great lengths to rewrite the desktop files handling to give you a way to look at conflicts. And not even about SLE conflicts, but I already do not dare to throw away work that upstream did differently. Greetings, Stephan - -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmoEe0ACgkQtTMYHG2NR9UMOACdEaLdkKMgH+HkT/Qkkz1qoJXT Nt4Aniql4AfIa3+RcLp0KFp5z9OCefkd =UCG7 -----END PGP SIGNATURE-----