Re: spaces at ends of filenames or directory names on Win32

Jeffrey Schwab wrote:
Larry Bates wrote:

IMHO leading and/or trailing spaces in filenames is asking for
incompatibilities with cross-platform file access.

With what platforms specifically?

Much like
using single-quote in filenames which are perfectly legal in
DOS/Windows, but Linux doesn't like much.

Uh... What Linux are you using? And what FS?

$ touch "'" && ls
'
$ rm "'"
$

I stand corrected if you put double quotes around filenames
it does work. That to me means that single quotes
in filenames are somehow "different" than other characters.
You must handle these filenames differently (at least from
the command line). Thanks for pointing this out.

-Larry Bates

.

Relevant Pages

  • Re: FAT32 vs NTFS
    ... both to save space and to preserve the filenames. ... And there are colons all over the place in the linux file ... > and one with ext3 for linux backups. ...
    (Debian-User)
  • Re: Linux and HPFS filenames
    ... characters from the filenames, no? ... From what I've seen linux isn't aware of this. ... > How can I copy them over with the .LONGNAME filename? ... nothing calls it with "LONGNAME" in the HPFS module for 2.6.10. ...
    (comp.os.linux.misc)
  • Re: Writing DOS disc images on Linux with RISC OS filetypes
    ... >> filetypes and long filenames, that is compiatable with both DOSFS and ... I've added support for RISC OS filetype and filename truncation to mtools, ... I might add support to Linux as well. ...
    (comp.sys.acorn.misc)
  • Re: Can mount but not unmount ISO images?!
    ... The kernel version is ... > First mistake. ... Never allow spaces in file or path names under Linux. ... >>mount at all I resorted to escaping the spaces in the filenames with the ...
    (comp.os.linux.misc)
  • Re: spaces at ends of filenames or directory names on Win32
    ... using single-quote in filenames which are perfectly legal in ... DOS/Windows, but Linux doesn't like much. ...
    (comp.lang.python)