Reuben Thomas wrote:
>I agree that this behaviour is undesirable. Unfortunately it's deep-seated.
>I have done some work on it, but I don't yet have something I can release.
Oh cool, so I'm not the first person to notice, and there's already been
some progress.
Quick thought about a way this coul
On Wed, 1 Mar 2023 at 01:33, Zefram wrote:
>
> The invocation with both encodings the same superficially looks like
> it's requesting an identity transformation, and it would correctly have
> the behaviour of an identity transformation on input that were correctly
> encoded. Because of the input
Package: recode
Version: 3.6-24
Severity: normal
recode(1) usually checks that its input conforms to the specified input
encoding, and signals an error if it doesn't:
$ echo $'L\xe9on' | recode utf8..utf7
Lrecode: Invalid input in step `UTF-8..UNICODE-1-1-UTF-7'
But if the output encoding happen
3 matches
Mail list logo
