[opensuse-translation] Info on packages/pot files
Hi all, I tried to run the prepare_split.sh script that generates packages/pot files and then applied them to fully translated po files. As a result, excluding factory.pot, remaining po files count 605 fuzzy and 413 untranslated strings. Now, what is the deadline for translation submission of these po files? Is it still the end of October? Moreover, how can we (as translators) be warned about changes in packages files? Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Hi all, I tried to run the prepare_split.sh script that generates packages/pot files and then applied them to fully translated po files.
As a result, excluding factory.pot, remaining po files count 605 fuzzy and 413 untranslated strings. That's a lot.
Now, what is the deadline for translation submission of these po files? Is it still the end of October? We can submit them any time, bascially we can checkin a new round
Am Montag, 10. Oktober 2011, 12:58:46 schrieb Andrea Turrini: the minute before we do the GM. But if you want to have it tested, you better commit before RC2 deadline - october 28th. And remember: I said _before_ that :)
Moreover, how can we (as translators) be warned about changes in packages files?
They change all the time - or what do you mean? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 10/10/2011 03:32 PM, Stephan Kulow wrote:
We can submit them any time, bascially we can checkin a new round the minute before we do the GM. But if you want to have it tested, you better commit before RC2 deadline - october 28th. And remember: I said _before_ that :)
OK.
Moreover, how can we (as translators) be warned about changes in packages files?
They change all the time - or what do you mean?
I mean packages/pot files depend on current content of factory/live/repo-oss, don't them? So I think their generation can be triggered by some event (such as the generation of the building for a specific release like MS5, MS6, beta, rc1) and propagated to .po files. So translators know that there might be changes in packages/po files and they can plan the translation as they want. Otherwise it happens as now: a lot of unexpected changes discovered only by chance. Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On maandag 10 oktober 2011 20:55:35 Andrea Turrini wrote:
I mean packages/pot files depend on current content of factory/live/repo-oss, don't them? So I think their generation can be triggered by some event (such as the generation of the building for a specific release like MS5, MS6, beta, rc1) and propagated to .po files. So translators know that there might be changes in packages/po files and they can plan the translation as they want.
I run every day a script with a number of svn up commands, also for packages/50-pot/ which give me some output when a file has changed. So I know that something did change. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On 10/10/2011 10:20 PM, Freek de Kruijf wrote:
I run every day a script with a number of svn up commands, also for packages/50-pot/ which give me some output when a file has changed. So I know that something did change.
Me too, but you may have noticed that packages/50-pot/ has not changed in these days (actually, last change was at the end of August). A question I forgot in the previous mail: how can I test packages translation? I have a testing installation of oS 12.1 with Italian packages installed (and updated this morning) but in zypper/YaST package summaries and descriptions are still in English. Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
On maandag 10 oktober 2011 22:31:30 Andrea Turrini wrote:
On 10/10/2011 10:20 PM, Freek de Kruijf wrote:
I run every day a script with a number of svn up commands, also for packages/50-pot/ which give me some output when a file has changed. So I know that something did change.
Me too, but you may have noticed that packages/50-pot/ has not changed in these days (actually, last change was at the end of August).
A question I forgot in the previous mail: how can I test packages translation? I have a testing installation of oS 12.1 with Italian packages installed (and updated this morning) but in zypper/YaST package summaries and descriptions are still in English.
So we need to know in which .mo file(s) these translation end up. After that we can find in which OBS project these files are generated. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Montag, 10. Oktober 2011 schrieb Andrea Turrini:
On 10/10/2011 10:20 PM, Freek de Kruijf wrote:
I run every day a script with a number of svn up commands, also for packages/50-pot/ which give me some output when a file has changed. So I know that something did change.
Me too, but you may have noticed that packages/50-pot/ has not changed in these days (actually, last change was at the end of August). You can have a cron job merging too. As I said: the repo changes every day and updating it a day before a milestone makes little sense.
A question I forgot in the previous mail: how can I test packages translation? I have a testing installation of oS 12.1 with Italian packages installed (and updated this morning) but in zypper/YaST package summaries and descriptions are still in English.
Your translations have to be put into package package-translations (also last update late august), which then updates http://download.opensuse.org/factory/repo/oss/suse/setup/descr/packages.it.g... and for me it works: LC_ALL=it zypper search bash gives "La Shell GNU Bourne-Again", which at least isn't english :) So to me it sounds like we need two cron jobs (either volunterrs or real scripts :): - merging package translations - submitting package-translations package to factory. The later I did now, but I'll forget again soon after ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Dienstag, 11. Oktober 2011 schrieb Stephan Kulow:
So to me it sounds like we need two cron jobs (either volunterrs or real scripts :): - merging package translations - submitting package-translations package to factory.
OK, I created a submitting cron job now. Let's see how well it works. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2011/10/11 Stephan Kulow
Am Dienstag, 11. Oktober 2011 schrieb Stephan Kulow:
So to me it sounds like we need two cron jobs (either volunterrs or real scripts :): - merging package translations - submitting package-translations package to factory.
OK, I created a submitting cron job now. Let's see how well it works.
Just to know, when does cron launch the script? In the meanwhile, fuzzy and untranslated strings are growing (+5 and +2 from my initial mail, respectively). Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Donnerstag, 13. Oktober 2011 schrieb Andrea Turrini:
2011/10/11 Stephan Kulow
: Am Dienstag, 11. Oktober 2011 schrieb Stephan Kulow:
So to me it sounds like we need two cron jobs (either volunterrs or real scripts :): - merging package translations - submitting package-translations package to factory.
OK, I created a submitting cron job now. Let's see how well it works.
Just to know, when does cron launch the script? In the afternoon. It submitted russian translations today.
Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2011/10/11 Stephan Kulow
Your translations have to be put into package package-translations (also last update late august), which then updates http://download.opensuse.org/factory/repo/oss/suse/setup/descr/packages.it.g...
and for me it works:
LC_ALL=it zypper search bash gives "La Shell GNU Bourne-Again", which at least isn't english :)
I am not able to obtain this. I'm currently running oS12.1 in VirtualBox (just updated), the package-translation package is installed. I tried to switch system language to Italian, (rebooted,) and descriptions are still in English. I have also set root LANG variable to it_IT.UTF-8, zypper is in Italian but description is still in English. If I use your command, everything is in English (Loading repository data...). I tried also to check whether the /usr/bin/translate-packages.pl script is invoked wrapping it in a bash script that simply echoes to a file but it seems that it is not invoked. Probably there is something broken in my testing installation. Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Dienstag, 11. Oktober 2011 schrieb Andrea Turrini:
2011/10/11 Stephan Kulow
: Your translations have to be put into package package-translations (also last update late august), which then updates http://download.opensuse.org/factory/repo/oss/suse/setup/descr/packages.i t.gz
and for me it works:
LC_ALL=it zypper search bash gives "La Shell GNU Bourne-Again", which at least isn't english :)
I am not able to obtain this. I'm currently running oS12.1 in VirtualBox (just updated), the package-translation package is installed. I tried to switch system language to Italian, (rebooted,) The package is not for users to install.
and descriptions are still in English. I have also set root LANG variable to it_IT.UTF-8, zypper is in Italian but description is still in English. If I use your command, everything is in English (Loading repository data...). LANG might be too little as LC_MESSAGES inherits LC_ALL
I tried also to check whether the /usr/bin/translate-packages.pl script is invoked wrapping it in a bash script that simply echoes to a file but it seems that it is not invoked.
Probably there is something broken in my testing installation.
As I said: package-translations is for creating packages.it Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2011/10/11 Stephan Kulow
The package is not for users to install.
OK. Removed.
and descriptions are still in English. I have also set root LANG variable to it_IT.UTF-8, zypper is in Italian but description is still in English. If I use your command, everything is in English (Loading repository data...). LANG might be too little as LC_MESSAGES inherits LC_ALL
In any case, I need to use at least LC_ALL=it_IT in order to keep Italian translation of zypper since LC_ALL=it is not enough in my system. Now I checked the cache of the repositories and packages.it.gz is not present there. Only .gz, .en.gz and .DU.gz. Probably this is the cause: I forced the generation of repository caches (zypper ref -f) and now I have Italian translations for descriptions and summaries. So I switched again the system to en_US, forced the regeneration of the cache and packages.it.gz disappeared. To obtain it again, I needed to do at least a "LANG=it_IT zypper ref -f" and then using "LANG=it_IT zypper se bash" I obtain Italian translation. OK, my testing system is not (so) broken and I have understood a lot of things about packages translations. Now there is a strange situation: since descriptions and summaries are translated, an user might want to search a package using a translated search string: (s)he will not obtain any result; (s)he must search in English to obtain something. I think this and the way to obtain translated descriptions after installation should be point out to users in some way but I have no idea at the moment. Regards, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Dienstag, 11. Oktober 2011 schrieb Andrea Turrini:
OK, my testing system is not (so) broken and I have understood a lot of things about packages translations.
Now there is a strange situation: since descriptions and summaries are translated, an user might want to search a package using a translated search string: (s)he will not obtain any result; (s)he must search in English to obtain something.
Yeah, that root's locale is english can be a problem
I think this and the way to obtain translated descriptions after installation should be point out to users in some way but I have no idea at the moment.
BTW; Yast behaves differently I believe. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2011/10/11 Stephan Kulow
Am Dienstag, 11. Oktober 2011 schrieb Andrea Turrini:
OK, my testing system is not (so) broken and I have understood a lot of things about packages translations.
Now there is a strange situation: since descriptions and summaries are translated, an user might want to search a package using a translated search string: (s)he will not obtain any result; (s)he must search in English to obtain something.
Yeah, that root's locale is english can be a problem
I think this and the way to obtain translated descriptions after installation should be point out to users in some way but I have no idea at the moment.
BTW; Yast behaves differently I believe.
I do not think so: I tested search using YaST as root with LANG=it_IT and as ordinary user that has Italian as main language and in both cases I obtained the above situation, even if YaST's interface is in Italian. The same happens with zypper run as root or ordinary user. Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Dienstag, 11. Oktober 2011 schrieb Andrea Turrini:
2011/10/11 Stephan Kulow
: The package is not for users to install.
OK. Removed.
and descriptions are still in English. I have also set root LANG variable to it_IT.UTF-8, zypper is in Italian but description is still in English. If I use your command, everything is in English (Loading repository data...).
LANG might be too little as LC_MESSAGES inherits LC_ALL
In any case, I need to use at least LC_ALL=it_IT in order to keep Italian translation of zypper since LC_ALL=it is not enough in my system.
I asked the zypper maintainer to check how much effort it is to make zypper fetch all system locales. It knows about it from /var/lib/zypp/RequestedLocales Let's see what he'll find out. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
2011/10/18 Stephan Kulow
In any case, I need to use at least LC_ALL=it_IT in order to keep Italian translation of zypper since LC_ALL=it is not enough in my system.
I asked the zypper maintainer to check how much effort it is to make zypper fetch all system locales. It knows about it from /var/lib/zypp/RequestedLocales
In my system, the content of /var/lib/zypp/RequestedLocales is: ---8<--- # zypp::RequestedLocales generated Mon 14 Mar 2011 02:52:44 PM CET # it en_US # ---8<--- but as I said, zypper is in English when using LC_ALL=it, in Italian when using LC_ALL=it_IT. The strange thing is that /usr/share/locale/it_IT/LC_MESSAGES/ is empty while /usr/share/locale/it/LC_MESSAGES/ contains over 850 files, including zypper.mo with Italian translation (from package zypper). There is another zypper.mo, from package translation-update-it, in /usr/share/locale-langpack/it/LC_MESSAGES/ that is the file actually used by zypper. So it seems that zypper uses zypper.mo in it/LC_MESSAGES when LC_ALL=it_IT is used, but fails to find zypper.mo when LC_ALL=it is used. A similar thing happens in the oS 12.1 testing installation. Bug report? Best, Andrea -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
Am Dienstag, 18. Oktober 2011 schrieb Andrea Turrini:
2011/10/18 Stephan Kulow
: In any case, I need to use at least LC_ALL=it_IT in order to keep Italian translation of zypper since LC_ALL=it is not enough in my system.
I asked the zypper maintainer to check how much effort it is to make zypper fetch all system locales. It knows about it from /var/lib/zypp/RequestedLocales
In my system, the content of /var/lib/zypp/RequestedLocales is:
---8<--- # zypp::RequestedLocales generated Mon 14 Mar 2011 02:52:44 PM CET # it en_US # ---8<--- but as I said, zypper is in English when using LC_ALL=it, in Italian when using LC_ALL=it_IT. The strange thing is that /usr/share/locale/it_IT/LC_MESSAGES/ is empty while /usr/share/locale/it/LC_MESSAGES/ contains over 850 files, including zypper.mo with Italian translation (from package zypper). There is another zypper.mo, from package translation-update-it, in /usr/share/locale-langpack/it/LC_MESSAGES/ that is the file actually used by zypper. So it seems that zypper uses zypper.mo in it/LC_MESSAGES when LC_ALL=it_IT is used, but fails to find zypper.mo when LC_ALL=it is used.
A similar thing happens in the oS 12.1 testing installation.
Bug report? Hmm that would be a problem in glibc, but I'm not expert in all these LC_*
Greetings, Stephan -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org
participants (3)
-
Andrea Turrini
-
Freek de Kruijf
-
Stephan Kulow