Re: [PATCH v11 07/10] convert: check for detectable errors in UTF encodings
Show 10 quoted lines
> On 09 Mar 2018, at 20:00, Junio C Hamano <gitster@pobox.com> wrote:
>
> lars.schneider@autodesk.com writes:
>
>> + const char *advise_msg = _(
>> + "The file '%s' contains a byte order "
>> + "mark (BOM). Please use %.6s as "
>> + "working-tree-encoding.");
>
> I know that this will go away in a later step, but why ".6"?
I deleted the original comment in the rebase, sorry:
/*
* This advice is shown for UTF-??BE and UTF-??LE
* encodings. We truncate the encoding name to 6
* chars with %.6s to cut off the last two "byte
* order" characters.
*/- Lars