git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation/i18n.txt: clarify character encoding support

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 15, 2015, 00:12 UTC
Message-ID
<xmqqmw01ltid.fsf@gitster.dls.corp.google.com>
In-Reply-To
<557C9161.6020703@gmail.com>
Karsten Blees <karsten.blees@gmail.com> writes:
Show 14 quoted lines
> diff --git a/Documentation/i18n.txt b/Documentation/i18n.txt
> index e9a1d5d..e5f6233 100644
> --- a/Documentation/i18n.txt
> +++ b/Documentation/i18n.txt
> @@ -1,18 +1,28 @@
> -At the core level, Git is character encoding agnostic.
> -
> - - The pathnames recorded in the index and in the tree objects
> -   are treated as uninterpreted sequences of non-NUL bytes.
> -   What readdir(2) returns are what are recorded and compared
> -   with the data Git keeps track of, which in turn are expected
> -   to be what lstat(2) and creat(2) accepts.  There is no such
> -   thing as pathname encoding translation.
> +Git is to some extent character encoding agnostic.

I do not think the removal of the text makes much sense here unless you add the equivalent to the new text below.

Show 7 quoted lines
>   - The contents of the blob objects are uninterpreted sequences
>     of bytes.  There is no encoding translation at the core
>     level.
>  
> - - The commit log messages are uninterpreted sequences of non-NUL
> -   bytes.
> + - Pathnames are encoded in UTF-8 normalization form C. This

That is true only on some systems like OSX (with HFS+) and Windows, no? BSDs in general and Linux do not do any such mangling IIRC. I am OK with mangling described as a notable oddball to warn users, though; i.e. not as a norm as your new text suggests but as an exception.

> +   platforms. If file system APIs don't use UTF-8 (which may be
> +   file system specific), it is recommended to stick to pure
> +   ASCII file names.

Hmph, who endorsed such a recommendation? It is recommended to stick to whatever naming scheme that would not cause troubles to project participants. If your participants all want to (and can) use ISO-8859-1, we do not discourage them from doing so.

Previous: Karsten BleesNext: Karsten Blees
Message 2 of 6 in “Documentation/i18n.txt: clarify character encoding support”
  1. Documentation/i18n.txt: clarify character encoding supportKarsten Blees, Jun 13, 2015
  2. Junio C HamanoJun 15, 2015
  3. Karsten BleesJun 15, 2015
  4. Junio C HamanoJun 17, 2015
  5. Documentation/i18n.txt: clarify character encoding supportKarsten Blees, Jul 1, 2015
  6. Torsten BögershausenJul 2, 2015

Read the whole thread, see it on lore, or plain text.

$ 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.