{"thread":{"id":"2488","subject":"Re: GIT character codecs","startedAt":"2005-11-13T20:52:40Z","lastAt":"2005-11-13T20:52:40Z","messageCount":1,"participants":["Marco Costalba"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"11743","messageId":"20051113205241.70221.qmail@web26301.mail.ukl.yahoo.com","threadId":"2488","inReplyTo":null,"subject":"Re: GIT character codecs","fromName":"Marco Costalba","fromEmail":"mcostalba@yahoo.it","sentAt":"2005-11-13T20:52:40Z","receivedAt":"2005-11-13T20:52:40Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"Linus Torvalds wrote:\n\n>\n>On Sun, 13 Nov 2005, Marco Costalba wrote:\n>\n>>If encoding is a per-blob _and_ per-log message property a real solution, although cumbersone,\n>>could be that git stores encoding togheter with the blob and the commits.\n>\n>\n>We'd be much better off with just saying \"we encourage people to use \n>utf-8, but if you don't, just set your locale to make things show up \n>properly\".\n>\n>utf-8 is clearly the future, and if we make git internally aware of \n>locales, that's just going to complicate things. And usually for no good \n>reason, since users don't really care that much.\n>\n\nYes, I agree with you and Junio, a workaround like let the user to choose the code page \nin the viewer is more then enough.\n\nAnd also in this case, a choice between the local codec and utf-8 should take almost \nall cases.\n\nBecause of this, I added a text codec selector in qgit, reachable from settings menu.\n\nThere is a new release, qgit-0.97.2, with this new feature and some good\nannotate fixes.\n\nFor the people interested the page with all the links is:\n http://digilander.libero.it/mcostalba/\n\n  Marco\n\nP.S: Now I can finally see Junio japanese name ;-)\n\n\n\n\t\n\t\t\n__________________________________ \nYahoo! Mail - PC Magazine Editors' Choice 2005 \nhttp://mail.yahoo.com\n"}]}