On Oct 20, 3:50 pm, Paulo Cassiano <pcassi...@gmail.com> wrote:

> I tryed to set the i18n as you ask me to do, but doesn't work... My
> DOS prompt shows me characters like <E1><E7>... <F4> in the accents
> place...
>
> Now I'll try to set a default editor. I hope this works for me.
[...]

If you managed to make several commits with i18n.commitencoding *not*
set to the charset matching your windows' code page, then commit
messages of those commits are messed because Git interprets them as
UTF-8. i18n.commitencoding setting makes Git add special header to
every commit object you're making, so that it's able to re-encode
commit messages to your local charset when you do `git log` or
equivalent. So that option only affects commits made after it was set.

If it's not the case, re-check whether the option is really set and
spelled correctly by running

git config --list | findstr commitencoding

in your repository's working directory.

The best bet is just to create a test repository from scratch, set the
option being discussed on it, make several commits with non-ASCII
messages and verify everything works OK, including the output of `git
log` and the display in gitk.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to