Re: gitweb: charset problem

From: Junio C Hamano <junkio@cox.net>
Date: Oct 25, 2005, 17:44 UTC
Message-ID: <7v64rlfq40.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0510251138290.25300@iabervon.org>

Daniel Barkalow <barkalow@iabervon.org> writes:

Show 5 quoted lines

> It wouldn't be hard to convert at some point between the editor and the 
> commit object, and you don't re-edit the commit objects like you do 
> tracked files. It probably wouldn't even be hard for commit-tree to 
> convert its input based on locale. (And stuff which prints commit contents 
> for user consumption probably ought to re-encode it if necessary, too)

Don't get me wrong. I am not opposed to giving preferential treatment to UTF-8 by supporting it better. I think it may be a good idea to have an *option* in commit-tree and mktag to convert from LC_CTYPE to utf-8, just like mailinfo does.

I am just opposing to make UTF-8 mandatory.