Le mardi 5 mars 2013 01:16:52, Bill Allombert a écrit : > On Tue, Mar 05, 2013 at 12:06:06AM +0000, Roger Leigh wrote: > > We have defaulted to UTF-8 locales for over a decade now. Unless > > there are compelling reasons not to use UTF-8 locales, maybe we > > could perhaps consider retiring them and having everything be > > UTF-8 by default at this point. If we do require this in > > userspace, then the naming restrictions could also be enforced > > in-kernel e.g. with create/open with O_CREAT to disallow non-UTF-8 > > filename creation. > > My understanding is that we are supporting some character set that are > still not included in unicode. Forgive me if I missed something but it seems to me that even if we are supporting only charset included in unicode, people could have files created with another distribution / OS not encoded in UTF-8. So I don't think it's possible / desirable to deny opening UTF-8 filename in the kernel. > > Cheers, Best regards, Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part.