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

Re: filename encoding (was: ISO-2022)

To: linux-utf8@xxxxxxxxxxxx
Subject: Re: filename encoding (was: ISO-2022)
From: David Starner <dstarner98@xxxxxxxxxxxxx>
Date: Thu, 1 Feb 2001 21:12:18 -0600
In-reply-to: <87d7d193yo.wl@surfchem0.riken.go.jp>; from tkubota@riken.go.jp on Fri, Feb 02, 2001 at 12:08:31PM +0900
References: <87k87ajqzd.wl@surfchem0.riken.go.jp> <Pine.LNX.4.21.0102011758320.9748-100000@zodiac.mimuw.edu.pl> <87d7d193yo.wl@surfchem0.riken.go.jp>
Reply-to: linux-utf8@xxxxxxxxxxxx
Sender: owner-linux-utf8@xxxxxxxxxxxx
User-agent: Mutt/1.3.12i

On Fri, Feb 02, 2001 at 12:08:31PM +0900, Tomohiro KUBOTA wrote:
> Passing locale-encoding to libc/kernel without telling the locale
> causes a problem.  In some encodings, a code of '/' may appear in
> the 2nd byte of multibyte character or in a certain shift state.

Those encodings aren't used in Unix filesystems. That's why UTF-8
was created.

-- 
David Starner - dstarner98@xxxxxxxxxxxxx
Pointless website: http://dvdeug.dhis.org
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/

References:
- Re: filename encoding (was: ISO-2022)
  - From: Tomohiro KUBOTA
- Re: filename encoding (was: ISO-2022)
  - From: Marcin 'Qrczak' Kowalczyk
- Re: filename encoding (was: ISO-2022)
  - From: Tomohiro KUBOTA

Prev by Date: Re: filename encoding (was: ISO-2022)
Next by Date: Re: filename encoding (was: ISO-2022)
Previous by thread: Re: filename encoding (was: ISO-2022)
Next by thread: Re: filename encoding (was: ISO-2022)
Index(es):
- Date
- Thread