From: Yi EungJun <semtlenori@gmail.com>
To: git@vger.kernel.org
Cc: Yi EungJun <eungjun.yi@navercorp.com>, Jeff King <peff@peff.net>
Subject: [PATCH] diff-highlight: Fix broken multibyte string
Date: Tue, 31 Mar 2015 00:55:33 +0900 [thread overview]
Message-ID: <1427730933-26189-1-git-send-email-eungjun.yi@navercorp.com> (raw)
From: Yi EungJun <eungjun.yi@navercorp.com>
Highlighted string might be broken if the common subsequence is a proper subset
of a multibyte character. For example, if the old string is "진" and the new
string is "지", then we expect the diff is rendered as follows:
-진
+지
but actually it was rendered as follows:
-<EC><A7><84>
+<EC><A7><80>
This fixes the bug by splitting the string by multibyte characters.
---
contrib/diff-highlight/diff-highlight | 25 +++++++++++++++++++++++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/contrib/diff-highlight/diff-highlight b/contrib/diff-highlight/diff-highlight
index 08c88bb..2662c1a 100755
--- a/contrib/diff-highlight/diff-highlight
+++ b/contrib/diff-highlight/diff-highlight
@@ -2,6 +2,9 @@
use warnings FATAL => 'all';
use strict;
+use File::Basename;
+use File::Spec::Functions qw( catdir );
+use String::Multibyte;
# Highlight by reversing foreground and background. You could do
# other things like bold or underline if you prefer.
@@ -24,6 +27,8 @@ my @removed;
my @added;
my $in_hunk;
+my $mbcs = get_mbcs();
+
# Some scripts may not realize that SIGPIPE is being ignored when launching the
# pager--for instance scripts written in Python.
$SIG{PIPE} = 'DEFAULT';
@@ -164,8 +169,8 @@ sub highlight_pair {
sub split_line {
local $_ = shift;
- return map { /$COLOR/ ? $_ : (split //) }
- split /($COLOR*)/;
+ return map { /$COLOR/ ? $_ : ($mbcs ? $mbcs->strsplit('', $_) : split //) }
+ split /($COLOR)/;
}
sub highlight_line {
@@ -211,3 +216,19 @@ sub is_pair_interesting {
$suffix_a !~ /^$BORING*$/ ||
$suffix_b !~ /^$BORING*$/;
}
+
+# Returns an instance of String::Multibyte based on the charset defined by
+# i18n.commitencoding or UTF-8, or undef if String::Multibyte doesn't support
+# the charset.
+sub get_mbcs {
+ my $dir = catdir(dirname($INC{'String/Multibyte.pm'}), 'Multibyte');
+ opendir my $dh, $dir or return;
+ my @mbcs_charsets = grep s/[.]pm\z//, readdir $dh;
+ close $dh;
+ my $expected_charset = `git config i18n.commitencoding` || "UTF-8";
+ $expected_charset =~ s/-//g;
+ my @matches = grep {/^$expected_charset$/i} @mbcs_charsets;
+ my $charset = shift @matches;
+
+ return eval 'String::Multibyte->new($charset)';
+}
--
2.3.2.209.gd67f9d5.dirty
next reply other threads:[~2015-03-30 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 15:55 Yi EungJun [this message]
2015-03-30 22:16 ` [PATCH] diff-highlight: Fix broken multibyte string Jeff King
2015-04-03 0:49 ` Kyle J. McKay
2015-04-03 1:24 ` Jeff King
2015-04-03 1:59 ` Kyle J. McKay
2015-04-03 21:47 ` Jeff King
2015-04-03 2:19 ` Yi, EungJun
2015-04-03 22:08 ` Jeff King
2015-04-03 22:24 ` Kyle J. McKay
2015-04-04 14:10 ` Jeff King
2015-04-03 22:15 ` [PATCH v3] diff-highlight: do not split multibyte characters Kyle J. McKay
2015-04-04 14:09 ` Jeff King
2015-04-04 14:47 ` Yi, EungJun
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=1427730933-26189-1-git-send-email-eungjun.yi@navercorp.com \
--to=semtlenori@gmail.com \
--cc=eungjun.yi@navercorp.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).