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
