On Wed, 1 Mar 2023 at 01:33, Zefram <zef...@fysh.org> 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 checking that recode(1) usually provides, > it seems like this kind of invocation would be useful, as something > that copies its input while checking the encoding. Apparently it's > being optimised incorrectly, to a pure identity transformation without > the checking. >
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. Here's the existing upstream issue: https://github.com/rrthomas/recode/issues/37 -- https://rrt.sc3d.org
