To: linux-kernel@vger.kernel.org
From: hpa@zytor.com (H. Peter Anvin)
Subject: Re: [PATCH] UTF-8ifying the kernel source
Date: Tue, 9 Mar 2004 00:30:05 +0000 (UTC)
Organization: Transmeta Corporation, Santa Clara CA
Message-ID: <c2j36d$2ej$1@terminus.zytor.com>
References: <20040304100503.GA13970@havoc.gtf.org> <20040305232425.GA6239@havoc.gtf.org> <c2b2o0$cbp$1@terminus.zytor.com> <1078571331.963.3.camel@bip.parateam.prv>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit
NNTP-Posting-Date: Tue, 9 Mar 2004 00:30:05 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1112
Lines: 28

Followup to:  <1078571331.963.3.camel@bip.parateam.prv>
By author:    Xavier Bestel <xavier.bestel@free.fr>
In newsgroup: linux.dev.kernel
>
> Le sam 06/03/2004 ? 00:33, H. Peter Anvin a ?crit :
> > Followup to:  <20040305232425.GA6239@havoc.gtf.org>
> > By author:    David Eger <eger@havoc.gtf.org>
> > In newsgroup: linux.dev.kernel
> > 
> > > The third patch concerns 8-bit characters embedded in C strings.
> > > These are almost always output to devfs or proc.  The characters used are
> > > the degrees symbol (for ppc temp. sensors) and mu (for micro-seconds).
> >
> > I would highly vote for making those UTF-8 unless it breaks protocol.
> 
> ISO-8859-1 characters are mostly the same in UTF-8.
> 

Unicode, yes.  UTF-8, no.  The ISO-8859-1 character "?" (0xC5) does,
indeed correspond to Unicode character U+00C5, but it's encoded 0xC3
0x85 in UTF-8.

	-hpa
-
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/