On 18/01/2019 09.40, Rainer Hantsch wrote:
Am Freitag, 18. Jan 2019, 09:27:41 schrieb Johannes Meixner:
Hello,
On Jan 18 08:52 Rainer Hantsch wrote (excerpt):
While I use iso-8859-1 in my systems, my friend uses utf-8. ... convert filenames on the fly ...
why converting only the file name but not the file content?
Wouldn't such a half-baked conversion make things even worse because then the file name encoding would no longer match its content encoding which means in any locale either the file name or its content would be shown wrong unless it is ASCII which is the only encoding that "just works" (I already hear them screaming "nowadays all is UTF-8" ;-)
Hello Johannes. This is not "half baked". Converting the content of a file is often not possible. You cannot simply run everything (including the file content) through a translator, this will damage most of the files abd only work in pure text files.
I guess Johannes was using irony ;-)
For some more fun in encoding hell have a look at https://en.opensuse.org/SDB:Plain_Text_versus_Locale
Interesting! Didn't know of this one.
I know nothing about NFS details but I guess that for NFS a filename is a plain sequence of bytes.
AFAIK, it is so for any filesystem. Best is to use software at the other end that uses the same encoding as the filesystem. Yes, it is a nuisance. Although Linux supports in fstab an entry for the encoding on fat or ntfs, I don't know how that works. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)