On Mon, Aug 16, 2021 at 12:53:36PM -0400, Jeff King wrote: > But an alternative workflow, if you really want UTF-16 in the working > tree, is to convert between UTF-8 and UTF-16 as the files go in and out > o the working tree. There's no built-in support for that, but you could > do it with a custom clean/smudge filter. That would let Git store UTF-8 > internally, do diffs, etc. Oh, by the way, I totally forgot that we added an internal version of this, which is easier to configure and much more efficient. See the "working-tree-encoding" attribute in "git help attributes". Just in case you do want to go that route. -Peff
