Jiang Xin wrote: > I saw Ævar's bug report on xgettext to the GNU gettext list: > > * http://git.661346.n2.nabble.com/GETTEXT-BUG-xgettext-1-can-t-extract-quot-gettext-foo-quot-td7560744.html > > May be post to a more official mailing list, such as bug-gnu-utils at > https://lists.gnu.org/mailman/listinfo/bug-gnu-utils will get some response, I think bug-gettext is the right place: http://lists.gnu.org/archive/html/bug-gettext/2012-06/msg00003.html > but I doubt there won't be a clear resolution in xgettext. The double negative is leaving me confused. :) Are you saying you doubt that anyone will come up with a patch to fix xgettext, or that you doubt that the result will be satisfactory? [...] > Write a wrapper for gettext and extract messages using > 'xgettext --keyword=<gettext-wrapper>' is a reasonable solution. For what it's worth that does seem to me like the most sensible workaround in the short term. :/ gittext () { # or sane_gettext or literal_gettext or something gettext -- "$1" } gittextln () { gettext -- "$1" echo } Thanks, Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html