Half-Request: Better Compatibility with OS X about mktorrent HOT 6 OPEN

As the torrent is created with a file name encoded in NFD, when attempting to seed on another operating system, the file name is different and as such the torrent client thinks the file does not exist. I often create torrents on macOS and seed on Linux. Currently, I have to first ensure there are no accents, diacritics, or non-Latin characters in the file name before creating.

from mktorrent.

I just wanted to confirm that I'm also encountering this issue, and that it is definitely a property of mktorrent on macOS.

APFS (compared to HFS) seems to be happy to allow you to write unicode filenames with NFC-normalized characters, and they will stay that way, but mktorrent seems to read and generate its bencoded data structure with the path strings re-normalized back to NFD. This is how we get into the scenario that @gennaios mentioned, where it's even possible to generate a torrent on macOS, load it into a torrent client on that same system, and have it fail verification. This would require torrent clients to auto-normalize back to NFC unicode, which I can at least say that Deluge on linux is not doing.

from mktorrent.

The above user deleted their account so I assume the offer to add this is off the table, but it would definitely be a welcome addition as this has been giving me problems lately!

from mktorrent.

@denkristoffer if this issue is still relevant, could you please elaborate the nature of the problems it's causing?

from mktorrent.

@gennaios thanks for the explanation.

from mktorrent.

Any updates as to when this might be addressed? Mentioning it to someone, he said with accents, the created torrent file from macOS is even unusable on any system, even on macOS itself.

from mktorrent.