Filename too long for destination folder
When your system displaces the following message “File names too long for destination folder” this means that the file name which you have opted is too lengthy to get stored. Thus the system shows the error.
E.g. your text file has a file extension of .txt which adds 4 characters to the length making 224 characters and if it’s on your memory card it will have a path something like E:\ which adds 3 characters to the length making it 227 characters.
The problem is when you copy the file to another location such as a new laptop; you need to make sure that the path doesn’t make you exceed the 260 character limit. For instance you might copy your file into a sub folder within your documents folder which gives you a total of more than 260 characters.
For example the path might be something like C:\Users\Username\Documents\My Text Documents\
If you don’t want to shorten the filename you can structure your folders / sub folders in the same way as they are on your desktop computer or try shortening the folder names.
Best Exercise / Avoid Illegal Fonts
The key communication is this: As much as likely, you should escape using very long filenames, since it will source issues as your documents move from one CPU or device to another. Falling the depth of nested files on a Windows system can also support. The harmless habit is to play to the most preventive common denominator, which is the pathname dependent performance in Windows, which outcomes in an indeterminate inferior limit which may be distant less than that permissible on either Carrier or Mac.
Explanation
The best answer, particularly with esteem to Windows, is to get in the custom of using filenames of distant less than 260 characters. If you normally plan to keep file names to 100 fonts or less, this gives you a moderate quantity of headroom for pathname addictions. Keeping filenames to 50 letterings or less is equal better. Though Mac workers can safely use filenames to their bound of 255 on recent varieties of OS X, responsibility so is not a good repetition in mixed platform setting and will run afoul of both Windows and Carrier.
If located in the Transporter folder, a file with a term over 217 characters will not sync from the computer on which it created to any Carrier. If located in the Transporter Public library, a file with a term over 218 characters will duplicate to one Transporter but will not sync to any additional Carrier devices. Attempting to operate such a file from a Windows PC may cause one of several conceivable Windows issues, as defined in Additional information, below.
The aim that Transporter software bounds names to 218 characters is so that specific of the name space is kept for temporary metadata and the conception of temp files, both of which need temporary trappings to filenames. This exercise is not unique to Carrier, and you might happenstance the same issue with other requests if your filenames are assertive the file system limit.
Extra information
Experience on name length for Mac and Windows
Very long filenames present problems in a mixed platform situation, because the way that different effective systems treat them is not constant. The Transporter-compatible varieties of OS X, for case, allow a filename of up to 255 fonts, including the file postponement. This means that a filename could be any 251 lawful characters plus “.txt”,
Windows has a theoretic maximum of 260 characters, but it also has a pathname dependence that can be difficult, well beyond the choice of this article. It’s adequate to say two effects: First, any filename on your Gaps system might max out far fewer than 260. Second, since of the pathname dependence, it’s generally incredible to tell you an exact same number as supervision for Windows.
The length of the encircling pathname is not straight subtracted from the 255-character filename border, so you can commonly move files among folders without name measurement penalty or difference. The exclusion to this is if you have any tracks in which the total would outstrip 1024 characters, which is characteristically only a query for software developers. Designer forums, counting Apple’s own are the finest place for any info on pathnames that surpass 1024 characters. Even users should simply cut any path of nested files that exceeds 1024 characters.
When distributing with filenames that are too extended, you might see one of numerous generic Windows posts about the copy being lost or failing. If you see such a communication and don’t know why you’re receiving it, try curbing the filename. Since of Windows’ pathname dependence, a filename that appears small might actually be very long at its envisioned copy terminus; variations on that subject might be problematic to anticipate–if in hesitation, experiment
