On Mon, Aug 05, 2024 at 08:44:29PM +0000, Kepa wrote:
> Funny: the path was p:/170 Buzon/oq.pdf, where the "o" was accentuated: https://en.m.wikipedia.org/wiki/%C3%93

Perhaps relevant:

 - what file systems are on each of those drives? NTFS? some Linux?
   (Background: most Unix/Linux file systems consider file names
   as strings of bytes. What encoding /characters/ have there is
   up to the application [1]; NTFS has UTF-16 encoded Unicode, although
   if you access it with POSIX fopen(), it gets translated to UTF-8).

 - what applications do you access "normally" the "drive" which is
   showing the problem? What did you create the file with?

Cheers

[1] typically to the process's locale's encoding which creates/accesses
   it. Lots of fun when they're not consistent :-)

-- 
t