Paul Eggert wrote:
> I guess I thought it was specified. The gettext manual says something
> like this under "xgettext Invocation":
>
>`-k KEYWORDSPEC'
>`--keyword[=KEYWORDSPEC]'
> Additional keyword to be looked for (without KEYWORDSPEC means not
> to use default keywords
Bruno Haible <[EMAIL PROTECTED]> writes:
> xgettext is not guaranteed to work in this situation. Basically, there
> are too many tokens between the _ and the strings. And there are two
> strings. Should xgettext extract the first or the second string? Or both?
> It is all unspecified.
I guess I t
Paul Eggert wrote:
> but can you please hoist the call to gettext
> outside the conditional? That is a tad easier for me to read and
> typically generates more-compact code. Something like this:
>
> error (0, 0,
> _(problem == -1
>? "invalid argument %s for %s"
>
Bruno Haible <[EMAIL PROTECTED]> writes:
> ! error (0, 0,
> ! (problem == -1
> ! ? _("invalid argument %s for %s")
> ! : _("ambiguous argument %s for %s")),
> ! quotearg_n_style (0, ARGMATCH_QUOTING_STYLE, value),
>quote_n (1, context));
That looks good, thanks, bu
