Jan Hendrik wrote:
> Concerning Re: ntfs naming conventions
> Dave Levitt wrote on 16 Sep 2009, 9:58, at least in part:
>
>> The Win32 'CreateFile' API will cope with file and directory names
>> [embedded, leading and trailing spaces] without issue. A handle to the
>> file will be returned to the calling process.
>>
>> The Console Command Processor [e,g, cmd.exe] will only process a
>> subset of the available file names, trimming strings as part of the
>> parsing process. So, a program can create a file entry that cannot
>> easily be manipulated from the standard Windoze command prompt.
>>
>> If you install an alternate command prompt [e.g. a Cygwin bash shell]
>> the shell's regular expression features should allow oddly named files
>> to be manipulated.
>
> Interesting. I just had tried to rename an existing file in Total
> Commander (file manager), with the results given. Saving a
> message from Pegasus Mail results in the same behaviour.
From MSDN ->File Names, Paths, and Namespaces page
(http://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx):
"...Do not end a file or directory name with a trailing space or a
period. Although the underlying file system may support such names, the
operating system does not. However, it is acceptable to start a name
with a period."
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2395723
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-16 22:03:35 CEST