On อ., 2005-08-09 at 16:44 +0930, Clytie Siddall wrote: > Hi guys :) > > I submitted an updated file today, and fortunately the commit check > caught a variable which hadn't been changed. > > But my msgfmt check turned up clean. I find this very puzzling, since > the variable was definitely wrong. >
Not sure if it's the best advice, but I did this for a load of gtranslator po files recently (changed 'translator_credits' to 'translator-credits' in all files with sed), and found a couple of them would no longer commit (due to new msgfmt checks). I fixed those cases where I could and simply commented out the ones that I couldn't (only a handful of cases). Hopefully, next time the translators looks over those files they'll get fixed up properly. > I'm using: > > msgfmt -cv > > and normally that catches all the usual errors, including disparate > printfs. > What version of gettext are you using? I just checked, the version of gettext running on container for the commit check is 0.11.4. I didn't realise it was that ancient! I just tried to rebuild a more recent one (from FC4's 0.14.3 SRPM), but it's not playing nicely with the older auto* environment on the gnome.org servers (and I don't fancy upgrading all that too just to rebuild a gettext RPM!). CCing infrastructure: Consider this a 'todo' item to upgrade gettext on container. Or, arrange to get the machines upgraded to RHEL4 (or anything more up-to-date than bloody RHEL3!!!). -- Ross > > Can someone help me sort this out, please? I don't want to submit > incorrect files. :( > > from Clytie (vi-VN, Vietnamese free-software translation team / nhóm > Việt hóa phần mềm tự do) > http://groups-beta.google.com/group/vi-VN > > > _______________________________________________ > gnome-i18n mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gnome-i18n _______________________________________________ Gnome-infrastructure mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-infrastructure
