From: Willy Tarreau <w@1wt.eu>
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [2.6 patch] UTF-8 fixes in comments
Date: Tue, 29 Apr 2008 01:05:25 +0200 [thread overview]
Message-ID: <20080428230524.GK8474@1wt.eu> (raw)
In-Reply-To: <20080428154023.GU2813@cs181133002.pp.htv.fi>
On Mon, Apr 28, 2008 at 06:40:23PM +0300, Adrian Bunk wrote:
> This patch converts some non-UTF-8 encoded text in comments to UTF-8.
Is this really needed Adrian ? I mean, everyone reads iso-8859-1, not
everyone reads UTF-8. Now I get random crappy chars which cripple my
xterms when reading such comments, and I have to do a full-reset once
I've read them. It's not as if it was *that* important, and to be
honnest, if you had not sent this patch, I would not even have known
that non-ASCII characters were here. However, it will quickly get
annoying if a recursive grep returns those pesky codes on non-compatible
consoles...
Quite frankly, it does not bring anything beyond trouble. I'm not adding
a NAK here because I find this rude, but I don't like the orientation
we're taking with the sources. We should not force people to install
version X or Y of a particular system just to read sources.
In fact, I would have better converted accentuated chars to their ASCII
equivalent to be more friendly with people who only read 7-bit.
Regards,
Willy
next prev parent reply other threads:[~2008-04-28 23:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 15:40 [2.6 patch] UTF-8 fixes in comments Adrian Bunk
2008-04-28 23:05 ` Willy Tarreau [this message]
2008-04-29 1:29 ` H. Peter Anvin
2008-04-29 5:06 ` Willy Tarreau
2008-04-29 6:04 ` H. Peter Anvin
2008-04-29 7:29 ` Adrian Bunk
2008-04-29 8:14 ` Willy Tarreau
2008-04-29 9:06 ` Helge Hafting
2008-04-29 9:33 ` Alan Cox
2008-04-29 10:09 ` Willy Tarreau
2008-04-29 10:10 ` Alan Cox
2008-04-29 10:33 ` Willy Tarreau
2008-04-29 10:34 ` Alan Cox
2008-04-29 22:12 ` Willy Tarreau
2008-04-29 22:15 ` Alan Cox
2008-04-29 23:05 ` Willy Tarreau
2008-05-01 20:18 ` H. Peter Anvin
2008-05-01 9:46 ` Alexander E. Patrakov
2008-04-29 19:33 ` H. Peter Anvin
2008-04-29 10:42 ` Adrian Bunk
2008-04-29 11:06 ` Willy Tarreau
2008-04-29 11:27 ` Adrian Bunk
2008-04-29 11:32 ` Adrian Bunk
2008-04-29 20:18 ` Jeremy Fitzhardinge
2008-04-30 9:15 ` Helge Hafting
2008-04-30 19:22 ` Adrian Bunk
2008-04-30 19:42 ` H. Peter Anvin
2008-04-29 9:43 ` Adrian Bunk
2008-04-29 19:31 ` H. Peter Anvin
2008-04-29 20:05 ` Willy Tarreau
2008-04-29 20:09 ` H. Peter Anvin
2008-05-09 12:48 ` David Kågedal
2008-04-29 9:01 ` Alan Cox
2008-04-29 9:19 ` Jan Engelhardt
2008-04-29 9:34 ` Willy Tarreau
2008-04-29 9:41 ` Alan Cox
2008-04-29 12:18 ` KOSAKI Motohiro
-- strict thread matches above, loose matches on Subject: below --
2008-04-30 0:08 Samuel Thibault
2008-04-30 3:38 ` Chris Adams
2008-04-30 9:38 ` Samuel Thibault
2008-04-30 19:45 ` Willy Tarreau
2008-04-30 19:49 ` Willy Tarreau
2008-05-03 23:50 ` Samuel Thibault
2008-05-04 8:55 ` Willy Tarreau
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=20080428230524.GK8474@1wt.eu \
--to=w@1wt.eu \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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