  the process of filename mangling, in computing, involves a re-writing of the file name for compatibility at the operating system level. it occurs when a filename on a filesystem appears in a form incompatible with the operating system accessing it. such mangling occurs, for example, on computer networks when a windows machine attempts to access a file on a unix server and that file has a filename which includes characters not valid in windows. == examples == * unix file names can contain colons or backslashes, whereas windows interprets such characters in other ways. accordingly, software could mangle the unix file "notes: 11\04\03" as "notes_ 11-04-03" to enable windows software to remotely access the file. * other unix-like systems, such as samba on unix, use different mangling systems to map long filenames to dos-compatible filenames (although samba administrators can configure this behavior in the config file). * probably the best-known example of name mangling occurs on vfat file systems on versions of windows from windows 95 onwards. the vfat specification allows long file names (lfns). for backwards-compatibility with ms-dos and older windows software, which recognizes filenames of a maximum of 11 characters in length with 8.3 format (i.e.: an eight-letter filename, a dot and a three-letter extension), files with lfns get stored on disk in 8.3 format, with the long file name stored elsewhere on the disk. normally, when using compatible windows programs which use standard windows methods of reading the disk, the i/o subsystem returns the long filename to the program &mdash; however, if an old dos application or an old windows application tries to address the file, it will use the older, 8.3-only apis, or work at a lower level and perform its own disk access, which results in the return of an 8.3 filename. in this case, the filenames become mangled by taking the first six non-space characters in the filename and adding a tilde (~
Computer_file_systems Computer_files