[Standards] Call for Experience: Advancement of XEP-0071 (XHTML-IM) to Final

Kozlov Konstantin yagiza at yandex.ru
Mon Oct 1 16:18:01 UTC 2012


28.09.2012, 16:23, "Sergey Dobrov" <Binary at JRuDevels.org>:
> On 09/28/2012 06:35 AM, Peter Saint-Andre wrote:
>>>  Another bigger problem is smilies. It's not obvious when the
>>>  client should render smilies and when not. I'd prefer to forbid any
>>>  text-based smilies in the XHTML-IM content
>>  Some of us actually prefer textual emoticons. :)
> Actually, me too :) But them have some problems to parse here, it adds
> some extra <img> tags actually in the mark up. :) So I'd prefer client
> to replace textual smilies BEFORE send them to the network. Obviously,
> the plain text representation of a message will be unchanged.
>>  Feel free to look at the old XEP-0038 for further considerations.
>>>  but such way we really need a standardized way to attach images to
>>>  a body.
>>  IMHO that would be XEP-0231.
> Yes, it seems to be pretty good here but it will be impossible to read
> images when your competitor is offline that can be nasty. But I don't
> know how to solve the problem anyway.

The only solution I see is adding special considerations for smilies. The smilies should be converted to some special type of images to allow client on the other side translate it.
I can suggest two possible syntaxes:
1. <img /> element without "src" attribute at all, which "alt" attribute contains textual representation of the smilie, so translator either translate it and display smilie image, or display alternative text if it cannot translate (or do not want to translate it at all, eg. smilie tranlation is diabled).
2. <img /> element with "src" attribute, containing URL with special scheme (eg. "smilie:"), whith path, containing properly escaped textual representation of the smilie.

With my best regards,

More information about the Standards mailing list