[JDEV] formatting in messages

Sat Sep 2 16:18:51 CDT 2000

See: http://docs.jabber.org/jpg/refmessage.html

Rich Text
To extend messages for more "rich" text, the Jabber protocol encourages use of XHTML Basic. A plain text copy of the message should be included in the standard body so that clients that do not support XHTML Basic can still view the message. An example of using XHTML Basic is provided in the examples below. 

Example 2. Basic Jabber Message Using XHTML Basic

<message to="horatio at denmark"> 
  <body>Angels and Ministers of Grace, defend us!</body>
  <html xmlns="http://www.w3.org/TR/xhtml-basic">
    <body>
      <div style="font-size: medium; color: red; text-align: center">
        Angels and Ministers of Grace, defend us!
      </div>
    </body> 
  </html> 
</message>

--

At one point we suggested using a client feature negotiation IQ namespace, but that never really took off. I'm unsure if there plans for pushing and expanding this in the near future or not. temas?

On Sat, Sep 02, 2000 at 02:00:32PM -0700, Rob Brown wrote:
> 
> 
> (just as I was about to post this, I see Wally's fascinating Universal 
> Picture Language thing....which makes the below suggestion seem entirely 
> uninspired. :-) )
> 
> I couldn't find anything in the docs indicating whether it is allowable for 
> messages to include any sort of html-style formatting.  I understand that 
> current clients probably don't support it, but it would be nice to at least 
> account for it in the format of messages so that future clients may.  As a 
> start, say I want to put a bold or italic or something by using <b></b> 
> tags or the like.
> 
> I would expect some people would argue that instant messaging is by nature 
> instant, and therefore this is inappropriate, but IMHO that's a bit short 
> sighted.  But I don't want to start a religious debate. :)
> 
> A nice approach might be if a client was able to "publish" its display 
> capabilities, so the sender would know whether or not it is appropriate to 
> send formatted messages.  Alternatively (or in addition) the server might 
> be able to do the work of stripping out tags that less-sophisticated 
> receiving clients will not be able to display, and maybe even do some 
> "translation" for plain-text-only clients: for instance surrounding bolded 
> text with *'s or replacing excerpt bars with >'s or the like.
> 
> Any thoughts on this?  I'd guess that XHTML would be appropriate so it more 
> properly fits into an XML model.
> 
> BTW, I'm not really suggesting anyone get to work on this right away (other 
> than to possibly keep such things in mind as protocols/formats are developed).
> 
> -rob
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> 

-- 
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/1efee437/attachment-0002.pgp>