Re: Can't integrate translation in module sawfish i gnome git
2010/1/17 Christopher Roy Bratusek : > Am Sat, 16 Jan 2010 22:25:59 +0100 > schrieb Kenneth Nielsen : > >> >> >> >> Please fix this module so that we can use standard tools and >> >> procedures. >> > >> > This has been fixed in December. You can safely trust damned-lies >> > now. It relies on the committed po/sawfish.pot file. >> >> Yes, but I was also refering to the other issues, I still can't use >> intltool-update. > > If you would use intltool-update then the majority of strings would get > marked as deprecated, though they aren't, the issue is known, but not > all parts are fixed yet. Intltool can't catch up the strings from > Sawfish which aren't part of an alist or a list. so 80% of the strings > will end up #~'ed. > > Chris Yes I understand that. My second and third e-mail was just me desperately begging you guys to fix it, as soon as possible, as we really don't _need_ any extra modules with non-standard committing methods. Kind regards Kenneth Nielsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Claude Paroz , Sun, 17 Jan 2010 22:32:47 +0100: > Le dimanche 17 janvier 2010 à 17:31 +0100, Petr Kovar a écrit : > > Christopher Roy Bratusek , Sun, 17 Jan 2010 07:46:49 > > +0100: > > > > > Am Sat, 16 Jan 2010 22:25:59 +0100 > > > schrieb Kenneth Nielsen : > > > > > > > > Yes, but I was also refering to the other issues, I still can't use > > > > intltool-update. > > > > > > If you would use intltool-update then the majority of strings would > > > get marked as deprecated, though they aren't, the issue is known, but > > > not all parts are fixed yet. Intltool can't catch up the strings from > > > Sawfish which aren't part of an alist or a list. so 80% of the strings > > > will end up #~'ed. > > > > I think that a short notice on this intltool issue should be added to > > the appropriate Damned Lies page then, so committers are aware of it. > > Good suggestion. I added an automated notice whenever the pot generation > method is not standard (in damned-lies structure, when the > domain.pot_method field is not empty). > In addition to sawfish, several other modules are concerned (damned-lies > itself, GIMP help, libgweather po-locations, ...). Great! You just took it to perfection. :-) Thank you, Claude. Cheers, Petr Kovar ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Le dimanche 17 janvier 2010 à 17:31 +0100, Petr Kovar a écrit : > Christopher Roy Bratusek , Sun, 17 Jan 2010 07:46:49 > +0100: > > > Am Sat, 16 Jan 2010 22:25:59 +0100 > > schrieb Kenneth Nielsen : > > > > > > Yes, but I was also refering to the other issues, I still can't use > > > intltool-update. > > > > If you would use intltool-update then the majority of strings would get > > marked as deprecated, though they aren't, the issue is known, but not > > all parts are fixed yet. Intltool can't catch up the strings from > > Sawfish which aren't part of an alist or a list. so 80% of the strings > > will end up #~'ed. > > I think that a short notice on this intltool issue should be added to the > appropriate Damned Lies page then, so committers are aware of it. Good suggestion. I added an automated notice whenever the pot generation method is not standard (in damned-lies structure, when the domain.pot_method field is not empty). In addition to sawfish, several other modules are concerned (damned-lies itself, GIMP help, libgweather po-locations, ...). Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Christopher Roy Bratusek , Sun, 17 Jan 2010 07:46:49 +0100: > Am Sat, 16 Jan 2010 22:25:59 +0100 > schrieb Kenneth Nielsen : > > > >> > > >> Please fix this module so that we can use standard tools and > > >> procedures. > > > > > > This has been fixed in December. You can safely trust damned-lies > > > now. It relies on the committed po/sawfish.pot file. > > > > Yes, but I was also refering to the other issues, I still can't use > > intltool-update. > > If you would use intltool-update then the majority of strings would get > marked as deprecated, though they aren't, the issue is known, but not > all parts are fixed yet. Intltool can't catch up the strings from > Sawfish which aren't part of an alist or a list. so 80% of the strings > will end up #~'ed. I think that a short notice on this intltool issue should be added to the appropriate Damned Lies page then, so committers are aware of it. Best, Petr Kovar ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Am Sat, 16 Jan 2010 22:25:59 +0100 schrieb Kenneth Nielsen : > >> > >> Please fix this module so that we can use standard tools and > >> procedures. > > > > This has been fixed in December. You can safely trust damned-lies > > now. It relies on the committed po/sawfish.pot file. > > Yes, but I was also refering to the other issues, I still can't use > intltool-update. If you would use intltool-update then the majority of strings would get marked as deprecated, though they aren't, the issue is known, but not all parts are fixed yet. Intltool can't catch up the strings from Sawfish which aren't part of an alist or a list. so 80% of the strings will end up #~'ed. Chris > Regards Kenneth > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
>> >> Please fix this module so that we can use standard tools and procedures. > > This has been fixed in December. You can safely trust damned-lies now. > It relies on the committed po/sawfish.pot file. Yes, but I was also refering to the other issues, I still can't use intltool-update. Regards Kenneth ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Le mercredi 13 janvier 2010 à 20:51 +0100, Kenneth Nielsen a écrit : > 2009/12/18 Christopher Roy Bratusek : > > Am Fri, 18 Dec 2009 00:24:24 +0100 > > schrieb Andre Klapper : > > > >> Am Donnerstag, den 17.12.2009, 23:58 +0100 schrieb Kenneth Nielsen: > >> > There is apparently somthing wrong in the sawfish repository on > >> > gnome > >> > >> Fixed. > >> > >> andre > >> > > > > Actually you're fix was not correct, as the file does still exist, but > > it's now called lisp/sawfish/wm/commands/launcher.jl. I really fixed it > > right now. Also I've added some other files to the list (and check for > > more). > > > > Also using intltool for translating sawfish is not recommended, as > > intltool can only recognize strings surounded by (_ ) but most of > > sawfishs strings aren't. Now if you use intltool-update will mark all > > *valid* strings as #~. So for the time beeing, you should make sure > > that the old strings are not disabled/untranslated when using intltool. > > > > Current sane way is to do the following: > > > > cd po > > > > # generates a *complete* .pot > > ./make-pot > > > > # updates all po files against the new pot file > > for PO in $(ls *.po); do > >./update.sh $(basename $PO .po) > > done > > > > Editing the po file NOW is safe. > > > > I know that this is not optimal, sorry. > > That's a bit of an understatement ;) First, people pull the file they > translate directly from damned lies the same way they do for all other > modules in GNOME. I have no way of imposing these restrictions on > people. Second, I am the person the integrates all the GNOME > translations from my entire team, suffice it to say that it is > somewhat inconvenient when a module requires special attention when > pulling the file or integrating. Third, I now already have a > translation, that is probably based on an old version and I still need > a way to integrate it. > > I can't run the makepot thingy, because I don't have all the > dependencies. Could you e-mail me a fresh pot-file, then I can > msgmerge against that, and then integrate the result? > > Please fix this module so that we can use standard tools and procedures. This has been fixed in December. You can safely trust damned-lies now. It relies on the committed po/sawfish.pot file. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
2009/12/18 Christopher Roy Bratusek : > Am Fri, 18 Dec 2009 00:24:24 +0100 > schrieb Andre Klapper : > >> Am Donnerstag, den 17.12.2009, 23:58 +0100 schrieb Kenneth Nielsen: >> > There is apparently somthing wrong in the sawfish repository on >> > gnome >> >> Fixed. >> >> andre >> > > Actually you're fix was not correct, as the file does still exist, but > it's now called lisp/sawfish/wm/commands/launcher.jl. I really fixed it > right now. Also I've added some other files to the list (and check for > more). > > Also using intltool for translating sawfish is not recommended, as > intltool can only recognize strings surounded by (_ ) but most of > sawfishs strings aren't. Now if you use intltool-update will mark all > *valid* strings as #~. So for the time beeing, you should make sure > that the old strings are not disabled/untranslated when using intltool. > > Current sane way is to do the following: > > cd po > > # generates a *complete* .pot > ./make-pot > > # updates all po files against the new pot file > for PO in $(ls *.po); do > ./update.sh $(basename $PO .po) > done > > Editing the po file NOW is safe. > > I know that this is not optimal, sorry. That's a bit of an understatement ;) First, people pull the file they translate directly from damned lies the same way they do for all other modules in GNOME. I have no way of imposing these restrictions on people. Second, I am the person the integrates all the GNOME translations from my entire team, suffice it to say that it is somewhat inconvenient when a module requires special attention when pulling the file or integrating. Third, I now already have a translation, that is probably based on an old version and I still need a way to integrate it. I can't run the makepot thingy, because I don't have all the dependencies. Could you e-mail me a fresh pot-file, then I can msgmerge against that, and then integrate the result? Please fix this module so that we can use standard tools and procedures. Regards Kenneth > > BTW: All (known) UTF-8/CYK issues in librep/sawfish are gone :) > > Chris > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Le samedi 19 décembre 2009 à 11:21 +0100, Christopher Roy Bratusek a écrit : > Am Sat, 19 Dec 2009 11:06:24 +0100 > schrieb Claude Paroz : > > > Le samedi 19 décembre 2009 à 11:02 +0100, Christopher Roy Bratusek a > > écrit : > > > Am Sat, 19 Dec 2009 09:56:57 +0100 > > > schrieb Claude Paroz : > > > > > > > Le vendredi 18 décembre 2009 à 23:10 +0100, Christopher Roy > > > > Bratusek a écrit : > > > > > Am Fri, 18 Dec 2009 22:51:11 +0100 > > > > > schrieb Claude Paroz : > > > > > > > (...) > > > > > > > > > > > > Hi Chris, > > > > > > > > > > > > Damned-Lies supports special way to generate pot files, under > > > > > > two conditions: > > > > > > - the custom script should apply in a clean tree (that is > > > > > > without requiring an autogen/configure) > > > > > > - the custom script should be written in a 'standard' (no > > > > > > troll intent!) language (e.g. bash, perl, python). > > > > > > > > > > > > Another way would be to commit the pot file in Git and > > > > > > Damned-Lies could use it to generate stats. I know it's > > > > > > suboptimal to commit generated files, but it would be a > > > > > > workaround. > > > > > > > > > > > > Claude > > > > > > > > > > > > > > > > Hi Claude, > > > > > > > > > > both scripts are shell scripts, which should work with any > > > > > modern sh. I just commited a little change to make-pot to make > > > > > it work in a clean tree (it checks wether $(srcdir)/DOC exists > > > > > or not, and creates it, if not -- the DOC file is generated by > > > > > repdoc, which makes the difference between a intltool or > > > > > make-pot generated pot-file: it detects all strings). update.sh > > > > > works, if there's a pot file in the tree. > > > > > > > > ./make-pot: 25: repdoc: not found > > > > > > > > repdoc/rep seem not to be commonly installed programs (librep9 > > > > package). Is it possible for you to find equivalent commands in > > > > standard tools? > > > > > > > > Claude > > > > > > > > > > Haven't thought about that. Well, I guess there's no other suitable > > > app. > > > > What about committing the pot file in the repository? > > > > Claude > > OK. I just commited the pot file. As Sawfish 1.6.0 is beeing released > on Tuesday, there shouldn't be any string changes from now on. Damned-Lies is now using the pot file from the repository to generate stats for sawfish: http://l10n.gnome.org/module/sawfish/ Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Am Sat, 19 Dec 2009 11:06:24 +0100 schrieb Claude Paroz : > Le samedi 19 décembre 2009 à 11:02 +0100, Christopher Roy Bratusek a > écrit : > > Am Sat, 19 Dec 2009 09:56:57 +0100 > > schrieb Claude Paroz : > > > > > Le vendredi 18 décembre 2009 à 23:10 +0100, Christopher Roy > > > Bratusek a écrit : > > > > Am Fri, 18 Dec 2009 22:51:11 +0100 > > > > schrieb Claude Paroz : > > > > > (...) > > > > > > > > > > Hi Chris, > > > > > > > > > > Damned-Lies supports special way to generate pot files, under > > > > > two conditions: > > > > > - the custom script should apply in a clean tree (that is > > > > > without requiring an autogen/configure) > > > > > - the custom script should be written in a 'standard' (no > > > > > troll intent!) language (e.g. bash, perl, python). > > > > > > > > > > Another way would be to commit the pot file in Git and > > > > > Damned-Lies could use it to generate stats. I know it's > > > > > suboptimal to commit generated files, but it would be a > > > > > workaround. > > > > > > > > > > Claude > > > > > > > > > > > > > Hi Claude, > > > > > > > > both scripts are shell scripts, which should work with any > > > > modern sh. I just commited a little change to make-pot to make > > > > it work in a clean tree (it checks wether $(srcdir)/DOC exists > > > > or not, and creates it, if not -- the DOC file is generated by > > > > repdoc, which makes the difference between a intltool or > > > > make-pot generated pot-file: it detects all strings). update.sh > > > > works, if there's a pot file in the tree. > > > > > > ./make-pot: 25: repdoc: not found > > > > > > repdoc/rep seem not to be commonly installed programs (librep9 > > > package). Is it possible for you to find equivalent commands in > > > standard tools? > > > > > > Claude > > > > > > > Haven't thought about that. Well, I guess there's no other suitable > > app. > > What about committing the pot file in the repository? > > Claude OK. I just commited the pot file. As Sawfish 1.6.0 is beeing released on Tuesday, there shouldn't be any string changes from now on. Chris ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Le vendredi 18 décembre 2009 à 23:10 +0100, Christopher Roy Bratusek a écrit : > Am Fri, 18 Dec 2009 22:51:11 +0100 > schrieb Claude Paroz : > > > Le vendredi 18 décembre 2009 à 18:04 +0100, Christopher Roy Bratusek a > > écrit : > > (...) > > > Also using intltool for translating sawfish is not recommended, as > > > intltool can only recognize strings surounded by (_ ) but most of > > > sawfishs strings aren't. Now if you use intltool-update will mark > > > all *valid* strings as #~. So for the time beeing, you should make > > > sure that the old strings are not disabled/untranslated when using > > > intltool. > > > > > > Current sane way is to do the following: > > > > > > cd po > > > > > > # generates a *complete* .pot > > > ./make-pot > > > > > > # updates all po files against the new pot file > > > for PO in $(ls *.po); do > > > ./update.sh $(basename $PO .po) > > > done > > > > > > Editing the po file NOW is safe. > > > > > > I know that this is not optimal, sorry. > > > > Hi Chris, > > > > Damned-Lies supports special way to generate pot files, under two > > conditions: > > - the custom script should apply in a clean tree (that is without > > requiring an autogen/configure) > > - the custom script should be written in a 'standard' (no troll > > intent!) language (e.g. bash, perl, python). > > > > Another way would be to commit the pot file in Git and Damned-Lies > > could use it to generate stats. I know it's suboptimal to commit > > generated files, but it would be a workaround. > > > > Claude > > > > Hi Claude, > > both scripts are shell scripts, which should work with any modern sh. I > just commited a little change to make-pot to make it work in a clean > tree (it checks wether $(srcdir)/DOC exists or not, and creates it, if > not -- the DOC file is generated by repdoc, which makes the difference > between a intltool or make-pot generated pot-file: it detects all > strings). update.sh works, if there's a pot file in the tree. ./make-pot: 25: repdoc: not found repdoc/rep seem not to be commonly installed programs (librep9 package). Is it possible for you to find equivalent commands in standard tools? Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Am Fri, 18 Dec 2009 22:51:11 +0100 schrieb Claude Paroz : > Le vendredi 18 décembre 2009 à 18:04 +0100, Christopher Roy Bratusek a > écrit : > (...) > > Also using intltool for translating sawfish is not recommended, as > > intltool can only recognize strings surounded by (_ ) but most of > > sawfishs strings aren't. Now if you use intltool-update will mark > > all *valid* strings as #~. So for the time beeing, you should make > > sure that the old strings are not disabled/untranslated when using > > intltool. > > > > Current sane way is to do the following: > > > > cd po > > > > # generates a *complete* .pot > > ./make-pot > > > > # updates all po files against the new pot file > > for PO in $(ls *.po); do > > ./update.sh $(basename $PO .po) > > done > > > > Editing the po file NOW is safe. > > > > I know that this is not optimal, sorry. > > Hi Chris, > > Damned-Lies supports special way to generate pot files, under two > conditions: > - the custom script should apply in a clean tree (that is without > requiring an autogen/configure) > - the custom script should be written in a 'standard' (no troll > intent!) language (e.g. bash, perl, python). > > Another way would be to commit the pot file in Git and Damned-Lies > could use it to generate stats. I know it's suboptimal to commit > generated files, but it would be a workaround. > > Claude > Hi Claude, both scripts are shell scripts, which should work with any modern sh. I just commited a little change to make-pot to make it work in a clean tree (it checks wether $(srcdir)/DOC exists or not, and creates it, if not -- the DOC file is generated by repdoc, which makes the difference between a intltool or make-pot generated pot-file: it detects all strings). update.sh works, if there's a pot file in the tree. Chris ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Le vendredi 18 décembre 2009 à 18:04 +0100, Christopher Roy Bratusek a écrit : (...) > Also using intltool for translating sawfish is not recommended, as > intltool can only recognize strings surounded by (_ ) but most of > sawfishs strings aren't. Now if you use intltool-update will mark all > *valid* strings as #~. So for the time beeing, you should make sure > that the old strings are not disabled/untranslated when using intltool. > > Current sane way is to do the following: > > cd po > > # generates a *complete* .pot > ./make-pot > > # updates all po files against the new pot file > for PO in $(ls *.po); do > ./update.sh $(basename $PO .po) > done > > Editing the po file NOW is safe. > > I know that this is not optimal, sorry. Hi Chris, Damned-Lies supports special way to generate pot files, under two conditions: - the custom script should apply in a clean tree (that is without requiring an autogen/configure) - the custom script should be written in a 'standard' (no troll intent!) language (e.g. bash, perl, python). Another way would be to commit the pot file in Git and Damned-Lies could use it to generate stats. I know it's suboptimal to commit generated files, but it would be a workaround. Claude ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Am Fri, 18 Dec 2009 00:24:24 +0100 schrieb Andre Klapper : > Am Donnerstag, den 17.12.2009, 23:58 +0100 schrieb Kenneth Nielsen: > > There is apparently somthing wrong in the sawfish repository on > > gnome > > Fixed. > > andre > Actually you're fix was not correct, as the file does still exist, but it's now called lisp/sawfish/wm/commands/launcher.jl. I really fixed it right now. Also I've added some other files to the list (and check for more). Also using intltool for translating sawfish is not recommended, as intltool can only recognize strings surounded by (_ ) but most of sawfishs strings aren't. Now if you use intltool-update will mark all *valid* strings as #~. So for the time beeing, you should make sure that the old strings are not disabled/untranslated when using intltool. Current sane way is to do the following: cd po # generates a *complete* .pot ./make-pot # updates all po files against the new pot file for PO in $(ls *.po); do ./update.sh $(basename $PO .po) done Editing the po file NOW is safe. I know that this is not optimal, sorry. BTW: All (known) UTF-8/CYK issues in librep/sawfish are gone :) Chris ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Can't integrate translation in module sawfish i gnome git
Am Donnerstag, den 17.12.2009, 23:58 +0100 schrieb Kenneth Nielsen: > There is apparently somthing wrong in the sawfish repository on gnome Fixed. andre -- mailto:ak...@gmx.net | failed http://www.iomc.de/ | http://blogs.gnome.org/aklapper ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Can't integrate translation in module sawfish i gnome git
Halle gnome-i18n peeps and sawfish devs There is apparently somthing wrong in the sawfish repository on gnome git. When I try to run intltool-update against the module, I get the same error as is also listed on damned lies: intltool-update -g 'sawfish' -p xgettext: error while opening "./../lisp/sawfish/wm/commands/user.jl" for reading: No such file or directory ERROR: xgettext failed to generate PO template file. Please consult error message above if there is any. Could someone please look into this? Thanks in advance Kenneth Nielsen ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
