Kevin Daudt <m...@ikke.info> writes: > 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 <m...@ikke.info> > --- > I do wonder why this code is using octal values in the first place, > rather than using hex values.
Most likely for portability to non GNU and less widely used systems. Thanks for spotting these \777s. Will apply.
