[Top][All Lists]

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

[bug-gnulib] Re: ISSLASH on Woe32

From: Ian Abbott
Subject: [bug-gnulib] Re: ISSLASH on Woe32
Date: Thu, 28 Apr 2005 11:28:05 +0100
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)

On 28/04/2005 02:18, Tor Lillqvist wrote:
the byte 0x5C occurs as second byte of some multibyte characters. If such a
character is used inside a directory name, code that uses ISSLASH does not
work correctly. All gnulib modules that use ISSLASH are affected.

Could this also be a problem on Unix systems using multibyte encoded
(UTF-8) filesystems, if not now then in the future?

Nope. Unix kernels/filesystems don't care at all what encoding the
file names are in. Encodings are handled in userspace. The only thing
that matters is that a '/' (0x2F) or '\0' byte can't be part of a
directory entry name. I don't think this is going to change.

Maybe some (future) Unix systems support multi-byte encoded filenames
containing 0x3F in the second+ byte of a multi-byte character.

0x3F is '?'. You mean '/', 0x2F? I very much doubt that.

Oops! Yes, of course.

Anyway, I was being a bit thick, because *all* bytes in a UTF-8 encoded character > U+007F (i.e. all characters requiring more than one byte) will be > 0x7F, so they won't contain 0x5C or 0x2F (or 0x3F:-).

-=( Ian Abbott @ MEV Ltd.    E-mail: <address@hidden>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

reply via email to

[Prev in Thread] Current Thread [Next in Thread]