Message-Id: <6.1.1.1.0.20040620135751.0e03fd50@no.incoming.mail>
Date: Sun, 20 Jun 2004 14:06:57 -0600
To: David Woodhouse <dwmw2@infradead.org>
From: Jeff Woods <Kazrak+kernel@cesmail.net>
Subject: Re: [PATCH] Stop printk printing non-printable chars
Cc: matthew-lkml@newtoncomputing.co.uk, linux-kernel@vger.kernel.org
In-Reply-To: <1087741064.28195.24.camel@localhost.localdomain>
References: <20040618205355.GA5286@newtoncomputing.co.uk>
 <1087643904.5494.7.camel@imladris.demon.co.uk>
 <20040619154907.GE5286@newtoncomputing.co.uk>
 <1087741064.28195.24.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1252
Lines: 28

A LKML meta-patch:

@On Sat, 2004-06-19 at 16:49 +0100, matthew-lkml@newtoncomputing.co.uk wrote:
  Please forgive me if I'm wrong on this, but I seem to remember reading
  something a while ago indicating that the kernel is and always will be
-internally English (i.e. debugging messages and the like) as there is no
+internally that subset of English representable in 7-bit ASCII
+(i.e. debugging messages and the like) as there is no
  need to bloat it with many different languages (that can be done in
  userspace). As printk is really just a log system, I personally don't
  see any way that it should ever print anything other than ASCII.

P.S.  At 6/20/2004 03:17 PM +0100, David Woodhouse wrote:
>It's very naïve of you to think that English means nothing but ASCII.
>Non-ASCII characters play a very important rôle even in English
>communication.

Thank you for illustrating the point that maximizing portability and 
compatibility favors simplicity.
--
Jeff Woods <kazrak+kernel@cesmail.net> 


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/