Le lundi 30 mai 2011 à 07:57 +0200, Pau Iranzo a écrit : > Hi, Claude, > > 2011/5/27 Claude Paroz <cla...@2xlibre.net> > Hi Pau, > > Your xgettext call is not correct. -f is not intended to > define files to > extract strings from, but a file which might contain a list of > paths to > consider for extraction. Please read 'man xgettext' again. > > But you are also right: there is no pure xgettext javascript > parser. > Even if most of the time the default C parser will do it fine > (or the > Perl one in certain cases), this is an issue where I think we > need > someone to step up and write a dedicated parser. > > > I've found this tutorial: > http://live.gnome.org/GnomeShell/Extensions/FAQ/CreatingExtensions > > But using this command to generate a pot file: > xgettext -k_ -kN_ -o messages.pot extension.js > > Seems to not work either. Gettext says that it can't recognise the > «js» extension: > > [pau@localhost weat...@venemo.net]$ xgettext -k_ -kN_ -o messages.pot > extension.js > xgettext: avís: l’extensió «js» del fitxer «extension.js» no és > coneguda; es provarà amb el llenguatge «C» > > (warning: the 'js' extension is unknown, trying with C language) > > I'm using Fedora 15 and have installed the translator-toolkit. Am I > missing any libraries?
Mmmmh... did you really read my mail :-) The warning you obtain is an awaited behaviour. Just check messages.pot which should contain extracted strings. Claude -- www.2xlibre.net _______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
