--- Begin Message ---
Subject: |
tests/printf/printf-cov failure on macOS |
Date: |
Mon, 18 Nov 2024 23:41:46 -0500 |
The u4 and U8 tests in tests/printf/printf-cov.pl fail on macOS 15:
u4...
printf: test u4: stdout mismatch, comparing u4.1 (expected) and u4.O (actual)
*** u4.1 Mon Nov 18 23:30:03 2024
--- u4.O Mon Nov 18 23:30:03 2024
***************
*** 1 ****
! 0
\ No newline at end of file
--- 1 ----
! \u0030
\ No newline at end of file
U8...
printf: test U8: stdout mismatch, comparing U8.1 (expected) and U8.O (actual)
*** U8.1 Mon Nov 18 23:30:03 2024
--- U8.O Mon Nov 18 23:30:03 2024
***************
*** 1 ****
! 0
\ No newline at end of file
--- 1 ----
! \u0030
\ No newline at end of file
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#74428: tests/printf/printf-cov failure on macOS |
Date: |
Tue, 19 Nov 2024 18:31:31 +0000 |
User-agent: |
Mozilla Thunderbird Beta |
On 19/11/2024 17:34, Bruno Haible wrote:
Pádraig Brady wrote:
I would prefer to bypass the ASCII case if CODE >= 0 && CODE < 128.
However is that generally correct?
Yes, at least for CODE >= 32 && CODE < 128 it is correct.
This can be seen from the list of supported locale encodings in
gnulib/lib/localcharset.h.
OK I've adjusted our test to use \u00032 instead,
and tested the attached code, which I'll push later.
thanks,
Pádraig
gnulib-uc-ascii.diff
Description: Text Data
--- End Message ---