From: しらいしななこ <nanako3@bluebottle.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Tsugikazu Shibata <tshibata@ab.jp.nec.com>, git@vger.kernel.org
Subject: Re: [PATCH 3/2] attribute "coding": specify blob encoding
Date: Fri, 04 Jan 2008 06:23:25 +0900 [thread overview]
Message-ID: <200801032128.m03LSIn2022902@mi0.bluebottle.com> (raw)
In-Reply-To: <7vsl1gy2si.fsf@gitster.siamese.dyndns.org>
Quoting Junio C Hamano <gitster@pobox.com>:
> This teaches "diff hunk header" function about custom character
> encoding per path via gitattributes(5) so that it can sensibly
> chomp a line without truncating a character in the middle.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>
> * This is not intended for serious inclusion, but was done more
> as a demonstration of the concept, hence [3/2].
Why not? It looks a useful addition for us Japanese people.
> +static struct {
> + const char *coding;
> + sane_truncate_fn fn;
> +} builtin_truncate_fn[] = {
> + { "euc-jp", truncate_euc_jp },
> + { "utf-8", NULL },
> +};
Can you also do JIS and Shift JIS? I ask because many of my old notes are in Shift JIS and I think it is the same for many other people.
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
----------------------------------------------------------------------
Get a free email account with anti spam protection.
http://www.bluebottle.com/tag/2
next prev parent reply other threads:[~2008-01-03 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 23:20 [RFC/PATCH] fix "git diff" to create wrong UTF-8 text Tsugikazu Shibata
2008-01-02 5:26 ` Junio C Hamano
2008-01-02 9:49 ` [PATCH 1/2] utf8_width(): allow non NUL-terminated input Junio C Hamano
2008-01-02 9:50 ` [PATCH 2/2] diff: do not chomp hunk-header in the middle of a character Junio C Hamano
2008-01-02 9:50 ` [PATCH 3/2] attribute "coding": specify blob encoding Junio C Hamano
2008-01-03 21:23 ` しらいしななこ [this message]
2008-01-03 21:54 ` Junio C Hamano
2008-01-04 16:16 ` Tsugikazu Shibata
2008-01-04 20:53 ` Junio C Hamano
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=200801032128.m03LSIn2022902@mi0.bluebottle.com \
--to=nanako3@bluebottle.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tshibata@ab.jp.nec.com \
/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).