Petr Baudis <pasky@suse.cz> writes: > Dear diary, on Fri, Nov 03, 2006 at 11:44:48PM CET, I got a letter > where Junio C Hamano <junkio@cox.net> said that... >> Jakub Narebski <jnareb@gmail.com> writes: >> > Which solution do you think it's best? >> >> Sorry, if it was not clear in my message, I wanted to say that I >> kinda liked those "control pictures" in U+2400 range. > > In principle, right now it should be pretty easy for a project that for > some reason does not use UTF-8 in commits etc. to adjust gitweb to work > properly, right? Just change the encoding in HTTP headers and you're > done, I think. > > Is it worth trying to preserve that flexibility? Absolutely, and I got your point. Maybe <blink>\011</blink> would be more portable and appropriate. Also munging [:cntrl:] would break iso-2022 encoding if it munges ESC, but the function under discussion was only for paths and I think no sane platform would use iso-2022 for filenames. Each repository has commit charset/encoding configuration item if I am not mistaken, so it is probably a sane thing to do to convert commit messages from that uniformly to utf-8, I think. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Sat Nov 04 11:03:21 2006
This archive was generated by hypermail 2.1.8 : 2006-11-04 11:04:23 EST