[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gettext feature request
From: |
Chet Ramey |
Subject: |
Re: gettext feature request |
Date: |
Tue, 27 Jul 2021 10:39:12 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 |
On 7/24/21 4:45 PM, Jean-Jacques Brucker wrote:
>
> 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.
OK, so the result is effectively single-quoted instead of double-quoted.
>> What about an option to enable this variant behavior? What do you think
>> would be a suitable name?
>>
> For testing purpose, option-name: *gettext*.
That's not a good name. It provides no insight about the option or its
purpose. Maybe something like `quote_translation'.
> But if possible, I would
> prefer such feature enabled by default, then *nogettext* to disable.
That's not backwards compatible, so the best thing for you to do would be
to set this option in the places where it matters for your scripts, maybe
in a script configuration file.
> As of today (bash 5.1.x), *-g* and *-G* are also available.
It will be an option to `shopt', not `set -o'.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Re: gettext feature request, Léa Gris, 2021/07/24
Re: gettext feature request, Eli Schwartz, 2021/07/29