From: Jonathan Nieder <jrnieder@gmail.com>
Date: Wed, 09 Mar 2011 20:51:55 GMT
Subject: Re: [PATCH 2/2] i18n: avoid conflict with ngettext from libintl
Message-ID: <20110309205155.GC22292@elie>
In-Reply-To: <7vfwqw9g9b.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:

> Hmph.  An obviously safer alternative would be to use git_ngettext() in
> our source all over the place, and it would by even more peace of mind but
> that is even longer.

Right.  That is tempting.

Ævar, is there some usual or obvious abbreviated form for ngettext we
could use to avoid this fuss altogether?

> Also the same problem exists already for the _() macro.

The usual convention is that the _() macro is private to each
application.  libintl provides a gettext function or macro, and
various programs do

	#define _(msg) gettext(msg)

in some private header (that does not pollute the public namespace)
for notational convenience.