On Thu, 2008-02-07 at 21:47 +0000, Peter Clifton wrote: > Don't get me wrong.. I'm not "anti" fixing this, I'm just struggling to > figure out how best to do it in a way which doesn't break all the > benefits which intltool brings on systems which do have it.
Ok, for now, I think intltool must die. If we re-introduce its benefits: * Translatable strings from desktop integrations files ends up in .pot template, allowing easy translation by "usual" means. * Translations for mime registrations are shared for both the XDG and KDE versions. Then it must be in a more sane way (with less dependencies). The thought which struck me was to write a program to run on the build host, which used any available gettext infrastructure to translate the required strings into any language listed in po/LINGUAS at build time. For now, I've not done this.. its late, and I'm not sure what the effort / benefit ratio is that high. These strings won't change too often, and for now... if a translator wants to add a new language, they will have to add lines to the appropriate .desktop or .xml files. The patch isn't pushed yet, but you can see it here: http://repo.or.cz/w/geda-gaf/pcjc2.git http://repo.or.cz/w/geda-gaf/pcjc2.git?a=commitdiff;h=4deb188c9f1e23b2b247be833deb0c4fd96134f6 I expect a similar intltool-ectomy will be good for PCB, assuming the PCB developers agree. For now, I will keep it in xgsch2pcb, since it would need replacing with another tool to extract and manage the translations from the python code. Best wishes, Peter (willing to listen to reason / peer pressure) Clifton. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
