From: Pete Zaitcev <zaitcev@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>,
David Woodhouse <dwmw2@infradead.org>,
Anton Vorontsov <cbou@mail.ru>, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, kernel-discuss@handhelds.org,
Andrew Morton <akpm@osdl.org>,
zaitcev@redhat.com
Subject: Re: [PATCH 8/8] One Laptop Per Child power/battery driver
Date: Sat, 12 May 2007 10:03:21 -0700 [thread overview]
Message-ID: <20070512100321.c54f3dbe.zaitcev@redhat.com> (raw)
In-Reply-To: <20070507222311.4589fc8a@the-village.bc.nu>
On Mon, 7 May 2007 22:23:11 +0100, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> We had this discussion before. Kernel sources should use utf-8 for
> comments where neccessary. Many names cannot be correctly represented in
> US ascii, and mangling them is just plain rude.
I have to disagree here. It is using the native alphabet for the name
which is very rude, because non-native hackers cannot read it. This is
true on systems which can display the name correctly, which may come
as a surprise to you. I used to receive e-mails from Mr. मयंक जैन at work.
Do you know who the heck he is? I sure didn't. Beautiful gliphs though!
One peculiar thing I have observed is how all this "UTF-8 in names"
nonsense is being pushed by western Europeans. Why? That's because
their umlauts are grandfathered in, and because English speakers _can_
read their names approximately, simply by ignoring all the strokes
above the letter (or, in Norwegians and Polaks cases, going through
the letter). So do not try to pretend that "correctness" has anything
to do with your demands. Nowhere the ethnocentrism comes through clearer
than in demanding that everyone in the world were able to read names
spelled as convenient for you and not for them.
-- Pete
next prev parent reply other threads:[~2007-05-12 17:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 21:33 [PATCH 8/8] One Laptop Per Child power/battery driver Anton Vorontsov
2007-05-07 14:04 ` Pavel Machek
2007-05-07 14:12 ` Anton Vorontsov
2007-05-07 15:10 ` David Woodhouse
2007-05-07 19:49 ` Pavel Machek
2007-05-07 19:51 ` David Woodhouse
2007-05-07 20:38 ` Pavel Machek
2007-05-07 21:43 ` Alan Cox
2007-05-08 5:39 ` Willy Tarreau
2007-05-07 20:04 ` Satyam Sharma
2007-05-08 17:45 ` Maciej W. Rozycki
2007-05-08 17:52 ` Stephen Clark
2007-05-08 17:52 ` David Woodhouse
2007-05-09 14:23 ` Maciej W. Rozycki
2007-05-09 14:46 ` David Woodhouse
2007-05-09 20:33 ` Pavel Machek
2007-05-11 12:43 ` David Woodhouse
2007-05-11 13:21 ` Pavel Machek
2007-05-12 21:11 ` Adrian Bunk
2007-05-12 23:20 ` Pavel Machek
2007-05-13 4:45 ` David Woodhouse
2007-05-13 16:40 ` Krzysztof Halasa
2007-05-11 13:21 ` Alan Cox
2007-05-11 13:45 ` Satyam Sharma
2007-05-12 16:35 ` Pete Zaitcev
2007-05-13 5:39 ` David Woodhouse
2007-05-13 6:03 ` Pete Zaitcev
2007-05-13 6:21 ` David Woodhouse
2007-05-07 21:23 ` Alan Cox
2007-05-07 21:55 ` Dmitry Torokhov
2007-05-07 22:02 ` Alan Cox
2007-05-08 12:18 ` Stephen Clark
2007-05-12 17:03 ` Pete Zaitcev [this message]
2007-05-12 19:27 ` Alan Cox
2007-05-12 19:31 ` Russell King
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=20070512100321.c54f3dbe.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cbou@mail.ru \
--cc=dwmw2@infradead.org \
--cc=gregkh@suse.de \
--cc=kernel-discuss@handhelds.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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