"The beets blog: our solution for the hell that is filename encoding, such as it is. "

[Lynn McGuire]

"The beets blog: our solution for the hell that is filename encoding,
such as it is."
http://beets.io/blog/paths.html

"By far, the worst part of working on beets is dealing with filenames.
And since our job is to keep track of your files in the database, we
have to deal with them all the time. This post describes the filename
problems we discovered in the project’s early days, how we address them
now, and some alternatives for the future."

As having traveled down this road very recently in our combined C++ and
Fortran code, this is very interesting.

Lynn

[Alf P. Steinbach]

I'm thinking that for display of *nix paths one can use statistical ways
of inferring the encoding (if any), complemented with simply letting the
user choose the encoding assumption, including choosing a local default.

People so often forget that the user is part of the system and can do
things easily that the computer part cannot.

It was part of Microsoft's 1995 user interface guidelines, to let the
user always be in charge, and the one initiating actions. Around 2005 or
thereabouts, ten years later, it was forgotten, replaced by we-know-best
and it's-our-machine. Today their UIs suck in every way, including speed
(which is extreme, considering the speed of PCs has kept on increasing).
But. Even if one big player has forgotten that computer systems are for
the users and not the other way around, I say /we/ can remember.

Cheers!,

- Alf

[wyn...@gmail.com]

Lynn McGuire於 2018年5月6日星期日 UTC+8上午6時46分00秒寫道：

On linux, filename should be simple (it now seems just utf8 string)
The bigger issue includes 'pathname'. But until pathname is fully
understood or some consensus established.
I don't think any artificial portable way should be standardized.
More, the question: Whats is a directory? still haunts me.