Re: [PATCH] gitweb: Measure offsets against UTF-8 flagged string

hift_JIS It means I need to split each lines of git-blame output at the very beginning, then convert the first-half as UTF-8 and the second-half as Shift_JIS. Sincerely, -- Shin Kojima

Re: [PATCH] gitweb: Measure offsets against UTF-8 flagged string

| commitdiff | tree raw | patch | inline | side by side (parent: 79e26fe) change master author Shin Kojima <s...@kojima.org> Wed, 2 May 2018 10:55:01 + (19:55 +0900) committer Shin Kojima <s...@kojima.org> Wed, 2 May 2018 10:55:01 + (

[PATCH] gitweb: Measure offsets against UTF-8 flagged string

using your name here, but the following URL can not find "match" occurances while using `git-instaweb` on the git repository. http://127.0.0.1:1234/?p=.git=search=HEAD=grep=Nar%C4%99bski Signed-off-by: Shin Kojima <s...@kojima.org> --- gitweb/gitweb.perl | 2 +- 1 file chan

Re: [PATCH v2] gitweb: apply fallback encoding before highlight

> Oh, don't get me wrong. I do think what the patch does is very > sensible and have no intention of rejecting it. I'm sorry for making you worry, my poor English had caused some misunderstanding. I raised this Shift_JIS related problem (a.k.a "ダメ文字" in Japanese) might attract your interest

Re: [PATCH v2] gitweb: apply fallback encoding before highlight

On Tue, May 03, 2016 at 11:33:42AM -0700, Junio C Hamano wrote: > Shin Kojima <s...@kojima.org> writes: > > > Some multi-byte character encodings (such as Shift_JIS and GBK) have > > characters whose final bytes is an ASCII '\' (0x5c), and they > > will be disp

[PATCH v2] gitweb: apply fallback encoding before highlight

:135: cannot convert my $v = " This patch prepare git blob objects to be encoded into UTF-8 before highlighting in the manner of `to_utf8` subroutine. Signed-off-by: Shin Kojima <s...@kojima.org> --- Changes for v2: - Add Signed-off-by Thanks, Shin Kojima gitweb/gitweb.perl | 3 +

[PATCH] gitweb: apply fallback encoding before highlight

Some multi-byte character encodings (such as Shift_JIS and GBK) have characters whose final bytes is an ASCII '\' (0x5c), and they will be displayed as funny-characters even if $fallback_encoding is correct. This is because `highlight` command always expects UTF-8 encoded strings from STDIN.