Chris Vine <ch...@cvine.freeserve.co.uk> skribis: > So far as filenames are concerned, > this seems to me to be something for which a fluid would be just the > thing - it could default to the locale encoding but a user could set it > to something else. I suppose command lines and environmental variables > are less problematic because they are usually local to a particular > machine, although that may not necessarily be so true these days for > command lines.
I makes some sense to have a fluid for that. That said, it’s not so great either: for each Unicode-capable library in use, people would end up define $THELIB_FILE_NAME_ENCODING. Apart from GLib, I think language run-time supports (Python, etc.) typically assume locale encoding too, no? Does anyone know of systems where the file name encoding is commonly different from locale encoding? Is it the case on Windows? Ludo’.
