Actually, the nick in nmdc should be treated as a binary blob and kept separate from the display nick (which probably should be converted disregarding encoding errors...)...then findlegacy would not have to bother with encodings at all... converting everything to utf8 in nmdc is not very friendly towards other clients / legacy users. we've covered this before in other contexts I believe, but noone's cared enough to actually fix it...
-- ClientManager::findLegacyUser(), assertion "aNick.size() > 0" fails https://bugs.launchpad.net/bugs/321246 You received this bug notification because you are a member of LinuxDC++ Team, which is subscribed to LinuxDC++. Status in DC++: Fix Committed Status in Linux DC++: Confirmed Bug description: I have no idea why this happened. I was doing some testing (tried and true random clicking) on some Russian hub, and I can't make it happen again. The address of the hub was lost when the application failed assertion, unfortunately. linuxdcpp: dcpp/ClientManager.cpp:187: dcpp::UserPtr dcpp::ClientManager::findLegacyUser(const std::string&) const: Försäkran "aNick.size() > 0" falsk. _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : [email protected] Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
