[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: Thu, 12 Aug 2021 00:35:27 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0

Le 10/08/2021 à 17:22, Chet Ramey a écrit :
This is the current description:

                If  set,  bash encloses the translated results of $"..."
                quoting in single quotes instead of double  quotes.   If
                the string is not translated, this has no effect.

It will be in the next devel branch push.

Thank a lot Chet.

I still think it would have been more consistent to extend the $'...' syntax.

But this change is already a great feature, and I hope the gettext developers will warmly welcome it and then update their documentation.

Finally, this functionality which already reinforces the security, does not prevent another option which one could call 'translate_c_string' to translate the $'strings' (without any expansion).

(my idea of an additional variable like 'TEXTCDOMAIN' was indeed not that great)

If both options existed ('noexpand_translation' AND 'translate_c_string'), I would prefer to use the second which is even more secure (either my strings are translated or they are not, but they can never be expanded).

But already I'm delighted to not plan horrible workarounds anymore, and if only 'noexpand_translation' is released, I'll be happy to use it. :-)


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]