Re: [PATCH v9 4/8] utf8: add function to detect a missing UTF-16/32 BOM

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 6, 2018, 22:53 UTC
Message-ID: <xmqq8tb43jfe.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <0DCED348-C6DB-49B2-8C0A-E4E1F485B255@gmail.com>

Lars Schneider <larsxschneider@gmail.com> writes:

Show 7 quoted lines

>>  Also "UTF16" or other spelling
>> the platform may support but this code fails to recognise will go
>> unchecked.
>
> That is true. However, I would assume all iconv implementations use the
> same encoding names for UTF encodings, no? That means UTF16 would never be
> valid. Would you agree?

After seeing "UTF16" and others in "iconv -l | grep -i utf" output, I am not sure what you mean by "Would you agree?" People can say in their .gitattributes file that this path is in "UTF16" without dash and that is what will be fed to this coe, no?

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.