From: Junio C Hamano Date: Mon, 01 Jan 2007 19:44:15 GMT Subject: Re: i18n, alternative solution Message-ID: <7vy7om7cs0.fsf@assigned-by-dhcp.cox.net> In-Reply-To: <200701011547.48697.robin.rosenberg.lists@dewire.com> Robin Rosenberg 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.