Re: GIT character codecs

From: Junio C Hamano <junkio@cox.net>
Date: Nov 13, 2005, 10:21 UTC
Message-ID: <7v3bm0c0gf.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20051113081443.38296.qmail@web26309.mail.ukl.yahoo.com>

Marco Costalba <mcostalba@yahoo.it> writes:

> But I'm a bit reclutant to add this 'codec list' stuff
> because, as said, is *not* the real solution.

Why isn't it real? UNIX files do not declare what encoding they are in, and people get their work done with existing viewing or editing tools (e.g. vi, less, emacs, firefox [*1*], ...). How is your situation any different?

I suspect you could just take the default from LANG and LC_CTYPE to cover 98% of the cases, and to cover the rest 2% the problematic cases have a per-window override menu. If you first implement only the locale support without per-window override and tell your users to set these environment variables to iso-8859-15 when running qgit on your Italian project repository (or use utf-8 on git.git), wouldn't that be sufficient for most everyday uses?

[Footnotes]

*1* Ok, firefox is a bit different because they can read charset attribute from content type, but even so they have a manual override from View->CharEncoding menu to let their users cope with broken pages.