On Sat, Oct 03, 2026 at 08:25:58PM +0300, Eli Zaretskii wrote: > > Date: Sat, 3 Oct 2026 18:13:00 +0200 > > From: Patrice Dumas <[email protected]> > > > > The tests fail for msys2 in CI because of CRLF versus LF mainly in > > output and sometime in input (and Perl/C differences that could be > > overxome if what we want is clear). > > Tests shouldn't fail due to end-of-line (EOL) format differences. The > easiest way to avoid that is (a) to use Diff instead of cmp to compare > output with expected output, and (b) use the --strip-trailing-cr > command-line option to Diff. > > On my system, 'diff' is a shell script that invokes Diff the program > with the --strip-trailing-cr option, and because of this tests rarely > if ever fail due to EOL format differences
Actually I found a thread, and there is code in configure.ac about this issue for install-info tests, with that solution. https://lists.gnu.org/archive/html/bug-texinfo/2022-10/msg00229.html > > How should CRLF be treated in input for native Windows? Should they be > > treated as a logical end of line (the same as a LF in posix systems), or > > as a CR character followed by an end of line? > > The former. It should be okay to have Texinfo source file with CRLF > end-of-line, IMO, because they can be produced by editors which > default to that, or maybe even support only that. As I said in another mail, LF should be accepted too on Windows. > > 2) output > > > > For LaTeX, HTML, DocBook and plaintext..., we have textual output files. > > Should the end of line in output files be CRLF or LF? > > In general, IMO the preference should be to produce native EOL format, > because the output files can be read by arbitrary native tools, some > of which might have problems with Unix-style newline-only EOL format. Ok. -- Pat
