On 2/10/25, 5:43 PM, "Patrice Dumas" <pertu...@free.fr> wrote:
> On Fri, Feb 07, 2025 at 10:34:47AM +0000, Gavin Smith wrote:
> > On Wed, Feb 05, 2025 at 05:05:33PM -0500, Daniel Macks wrote:
> > > For the first one, test-suite.log has:
> > > 
> > > FAIL: test_scripts/encoded_non_ascii_command_line.sh
> > > ====================================================
> > It is not just that one byte.  The reference results have %c3%a9 and what
> > was produced is e%cc%81.  This is different ways of outputting the é 
> > character
> > (e with acute accent).  You can check this on the command line with
> > 
> >   LC_ALL=C printf 'e\xCC\x81'
> > 
> > and
> > 
> >   LC_ALL=C printf '\xC3\xA9'
> > 
> > Perhaps some Unicode normalisation step is missing and/or faulty.
>
> I just commited a possible fix:
> https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=bc756a46f8329e5475321edf21615278444dd384

Applying that to 7.2 cleared all 6 fails in test_scripts. Yay thanks! I now get 
as far as some other fails in many_input_files (the test-suite aborted prior to 
this point previously).

FAIL: output_dir_non_ascii.sh
FAIL: output_dir_file_non_ascii.sh

The preceding patch has no effect on this behavior, but the diffs/ files seem 
to indicate the same encoding problem as the test_scripts cases, for example:

$ cat tp/tests/many_input_files/diffs/output_dir_non_ascii.diff
Only in diffs/staging/output_dir_non_ascii_res: encod%c3%a9
Only in output_dir_non_ascii: encode%cc%81

Maybe the same type of patch needs to be applied elsewhere?

dan





Reply via email to