[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gettext feature request
From: |
Lawrence Velázquez |
Subject: |
Re: gettext feature request |
Date: |
Sat, 31 Jul 2021 16:57:32 -0400 |
User-agent: |
Cyrus-JMAP/3.5.0-alpha0-545-g7a4eea542e-fm-20210727.001-g7a4eea54 |
On Sat, Jul 31, 2021, at 4:17 PM, Jean-Jacques Brucker wrote:
> The advantage of adding such variable is that we could use more easily
> different mo files in a same bash execution :
>
> (at least) one "legacy" (for /$"..."/) and (at least) one 'C-strings'
> (for /$'...'/), which could then be shared with a C program (For example
> lazy people could then reuse coreutils mo files, as they contain lot of
> frequently-used-everywhere strings, while using their own mo file for
> "legacy" strings).
I'm a little confused. My impression was that this hypothetical
option would *disable expansion* in $"...", not *enable translation*
in $'...'. I wasn't under the impression that reappropriating
$'...' for translation was on the table?
--
vq
Re: gettext feature request, Léa Gris, 2021/07/24
Re: gettext feature request, Eli Schwartz, 2021/07/29