Version: (using KDE 4.1.2) Installed from: Ubuntu Packages I maintain an emoticon theme that works with a lot of different clients. Unfortunately, every client has a different format for the definition file, so what I do is zip the images and put all the various definition files in there too, each client will then find the file it's looking for, including kopete. As of kopete-kde4, or kde-4.1.2, which is where I first found the bug, the emoticon set can no longer be loaded correctly. I've looked at how emoticons are defined in kde4 and the format seems to have changed. I can produce an emoticons.xml file that fits the bill, but the theme is still not loaded correctly. What I suspect is that pidgin's "theme" file is found and read first. Unfortunately, the result is epic fail (it loads correctly in pidgin, obviously), what I get in the gui is an empty list. If I delete this file, kopete presumably finds emoticons.xml (or maybe icondef.xml, who the heck knows) and does load the set correctly.
Created attachment 28319 [details] the emoticon theme in question The purpose of this file is to be loaded and work in as many different clients as possible. Verified to work in kopete (kde3), gaim, gajim, psi. As you'll find, it also contains the scripts I use to generate these definition files.
Created attachment 28320 [details] same file, but "theme" missing, loads okay
Created attachment 28321 [details] load failed screenshot
Created attachment 28322 [details] load ok screenshot
Trying to reassign.
SVN commit 907952 by segato: sort the kemoticons provider by priority so if we have multiple theme file we will use the provider with higher priority(in this case the kde one) CCBUG: 174259 M +6 -0 kemoticons.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=907952
SVN commit 907953 by segato: use a qregexp to split the line since we can have tabs instead of spaces BUG: 174259 M +1 -1 pidgin_emoticons.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=907953
Excellent! Any chance this might get snuck into KDE 4.2? :)
yeah it's already fixed in the 4.2 branch too