-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathNonStandard.html
More file actions
executable file
·113 lines (80 loc) · 3.28 KB
/
NonStandard.html
File metadata and controls
executable file
·113 lines (80 loc) · 3.28 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
<!DOCTYPE HTML PUBLIC "-//W3O//DTD WWW HTML 2.0//EN">
<HTML>
<HEAD>
<TITLE>Obsolete Elements of HTML</TITLE> <NEXTID
N="z61"></HEAD>
<BODY>
<H1>Obsolete elements</H1>
<P>The following <A HREF="Tags.html" NAME="z57">elements of HTML</A>
are obsolete. It is recommended that client implementors implement
the obsolete forms for compatibility with old servers.
<H3><A NAME="PLAINTEXT.index">Plaintext</A></H3>
<P>Status: <A HREF="StatusMeanings.html#z8"
NAME="z59">Obsolete</A>.
<P>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.
<P>An example if its use is:
<PRE> <A HREF="HTML.dtd.html#z35" NAME="z53"><PLAINTEXT></A>
0001 This is line one of a ling listing
0002 file from <any@host.inc.com> which is sent
</PRE>
<P>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.
<H3><A NAME="XMP.index">XMP</A> and <A
NAME="LISTING.index">LISTING</A>: <A NAME="z8">Example sections</A></H3>
<P>Status: <A HREF="StatusMeanings.html#z8"
NAME="z60">Obsolete</A>. This are in use and should be recognized
by browsers. New servers should use <A
HREF="#z31" NAME="z35"><PRE></A> instead.
<P>These styles allow text of fixed-width characters to be embedded
absolutely as is into the document. The syntax is:
<PRE> <LISTING>
...
</LISTING>
</PRE>
<P>or
<PRE> <XMP>
...
</XMP>
</PRE>
<P>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:
<UL>
<LI>The text may contain any ISO Latin printable characters,
but not the end tag opener. (See <A
REL="SUBDOCUMENT" HREF="LiteralHistory.html"
NAME="z50">Historical note</A> )
<LI>Line boundaries are significant, except any occurring immediately
after the opening tag or before the closing tag.
and are to be rendered as a move to the start of a new line.
<LI>The ASCII Horizontal Tab (HT) character must be interpreted
as the smallest positive nonzero number of spaces which will
leave the number of characters so far on the line as a multiple
of 8. Its use is not recommended however.
</UL>
<P>The <A NAME="z51">LISTING</A> element is portrayed so that
at least 132 characters will fit on a line.
The <A NAME="z22">XMP </A>
elementis portrayed in a font so that at least 80 characters
will fit on a line but is otherwise identical to LISTING.
<H3>Highlighted Phrase HP1 etc</H3>
<P>Status: <A HREF="StatusMeanings.html#z4"
NAME="z52">Obsolete</A>. These tags like all others should be
ignored if not implemented. Replaced will more meaningful elements
-- see <A HREF="Highlighting.html" NAME="z39">character highlighting</A>
.
<H4>Examples of use:</H4>
<PRE> <HP1>...</HP1> <HP2>... </HP2> etc.
</PRE>
<H3>Comment element</H3>
<P>Status: <A HREF="StatusMeanings.html#z8"
NAME="z58">Obsolete</A>
<P>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.
</BODY>
</HTML>