BitTorrent encoding error: Difference between revisions
m (→=: correction) |
No edit summary |
||
| Line 1: | Line 1: | ||
== What does this type of error mean? == | |||
This error means that the torrent contained something that seemed to violate the standard torrent format, or something that your system may have trouble with. Usually Shareaza deals with these problems automatically, but you may notice that the torrented files have odd names when completed. It's also possible that these torrents won't work on all clients. | This error means that the torrent contained something that seemed to violate the standard torrent format, or something that your system may have trouble with. Usually Shareaza deals with these problems automatically, but you may notice that the torrented files have odd names when completed. It's also possible that these torrents won't work on all clients. | ||
| Line 7: | Line 8: | ||
Also, if you have trouble seeding, look in the incomplete folder to make sure there is already no incomplete file for the torrent accidently left there by the program. If there is, delete it, and try reseeding again. | Also, if you have trouble seeding, look in the incomplete folder to make sure there is already no incomplete file for the torrent accidently left there by the program. If there is, delete it, and try reseeding again. | ||
=== | == Is this a bug? == | ||
It's not a bug. It is just the | It's not a bug. It is just the truth - uTorrent (and several other [[BitTorent]] clients) produces .torrent files with trigger the encoding error warning, as they use a non-unicode codepage for creating file names inside the .torrent files. So for example a torrent created on a Japanese Windows with hiragana symbols in the file name will NOT be saved properly on a Greek copy of Windows. | ||
Torrents can usually be 'repaired' be running them through a good torrent creation application, like [http://krypt.dyndns.org:81/torrent/maketorrent/ MakeTorrent2], which will fix any errors in it. But this will usually change the torrent's infohash, meaning the tracker and other torrenters who were uploading or downloading the previous torrent will not connect to you. So this is not really useful as a method of reseeding. | Torrents can usually be 'repaired' be running them through a good torrent creation application, like [http://krypt.dyndns.org:81/torrent/maketorrent/ MakeTorrent2], which will fix any errors in it. But this will usually change the torrent's infohash, meaning the tracker and other torrenters who were uploading or downloading the previous torrent will not connect to you. So this is not really useful as a method of reseeding. | ||
In order to avoid such problems with your own torrents, please use the [[Shareaza Torrent Wizard]], as it produces correctly encoded torrents. | |||
Revision as of 15:31, 23 October 2009
What does this type of error mean?
This error means that the torrent contained something that seemed to violate the standard torrent format, or something that your system may have trouble with. Usually Shareaza deals with these problems automatically, but you may notice that the torrented files have odd names when completed. It's also possible that these torrents won't work on all clients.
If you get a message about an encoding error, you may have trouble reseeding the torrent with Shareaza.
Try changing the advanced setting BitTorrent.TorrentIgnoreErrors to TRUE to force Shareaza to seed the torrent.
Also, if you have trouble seeding, look in the incomplete folder to make sure there is already no incomplete file for the torrent accidently left there by the program. If there is, delete it, and try reseeding again.
Is this a bug?
It's not a bug. It is just the truth - uTorrent (and several other BitTorent clients) produces .torrent files with trigger the encoding error warning, as they use a non-unicode codepage for creating file names inside the .torrent files. So for example a torrent created on a Japanese Windows with hiragana symbols in the file name will NOT be saved properly on a Greek copy of Windows.
Torrents can usually be 'repaired' be running them through a good torrent creation application, like MakeTorrent2, which will fix any errors in it. But this will usually change the torrent's infohash, meaning the tracker and other torrenters who were uploading or downloading the previous torrent will not connect to you. So this is not really useful as a method of reseeding.
In order to avoid such problems with your own torrents, please use the Shareaza Torrent Wizard, as it produces correctly encoded torrents.