SailorMax Posted November 12, 2005 Report Share Posted November 12, 2005 uTorrent 1.2 show it in wrong codepage... Link to comment Share on other sites More sharing options...
Ultima Posted November 12, 2005 Report Share Posted November 12, 2005 Unicode isn't implemented yet... SEARCH! Link to comment Share on other sites More sharing options...
Kommander_SER Posted December 12, 2005 Report Share Posted December 12, 2005 Unicode isn't implemented yet...Ok µTorrent is now Unicode, but it dosen't work in v1.3 Build 364.I use russian private tracker and i get follow Tracker Status message:I'm running WinXP SP2 Pro German.To get µTorrent to show the correct symbols, I can change the codepage, but I have to reboot, and german soft doesn't workcorrect.Or with AppLocale from M$ is to myny work for each start.Also there musst be a error in µTorrent Unicode impimintation!Please help. And sorry for my English. Link to comment Share on other sites More sharing options...
Inf Posted December 12, 2005 Report Share Posted December 12, 2005 That text is NOT unicode, there is nothing the unicode support or anything related could do to solve this. There is no way for utorrent to know what charset to use for displaying that 256 characters set, thats why the default encoding (your system locale) is being used. Link to comment Share on other sites More sharing options...
Firon Posted December 13, 2005 Report Share Posted December 13, 2005 The tracker announce doesn't provide an encoding (it's not possible to send encoding in an HTTP message I think, but who knows) Link to comment Share on other sites More sharing options...
idle.newbie Posted December 13, 2005 Report Share Posted December 13, 2005 another similar problem, [Comment:] filed didn't translate with encoding field.looks like translated as system default code page, not UTF8. BC made torrent it has comment and comment.utf-8 fields, what i saw in General tab the Comment in uT was GBK comment field translated as default system code page(Big5) == garbage. Link to comment Share on other sites More sharing options...
Joes Posted December 13, 2005 Report Share Posted December 13, 2005 Does µTorrent support "Content-Type:" decoding in http reply headers ?Image that was provided contains russian letters in CP1251 encoding showed using ISO-8859-1 characters. Link to comment Share on other sites More sharing options...
Kommander_SER Posted December 13, 2005 Report Share Posted December 13, 2005 Is there any solution for this problem?sorry for offtopic Link to comment Share on other sites More sharing options...
splintax Posted December 15, 2005 Report Share Posted December 15, 2005 How is that offtopic? As Firon said, I'm not sure if a character encoding can even be sent with tracker messages. However I imagine that µT would be able to support it if there such information was provided. Link to comment Share on other sites More sharing options...
Firon Posted December 15, 2005 Report Share Posted December 15, 2005 idle.newbie: your problem isn't similar, some versions of BitComet are stupid and use .utf-8 keys instead of using utf-8 for the normal keys (neither Az nor µT read .utf-8 keys, only BitComet). A properly made UTF-8 torrent won't have those problems (or one that specified a proper encoding)Joes: I don't think that's part of the tracker spec... Link to comment Share on other sites More sharing options...
dAbReAkA Posted December 15, 2005 Report Share Posted December 15, 2005 tracker status messages seem to be okay here.. cyrillic(bulgarian) Link to comment Share on other sites More sharing options...
Joes Posted December 15, 2005 Report Share Posted December 15, 2005 Firon: Well, it is part of HTTP spec which is used by bittorrent client to communicate with tracker ;-) Link to comment Share on other sites More sharing options...
Firon Posted December 15, 2005 Report Share Posted December 15, 2005 Yes, but what the tracker spec uses might not be the entire set of HTTP messages. Link to comment Share on other sites More sharing options...
idle.newbie Posted December 16, 2005 Report Share Posted December 16, 2005 i knew proper UTF8 torrent works fine. just a suggestion for µT to translate comment field like path fields by encoding tag, for old ANSI torrents with encoding tag. AZ got no problem here(name/path/comment). Link to comment Share on other sites More sharing options...
Firon Posted December 16, 2005 Report Share Posted December 16, 2005 Oh, so it's not applying the encoding defined in the torrent to the comment? I know it does for name and path, at least. Link to comment Share on other sites More sharing options...
Joes Posted December 17, 2005 Report Share Posted December 17, 2005 Yeap. Torrent is made with UTF8, for example, but tracker reply is in CP1251 or KOI8-R. Though, all necessary HTTP headers (like mentioned Content-Type is present). Link to comment Share on other sites More sharing options...
Firon Posted December 17, 2005 Report Share Posted December 17, 2005 I meant the comment section, not tracker status. Link to comment Share on other sites More sharing options...
Joes Posted December 17, 2005 Report Share Posted December 17, 2005 Oh, nevermind then Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.