t0028: fix wrong octal values for BOM in setup
The setup code uses octal values with printf to generate a BOM for UTF-16/32 BE/LE. It specifically uses '\777' to emit a 0xff byte. This relies on the fact that most shells truncate the value above 0o377. Ash however interprets '\777' as '\77' + a literal '7', resulting in an invalid BOM. Fix this by using the proper value of 0xff: '\377'. Signed-off-by: Kevin Daudt <me@ikke.info> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Kevin Daudt committed
Feb 11, 2019 at 22:38 UTC
99e9ab54aba21b8fa368f20e6b3585d95b1c4d37
1 file changed
+4
-4
t/t0028-working-tree-encoding.sh
+4
-4
@@ -22,12 +22,12 @@ test_expect_success 'setup test files' '
22
# BOM tests
23
printf "\0a\0b\0c" >nobom.utf16be.raw &&
24
printf "a\0b\0c\0" >nobom.utf16le.raw &&
25
- printf "\376\777\0a\0b\0c" >bebom.utf16be.raw &&
26
- printf "\777\376a\0b\0c\0" >lebom.utf16le.raw &&
25
+ printf "\376\377\0a\0b\0c" >bebom.utf16be.raw &&
26
+ printf "\377\376a\0b\0c\0" >lebom.utf16le.raw &&
27
printf "\0\0\0a\0\0\0b\0\0\0c" >nobom.utf32be.raw &&
28
printf "a\0\0\0b\0\0\0c\0\0\0" >nobom.utf32le.raw &&
29
- printf "\0\0\376\777\0\0\0a\0\0\0b\0\0\0c" >bebom.utf32be.raw &&
30
- printf "\777\376\0\0a\0\0\0b\0\0\0c\0\0\0" >lebom.utf32le.raw &&
29
+ printf "\0\0\376\377\0\0\0a\0\0\0b\0\0\0c" >bebom.utf32be.raw &&
30
+ printf "\377\376\0\0a\0\0\0b\0\0\0c\0\0\0" >lebom.utf32le.raw &&
31
32
# Add only UTF-16 file, we will add the UTF-32 file later
33
cp test.utf16.raw test.utf16 &&