Re: t0028-working-tree-encoding.sh test #3 data

2019-03-09 Thread Torsten Bögershausen
On Sat, Mar 09, 2019 at 08:57:07PM -0500, Jeffrey Walton wrote: > On Sat, Mar 9, 2019 at 11:10 AM Torsten Bögershausen wrote: > > > > On Sat, Mar 09, 2019 at 09:36:34AM -0500, Jeffrey Walton wrote: > > > > > > I'm experiencing a failure in t0028-working-tree-encoding.sh. The > > > first failure is

Re: t0028-working-tree-encoding.sh test #3 data

2019-03-09 Thread Jeffrey Walton
On Sat, Mar 9, 2019 at 11:10 AM Torsten Bögershausen wrote: > > On Sat, Mar 09, 2019 at 09:36:34AM -0500, Jeffrey Walton wrote: > > > > I'm experiencing a failure in t0028-working-tree-encoding.sh. The > > first failure is test #3. The source states "source (test.utf16lebom, > > considered UTF-16L

Re: t0028-working-tree-encoding.sh test #3 data

2019-03-09 Thread Torsten Bögershausen
On Sat, Mar 09, 2019 at 09:36:34AM -0500, Jeffrey Walton wrote: > Hi Everyone, > > I'm experiencing a failure in t0028-working-tree-encoding.sh. The > first failure is test #3. The source states "source (test.utf16lebom, > considered UTF-16LE-BOM)" but it looks like a UTF16-LE BOM followed by > a U

t0028-working-tree-encoding.sh test #3 data

2019-03-09 Thread Jeffrey Walton
Hi Everyone, I'm experiencing a failure in t0028-working-tree-encoding.sh. The first failure is test #3. The source states "source (test.utf16lebom, considered UTF-16LE-BOM)" but it looks like a UTF16-LE BOM followed by a UTF32-LE stream. Am I misunderstanding the data presentation? $ ./t0028-wo