public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Woodhouse <dwmw2@infradead.org>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	Satyam Sharma <satyam.sharma@gmail.com>,
	Anton Vorontsov <cbou@mail.ru>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, kernel-discuss@handhelds.org,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 8/8] One Laptop Per Child power/battery driver
Date: Sat, 12 May 2007 23:11:44 +0200	[thread overview]
Message-ID: <20070512211144.GO7984@stusta.de> (raw)
In-Reply-To: <20070511132116.GH4052@ucw.cz>

On Fri, May 11, 2007 at 01:21:16PM +0000, Pavel Machek wrote:
> Hi!
> 
> > > > > And how about serial terminals?
> > > > 
> > > > It works fine over serial terminals. Why wouldn't it?
> > > 
> > > He probably means serial terminals... like physical vt100. I used to
> > > have one (vt302 compatible or something).  Most emulators still
> > > emulate vt100, and yes, vt100 predates utf-8. 
> > 
> > I have a serial terminal which can only do lower case (well, actually
> > capitals but it's all mapped to lower case since that's more useful).
> > 
> > When I write code on it, I can't do capital letters. But do I try to
> > _force_ you to use only capitals because of my limited terminal?
> 
> If I wrote int j, J; in my code, you'd have valid case wanting me to
> fix it. And I simply want you to fix useless uses of utf-8. And evil
> uses utf8, like int voltage; /* ??V */. I do not know what is so hard
> to understand.
> 
> You are intentionally making code hard to read. Stop trying to merge
> that crap.

It was °C, and that's IMHO better readable than some kind of "degrees C".

Only using 7bit ASCII might have been a good advice in the last 
millenium. But in the current millenium, most environments handle UTF-8 
just fine.

And we are only talking about documentation and comments - IOW, things 
not visible for someone running a kernel. Code (including printk's) must 
stay 7bit ASCII.

In the worst case, if you managed to find a not UTF-8 capable 
environment for viewing the kernel sources, the few characters that are 
not 7bit ASCII are displayed incorrectly, and you'll have to guess which 
character someone might place in front of a "C" describing something 
named wBAT_TEMP (you will likely guess it correctly).

And it's nothing new, comments containing non 7bit ASCII characters are 
already present in 10 year old kernels (often, but not limited to,
developer's names).

> 							Pavel

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-05-12 21: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 [this message]
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
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=20070512211144.GO7984@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=cbou@mail.ru \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@suse.de \
    --cc=kernel-discuss@handhelds.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=pavel@ucw.cz \
    --cc=satyam.sharma@gmail.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