[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ashCi0p6t_CegboC@raf.org>
Date: Fri, 9 Oct 2026 12:25:31 +1100
From: raf <musl@....org>
To: musl@...ts.openwall.com
Subject: Re: fnmatch: invalid multibyte sequence in the string is
taken as end of string ("" matches "\xff" in UTF-8 locales)
On Thu, Oct 08, 2026 at 09:44:20PM +0200, Thorsten Glaser <tg@...bsd.de> wrote:
> On Thu, 8 Oct 2026, Rich Felker wrote:
>
> >Putting byte strings that are not valid characters into filenames is
> >generally not a supported usage (by musl or by the standards).
>
> It is, in POSIX. Filenames are indeed just bytes, not characters;
> arbitrary bytes except slash and NUL.
>
> bye,
> //mirabilos
> --
> “It is inappropriate to require that a time represented as
> seconds since the Epoch precisely represent the number of
> seconds between the referenced time and the Epoch.”
> -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
Linux, FreeBSD, OpenBSD, NetBSD, and Solaris allow binary filenames.
Windows/Cygwin and macOS are the only systems I have that require them
to be text.
Also, if one user's locale uses UTF-8, and another user on the same
system uses a Latin-1 locale, there can be text filenames created
by one user that look like binary to the other user.
cheers,
raf
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
