From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261834AbUBWGKW (ORCPT ); Mon, 23 Feb 2004 01:10:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261835AbUBWGKW (ORCPT ); Mon, 23 Feb 2004 01:10:22 -0500 Received: from [212.28.208.94] ([212.28.208.94]:46346 "HELO dewire.com") by vger.kernel.org with SMTP id S261834AbUBWGKT (ORCPT ); Mon, 23 Feb 2004 01:10:19 -0500 From: Robin Rosenberg To: "Norman Diamond" Subject: Re: UTF-8 filenames Date: Mon, 23 Feb 2004 07:10:12 +0100 User-Agent: KMail/1.6.1 Cc: "Jamie Lokier" , References: <18de01c3f93f$dc6d91d0$b5ee4ca5@DIAMONDLX60> <20040222204541.GA26793@mail.shareable.org> <008d01c3f99c$9033e3c0$34ee4ca5@DIAMONDLX60> In-Reply-To: <008d01c3f99c$9033e3c0$34ee4ca5@DIAMONDLX60> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200402230710.12549.robin.rosenberg.lists@dewire.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Monday 23 February 2004 00.35, Norman Diamond wrote: > Of course. Perhaps my use of reductio al absurdum was unclear. I was > trying to show that UTF-8, despite its sanity, is not universally agreeable. > The actual reason is because it came late to the scene (around 20 years ago) > and it is not backwards compatible. Even later, it's from 1992 I believe and a standard even later. That is long after we went from national variants of ASCII to ISO-Latin-1. If I recall it correctly it was the years around 1987 that we started having multiple encodings fo text. -- robin