The following elements of HTML are obsolete. It is recommended that client implementors implement the obsolete forms for compatibility with old servers.
Status: Obsolete .
The empty PLAINTEXT tag terminates the HTML entity. What follows is not SGML. In stead, there's an old HTTP convention that what follows is an ASCII (MIME "text/plain") body.
An example if its use is:
<PLAINTEXT> 0001 This is line one of a ling listing 0002 file from <firstname.lastname@example.org> which is sent
This tag allows the rest of a file to be read efficiently without parsing. Its presence is an optimization. There is no closing tag. The rest of the data is not in SGML.
Status: Obsolete . This are in use and should be recognized by browsers. New servers should use <PRE> instead.
These styles allow text of fixed-width characters to be embedded absolutely as is into the document. The syntax is:
<LISTING> ... </LISTING>
<XMP> ... </XMP>
The text between these tags is to be portrayed in a fixed width font, so that any formatting done by character spacing on successive lines will be maintained. Between the opening and closing tags:
The LISTING element is portrayed so that at least 132 characters will fit on a line. The XMP elementis portrayed in a font so that at least 80 characters will fit on a line but is otherwise identical to LISTING.
Status: Obsolete . These tags like all others should be ignored if not implemented. Replaced will more meaningful elements -- see character highlighting .
<HP1>...</HP1> <HP2>... </HP2> etc.
A comment element used for bracketing off unneed text and comment has been introduced in some browsers but will be replaced by the SGML command feature in new implementations.