Re: [PATCH v7 0/7] convert: add support for different encodings
- From
Jeff King <peff@peff.net>
- Date
- Feb 27, 2018, 21:58 UTC
- Message-ID
- <20180227215845.GA11187@sigill.intra.peff.net>
- In-Reply-To
- <xmqqd10qp07d.fsf@gitster-ct.c.googlers.com>
On Tue, Feb 27, 2018 at 01:55:02PM -0800, Junio C Hamano wrote:
Show 12 quoted lines
> Jeff King <peff@peff.net> writes: > > > Of the three solutions, I think the relative merits are something like > > this: > > ... > > 3. w-t-e (Lars's patch) > > I thought Lars's w-t-e was about keeping the in-repo contents in > UTF-8 and externalize in whatever encoding (e.g. UTF-16), so it > won't help the issue hosting folks want to deal with, i.e. showing > in-repo data that is stored in a strange binary-looking encoding in > a more reasonable encodign while diffing, no?
I thought it solved that by the hosting folks never seeing the strange binary-looking data. They see only utf8, which diffs well.
-Peff