Re: Last mile to 1.0?
- From
- Alexey Nezhdanov <snake@penza-gsm.ru>
- Date
- Jul 18, 2005, 06:48 UTC
- Message-ID
- <200507181048.50303.snake@penza-gsm.ru>
- In-Reply-To
- <7vfyucfzgt.fsf@assigned-by-dhcp.cox.net>
Monday, 18 July 2005 09:35 Junio C Hamano wrote:
Show 9 quoted lines
> Alexey Nezhdanov <snake@penza-gsm.ru> writes: > > I'd add the UTF-8 native support. Currently neither commit nor gitk > > doesn't support that. Probably this should be done at as low as possible > > level. > > I do not understand your proposal. Care to clarify? You can > write your commit messages in UTF-8 today and "git-cat-file > commit $commit_ID", which is as low level as you can go, gives > you that commit message in UTF-8.
Yes. But it have not integration with user environment. Personally I use koi8-r environment and doing "cg commit" (and probably "git commit" too) results in koi8-r text written as commit text. I remember that this issue were discussed on this list and all come to conclusion that utf-8 is the only sane encoding that can be used in this case. But this should not be user's problem - it's just the UI that doesn't understands when transcoding should be done. Similarly - when I start gitk then I see only weird symbols instead of commit text, not matter what encoding I use for commits - koi8-r or utf-8. BTW russian koi8-r encoded text _in_diff_contents_ show correctly. Wonder why...
-- Respectfully Alexey Nezhdanov