[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gettext feature request

From: Jean-Jacques Brucker
Subject: Re: gettext feature request
Date: Sat, 24 Jul 2021 22:45:40 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0

Le 24/07/2021 à 20:48, Chet Ramey a écrit :
So you want a translation feature without any further interpretation? Or
one just without command substitution?

Translation feature without any further interpretation.


 * eases interoperability of *.mo files (eg: may then be shared with
   with C programs)
 * more coherent with other single quoted string (would only differ by
   interpreting escaped chars even if not used with printf or echo -e)
 * implies better string factorization (force things like /printf
   $'file %s is too big\n' .../ instead of /echo $'file $f is too big'/
   and later /echo $'file ${fl[$n]} is too big'/)

I see no cons.

What about an option to enable this variant behavior? What do you think
would be a suitable name?

For testing purpose, option-name: *gettext*. But if possible, I would prefer such feature enabled by default, then *nogettext* to disable.
As of today (bash 5.1.x), *-g* and *-G* are also available.


Attachment: OpenPGP_0xA3983A40D1458443.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]