> Date: Wed, 16 Sep 2026 16:47:28 +0200 > From: [email protected] > Cc: [email protected], [email protected] > > On Wed, Sep 16, 2026 at 05:07:28PM +0300, Eli Zaretskii wrote: > > > Date: Wed, 16 Sep 2026 15:55:27 +0200 > > > From: [email protected] > > > Cc: Gavin Smith <[email protected]>, [email protected] > > > It depends where. If it is some isolated sequence, you get some message > > > that there is something wrong going on, but the result should be usable. > > > > OK, but what happens with the byte sequence which couldn't be > > converted in this case? is it skipped, and thus nothing due to it will > > appear in the produced Info file? > > If it happens upon reading the Texinfo input file, there is an error > message in Perl and in C, the byte sequence is skipped in C, it will not > appear in the tree at all, in Perl it depends on what Encode::decode > does, I think that it is skipped too.
I wonder whether skipping is the best we can do. How about emitting something instead, like a string showing the un-decodable bytes in hex or something?
