Re: console translator set without encoding
- To: Danilo Segan <dsegan@gmx.net>
- Cc: Marcus Brinkmann <marcus.brinkmann@ruhr-uni-bochum.de>, Thomas Bushnell BSG <tb@becket.net>, Patrick Strasser <patrick.strasser@tugraz.at>, debian-hurd@lists.debian.org, bug-hurd@gnu.org, Ognyan Kulev <ogi@fmi.uni-sofia.bg>
- Subject: Re: console translator set without encoding
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- Date: Sun, 23 Jan 2005 14:04:34 +0100
- Message-id: <20050123130434.GA3112@bouh.labri.fr>
- Mail-followup-to: Danilo Segan <dsegan@gmx.net>, Marcus Brinkmann <marcus.brinkmann@ruhr-uni-bochum.de>, Thomas Bushnell BSG <tb@becket.net>, Patrick Strasser <patrick.strasser@tugraz.at>, debian-hurd@lists.debian.org, bug-hurd@gnu.org, Ognyan Kulev <ogi@fmi.uni-sofia.bg>
- In-reply-to: <878y6lkm8m.fsf@avet.kvota.net>
- References: <413D7137.8080605@tugraz.at> <413D8372.1080508@fmi.uni-sofia.bg> <413D8FCA.601@tugraz.at> <87mzv2qisw.wl@ulysses.g10code.de> <877jm6kw4e.fsf@becket.becket.net> <87k6q6qhby.wl@ulysses.g10code.de> <87pszyjg1q.fsf@becket.becket.net> <87is5qqcx9.wl@ulysses.g10code.de> <878y6lkm8m.fsf@avet.kvota.net>
Danilo Segan, le dim 23 jan 2005 01:44:25 +0100, a dit :
> Using normalized forms would then simply be up to the writer and
> reader, just as it is up to the writer and reader today to check for
> all of "Music", "music", "mUSIC" and similar when a user actually
> searches for his music directory.
No !
Normalized form take care of glyphs that really can be coded several
different ways: for instance, latin e with acute accent may be directly
coded as 'é', but in unicode, may also be coded as 'e' followed by the
combining acute accent. These are really *two* ways to code *exactly*
the same thing (on the displaying point of view: an 'e' with an acute
accent above it). Hence normalization is needed to match both.
Regards,
Samuel
Reply to: