Re: [PATCH 2/n] gitweb: Use '&iquot;' instead of '?' in esc_path

From: Petr Baudis <pasky@suse.cz>
Date: Nov 4, 2006, 10:31 UTC
Message-ID: <20061104103156.GS20017@pasky.or.cz>
In-Reply-To: <7vr6wk3wpo.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Sat, Nov 04, 2006 at 01:02:43AM CET, I got a letter where Junio C Hamano <junkio@cox.net> said that...

Show 19 quoted lines

> 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.

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