Re: dirs with trailing . (period)
- From: ".._.." <.._..@xxxxxxxxxxx>
- Date: Fri, 19 Oct 2007 14:52:21 GMT
The allowed characters in folder names and file names are different from
Unix to Windows.
To make interoperablity, you need to follow BOTH of the standards with all
files and folders.
"." is an illegal character for the end of a folder name in the underlying
file system for Windows. The GUI will let you do it, but it's using a crude
work around to display the "."
For best results, use numbers, letters, underscores, and dashes for folder
names. NO SPACES. Use ALL lower case letters (Unix is case sensitive,
Windows is not.) Use three or four letter file extensions, or no file
extension. Use a single dot to differentiate the file extension from the
file name. Do not use more than one dot, do not use punctuation, etc.
"A. Vreugdenhil" <AVreugdenhil@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4AF22B61-2A87-4765-A3CB-ABFC97D3ABE0@xxxxxxxxxxxxxxxx
Yes, I noticed all that too.
Isn't it strange?
I'm writing a script that copies stuff to another server, but now it seems
I
can never upload perfectly valid dirs if their names end with a period :(
At least two clients just create the given dir, but when you start
uploading
the contents the dirs has not been created but an entirely different dir
has.
Is this a bug or what???
"Bernard Cheah [MVP]" wrote:
I tested with w2k3, it won't allows me to create 'test.' directoy but
'test,' is acceptable.
if windows detects that a period is and the end, it truncate it making it
'test' only for the folder name.
.
- References:
- Re: dirs with trailing . (period)
- From: Bernard Cheah [MVP]
- Re: dirs with trailing . (period)
- From: A. Vreugdenhil
- Re: dirs with trailing . (period)
- Prev by Date: Re: Passive Mode issue
- Next by Date: Re: dirs with trailing . (period)
- Previous by thread: Re: dirs with trailing . (period)
- Next by thread: Re: dirs with trailing . (period)
- Index(es):
Relevant Pages
|
Loading