bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Corrupted multibyte characters in command substitutions fixes may be


From: Alex fxmbsw7 Ratchev
Subject: Re: Corrupted multibyte characters in command substitutions fixes may be worse than problem.
Date: Mon, 7 Feb 2022 05:55:48 +0100

On Mon, Feb 7, 2022 at 3:37 AM Chet Ramey <chet.ramey@case.edu> wrote:
>
> On 2/6/22 5:11 PM, Alex fxmbsw7 Ratchev wrote:
> > i just have a small question here
> > the dropping of null bytes is no friend of me and i understand you're
> > there to skip it instead of process, which results in null bytes gone
> > which is not much of an use
> >
> > 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
>
> OK, say they're still there. What use are they? What are you going to do
> with them?

it'd be a big wonder to me
this is about data preservance, aka not mangling
if the nulls are present, internal variables can be used for any kind
of input rather than only files
its only a plus to have em

 --
> ``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/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]