![]() ![]() The 0x05 character is/was used to denote a deleted object by replacing the first character of the object. doesn't seem to apply to modern systems.) The ^ character cannot be used in object names. Windows and Linux both prohibit forward-slash (/). Only the NUL character is technically prohibited in object names. Objects can contain multiple sequential spaces, but some applications may not be able to access them. Objects can begin with a space or a dot, but most applications disallow it. This is a hold over of 8.3 space padding and dot extensions. Objects cannot end with a space or a dot or sequences of dots and spaces. The characters \ / : * ? " | and control characters 0-31 are forbidden in object names. I encounter these periodically, and I'm kind of hoping to build a reference of all known quirks, no matter how quarky. Also maybe worth noting any common peculiarities exhibited by other software such as of handling filenames with multiple sequential spaces, or containing DOS device names (AUX CON NUL PRN CLOCK$ KEYBD$). This can also extend to arbitrary limitations within operating system software itself, such as Windows Explorer's arbitrary prohibition against renaming files with leading spaces or leading periods (perfectly legal by other means). ![]() I am curious what edge cases we know about with regard to file and folder naming on various file systems in various operating systems, such as prohibited characters, leading and trailing characters, and other abortions. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |