Chris Vine <[email protected]>: > On Tue, 14 Feb 2017 21:52:01 +0000 (UTC) > Mike Gran <[email protected]> wrote: >> True. Linux should follow OpenBSD and make all locales UTF-8. > > Filenames and locales are not necessarily related.
Linux *could* force that reality. > When you access a networked file system, you get the filename encoding > you are given, which may or may not be the same as the particular > locale encoding on your particular machine on one particular day, and > may or may not be a unicode encoding. Linux *could* provide a seamless translation, or it *could* refuse to mount filesystems that don't comply with its requirements. > Linux is capable of treating filenames as just a null-terminated array > of bytes with '/' as the directory separator. It is encoding agnostic, > and that works just fine. Bottom line: that's just the way things are in Linux. Programming languages like Guile should not try to create another abstraction layer on top of it. Marko
