Re: extending the blame callback

On 06.01.2019 15:05, Branko Čibej wrote:
> Until we have better support for other Unicode representations, we
> should detect that null byte and include it as part of the reported
> blame line.

That might also imply detecting that the file encoding is not UTF-16-BE
instead ... which could very likely also have a null byte after the 0x0a
that does belong to the next line. I'd suggest checking for odd/even
offsets of the newline byte, since both UTF-16 representations must have
an even number of bytes in each line. It would be nice to avoid
treating, e.g., U+010A as a line break ...

-- Brane
Received on 2019-01-06 15:15:28 CET