tor 2008-05-29 klockan 10:11 -0600 skrev Peter Saint-Andre: > On 05/28/2008 11:50 PM, Marcus Lundblad wrote: > > Hello. > > > > I should probably begin by introducing myself. My name is Marcus. > > > > I have recently been looking at XEP 0231, escpecially the part about > > sending an embedded image in an XHTML-IM stanza. > > Using this specification, I have implemented support in Pidgin > > (libpurple) to use the infrastructure there used for "custom smiley > > support" (at this point only for MSN protocol) to implement use-case 3.1 > > of the XEP. > > There is one thing that is a bit of a concern. In current versions of > > Pidgin, the img tags in XHTML-IM messages are completly ignored, > > resulting in an empty message in the case of a message consisting of > > only one such emoticon image. > > > > What would be nice was if there was a way for the client to advertise > > support for displaying such images. > > Do you mean (1) support for <img/> from XEP-0071 or (2) support for the > messaging use case in XEP-0231? If (2) then we could define a service > discovery feature for that, as we did in XEP-0231 for file transfer preview. >
Hi. I mean support for messaging use case in XEP-0231. The current implementation of XEP-0071 in Pidgin ignores the <img/> tags completely. By having a service discovery for this use case, we could either revert to just inserting the text representation of the emoticon or disable these custom emoticons if the remote side doesn't advertize support. I don't know how it would work for MUC's, though. Maybe it can determin if all participants supports it, I'm not too familiar with the service discovery part. And also, I saw that Phil Hannent had written a post on the same subject earlier, since I just subscribed to this list I might answer those questions here. The protocol used follows the messaging use case in XEP-0231. The user can add emoticons locally and assign a shortcut to them. When sending a custom emoticon (by typing its shortcut or selecting it in the GUI) the text will get converted to an <img/> tag referring an included <data/> element (if it hasn't been used before in the conversation). There is also a context menu for received emoticons so that a user can save received emoticons (with a shortcut as above). The UI is shared with other protocols so that the appearance is the same. It is currently not possible to export bundles of emoticons, but that could be an interesting idea. The API for the emoticon storage has been prepared for future support of "profiles". That could perhaps be used to create groups containing smileys. //Marcus > > Then it could either just send the > > text representation, or completely disable using those emoticons in such > > conversations. > > > > What do you think? AFAIK the XEP is still being worked on... > > Yes, everything is a work in progress. :) > > Peter > -- Marcus Lundblad Phone +46 (0)18 250582 | Cell +46 (0)733 386299 XMPP [EMAIL PROTECTED] | ICQ 11604698 MSN [EMAIL PROTECTED] | Y!M marcuslundblad --
