[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: Ulrich Drepper <drepper@xxxxxxxxxx>
Date: 01 Feb 2001 19:14:09 -0800
In-reply-to: Tomohiro KUBOTA's message of "Fri, 02 Feb 2001 12:08:31 +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: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Capitol Reef)

Tomohiro KUBOTA <tkubota@xxxxxxxxxxx> writes:

> Thus, either of them should be taken:
>  1. libc/kernel accepts only UTF-8 filenames.
>  2. libc/kernel knows the locale.

None of this.  Neither the kernel nor libc will ever do anything about
the encoding of filenames etc.  There are these stupid Winblows
exceptions of course but not for real filesystems.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/

Follow-Ups:
- Re: filename encoding (was: ISO-2022)
  - From: David Starner
- Re: filename encoding
  - From: Kai Henningsen

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