- at least understand that this divides into paragraphs. Basic support for the various align types would be nice - This generally means italics
through
- The general headings, h1 is usually displayed with largest font size. Client should also understand that a /n is implied after a heading
- Client should understand this is a paragraph, and be sure to end with a
- At absolute least, translate to " and to ", so things will appear in quotes. A proper client will also understand nested quoting - Most clients should recognize this as bold - Clients should recognize at least http:// links (should they support jabber: as meaning a jabber user?), with optional support for mailto:. Relative links should be supported at the client's discresion optional, but recommended: - If the image is pointing somewhere that the client can find it, feel free to display it. This might be useful for clients which wish to be more graphical - they can ship with standard images, and somehow the UI can allow users to select them and display to each other. It is recommended that clients be able to display the alt text for images. (Not necessarily the images themselves) - this is used to designate a fragment of computer code - perhaps make this in a fixed font. It would be nice to see computer code exchanged with things like this instead of with quotations around it - Understand that this means text should be indented, and that its children, are unordered (be sure to close the 's) - Understand that this means text should be indented, and that its children, , are ordered, usually this means with numbers, optional support for type numbering styles optional: - If you want to do something special to an address and - if you wish to expand the title's of these on mouseover - "Contains a citation or a reference to other sources. " - "Indicates that this is the defining instance of the enclosed term. " - "Indicates text to be entered by the user." - pre-formatted text. If possible, do not wrap text within , as it should have its own wrapping - "Designates sample output from programs, scripts, etc." - "Indicates an instance of a variable or program argument." and its buddies and - these are used for definition lists. Not that much more useful than and ... not needed: - None of the input types or forms are needed. <table> <caption> <td> <th> <tr> - Most clients will not render tables properly, and they aren't worth the effort for an IM system <title> - This should not supercede the <message><subject> <head> - There is nothing within <head> which is needed - There is no need when we don't support styles <meta> - If your client does have a good use for this, feel free <link> - Style sheets are not supported, they are too difficult <base> - absolutely no need Styles in Jabber XHTML he purpose of this document is to define a standardized method of conveying style in jabber messages. Generally, this is expected to be used in combination with the Jabber XHTML Recommendation. These styles are based upon CSS, and are actually legal CSS. However, due to the incredible amount of effort it takes to write a full CSS parser, this document provides pre-defined classes which clients are expected to be able to understand if they claim to support jabber styles. The basic method for defining a style is by placing the attribute class inside of an element which contains other elements or text (i.e., NOT ). Clients should simply be able to understand the basics, such as Small text here. If no other element is available, clients should use to define a class (Text which changes fonts). If necessary, <div> may also be used in place of , however in most circumstances, should be used. This document is divided based upon class name. ---------- font-size-[xx-small | x-small | small | medium | large | x-large | xx-large ] http://www.w3.org/TR/REC-CSS1#font-size 'medium' should be set to whatever the default font size is that the user has set. These size names are far more universal than 'pt' or 'px' Be careful not to make IE's mistake of making 'small' the default font size. That will mess everything up. ---------- font-family-[serif | sans-serif | cursive | fantasy | monospace ] http://www.w3.org/TR/REC-CSS1#font-family Unfortunately, there's no easy way to determine which fonts are installed on other clients. If you wish to specify a specific font, the only easy way to do so is . It is recommended that clients which would like to allow specific fonts to be chosen understand at least that basic amount of CSS. Otherwise, simply use the pre-defined classes. ---------- color http://www.w3.org/TR/REC-CSS1#color This is another unfortunate case where basic parsing is required. See http://www.w3.org/TR/REC-CSS1#color-units Conformance with this document only requires a recognition of #rrggbb, aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white, and yellow. ---------- background-color http://www.w3.org/TR/REC-CSS1#background-color See color. ---------- background-image http://www.w3.org/TR/REC-CSS1#background-image This is not required for conformance with this document, but some clients may wish to use it. ---------- text-decoration-[ none | underline | overline | line-through ] http://www.w3.org/TR/REC-CSS1#text-decoration Underline and line-through are recommended. ---------- text-align-[ left | right | center | justify ] http://www.w3.org/TR/REC-CSS1#text-align This is not required for conformance with this document, but some clients may wish to use it.