I just thought, we could do something along the lines of Microformats, e.g:
Hello, <span rel="emoticon" title=":-)">:D</span>.Where 'rel' signifies that it is an emoticon and 'title' is the parent of the emoticon (the fall-back). Seems to work pretty well and I don't think it will break existing clients...
Michal 'vorner' Vaner wrote:
Hello On Mon, Sep 03, 2007 at 05:32:34PM +0200, Jonathan Chayce Dickinson wrote:What you said is very true Michal, but you haven't taken it one step back.If the truth be told, these clients are processing XML. The sooner they wake up and smell the coffee and use a proper XML processing framework instead of shoddy home-grown ones, the better. There are plenty frameworks out there, just plug-n-play...<joke> Would you be so kind and plug-n-playd me one in mcabber, please? ;-) </joke>XML stands for eXtensible Markup Language, note the 'extensible', you should be able to add to it without worry for backward compatibility. The fact that their client can not support extra attributes is, in reality, a *bug*.Sure, I know. It is. Bugs are everywhere :-(. But, as you noticed, you probably need a home-grown XML syntethyzer, since you are not allowed to put many other things into the XML stream (like processing instructions). And you need at last to modify that one to handle attributes in different namespace than their tag. They need to generate and place XML namespace prefixes there, remember them, atc. As I said, your way is 100% valid and correct. But I just think the way with separate tag will cause in less effort implementing it. Is there any advantage in your way? If there is, I have no objections using it.
-- jonathan chayce dickinson ruby/c# developer cell: +27741863698 email: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] <some profound piece of wisdom>
smime.p7s
Description: S/MIME Cryptographic Signature
