unsupported caracters?

Windows specific questions, problems.
Post Reply
flitox

unsupported caracters?

Post by flitox »

hello,

i'm noticing that qbt replaces é letter by a _, which mean that all previouly download (i'm importing my torrents from utorrent) that have those letter cant reach 100%.
am i going to have other bad surprises like this??
also the idea that next torrents i'm going to download containing weird letters in the files name will have them replaced by a _ isn't too pleasing
sledgehammer_999
Administrator
Administrator
Posts: 2443
Joined: Sun Jan 23, 2011 1:17 pm

Re: unsupported caracters?

Post by sledgehammer_999 »

That means the user who created those didn't use a correct torrent creator. Those strings should be saved as utf8 in .torrent file. qbt (well its backend libtorrent) replaces characters that don't use the correct character encoding.
You could open a bug at the libtorrent bugtracker and attach one those for inspection by libtorrent's author. -> https://code.google.com/p/libtorrent/issues/list
flitox

Re: unsupported caracters?

Post by flitox »

is there a way to know if it encoded in utf8 if i open the .torrent file with notepad??
i did try try to search for that on the last one i step on and result returned nothing
AsaRossoff

Re: unsupported caracters?

Post by AsaRossoff »

If you want to try to check yourself, you might be able to tell using a tool like BEncode Editor: https://sites.google.com/site/ultimasit ... ode-editor

...which will parse the torrent file and show you it's decoded contents (and let you mess it up by changing it, which you probably don't want to do).
flitox

Re: unsupported caracters?

Post by flitox »

the problem was only a badly created torrent file i guess. if if renamed the faulty files by replacing the _ with the correct letter, everything went fine and i could reach the 100% check.

absolutly nothing to do with the topic above but since day 1 of use (i basically ran qbt for only a few dozen min on day zero and only add one torrent at that point), i couldn't get myself connected which seems to be a known bug (no big deal for the moment, i'm only importing my torrents). what is the easy way around it?? deleted all the settings files and reinstall qbt??
i'm also noticing today that when i want to minimize it, qbt can still be seen in the taskbar. couldn't remember if it was like that yesterday, i'd say no, otherwise i would have notice.... for the moment i'm still blaming the said bug above for that behaviour (just like the fact icouldn't check/uncheck the dht option...).

all i hope, this is not happening often, i'm leaving my previous client because of annoying stupid little bug like that
sledgehammer_999
Administrator
Administrator
Posts: 2443
Joined: Sun Jan 23, 2011 1:17 pm

Re: unsupported caracters?

Post by sledgehammer_999 »

Connect to internet? Try disabling/enabling utp in the options. Or putting a limit on your upload.
Taskbar? Do you want to minimize to tray/notification area? Then enable the appropriate option in the settings.
DHT greyed out? Can you post a screenshot?
flitox

Re: unsupported caracters?

Post by flitox »

morelikely something like this
http://qbforums.shiki.hu/index.php?topic=2392.0

except that my port is open.
DHT isn't greyed out,  ticking on the just do nothing
minimize to tray is enable, it just don't happen...

edit:
i deleted both qbittorrent.ini & qbittorrent-data.ini before updating to latest and now all is working correctly! :-)
but what you said about utp (making connection with tcp 1st) isn't true, i did the test, everytime utp is enable, i'm connecting with utp to peers. if disable, i'm connecting to the same peers with tcp
Last edited by flitox on Tue Apr 29, 2014 4:32 pm, edited 1 time in total.
User avatar
Nemo
Administrator
Administrator
Posts: 1744
Joined: Sat Jul 24, 2010 6:24 pm

Re: unsupported caracters?

Post by Nemo »

It is true that qBittorrent favors TCP over uTp but that doesn't say that it only needs to use TCP when you have uTp enabled. Of course it will also use uTp connections too which is normal. Also depends on other peers what way they are connecting to you. Sometimes it drops the peer (uTp) and connects back as TCP connection and backwards, or just stays with uTp/TCP. Perfectly normal behaviour.

If you only want TCP then disable uTp and you're done, simple.
Last edited by Nemo on Tue Apr 29, 2014 7:52 pm, edited 1 time in total.
Post Reply