git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Close <Benjamin.Close@clearchain.com>
To: Ismail D??nmez <ismail@pardus.org.tr>
Cc: Jakub Narebski <jnareb@gmail.com>,
	Martin Koegler <mkoegler@auto.tuwien.ac.at>,
	Junio C Hamano <gitster@pobox.com>,
	Alexandre Julliard <julliard@winehq.org>,
	git@vger.kernel.org,
	Perl Unicode Mailing List <perl-unicode@perl.org>,
	Dan Kogai <dankogai@dan.co.jp>
Subject: Re: Fix UTF Encoding issue
Date: Tue, 4 Dec 2007 09:34:34 +1030	[thread overview]
Message-ID: <20071203230432.GA1337@wolf.clearchain.com> (raw)
In-Reply-To: <200712040020.26773.ismail@pardus.org.tr>

On Tue, Dec 04, 2007 at 12:20:26AM +0200, Ismail D??nmez wrote:
> Monday 03 December 2007 Tarihinde 23:46:24 yazm????t??:
> > Jakub Narebski wrote:
> > > On Mon, 3 Dec 2007, Martin Koegler wrote:
> > >> On Mon, Dec 03, 2007 at 04:06:48AM -0800, Jakub Narebski wrote:
> > >>> Ismail D??nmez <ismail@pardus.org.tr> writes:
> > >>>> Monday 03 December 2007 Tarihinde 12:14:43 yazm??t?:
> > >>>>> Benjamin Close <Benjamin.Close@clearchain.com> writes:
> > >>>>>> -	eval { $res = decode_utf8($str, Encode::FB_CROAK); };
> > >>>>>> -	if (defined $res) {
> > >>>>>> -		return $res;
> > >>>>>> -	} else {
> > >>>>>> -		return decode($fallback_encoding, $str, Encode::FB_DEFAULT);
> > >>>>>> -	}
> > >>>>>> +	eval { return ($res = decode_utf8($str, Encode::FB_CROAK)); };
> > >>>>>> +	return decode($fallback_encoding, $str, Encode::FB_DEFAULT);
> > >>>>>>  }
> > >>
> > >> This version is broken on Debian sarge and etch. Feeding a UTF-8 and a
> > >> latin1 encoding of the same character sequence yields to different
> > >> results.
> >
> > For the record, this was on a debian sid machine.
> >
> > #perl --version
> > This is perl, v5.8.8 built for x86_64-linux-gnu-thread-multi
> >
> > and the result of not using the original patch was:
> >
> > <h1>Software error:</h1>
> > <pre>Cannot decode string with wide characters at
> > /usr/lib/perl/5.8/Encode.pm line 166. </pre>
> 
> Can you try the attached patch?

I confirm that the patch corrects the problem.

Without it I get the Cannot decode string error. With it gitweb displays
correctly.

Cheers,
	Benjamin

  reply	other threads:[~2007-12-03 23:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 10:02 Fix UTF Encoding issue Benjamin Close
2007-12-03 10:14 ` Junio C Hamano
2007-12-03 11:32   ` Ismail Dönmez
2007-12-03 12:06     ` Jakub Narebski
2007-12-03 16:38       ` Martin Koegler
2007-12-03 17:02         ` Jakub Narebski
2007-12-03 21:46           ` Benjamin Close
2007-12-03 22:20             ` Ismail Dönmez
2007-12-03 23:04               ` Benjamin Close [this message]
2007-12-03 23:37                 ` Jakub Narebski
2007-12-04  4:12                   ` Ismail Dönmez
2007-12-04  8:04             ` Martin Koegler
2007-12-04  8:12               ` Ismail Dönmez
2007-12-04  8:20                 ` Martin Koegler
2007-12-04  7:50           ` Martin Koegler
2007-12-04  7:55             ` Ismail Dönmez
2007-12-04  8:16               ` Martin Koegler
2007-12-04  8:28                 ` Ismail Dönmez
2007-12-04  8:33                   ` Ismail Dönmez
2007-12-04  8:44                     ` Martin Koegler
2007-12-04  8:47                       ` Ismail Dönmez
2007-12-04  8:55                         ` Ismail Dönmez
2007-12-04  9:07                           ` Jakub Narebski
2007-12-04 10:11                           ` Wincent Colaiuta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071203230432.GA1337@wolf.clearchain.com \
    --to=benjamin.close@clearchain.com \
    --cc=dankogai@dan.co.jp \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ismail@pardus.org.tr \
    --cc=jnareb@gmail.com \
    --cc=julliard@winehq.org \
    --cc=mkoegler@auto.tuwien.ac.at \
    --cc=perl-unicode@perl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).