Re: [PATCH v3 1/1] Support working-tree-encoding "UTF-16LE-BOM"

2019-01-30 Thread Torsten Bögershausen
c: Torsten Bögershausen > > Subject: [PATCH v3 1/1] Support working-tree-encoding "UTF-16LE-BOM" > > > > From: Torsten Bögershausen > > > > Users who want UTF-16 files in the working tree set the .gitattributes > > like this: > > test.txt workin

RE: [PATCH v3 1/1] Support working-tree-encoding "UTF-16LE-BOM"

2019-01-30 Thread Jason Pyeron
> -Original Message- > From: git-ow...@vger.kernel.org On Behalf Of > tbo...@web.de > Sent: Wednesday, January 30, 2019 10:02 AM > To: git@vger.kernel.org; adrigi...@gmail.com > Cc: Torsten Bögershausen > Subject: [PATCH v3 1/1] Support working-tree-encoding &qu

[PATCH v3 1/1] Support working-tree-encoding "UTF-16LE-BOM"

2019-01-30 Thread tboegi
From: Torsten Bögershausen Users who want UTF-16 files in the working tree set the .gitattributes like this: test.txt working-tree-encoding=UTF-16 The unicode standard itself defines 3 allowed ways how to encode UTF-16. The following 3 versions convert all back to 'g' 'i' 't' in UTF-8: a) UTF-1