From: mkoegler@auto.tuwien.ac.at (Martin Koegler)
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Ismail Dönmez" <ismail@pardus.org.tr>,
"Junio C Hamano" <gitster@pobox.com>,
"Alexandre Julliard" <julliard@winehq.org>,
"Benjamin Close" <Benjamin.Close@clearchain.com>,
git@vger.kernel.org
Subject: Re: Fix UTF Encoding issue
Date: Mon, 3 Dec 2007 17:38:56 +0100 [thread overview]
Message-ID: <20071203163856.GA24269@auto.tuwien.ac.at> (raw)
In-Reply-To: <m3prxougmx.fsf@roke.D-201>
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.
> >>
> >> I thought the standard catch ... throw idiom in Perl was to do the above
> >> like this:
> >>
> >> my $res;
> >> eval { $res = decode_utf8($str, Encode::FB_CROAK); };
> >> if ($@) {
> >> return decode($fallback_encoding, $str, Encode::FB_DEFAULT);
> >> }
> >> return $res;
> >
> > I think this is correct, but the current code in gitweb doesn't look correct
> > since it checks for $res and not $@.
>
> First version of the patch was created by Martin Koegler. I have
> participated in creating the version which is now in gitweb, but I
> have to say that I wrote it based on decode_utf8
> documentation... which doesn't necessarily agree with facts :-(
eval { $res = decode_utf8(...); }
if ($@)
return decode(...);
return $res
or
eval { $res = decode_utf8(...); }
if (defined $res)
return $res;
else
return decode(...);
show the same (wrong) behaviour on Debian sarge. They do not always
decode non UTF-8 characters correctly, eg.
#öäü does not work
#äöüä does work
On Debian etch, both versions are working.
> I'm all for the "throw idion" version. Ack.
mfg Martin Kögler
next prev parent reply other threads:[~2007-12-03 17:12 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 [this message]
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
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=20071203163856.GA24269@auto.tuwien.ac.at \
--to=mkoegler@auto.tuwien.ac.at \
--cc=Benjamin.Close@clearchain.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ismail@pardus.org.tr \
--cc=jnareb@gmail.com \
--cc=julliard@winehq.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).