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

Re: i18n, alternative solution

From
Junio C Hamano <junkio@cox.net>
Date
Jan 1, 2007, 19:44 UTC
Message-ID
<7vy7om7cs0.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200701011547.48697.robin.rosenberg.lists@dewire.com>
Robin Rosenberg <robin.rosenberg.lists@dewire.com> writes:
> What disturbes me is the complexity that the approach of storing multiple 
> encodings in the same repository results in.
We are not encouraging mixed encodings, mind you.

Even though we check and warn comits that do not have a valid UTF-8 string, the users can make mistakes and people need be able to look at them later. That is what we are solving.

At the same time we do NOT force inconvenience on projects that want to use legacy encoding for whatever reason. The world is not UTF-8 only, and encoding to UTF-8 is non-reversible a times (positive return value from iconv(3)). Always re-coding to UTF-8 will NOT be accepted to git for now. We can revisit this perhaps in 5 years.

Previous: Robin RosenbergNext: Robin Rosenberg
Message 2 of 3 in “i18n, alternative solution”
  1. Robin RosenbergJan 1, 2007
  2. Junio C HamanoJan 1, 2007
  3. Robin RosenbergJan 7, 2007

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.