[Standards] About XEP 0231

Peter Saint-Andre stpeter at stpeter.im
Thu May 29 18:05:17 UTC 2008

On 05/29/2008 11:34 AM, Marcus Lundblad wrote:
> 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.

I'm updating XEP-0231 with that information now.

> 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

It's always good to include <img alt=':-)'/> or whatever too.

> 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.

Sounds good!


Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20080529/95c47096/attachment.bin>

More information about the Standards mailing list