[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: filename and normalization (was gcc identifiers)

To: linux-utf8@xxxxxxxxxxxx
Subject: Re: filename and normalization (was gcc identifiers)
From: Jungshik Shin <jshin@xxxxxxxxxxx>
Date: Wed, 4 Dec 2002 19:13:42 -0500 (EST)
In-reply-to: <asm4nf$1cn$1@cesium.transmeta.com>
List-archive: <http://mail.nl.linux.org/linux-utf8/>
List-help: <mailto:listar@nl.linux.org?Subject=help>
List-owner: <mailto:riel@nl.linux.org>
List-post: <mailto:linux-utf8@nl.linux.org>
List-software: Listar version 1.0.0
List-subscribe: <mailto:linux-utf8-request@nl.linux.org?Subject=subscribe>
List-unsubscribe: <mailto:linux-utf8-request@nl.linux.org?Subject=unsubscribe>
Original-recipient: rfc822;linux-utf8-archive@nl.linux.org
Reply-to: linux-utf8@xxxxxxxxxxxx
Sender: linux-utf8-bounce@xxxxxxxxxxxx

On 4 Dec 2002, H. Peter Anvin wrote:

> By author:    Jungshik Shin <jshin@xxxxxxxxxxx>

> >  Whether you're convinced or not, it's not only in Unicode but also
> > inscribed in ISO 10646.

> Standards change.  "Forever" is a very long time.

  Where did I use the word? 'Inscribed'? Standards change, but they
also got obsolete by a new standard. ISO 10646 someday may be replaced by MGSO
(Milkyway Galactic Organization for Standardization) 2xqwew12343.

  Jungshik Shin

--
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/

References:
- Re: filename and normalization (was gcc identifiers)
  - From: H. Peter Anvin

Prev by Date: Re: RE: filename and normalization (was gcc identifiers)
Next by Date: Re: RE: filename and normalization (was gcc identifiers)
Previous by thread: Re: filename and normalization (was gcc identifiers)
Next by thread: Re: filename and normalization (was gcc identifiers)
Index(es):
- Date
- Thread