[libgweather] Created branch gnome-2-28

2009-12-18 Thread Frank Solensky
The branch 'gnome-2-28' was created pointing to:

 423ce93... Updated Danish translations

___
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 Thread Christopher Roy Bratusek
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

2009-12-18 Thread 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

___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: String additions to 'libgweather.master'

2009-12-18 Thread Claude Paroz
Le vendredi 18 décembre 2009 à 04:13 +, GNOME Status Pages a écrit :
> This is an automatic notification from status generation scripts on:
> http://l10n.gnome.org.
> 
> There have been following string additions to module 'libgweather.master':
> 
> + "Bangalore"
> + "Pune"
> + "St. Louis"
> 
> Note that this doesn't directly indicate a string freeze break, but it
> might be worth investigating.

Hi Frank,

Please read https://bugzilla.gnome.org/show_bug.cgi?id=507371#c29
Feel free to ask if something doesn't seem clear in this process.

Cheers,

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 Thread 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.

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