[opensuse-translation] webyast pots are obsolete
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 They are dated May 2010. I can not translate them till this is done. Bug 671870 - Webyast POTs are obsolete. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1Zmv8ACgkQtTMYHG2NR9V8/QCeIZC2uR04hP2AdA7gr1kZD8+L uxEAn0sE3cz3HFOS9ZqiIH63v7Qw+NIW =rxWk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
2011/2/15 Carlos E. R. <carlos.e.r@opensuse.org>:
They are dated May 2010. I can not translate them till this is done.
Bug 671870 - Webyast POTs are obsolete. Are you sure there's something THAT new? Latest tweet about webyast development is almost a year old... -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Tirsdag den 15. februar 2011 08:57:02 skrev Александр Мелентьев:
2011/2/15 Carlos E. R. <carlos.e.r@opensuse.org>:
They are dated May 2010. I can not translate them till this is done.
Bug 671870 - Webyast POTs are obsolete.
Are you sure there's something THAT new? Latest tweet about webyast development is almost a year old...
Maybe you shouldn't rely solely on microblogs for your information ;-) At least this is a lot less than one year old: http://lizards.opensuse.org/2010/12/21/easy-use-of-webyast-for-opensuse-11-3... -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Maybe you shouldn't rely solely on microblogs for your information ;-)
At least this is a lot less than one year old: http://lizards.opensuse.org/2010/12/21/easy-use-of-webyast-for-opensuse-11-3... I wasn't referring it is not developed anymore, I just doubt architectural changes will bring any modifications to the UI (and
2011/2/15 Martin Schlander <martin.schlander@gmail.com>: therefore translations) -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2011-02-15 at 14:24 +0300, Александр Мелентьев wrote:
I wasn't referring it is not developed anymore, I just doubt architectural changes will bring any modifications to the UI (and therefore translations)
Not a single letter changed in one year? Even so, pot files should be rebuilt, timestamps changed. If I see recent dates, my alarms do not fire even if I see nothing to translate. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1aeg8ACgkQtTMYHG2NR9XXKQCePtJIoBkvLuO7C1/f/1gEAzMW WLQAn3/fkoJU48lNqpxHFCM9bD8FT3SL =Yoqu -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2011-02-14 at 22:13 +0100, Carlos E. R. wrote:
They are dated May 2010. I can not translate them till this is done.
Bug 671870 - Webyast POTs are obsolete.
Ping! It looks the YaST devs are not interested in getting their work translated. If they aren't, good, its better for me, no job to do. :-/ - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1uM/YACgkQtTMYHG2NR9W8LQCeM4ByW+ZNf1qlCjwOdu1PxVbG XMgAn2aILs3nDt8qT+a+H6LZ0BEC/IY5 =mZYc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
hi there, well, i think we have to be more creative in that field. i guess we have to branch all webyast-*-ui package from YaST:Web project, generate the POT files, merge with existing translations, put it on our svn, collect back open add back our translations as a patch and hopefully the project owner will accept it. imho that's what we have to do with all opensuse releated projects. we dont have to wait for the developers but we have to collect everything we need for translations. build service is ready for that and developers will realize us. @Karl, what do you think? best k On Wed, Mar 2, 2011 at 1:11 PM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2011-02-14 at 22:13 +0100, Carlos E. R. wrote:
They are dated May 2010. I can not translate them till this is done.
Bug 671870 - Webyast POTs are obsolete.
Ping!
It looks the YaST devs are not interested in getting their work translated. If they aren't, good, its better for me, no job to do.
:-/
- -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAk1uM/YACgkQtTMYHG2NR9W8LQCeM4ByW+ZNf1qlCjwOdu1PxVbG XMgAn2aILs3nDt8qT+a+H6LZ0BEC/IY5 =mZYc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2011-03-02 at 13:52 +0100, Kálmán Kéménczy wrote:
well, i think we have to be more creative in that field. i guess we have to branch all webyast-*-ui package from YaST:Web project, generate the POT files, merge with existing translations, put it on our svn, collect back open add back our translations as a patch and hopefully the project owner will accept it.
imho that's what we have to do with all opensuse releated projects. we dont have to wait for the developers but we have to collect everything we need for translations. build service is ready for that and developers will realize us.
No, I will not do that. I translate, I will not go fishing for files. If the devs do not give us the files to translate, I conider they are not interested. Fine. They have to take responsibility. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEUEARECAAYFAk1uPvQACgkQtTMYHG2NR9Wl3ACYzVjQQNHFd2x1ASz96MZ0gY9v zgCghW0WDyQHQ3k3FA17BgOf8cgE9F4= =juAT -----END PGP SIGNATURE-----
No, I will not do that. I translate, I will not go fishing for files. If the devs do not give us the files to translate, I conider they are not interested. Fine.
They have to take responsibility.
I do understand your point of view. If I find the way I would fish for everyone and you can focus only on the translations. how do you like this scenario? k -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
If I find the way I would fish for everyone and you can focus only on the translations. how do you like this scenario? Kálmán, while your suggestion is way too generous, it is not what we need right now, IMHO. This thread clearly demonstrates that more info from developers is needed, since some translation-related decisions were taken in a closed-group manner. If translations are done by Novell team (which is like SLE situation and everybody is fine with it) then why would we bother to translate files in our repo and waste human resouces and stats page space on it? If translations are kept on gitorious then why would we bother to keep those files in our SVN-repo and waste CPU cycles and HDD space on it? We definitely have a gap here with developers-translators communication, so some things need a
2011/3/2 Kálmán Kéménczy <kkemenczy@opensuse.org>: little clarifying... Maybe you could contact webyast devs as a translation coordinator and ask for some feedback on this? -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Kálmán, while your suggestion is way too generous, it is not what we need right now, IMHO. This thread clearly demonstrates that more info from developers is needed, since some translation-related decisions were taken in a closed-group manner. If translations are done by Novell team (which is like SLE situation and everybody is fine with it) then why would we bother to translate files in our repo and waste human resouces and stats page space on it?
well, if the translations made by novell we have to pick them up. i don't like the parallel works either.
If translations are kept on gitorious then why would we bother to keep those files in our SVN-repo and waste CPU cycles and HDD space on it?
imho 1) gitorious is for developers, frequently changes repository and imho not worth to follow. 2) the stable or testable code should appears in build service and this is the nice point where we can jump into for release 3) we need one common place for translations and we just moved here, let's try to live here please clarify it someone from opensuse (eg. Karl :)
We definitely have a gap here with developers-translators communication, so some things need a little clarifying...
agree
Maybe you could contact webyast devs as a translation coordinator and ask for some feedback on this?
i am not a translation coordinator, but i will contact to the novell's localization manager about it, but they are only responsible for sle products and who knows which version appears in the 11.4, but i think this is a good start for the investigation. we are all know in our deep of our heart this is too late for 11.4, but we have to figure out how the things should work. Maybe Andreas or Coolo could help on that as well (added them to CC) best kalman -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2011-03-02 at 17:39 +0100, Kálmán Kéménczy wrote:
Kálmán, while your suggestion is way too generous, it is not what we need right now, IMHO. This thread clearly demonstrates that more info from developers is needed, since some translation-related decisions were taken in a closed-group manner. If translations are done by Novell team (which is like SLE situation and everybody is fine with it) then why would we bother to translate files in our repo and waste human resouces and stats page space on it?
well, if the translations made by novell we have to pick them up. i don't like the parallel works either.
No, if Novell translates the same files, then I will not touch the translation. That's the Spanish team policy. We do not work for SLES, nor do we want they intervening in our translations. Sigh... :-( - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1uum8ACgkQtTMYHG2NR9UyLgCeP36xKAvw6R8MbZKzxfw3o03v GP0An0IZgGskIyx4Rp+2RIBoOIZYDq7U =x9q8 -----END PGP SIGNATURE-----
well, if the translations made by novell we have to pick them up. i don't like the parallel works either.
No, if Novell translates the same files, then I will not touch the translation. That's the Spanish team policy. We do not work for SLES, nor do we want they intervening in our translations.
Sigh... :-(
maybe i do not understand well if novell translate e.g. webyast-modul1.es.po (based on version 1.0) for sles, your team will not translate the wabyast-modul1.es.po (based on version 1.2) for openSUSE? or you will not use the existing translations come from sles and you will retranslate it? i am confused a bit please let me know. thanks k -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LNX.2.00.1103030325250.9651@Telcontar.valinor> On Wednesday, 2011-03-02 at 23:25 +0100, Kálmán Kéménczy wrote:
maybe i do not understand well
if novell translate e.g. webyast-modul1.es.po (based on version 1.0) for sles, your team will not translate the wabyast-modul1.es.po (based on version 1.2) for openSUSE?
It is a duplication of work, but we do our own translation.
or you will not use the existing translations come from sles and you will retranslate it?
Yes, we will not use none of the sles translation. We decided on that time ago. The particular translator may look at, if he likes, the sles translation, then do his part as he likes. Which means that, if some new strings appear already translated from outside, ie, taken from the sles translation, we get "distressed". We have our own vocabulary and take pride in our work. Some of the words we used we have agreed on using them after weeks of discussion, so we get "mad" when we see the wrong word and we did not type it. Also, we do not like to find out that we are translating a bit of code that is not going to be used in openSUSE, but only for SLES - as they are paid and we are not. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1u/r4ACgkQtTMYHG2NR9X0IQCgjjtfEfh9Zu22h9kZAGSohgZx nFoAn026aMWQw/6fHE0lNpb6nbnk/op3 =epZ8 -----END PGP SIGNATURE-----
thanks to share this. best k On Thu, Mar 3, 2011 at 3:36 AM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID: <alpine.LNX.2.00.1103030325250.9651@Telcontar.valinor>
On Wednesday, 2011-03-02 at 23:25 +0100, Kálmán Kéménczy wrote:
maybe i do not understand well
if novell translate e.g. webyast-modul1.es.po (based on version 1.0) for sles, your team will not translate the wabyast-modul1.es.po (based on version 1.2) for openSUSE?
It is a duplication of work, but we do our own translation.
or you will not use the existing translations come from sles and you will retranslate it?
Yes, we will not use none of the sles translation. We decided on that time ago. The particular translator may look at, if he likes, the sles translation, then do his part as he likes.
Which means that, if some new strings appear already translated from outside, ie, taken from the sles translation, we get "distressed".
We have our own vocabulary and take pride in our work. Some of the words we used we have agreed on using them after weeks of discussion, so we get "mad" when we see the wrong word and we did not type it.
Also, we do not like to find out that we are translating a bit of code that is not going to be used in openSUSE, but only for SLES - as they are paid and we are not.
- -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAk1u/r4ACgkQtTMYHG2NR9X0IQCgjjtfEfh9Zu22h9kZAGSohgZx nFoAn026aMWQw/6fHE0lNpb6nbnk/op3 =epZ8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2011-03-03 at 16:15 +0100, Kálmán Kéménczy wrote:
thanks to share this.
Welcome :-) It is on record, anyway. In the Spanish mail list, where we decide things, and here, when we ask or are asked. - -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEARECAAYFAk1wC0IACgkQtTMYHG2NR9UznwCfW354dNKs+IdWMLo0fjydKQaD e+0Amwadj6nbvpYKGlR2H6v4ut+Q73/b =VZ6/ -----END PGP SIGNATURE-----
Hi all! Seems webyast is hosted on gitorious: gitorious.org/opensuse/yast-web-client/trees/master/ And if we search, the .pos are there, but if we compare the POT-Creation-Date of the files there and in our svn they are different: in our svn: http://svn.berlios.de/wsvn/opensuse-i18n/trunk/webyast/pt_BR/po/webyast-base... POT-Creation-Date: 2010-05-27 11:01+0200 in 'upstream' gitorious: http://gitorious.org/opensuse/yast-web-client/blobs/master/webclient/po/pt_B... POT-Creation-Date: 2010-09-01 10:38+0200 Also, seems that "Novell Language <language@novell.com>" is translating some languages, for the others they use our translations. Regards, Luiz 2011/3/2 Kálmán Kéménczy <kkemenczy@opensuse.org>:
hi there,
well, i think we have to be more creative in that field. i guess we have to branch all webyast-*-ui package from YaST:Web project, generate the POT files, merge with existing translations, put it on our svn, collect back open add back our translations as a patch and hopefully the project owner will accept it.
imho that's what we have to do with all opensuse releated projects. we dont have to wait for the developers but we have to collect everything we need for translations. build service is ready for that and developers will realize us.
@Karl, what do you think?
best k
On Wed, Mar 2, 2011 at 1:11 PM, Carlos E. R. <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2011-02-14 at 22:13 +0100, Carlos E. R. wrote:
They are dated May 2010. I can not translate them till this is done.
Bug 671870 - Webyast POTs are obsolete.
Ping!
It looks the YaST devs are not interested in getting their work translated. If they aren't, good, its better for me, no job to do.
:-/
- -- Cheers, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAk1uM/YACgkQtTMYHG2NR9W8LQCeM4ByW+ZNf1qlCjwOdu1PxVbG XMgAn2aILs3nDt8qT+a+H6LZ0BEC/IY5 =mZYc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (5)
-
Carlos E. R. -
Kálmán Kéménczy -
Luiz Fernando Ranghetti -
Martin Schlander -
Александр Мелентьев