it seems Linux uses the iso8859-1 character encoding for mounts. Note also that I'm not using mount manager (maybe mount manager adds iocharset=utf8 ?). But if other folks are facing similar issue, this is the way to go.
In Windows speak they are codepages, and cp437 is the standard codepage used by Windows.
They key here is not as such which codepage you use, but how consistent you are, as it is only a solution if ALL connections to the share, and the host itself if that creates files, use the same characterset.
And in this lies the problem: Windows (PC or Server) is a platform that can create files, and Windows to Windows connections always use their native characterset, and you can't change that when opening a share.
Samba, as a CIFS server, is able to convert, which is a feature that Synology uses in their NAS.
So if you create a file called "âêîôû.txt" in Windows, copy that (in Windows) to a share on a Synology, then look at that share on the NAS, it is still "âêîôû.txt", so correctly converted to utf-8. If you name an NFS mount from a linux machine (like your box) to that share, you will also see "âêîôû.txt". But if you make a CIFS mount from a linux machine, and you don't specifiy the other side uses utf-8, the connection defaults to a Windows characterset, and you will see "�����.txt".
In other words, if you connect to a Windows machine from linux, use CIFS. If you connect to a Linux machine, use NFS. Or know what you're doing and add iocharset to the mount options.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), Mutant HD66SE (S2+T2), (Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, for the forseeable future I will not be very active. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
