Re: Corrupted multibyte characters in command substitutions fixes may be worse than problem.

[Greg Wooledge]

On Sun, Feb 06, 2022 at 11:11:43PM +0100, Alex fxmbsw7 Ratchev wrote:
> [[ Regarding nul bytes discarded by command substitution ]]
> can't these \0 bytes be encoded at least when a utf8 locale is used as
> \u0 instead of dropping ? <the two utf 8 bytes> and a null, ... just
> prefix the utf 8 encoding chars to the null
> and they'd be safely maybe still here

There are other programming languages besides bash.  Some of them can
store NUL bytes internally, either by encoding and decoding them on the
fly, or by not using C-style strings internally (which means any system
calls require encoding/decoding the internal strings to C-style strings).

I urge you to learn one of these other languages, and use it.

Bash is a shell, not a full general-purpose programming language.  It's
not suited to all tasks.  Many other languages are *better* suited to
various tasks.  Using the best language for each task will make your
life easier.