Transmission

Hello.

Modern operating systems don't convert unicode to national charset - they use it in unicode-generation encodings (UCS-2 in Windows, UTF-8 in Linux and Solaris, but I don't know about BSD)/

Here goes piece of log generated with patch:
long name at 45 len 377 buf 423: /tank/data/torrents ...

Since nobody here understand what is UTF-8 I've written patch for some name trimming by 255 bytes.
This is draft with some debug output to file and it requires hard refinement.


*** utils.c-orig 2011-08-14 12:24:00.645183544 +0400
--- utils.c 2011-08-14 17:32:02.242301478 +0400 ...

I think it is impossible to explain anything if you don't understand that one character in UTF-8 is encoded by variable count of bytes, but unix'es e.g. linux and solaris do limit length of file name by BYTES not CHARACTERs.

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 ...

The issue appears on Solaris due to UTF-8 encoding, used there.
At Windows, NTFS uses at least two bytes for any character (UTF-16), and it guarantees 255 byte pairs (510 bytes).
At Solaris, ZFS uses at least one byte (UTF-8), and amount of space reserved is 255 single bytes, not pairs, so 255-byte ...

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.

But, if agree to this concept, we have as a consequence that if somebody creates a torrent with long filename (e.g. he ...

Moreover, even if offending file is excluded, transmission stops with the error "file name too long" on it.

It's not a limitation of Transmission, it's a limitation of the operating system or file system.

Thank you Captain Obvious. But how to get off this error?
Is there feature to automatically rename file to fit it to filesystem limitation?
E.g. many posters use single-byte encoding FSes to store ...