{"thread":{"id":"6270","subject":"Re: OT: character encodings (was: Linux 2.6.20-rc4)","startedAt":"2007-01-07T20:15:14Z","lastAt":"2007-01-08T01:53:51Z","messageCount":4,"participants":["Sean","Jan Engelhardt","Xavier Bestel","David Woodhouse"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"31076","messageId":"20070107151514.be9430b1.seanlkml@sympatico.ca","threadId":"6270","inReplyTo":"20070107200553.GA15101@redhat.com","subject":"Re: OT: character encodings (was: Linux 2.6.20-rc4)","fromName":"Sean","fromEmail":"seanlkml@sympatico.ca","sentAt":"2007-01-07T20:15:14Z","receivedAt":"2007-01-07T20:15:14Z","isPatch":false,"sender":{"key":"seanlkml@sympatico.ca","avatar":"https://gravatar.com/avatar/f92923f54fc08c401fc59b71829d4b89e9b8087fbba45ff87c82e6a83aee02ae?d=mp&s=160"},"body":"On Sun, 7 Jan 2007 15:05:53 -0500\nDave Jones wrote:\n\nIncluding the Git list...\n\n> On Sun, Jan 07, 2007 at 07:17:30PM +0000, Russell King wrote:\n> \n> > commit 24ebead82bbf9785909d4cf205e2df5e9ff7da32\n> > tree 921f686860e918a01c3d3fb6cd106ba82bf4ace6\n> > parent 264166e604a7e14c278e31cadd1afb06a7d51a11\n> > author Rafa³ Bilski 1167691774 +0100\n> > committer Dave Jones 1167799119 -0500\n> > \n> > and looking at that \"author\" closer with od:\n> > \n> > 0000140 74 68 6f 72 20 52 61 66 61 b3 20 42 69 6c 73 6b\n> > t h o r R a f a ³ B i l s k\n> > \n> > clearly not UTF-8. I doubt whether any of the commits I do on my\n> > en_GB ISO-8859-1 systems end up being UTF-8 encoded.\n> \n> This has been bugging me for a while.\n> Viewing the mail I applied in mutt shows his name correctly as Rafał\n> Applying it with git-applymbox and viewing the log on master.kernel.org\n> with git log shows Rafa And then later when put into email\n> it turns into Rafa³\n> \n> > But the point is there is charset damage which has happened _long_ before\n> > Linus' action. There is no character set defined for the contents of git\n> > repositories, and as such the output of the git tools can not be\n> > interpreted as any one single character set.\n> \n> If there's something I should be doing when I commit that I'm not,\n> I'll be happy to change my scripts. My $LANG is set to en_US.UTF-8\n> which should DTRT to the best of my knowledge, but clearly, that isn't\n> the case.\n"},{"id":"31078","messageId":"Pine.LNX.4.61.0701072139520.4365@yvahk01.tjqt.qr","threadId":"6270","inReplyTo":"20070107151514.be9430b1.seanlkml@sympatico.ca","subject":"Re: OT: character encodings (was: Linux 2.6.20-rc4)","fromName":"Jan Engelhardt","fromEmail":"jengelh@linux01.gwdg.de","sentAt":"2007-01-07T20:40:45Z","receivedAt":"2007-01-07T20:40:45Z","isPatch":false,"sender":{"key":"jengelh@linux01.gwdg.de","avatar":null},"body":"\n>On Sun, 7 Jan 2007 15:05:53 -0500\n>Dave Jones wrote:\n>\n>> If there's something I should be doing when I commit that I'm not,\n>> I'll be happy to change my scripts. My $LANG is set to en_US.UTF-8\n>> which should DTRT to the best of my knowledge, but clearly, that isn't\n>> the case.\n\nNo, LC_CTYPE defines what charset you use. (I may be wrong, though.)\n\n\n\t-`J'\n-- \n"},{"id":"31079","messageId":"1168204064.3806.40.camel@bip.parateam.prv","threadId":"6270","inReplyTo":"Pine.LNX.4.61.0701072139520.4365@yvahk01.tjqt.qr","subject":"Re: OT: character encodings (was: Linux 2.6.20-rc4)","fromName":"Xavier Bestel","fromEmail":"xavier.bestel@free.fr","sentAt":"2007-01-07T21:07:44Z","receivedAt":"2007-01-07T21:07:44Z","isPatch":false,"sender":{"key":"xavier.bestel@free.fr","avatar":null},"body":"Le dimanche 07 janvier 2007 à 21:40 +0100, Jan Engelhardt a écrit :\n> >On Sun, 7 Jan 2007 15:05:53 -0500\n> >Dave Jones wrote:\n> >\n> >> If there's something I should be doing when I commit that I'm not,\n> >> I'll be happy to change my scripts. My $LANG is set to en_US.UTF-8\n> >> which should DTRT to the best of my knowledge, but clearly, that isn't\n> >> the case.\n> \n> No, LC_CTYPE defines what charset you use. (I may be wrong, though.)\n\nIIRC LANG is a superset for all LC_* - i.e. if only LANG is defined, it\nsets all your locales, but you can individually set the charset, numeric\nformat, date format, etc.\n\n\tXav\n"},{"id":"31102","messageId":"1168221232.14763.80.camel@shinybook.infradead.org","threadId":"6270","inReplyTo":"45A17645.1030905@imap.cc","subject":"Re: OT: character encodings","fromName":"David Woodhouse","fromEmail":"dwmw2@infradead.org","sentAt":"2007-01-08T01:53:51Z","receivedAt":"2007-01-08T01:53:51Z","isPatch":false,"sender":{"key":"dwmw2@infradead.org","avatar":"https://gravatar.com/avatar/7afd4f07e0cf7d7e046ae2d23678296b37777c96488e6f3451e78a5514154ebd?d=mp&s=160"},"body":"On Sun, 2007-01-07 at 23:37 +0100, Tilman Schmidt wrote:\n> > That depends on your point of view. David's assertion was that git\n> > internally uses UTF-8.\n> \n> Well, I'm inclined to say he was wrong. Git internally is completely\n> oblivious to character encoding.\n\nSee the 'i18n.commitencoding' property, stored in the repository config\nand defaulting to UTF-8. Git is certainly capable of converting to its\ninternal storage encoding when you commit; if it doesn't do so by\ndefault then that would be a bug.\n\n-- \ndwmw2\n"}]}