What can I do to fix this problem.Error: File name too long(/name_of_file)
Thanks.
What can I do to fix this problem.Error: File name too long(/name_of_file)
Thank you Captain Obvious. But how to get off this error?Rolcol wrote:It's not a limitation of Transmission, it's a limitation of the operating system or file system.
It may be obvious to you but not to everyone, and certainly not to "Average Joe" users. The only real fix to this is to "fix" the OS or FS. Automatic renaming can be dangerous and will certainly take significant resources in getting it done properly, especially in consideration to where to apply the renaming.fidoman wrote:Thank you Captain Obvious. But how to get off this error?Rolcol wrote:It's not a limitation of Transmission, it's a limitation of the operating system or file system.
Is there feature to automatically rename file to fit it to filesystem limitation?
E.g. many posters use single-byte encoding FSes to store files, and if downloader uses UTF-8 filesystem, he get error if file name is a half of filename length limit, but uses national characters.
But, if agree to this concept, we have as a consequence that if somebody creates a torrent with long filename (e.g. he has very rare FS without limitations), there is no way to download it.blacke4dawn wrote: As for an issue with using different bit-lengths in different file systems then that is still an issue within the OS and not something that Transmission should "compensate" for.
Conversions are correct. No any choppings, you do misunderstand.blacke4dawn wrote:Not properly converting from UTF-16 to UTF-8 is either a failure of the OS or no indication of what encoding it was presented as originally. A properly done encoding conversion leaves the number of characters (keyword here is CHARACTERS, not bytes) the same, regardless of how many bytes are used per character in each encoding.
Just taking a UTF-16 character and chopping it up into two UTF-8 characters is an invitation for disaster. It's just not done not only for name length reasons but also to avoid "getting" the control characters, which I believe are the first 32 ASCII characters. The control characters are also labeled non-writable since they have no graphical representation, ever. Just chopping up UTF-16 characters into UTF-8 will most likely lead to one or more of these control characters being present in the file name.
Most Windows programms will fail when full path exceeds 255 characters (including Explorer and CMD.EXE). Linux has a pathname limit of 4,096.