[JDEV] formatting in messages

[Eliot Landrum]

On Sat, Sep 02, 2000 at 02:49:09PM -0700, Rob Brown wrote:
> At 04:18 PM 9/2/00 -0500, you wrote:
> >See: http://docs.jabber.org/jpg/refmessage.html
> 
> Guess I was looking in the wrong place, I'm surprised I missed that! (thanks)

That's what I'm here for. :)

> Sending a plain text message in addition to a formatted one seems to be an 
> awkward compromise to keep legacy systems still working, which isn't nearly 
> as necessary in Jabber as it was with email. 

Just a quick note here.. clients that don't support XHTML Basic are not "legacy" systems. No client should be forced to support anything more than they don't want to. Think of a CLI client that really has no use for XHTML (perhaps some, but not much). 

> I think it would be better to 
> only send the plain text one *unless* we know the client supports rich 
> text, and then send only the rich text one.

This presents problems. What if I'm offline and you can't "grep" my client to see if I support XHTML Basic? Or probably more likely, what if I'm online with two clients, one that does support XHTML Basic and one that doesn't. Now if I have the XHTML Basic client's resource as a top priority, your client would just send messages to me in XHTML Basic and not have plain text messages. The problem comes in when my XHTML Basic client suddenly goes offline. Now my plain text client is stuck with a blank message that it can't read. The point is that we're trying for maximum flexibility.

-- 
Eliot Landrum
eliot at landrum.cx
GnuPG ID: 8F5B499E

-Soli Deo Gloria-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20000902/99b7088c/attachment-0002.pgp>