Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262706AbUCEVDQ (ORCPT ); Fri, 5 Mar 2004 16:03:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262704AbUCEVDQ (ORCPT ); Fri, 5 Mar 2004 16:03:16 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:30736 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id S262713AbUCEVC7 (ORCPT ); Fri, 5 Mar 2004 16:02:59 -0500 Message-ID: <4048EADF.1060601@zytor.com> Date: Fri, 05 Mar 2004 13:02:23 -0800 From: "H. Peter Anvin" Organization: Zytor Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031030 X-Accept-Language: en, sv MIME-Version: 1.0 To: Mike Fedyk CC: linux-kernel@vger.kernel.org Subject: Re: [PATCH] UTF-8ifying the kernel source References: <20040304100503.GA13970@havoc.gtf.org> <4048EA87.1080304@matchmail.com> In-Reply-To: <4048EA87.1080304@matchmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 591 Lines: 20 Mike Fedyk wrote: >> >> OK, this is definitely a good reason to go to UTF-8 across the board. > > So when is "less" going to support utf8? Right now, it just shows > escape codes... :( > Why don't you ask the "less" maintainer about that? Right now, "less" seems to insist on showing ampersands for *any* non-ASCII character for me... -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/