> -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Erik Christiansen > Sent: Friday, 18 July 2014 5:21 PM > To: [email protected] > Subject: Re: Unable to remove file
<snip> > OK, if interworking with that other OS, e.g. via NFS or samba, then all > bets are off, and one survives as best one can. I've only ever gone as > far as serving read-only files, so safe naming was assured. > > ISTM that the problem would go away if NFS and samba provided filename > translation between OSs. Unfortunately that doesn't work either. "File Name", "File_Name", and "File-Name" (sans quotes) are all valid file names under Windows. So if Samba or NFS et al replace the space with another character, you would need a plethora of characters to replace the evil spaces, slashes, backslashes, dashes etc. along with a way of reversing the process to return the original filename back to the originating platform. Consider the following translations with character substitution active: Windows -> Samba -> Windows File Name -> File_Name -> File Name (Desired result) File_Name -> File_Name -> File Name (Borked result) Substitute any character you like for the translated character and there remains a translation failure mode. Unfortunately I can't see any way of keeping track of all of the possible ways that filenames could be munged ensure reliable two way translation. > Erik Morrie. _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
