Information obtained from http://blogs.msdn.com/brian_dewey/archive/2004/01/19/60263.aspx :
Due to the layering of Windows architecture, the definition of a "legal" file name may vary depending upon the component of the operating system you are dealing with.
· NTFS and the Posix subsystem have the most permissive definition of a "legal" name. The name may be up to 32,768 Unicode characters long. The name can contain trailing periods, trailing spaces, and two files may have names that differ only in case (e.g., README.TXT and readme.txt).
· The Win32 subsystem enforces additional constraints on legal file names. The name can be at most MAX_PATH characters long (defined in windef.h as 260 characters), may not have trailing dots or spaces, and file names are case preserving, not case sensitive — if two files exists with names that differ only in case, you will only be able to manipulate one of them through Win32 APIs.
Therefore, the problem you are facing with trailing spaces is not due to a defect in our component. Actually, it is an operating system (Win32 subsystem) limitation.
Also, a filename with a leading space will be reported without this space when the FTP server responds to a ls command. This makes the file impossible to be downloaded.
Ghislain
Technical Support and software developer
Xceed Software Inc.
Knowledge Base : http://xceed.com/kb/
Update Center : http://xceed.com/updates/
Documentation Center : http://xceed.com/doc/
For everything else, there is Google