[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: expr say "non integer argument"
From: |
Jim Meyering |
Subject: |
Re: expr say "non integer argument" |
Date: |
Fri, 19 Feb 2010 09:51:40 +0100 |
Voelker, Bernhard wrote:
> Eric Blake wrote:
>
>>According to Voelker, Bernhard on 2/18/2010 8:31 AM:
>>>> - error (EXPR_INVALID, 0, _("non-numeric argument"));
>>>> + error (EXPR_INVALID, 0, _("non-integer argument"));
>>>
>>> Maybe a dumb question:
>>> Why's the error message hardcoded?
>>
>>It isn't.
>>
>>> Isn't there localization for this error message?
>>
>> Yep - _("...") is the localization. It is a macro that calls gettext, and
>> gettext does all the work of translating it according to your locale
>> environment variables.
>
> so the patch implies that there's already a translation for
> "non-integer argument", right?
No. Once a new translatable string appears in a source file,
it propagates to the po/*.pot file for the next release.
- Re: expr say "non integer argument", (continued)
- Re: expr say "non integer argument", Eric Blake, 2010/02/18
- Re: expr say "non integer argument", jidanni, 2010/02/18
- Re: expr say "non integer argument", Eric Blake, 2010/02/18
- Re: expr say "non integer argument", jidanni, 2010/02/18
- diff "--git", jidanni, 2010/02/18
- Re: diff "--git", Alfred M. Szmidt, 2010/02/18
- Re: diff "--git", jidanni, 2010/02/18
- RE: expr say "non integer argument", Voelker, Bernhard, 2010/02/18
- Re: expr say "non integer argument", Eric Blake, 2010/02/18
- RE: expr say "non integer argument", Voelker, Bernhard, 2010/02/19
- Re: expr say "non integer argument",
Jim Meyering <=
- Re: expr say "non integer argument", Eric Blake, 2010/02/25
- Re: expr say "non integer argument", Eric Blake, 2010/02/25
- Re: expr say "non integer argument", Chris F.A. Johnson, 2010/02/18
- Re: expr say "non integer argument", jidanni, 2010/02/18