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

tbo...@web.de writes: > The unicode standard itself defines 3 possible ways how to encode UTF-16. > a) UTF-16, without BOM, big endian: > b) UTF-16, with BOM, little endian: > c) UTF-16, with BOM, big endian: Is it OK to interpret "possible" as "allowed" above? > iconv (and libiconv) can generat

[PATCH v2 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 working-tree-encoding=UTF-16 The unicode standard itself defines 3 possible ways how to encode UTF-16. The following 3 versions convert all back to 'g' 'i' 't' in UTF-8: a) UTF-