Follow-up Comment #5, bug #49654 (project gettext): Daiki,
> Bruno, are you willing to provide a patch for this? No, I'd leave that to you. I'm trying to focus on libiconv and libsigsegv in the moment. > I think it could also be worked around by disabling the auto-msgmerge rule in po/Makefile.in.in There are several ways in which PO files can be integrated into a release, compiled, and then installed on a user's system. For example: - The maintainer installs PO files manually, "make" merges them with the POT file, "make install" installs the .mo file. (This is what Makefile.in.in currently does.) - "make" fetches the PO file from the Translation project and msgmerges it. "make install" installs the .mo file. - You may omit msgmerge and thereby put old, unused messages into the .mo file. - Some of the gettext 'hello' examples use a Makefile.am instead of Makefile.in.in. In summary, there is considerable variation in the way the PO files are transmitted and msgmerged. But the common thing is that they use 'xgettext' (or some similar tool), 'msgmerge' (needed to filter out old, unused messages) and 'msgfmt'. I would therefore not try to fix a general problem with the tools by modifying Makefile.in.in. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?49654> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/