2011-02-11, 01:17
therealjoeblow Wrote:I tested with "," commas, it fails with that too. We could argue opinion on whether "." belongs, you will find hundreds of thousands of people the world over (if not millions) who regularly use "." in their filenames, and as far as at least windows based systems goes, here are the "official" rules:
Code:Legal characters in NTFS include the following:
[ ] . ; = ( ) and most other punctuation except those noted below
The period (.) cannot be the first or only character in the filename
Illegal Characters:
The following characters are not permitted in Windows file or directory names:
/ \ : * ? " < > |
Could we just agree that the script should work properly with *all* legal filenaming schemes, including all legal punctuation? Applications really shouldn't be starting new character-based filename constraints that aren't imposed by the OS. That will surely confuse users and lead to problems.
Cheers
The REAL Joe
The big problem with commas is that you use them to separate fields, attributes, etc when programming.
I think this is due to windows implementation of spaces in filenames you have to use quotes when there are spaces, so the commas in between get somehow lost.