From: robin_listas@es.invalid   
      
   On 2026-01-06 19:48, Lars Poulsen wrote:   
   > On 2026-01-06, The Natural Philosopher  wrote:   
   >> It was Mac OS-x where all filenames were in upper case, until they   
   >> allowed lower case too...   
   >>   
   >>    ..whereupon no program at all would then work and the use of 'strings'   
   >> revealed why. The same application would randomly use upper, lower or   
   >> camel case to refer to the same filename...safe in the certain knowledge   
   >> that the OS would translate it all to upper case. Except when it didn't.   
   >   
   > This is a big problem when writing programs for Windows and Linux.   
   > Windows is "Case Preserving" (allowing upper and lower case mixed names,   
   > but displaying them the way they were created) while Linux/eFS4   
   > requires full match on file names. When accessing Linux files from   
   > Windows, matches the Windows behavior. I REALLY wish that I could   
   > get the Windows behavior as a mount option in Linux, but apparently   
   > it is considered an unsurmountable problem that non-European languages   
   > / alphabets do not have the simple (mostly 1-1) relationship between   
   > upper-case and lower-case, so to do the "right" thing would require   
   > adding locale complexity in the file system. ("Is the mapping per-user   
   > or systemwide?", "What to do with ligatures?", etc).   
   >   
   > I wonder how Windows deals with that - Do they just limit the   
   > case-matching to UTF-8 characters from the European subset?   
   >   
      
   What happens when you export a linux mount using samba, and the mount   
   contains files that are different only in case?   
      
   --   
   Cheers, Carlos.   
   ES🇪🇸, EU🇪🇺;   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)