Zack Weinberg schrieb: > I was going to mess with libasio today, but instead, on .stripped I > tore out the awful, awful autoconf macros provided by the gettext > developers and substituted custom logic. This has several nice > consequences: the makefile is no longer at all recursive, we don't > need horrible hacks to stop the po subdirectory Makefile from stomping > on translations, the configure script no longer does a whole pile of > unnecessary tests, and I think detection of libintl and libiconv may > now actually be *correct* rather than mostly wrong. > > However, as ever when one messes with the Makefile, I may have broken > something. I'm particularly concerned about installation (it > *appears* to put the .mo files in the right place, but ...) and the > translation workflow, with which I am not very familiar. Please test.
Yes, unfortunately you seem to have broken it ;) The usual (German) translator workflow is $ make monotone.pot-update && make de.po-update but the first one already fails because of the dropped POTFILES.in: make: *** No rule to make target `POTFILES.in', needed by `Makefile'. Stop. This one now gets autogenerated, right? Thomas. -- GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
