(link removed by Mod and sent to dev)

Maybe this is also the case with other file name that start with punctuation.

Click on any of the red buttons below to download torrent.

(link removed by Mod and sent to dev)

Do torrent file names in Tixati use UTF-8? Why missed name start with punctuation when hash by other BT client？

Tixati uses UTF8 everywhere.

The only restriction is on "hidden" files/folders, which is any name that starts with a period ".".  It renames those into a leading underscore so they are visible in file explorer.  On Linux and Windows any file with leading period is hidden when browsing the shell.

All other characters are unrestricted except maybe in some older versions of windows that don't allow a few others like quotes and colons ":".

It has nothing to do with hidden files and files start with with a period ".", these are all files and folders that start with a period "_", and these torrents made by tixati can't be hashed 100% by other BT clients.

(Links removed by Mod and sent to Dev)

i990049  -> please re-post your pictures but with all file/folder names blurred.

torrent made by other BT client hash 100%


torrent made by tixati 3.29 hash 0% by other BT clients with file name start start with a period "_"


Why don't other torrents made by other BT clients have such problem?

Because you didn't do the same test.  Create the .torrent in qbittorrent and then clear it and reload it fresh from .torrent and the same thing will happen with those files.

OK there is a lot of confusion here.  So I will clear things up for anyone who may find this thread in the future.

Tixati (and other clients) will replace reserved characters in local file names with an underscore "_".  This happens when loading from a .torrent, and when creating a .torrent.

You can read up on what characters are reserved:

https://stackoverflow.com/questions/1976007/what-characters-are-forbidden-in-windows-and-linux-directory-names
https://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words

Basically, it's these:  \ / : ? " < > |  Also, leading dot and some others.

So, if you somehow have files/folder with reserved characters, and make a seed with them, in the .torrent file meta info those names will have underscores replace the bad characters.  This is fine, you can still seed those files because the client remembers the original names, even if they are invalid.  It is when they are placed into a saved .torrent file AND/OR reloaded from a .torrent that they are sanitized.

When you take the .torrent file and reload it, no matter what client, even the same one, the clean sanitized names won't match the pre-existing names with invalid characters, so it won't find the original files to hash, and they will be at 0% because the sanitized underscore names do not exist.

The reason you see that it's not happening in your qbittorrent example is because you created the torrent on it and are also seeding on the exact same client.  You didn't clear and re-load from .torrent.  Try creating your .torrent on qbittorrent, and then load it into tixati, and the exact same thing will happen.

If you create a .torrent from invalid file names, you won't be able to re-load that .torrent into ANY other client locally (tixati or not) and expect it to find those files with their invalid names for hashing.