Ah, so contrary to an earlier assertion in this thread, Git and Git diff command specifically DO understand Unicode -- just not in the outdated UTF-16 transformation format.
On Sunday, October 6, 2013 9:49:12 AM UTC-7, Peter Pitchford wrote: > > It turns out git diff doesn't understand utf-16 encoded files. The clue is > that the output says "Binary files" > I switched the encoding to utf-8 and git diff now shows the details. > > " UTF-16 is a historical accident that persists mainly due to inertia. > UTF-16 has no practical advantages over UTF-8, and it is worse in some > ways. " > http://benlynn.blogspot.com/2011/02/utf-8-good-utf-16-bad_07.html > I never knew that. > > On Sunday, October 6, 2013 11:15:44 AM UTC-4, Peter Pitchford wrote: >> >> Windows 7 >> Git Bash or Command line, both act the same. >> >> When I change a file and then run *git diff* I get: >> C:\workshop\git>git diff >> diff --git a/thirdfile.txt b/thirdfile.txt >> index 7caac66..f6eb45c 100644 >> Binary files a/thirdfile.txt and b/thirdfile.txt differ >> >> How do I get it to show the lines that have been changed? >> > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
