[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <as7eTlIDHJk6sluv@raf.org>
Date: Wed, 14 Oct 2026 12:43:42 +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:46:42PM -0400, Rich Felker <dalias@...c.org> wrote:
> On Fri, Oct 09, 2026 at 12:25:31PM +1100, raf wrote:
> > 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.
>
> A musl-based system doesn't have users with latin-1 locales because it
> does not have latin-1 locales.
>
> "All text is UTF-8" was one of the founding principles of musl. That's
> why we have iconv interfaces to support reading/converting legacy data
> (and in some cases, speaking it over legacy protocols) but don't have
> any way to use these as the multibyte encoding.
>
> Yes it's possible to use hybrid system with multiple libcs present in
> the same filesystem. It's now 2026 and the advisible way to do this
> even 15 years ago when musl first appeared was to use UTF-8 for all of
> them. If you really insist on not doing that, nobody can stop you, but
> it's not usage the project aims to facilitate.
>
> Rich
Yes, I realised that musl must be based on an all-UTF-8 design
when my patch to fix an infinite loop when faced with non-UTF-8
bytes wasn't included. I figured there must be no non-UTF-8 bytes.
That's why I never submitted my version to be considered for inclusion
in musl. I only sent it recently for interest's sake in response to the
recent patch.
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.
