Re: [PATCH] gitweb: use decode_utf8 directly
- From
- Ismail Dönmez <ismail@pardus.org.tr>
- Date
- May 1, 2007, 21:48 UTC
- Message-ID
- <200705020048.53853.ismail@pardus.org.tr>
- In-Reply-To
- <200705020044.47171.ismail@pardus.org.tr>
On Wednesday 02 May 2007 00:44:46 you wrote:
Show 24 quoted lines
> On Wednesday 02 May 2007 00:39:34 you wrote:
> > Ismail Dönmez <ismail@pardus.org.tr> writes:
> > > Ok found out the reason. decode() tries to decode data that is already
> > > UTF-8 and borks.
> > >
> > > This is from Encode.pm :
> > >
> > > sub decode_utf8($;$) {
> > > my ( $str, $check ) = @_;
> > > return $str if is_utf8($str); <--- Checks if the $str is already
> > > UTF-8 if ($check) {
> > > return decode( "utf8", $str, $check ); <--- Else do what gitweb
> > > does [...]
> > >
> > > So my patch is indeed correct.
> >
> > Ok, I think that makes it an improvement from the current code,
> > so I'd apply.
> >
> > But at the same time I wonder why should the callers be feeding
> > an already decoded string to to_utf8(). It might be that some
> > callers needs fixing.
>
> FWIW it was passing my name "İsmail Dönmez" based on user info I guess.I guess its line 1116:
if (check_export_ok("$projectroot/$path")) {
my $pr = {
path => $path,
owner => to_utf8($owner), <---- Here
};My system is configured for UTF-8 so $owner will be UTF-8 but in some systems it might not be so I don't think there is anything to fix here.
Regards, ismail