From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: [PATCH 0/2] Controversial blob munging series
Date: Sat, 21 Apr 2007 23:08:22 -0700 [thread overview]
Message-ID: <11772221041630-git-send-email-junkio@cox.net> (raw)
This is on top of 'next' I'll push out after I am done with
v1.5.1.2 I am preparing today.
[1/2] Add 'filter' attribute and external filter driver definition.
[2/2] Add 'ident' conversion.
I'll park them near the tip of 'pu', but consider they are
primarily for interested people to experiment with.
I suspect this might have helped me (and other Asians) a year
ago. I did not manage to configure my Emacs to work well with
utf-8 encoded Japanese text, and had some difficulties in
maintaining documentation for git-lost-found (it has my name
spelled in Japanese).
I could have had:
(in .git/info/attributes)
Documentation/git-lost-found.txt filter=eucjp-n-utf8
(in config)
[filter "eucjp-n-utf8"]
clean = nkf -E -w
smudge = nkf -W -e
so that checked-out copy is after "nkf -W -e" (filter to EUC-JP,
treating the input as UTF-8) to allow my Emacs work with EUC-JP.
Check-in will be done after "nkf -E -w" (filter to UTF-8,
treating the input as EUC-JP), which would keep the "official"
version in the repository as UTF-8. The best part of this is
that the configurations above are both private to me, and people
do not even have to know that I am suffering from the inability
to use UTF-8 in my editor.
These days I configured my Emacs to deal with UTF-8 much better
than when I added git-lost-found manual page, so I would not
need the above hack, though.
I also suspect a "fun but probably not very useful in practice"
application would be to have "indent" as the clean filter while
leaving "smudge" filter empty.
next reply other threads:[~2007-04-22 6:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 6:08 Junio C Hamano [this message]
2007-04-22 6:08 ` [PATCH 1/2] Add 'filter' attribute and external filter driver definition Junio C Hamano
2007-04-22 6:08 ` [PATCH 2/2] Add 'ident' conversion Junio C Hamano
2007-04-23 13:50 ` [PATCH 0/2] Controversial blob munging series Johannes Schindelin
2007-04-23 16:29 ` Julian Phillips
2007-04-23 16:54 ` Johannes Schindelin
2007-04-23 17:13 ` Junio C Hamano
2007-04-23 17:35 ` Johannes Schindelin
2007-04-23 18:42 ` Junio C Hamano
2007-04-23 18:49 ` Johannes Schindelin
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=11772221041630-git-send-email-junkio@cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.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).