Dear diary, on Sat, Nov 04, 2006 at 01:02:43AM CET, I got a letter where Junio C Hamano <junkio@xxxxxxx> said that... > Petr Baudis <pasky@xxxxxxx> writes: > > > Dear diary, on Fri, Nov 03, 2006 at 11:44:48PM CET, I got a letter > > where Junio C Hamano <junkio@xxxxxxx> said that... > >> Jakub Narebski <jnareb@xxxxxxxxx> 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. Actually Jakub is right, &#number; is always a Unicode codepoint, regardless of document encoding. Anything but <blink>! ;-) -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html