From: David Brown <mtd@davidb.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: "Jörn Engel" <joern@logfs.org>,
linux-mtd@lists.infradead.org,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Claim maintainership for block2mtd and update email addresses
Date: Tue, 8 Jan 2008 16:19:48 -0800 [thread overview]
Message-ID: <20080109001948.GA16644@old.davidb.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0801090016570.10908@axis700.grange>
On Wed, Jan 09, 2008 at 12:23:24AM +0100, Guennadi Liakhovetski wrote:
>On Tue, 8 Jan 2008, Jörn Engel wrote:
>
>> I'm happy if people spend effort and make unicode work. Until then I'll
>> semi-officially change my name to "Joern" and keep collecting unusual
>> specimens.
>
>Just wondering - nothing personal at all. What's the official plan for
>this - do we want (when utf8 works) to use utf8 codes for symbols only for
>languages mostly based on ASCII, like iso-8859-15, or for all?
UTF-8 already works fine in git. There is some support in recent versions
to allow commit messages and users to be specified in other encodings.
I think the issue here is with mailers modifying the encoding of data in
message files.
My reply header should be to Jörn, with a proper 'o' with two dots over it.
By default, my mailer wants to encode the message in iso-8859-1. If I add
a single unicode character, say '‣', then the whole message will get
encoded in UTF-8.
UTF-8 has the advantage of supporting nearly all character sets. The extra
space needed isn't really an issue for usernames or for comment messages.
Dave
prev parent reply other threads:[~2008-01-09 0:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-06 13:56 [PATCH] Claim maintainership for block2mtd and update email addresses Jörn Engel
2008-01-07 23:23 ` Andrew Morton
2008-01-08 1:06 ` Jörn Engel
2008-01-08 23:23 ` Guennadi Liakhovetski
2008-01-09 0:19 ` David Brown
2008-01-09 0:19 ` David Brown [this message]
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=20080109001948.GA16644@old.davidb.org \
--to=mtd@davidb.org \
--cc=akpm@linux-foundation.org \
--cc=g.liakhovetski@gmx.de \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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