l9g$K$O!"$=$NJ8=q$N(JURL$B$,;HMQ$5$l$k$Y$-$G$9!#J8=q$KH<$C$F$$$k(JHTTP$B%X%C%@$K$h$C$F4pHW(JURL$B$,>e=q$-$5$l$k$+$b$7$l$J$$$?$a!"$3$l$O$=$NJ8=q$r5a$a$k$N$K;H$o$l$?(JURL$B$HI,$:$7$bF1$8$b$N$G$"$kI,MW$O$J$$$3$H$KCm0U$7$F$/$@$5$$!#(J
In the absence of a BASE element the document URL should
be used. Note that this is not necessarily the same as the URL used to
request the document, as the base URL may be overridden by an HTTP
header accompanying the document.
<!ELEMENT META - O EMPTY -- $B0lHLA0CV$->pJs!!(JGeneric Metainformation --> <!ATTLIST META http-equiv NAME #IMPLIED -- HTTP$B1~Ez%X%C%@L>!!(JHTTP response header name -- name NAME #IMPLIED -- $BA0CV$->pJsL>!!(Jmetainformation name -- content CDATA #REQUIRED -- $B4XO">pJs!!(Jassociated information -- >
META$BMWAG$r;H$C$F!"Cx HTTP-EQUIV $BB0@-$O(JNAME $BB0@-$NBe$o$j$K;HMQ$9$k$3$H$,$G$-$^$9!#$3$NB0@-$O!"D61[=qN`E>Aw%W%m%H%3%k!J(JHTTP$B!K$K$h$C$FJ8=q$r $B$H$9$k$H!"(JHTTP$B%X%C%@$O
will result in the HTTP header:
$B$3$l$O!"4X78$7$F$$$kJ8=q$N?7$7$$%3%T!<$r$$$D LINK $B$OB>$NJ8=q$H%j%=!<%9$H$N4X78$rDj5A$9$k$?$a$N!"%a%G%#%"$+$iFHN)$7$?J}K!$rM?$($k$b$N$G$9!#(J
LINK $B$OHs>o$KAa$$;~4|$+$i(JHTML$B$K LINK $BMWAG$N4pK\E*$J;HMQK!$O(J $BDs0F$5$l$?4X78$NCM$K$O
Here are some proposed relationship values:
LINK$BMWAG$NNc(J
$B$3$3$K$OJ8=q$NK\J8$,F~$j$^$9!#(JBODY$B$N3+;O%?%0$H=*N;%?%0$O>JN,$9$k$3$H$,$G$-$^$9!#K\J8$K$OI}9-$$MWAG$,4^$^$l$^$9!#(J $B $BNc!!(JExample:
$B?'$O(J16$B?JK!$N?t;z!J(J COLOR= $B!X(J #C0FFC0 $B!Y$J$I!K$H$7$F!"0?$$$O!"9-$/CN$i$l$F$$$k(J16$B$N?'L>A0$N#1$D$H$7$F!"(JsRGB$B?'6u4V$GM?$($i$l$^$9!#(J
$B$3$l$i$N?'$O85!9!"%&%#%s%I%&%:(J VGA $B%Q%l%C%H$,07$&I8=`(J16 $B?'$H$7$FA*$P$l$F$$$?$b$N$G$9!#(J $BJ8=q$NK\J8$K=P$F$/$kMWAG$NBgH>$O!"Fs$D$N%0%k!<%W$KJ,$1$i$l$^$9!#0l$D$OCJMnJ,$1$r$9$k$^$H$aMWAG$G!"$b$&0l$D$O$=$l$r$7$J$$J8>OMWAG$G$9!#0lHLE*$J$^$H$aMWAG$H$7$F$O!"(JH1$B!A(JH6$B!'8+=P$7!"(JP$B!'CJMn!"(JLI$B!'0lMw9`L\!"(JHR$B!'?eJ?@~$J$I$,$"$j$^$9!#0lHLE*$JJ8>OMWAG$H$7$F$O!"(JEM$B!&(JI$B!&(JB$B!&(JFONT$B!';z$N6/D4!"(JA$B!'D6O":?!"(JIMG$B!&(JAPPLET$B!'Kd$a9~$_BP>]J*!"(JBR$B!'2~9T$J$I$,$"$j$^$9!#J8>OMWAG$,3g$j9~$a$k$N$OB>$NJ8>OMWAG$@$1$J$N$KBP$7$F!"$^$H$aMWAG$O0lHLE*$K!"J8>OMWAG$dB>$N$^$H$aMWAG!J8+=P$7$H08@h$r=|$/!K$r3g$j9~$`$h$&$KF/$/$3$H$KCm0U$7$F$/$@$5$$!#@5$7$$7?$OMWAG$K$h$C$FJQ$o$j$^$9!#(J H1,H2,H3,H4,H5,H6$B$OJ8=q$N8+=P$7$H$7$F;H$o$l$^$9!#>o$K3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#(JH1$BMWAG$O(JH2$BMWAG0J2<$h$j$b=EMW$G!"(JH6$BMWAG$O8+=P$7$H$7$F$N=EMW@-$,:GDc$N$b$N$H$J$j$^$9!#$h$j=EMW$J8+=P$7$O0lHLE*$K$=$l0J2<$N$b$N$h$jBg$-$J3h;z$GI=<($5$l$^$9!#DI2C$G$-$kB0@-$H$7$F!"8+=P$7$N0LCV7h$a$r$9$k(JALIGN$B$,$"$j!"
H1, H2, H3, H4,
H5 and H6 are used for document headings. You
always need the start and end tags. H1 elements are more
important than H2 elements and so on, so that
H6 elements define the least important level of headings.
More important headings are generally rendered in a larger font than
less important ones. Use the optional ALIGN attribute to
set the text alignment within a heading, e.g.
$B0LCV7h$a$r>JN,$9$k$H:8B7$($H$J$j$^$9$,!"$3$l$O(JDIV$BMWAG$+(JCENTER$BMWAG$G ADDRESS$BMWAG$O3+;O%?%0$H=*N;%?%0$rI,MW$H$7!"86Cx:n $BNc!!(JExample:
P$BMWAG$OCJMn$r@_$1$k$N$K;H$$$^$9!#$3$l$OMF$lJ*$G!"3+;O%?%0$,I,MW$G$9!#=*N;%?%0$O>o$K8lK!2r@O$K$h$C$FJd40$5$l$k$N$G!">JN,$G$-$^$9!#%f!<%6%(!<%8%'%s%H$O(JP$BMWAG$rCJMnJ,$1$9$Y$-$G$9!# $BNc!!(JExample:
$BCJMn$OIaDL!":8C<$rB7$(!"1&C<$KIT5,B'$JM>Gr$rIU$1$FI=$o$5$l$^$9!#!JLuCm!'1QJ8$G$OC18l$rESCf$G@Z$i$:$K=q$/$N$G!"2~9T$N0LCV$,8l$K$h$C$FJQ$o$j!"1&C<$,FL1z$K$J$j$^$9!#K.J8$G$O$I$3$G@Z$C$F$b9=$o$J$$$N$G!"1&C<$KIT5,B'$JM>Gr$,$D$/$3$H$O$"$j$^$;$s!K(JALIGN$BB0@-$r;H$&$H
Paragraphs are usually rendered flush left with a ragged right
margin. The ALIGN attribute can be used to explicitly
specify the horizontal alignment:
For example:
ALIGN$BB0@-$r>JN,$9$k$H:84s$;$K$J$j$^$9$,!"$3$l$O(JDIV$BMWAG$+(JCENTER$BMWAG$G>e=q$-$G$-$^$9!#(J $B0lMw9`L\$K$O$^$H$aMWAG$HJ8>OMWAG!"$5$i$KF~$l;R$K$7$?0lMw$,F~$l$i$l$^$9!#$?$@$7!"8+=P$7MWAG$H1|IUMWAG$O=|$-$^$9!#$3$N@)8B$O(J%flow$B $B=gITF10lMw$O <UL>
<LI> ...$B!!:G=i$N0lMw9`L\$G$9(J first list item
<LI> ...$B!!FsHVL\$N0lMw9`L\$G$9(J second list item
...
</UL>
UL$BMWAG$O=gITF10lMw$K;H$$$^$9!#3+;O%?%0$H=*N;%?%0$,>o$KI,MW$G$9!#(JLI$BMWAG$O3F!9$N9`L\$K;H$$$^$9!#(JLI$BMWAG$N=*N;%?%0$O>o$K>JN,$G$-$^$9!#(JLI$BMWAG$NCf$K0lMw$rF~$l;R$K$G$-$k$3$H$r3P$($F$*$$$F$/$@$5$$!#(JCOMPACT$BB0@-$N;HMQ$K$h$j!"%f!<%6%(!<%8%'%s%H$K0lMw$rC;=L7A$GI=<($9$k$h$&;X<($9$k$3$H$,$G$-$^$9!#(J UL $BMWAG$H(J LI $BMWAG$G$O!"(JTYPE $BB0@-$r;HMQ$7$F!"9`L\$N@hF,$KIU$1$kE@$N7A$r@_Dj$9$k$3$H$,$G$-$^$9!#CM$H$7$F;H$($k$N$O!"9u4]!&;M3Q!&Gr4]$N(J3$B$D$G$9!#(JTYPE $BB0@-$r>JN,$7$?>l9g$O0lHLE*$K!"F~$l;R$K$7$?=g=x$GJQ2=$7$^$9!#(J $B$3$N0lMw$O!"(J1993$BG/$K(JMosaic$B$G;HMQ$5$l$?9`L\5-9f$N867?$K@09g$9$k$h$&$KA*$P$l$?$b$N$G$9!#(J $B=xNs!JHV9fIU$-!K0lMw$O
Ordered (i.e. numbered) lists take the form: OL$BMWAG$G$O(JSTART$BB0@-$r;H$C$FHV9f$r2?HV$+$i;O$a$k$+@_Dj$9$k$3$H$,$G$-$^$9!#(JSTART$BB0@-$r>JN,$9$k$H(J1$BHV$+$i;O$^$j$^$9!#$3$l$r8e$+$i(JLI$BMWAG$N(JVALUE$BB0@-$G@_Dj$9$k$3$H$b$G$-$^$9!#$I$A$i$NB0@-$bCM$K@0?t$r;XDj$9$k$h$&$K$7$F$/$@$5$$!#$=$NA0$N0lMw$+$iB3$1$FHV9f$r?6$k$H$+!"HV9f$N$D$$$F$$$J$$$b$N$rHt$P$9$H$+$N;XDj$r$9$k$3$H$O$G$-$^$;$s!#(J COMPACT$BB0@-$N;HMQ$K$h$j!"%f!<%6%(!<%8%'%s%H$K0lMw$rC;=L7A$GI=<($9$k$h$&;X<($9$k$3$H$,$G$-$^$9!#(JOL$BMWAG$N(JTYPE$BB0@-$K$h$j!"HV9f$NI=<(7ABV$r@_Dj$9$k$3$H$,$G$-$^$9!#(J $BDj5A0lMw$O <DL>
<DT> $BMQ8l!!(Jterm name
<DD> $BMQ8l$NDj5A!!(Jterm definition
...
</DL>
DT$BMWAG$O!"J8>OMWAG$r $BNc$($P!!(JFor example:
$B$3$l$O
DL$BMWAG$X$N(JCOMPACT$BB0@-$NDI2C$K$h$j!"%f!<%6%(!<%8%'%s%H$K0lMw$rC;=L7A$GI=<($9$k$h$&;X<($9$k$3$H$,$G$-$^$9!#(J $B$3$NFs$D$NMWAG$O8E$/$+$i(JHTML$B$KAH$_9~$^$l$F$$$?$b$N$G$9!#$3$l$O(JUL$BMWAG$K;w$?=gITF10lMw$N$?$a$KMQ0U$5$l$F$$$^$9!#%f!<%6%(!<%8%'%s%H$O!"(J DIR $BMWAG$rCJAH$_$7$?3,AX0lMw$H$7$F!"(J MENU $BMWAG$rC1CJ$N8%N)$H$7$FI=$o$9$3$H$,4+$a$i$l$^$9!# PRE$BMWAG$r;H$&$H3d$jIU$1:Q$_J8>O$r SGML $BI8=`$,!"(J $B8lK!2r@O$K$*$$$F!"3+;O%?%0D>8e$"$k$$$O=*N;%?%0D>A0$N2~9T$r0z$-H4$/$h$&L?$8$k$3$H$KCm0U$7$F$/$@$5$$!#(J PRE $B$NFbMF$O!"CJMn$+$i%$%a!<%8$H%U%)%s%H%5%$%:$NJQ2=$r0z$-5/$3$9MWAG!"Nc$($P(JIMG $B!&(J BIG $B!&(J SMALL $B!&(J SUB $B!&(J SUP $B!&(J FONT $B$J$I$r=|30$7$?$b$N$KAjEv$7$^$9!#(J $B%f!<%6%(!<%8%'%s%H$NCf$K$O!"(J WIDTH $BB0@-$r07$&$b$N$,$"$j$^$9!#$3$l$OI,MW$H$5$l$k;z$N2#I}$K4X$9$k%R%s%H$r%f!<%6%(!<%8%'%s%H$KM?$($k$b$N$G$9!#%f!<%6%(!<%8%'%s%H$O$3$l$r;H$C$F!"E,@Z$J%U%)%s%H%5%$%:$rA*Br$9$k$+!"FbMF$rE,Ev$K;z2<$2$9$k$3$H$,$G$-$^$9!#(J PRE$BMWAG$NNc$r
Here is an example of a PRE element; a verse from
Shelley (To a Skylark):
$B?eJ?%?%VJ8;z!J(JUnicode,$BJF9q%"%9%-!<(J,$B9q:]I8=`2=5!9=(J 8859-1$B$N==?JK!#9HV$H$7$FId9f2=$5$l$F$$$k!K$O(J0$B$G$J$$:G>.$N?t$rC10L$H$9$k6uGr$H2r$NCM$K@_Dj$7$F$$$k$H!"J8=q$N3d$jIU$1$rB;$J$&$3$H$,$h$/$"$k$?$a$K!"$=$N;HMQ$OHs>o$KK>$^$7$/$J$$$b$N$G$9!#(J $B$3$l$i$O(JPRE$B$NF3F~0JA0$K$"$C$?3d$jIU$1:Q$_J8>O$N$?$a$N%?%0$G$7$?$,!":#$G$O;H$o$l$F$$$J$$$b$N$G$9!#%f!<%6%(!<%8%'%s%H$O!"5lHG$H$N8_49@-$N$?$a$K$3$l$i$r07$C$F$+$^$$$^$;$s!#?7$7$$J8=q$r=q$/:]$K$O!"$3$l$i$NMWAG$N;HMQ$OHr$1$J$/$F$O$J$j$^$;$s!#(J DIV $BMWAG$N;HMQ$K$h$j!"(JHTML $BJ8=q$r3FItJ,$+$i$J$k%T%i%_%C%I9=B$$H$7$F9=@.$9$k$3$H$,$G$-$^$9!#(JALIGN$BB0@-$N;HMQ$K$h$j!"(J DIV $BMWAG$NFbMF$r@0Ns$9$k$3$H$,$G$-$^$9!#$=$NCM$O:8$+Cf1{$+1&$N$$$:$l$+$G$9!#$3$l$OCJMnMWAG(J<P>$B$HF1$8Dj5A$N;EJ}$G$9!#(J DIV $B$O$^$H$aMWAG$HF1MM$NF/$-$r$9$k$b$N$J$N$G!"3+$$$F$$$k(J P $BMWAG$r(JDIV$B$,JD$8$k$3$H$KCm0U$7$F$/$@$5$$!#(J
$B$3$l$K2C$($F%f!<%6%(!<%8%'%s%H$O!"(JDIV $BMWAG$rCJMnJ,$1$9$k$3$H$r5a$a$i$l$F$$$^$;$s!#(J
CENTER$B$O(J ALIGN=CENTER $B$r;}$D(J DIV $B$KA4$/Ey$7$$$b$N$G$9!#(J
DIV $B$H(JCENTER$B$O$I$A$i$b3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#(J CENTER$B$O%M%C%H%9%1!<%W $B$3$l$OB>$N:nIJ$+$i$N0zMQItJ,$r3g$j9~$`$?$a$K;HMQ$5$l$^$9!#(J
$B3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#(J
$BB?$/$N>l9g$O;z2<$2$7$FI=<($5$l$^$9!#$?$H$($P!"(J from "The Two Towers" by J.R.R. Tolkien.
$B$3$l$O(J HTML $B=q<0$rDj5A$9$k$?$a$K;HMQ$5$l$^$9!##1$D$NJ8=q$KJ#?t$N=q<0$rCV$/$3$H$,$G$-$^$9!#(J
$B3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#(J
$BHs>o$KC1=c$J=q<0$K$O!"(JISINDEX $BMWAG$r;H$&$3$H$b$G$-$^$9!#(J
$B=q<0$K$O!"0l9T$^$?$OB??t9T$N=q$-9~$_Ms$d%i%8%*%\%?%s%0%k!<%W$d%A%'%C%/>#$d%a%K%e!<$J$I$N$h$&$J(J$B=q<0F~NOMs(J$B$r4^$`9-HO$J(J HTML $BI=5-$rF~$l$k$3$H$,$G$-$^$9!#(J $B=q<0$N $B2#7S@~$O9`L\$NJQ2=$rI=<($9$k$?$a$K;HMQ$7$F$+$^$$$^$;$s!#(J
$BFI$_>e$2<0$N%f!<%6%(!<%8%'%s%H$G$O!"7S@~$r5Y;_$H$7$FI=$9$3$H$,$G$-$^$9!#(J HR$B$OMF$lJ*$G$O$J$$$N$G!"=*N;%?%0$O=P$F$-$^$;$s!#B0@-$O(JALIGN, NOSHADE, SIZE ,WIDTH $B$G$9!#(J HTML 3.2 $B$K$O(JRFC 1942$B$GM?$($i$l$?;EMM=q$N9-HO$KIa5Z$7$?%5%V%;%C%H$,AH$_9~$^$l$F$*$j!"$3$l$r;H$C$FI=$rAH$s$@$j%l%$%"%&%H8z2L$rI=5-$7$?$j$9$k$3$H$,$G$-$^$9!#(J
$BFI$_>e$2<0$"$k$$$OJ8>O$N$_$r07$&%f!<%6%(!<%8%'%s%H$G$O!"FC$K8e $BI=AH$N0lHLE*$J7A$O
Tables take the general form:
TABLE $B$NB0@-$O!"A4$F%*%W%7%g%J%k$G$9!#(J
$B;XDj$r>JN,$9$k$H!"I=$O30OH$J$7$GI=<($5$l$^$9!#(J
$BI=$O0lHLE*$K!"<+F0E*$KFbMF$K8+9g$C$?Bg$-$5$K:n$i$l$^$9$,!"(J WIDTH $BB0@-$r;H$C$FI=$N2#I}$rDj$a$k$3$H$b$G$-$^$9!#(J
BORDER $B$H(J CELLSPACING $B$H(J CELLPADDING $B$OI=$N304Q$K$D$$$F$5$i$K>\:Y$J4IM}$r$9$k$b$N$G$9!#(J
$BI=Bj$O(J ALIGN $BB0@-$K$h$jI=$N:G>eIt$+:G2 $BI=$N3F9T$O(JTR$BMWAG$KF~$j$^$9!#(JTR$BMWAG$N=*N;%?%0$O>o$K>JN,2DG=$G$9!#I=$NOH$O%G!<%?$N$?$a$N(JTD$BMWAG$H8+=P$7$N$?$a$N(JTH$BMWAG$GDj5A$7$^$9!#(JTR$BF1MM!"MF$lJ*$G$9$,=*N;%?%0$O>JN,2DG=$G$9!#(JTH$B$H(JTD$B$G$O0J2<$N$h$&$JB0@-$r;}$D$3$H$,$G$-$^$9!#OHFb$NFbMF$r@0Ns$9$k(JALIGN$B$H(JVALIGN$B!"J#?t$N9T$^$?$ONs$r$^$?$0(JROWSPAN$B$H(JCOLSPAN$B!#OHFb$K$O!"=q<0F~NOMs$dB>$NI=AH$r4^$`!"9-HO$JB>$N$^$H$aMWAG$dJ8>OMWAG$rF~$l$k$3$H$,$G$-$^$9!#(J TABLE$BMWAG$O>o$K3+;O%?%0$H=*N;%?%0$NN>J}$,I,MW$G$9!#$3$l$O0J2<$NB0@-$r;}$A$^$9!#(J CAPTION$BMWAG$OM#0l$NB0@-$G$"$k(JALIGN$B$r;}$A!"$3$l$O(JALIGN=TOP$B$+(JALIGN=BOTTOM$B$N$$$:$l$+$H$J$j$^$9!#$3$l$r;H$&$H!"I=Bj$rI=$N:G>eIt$N>e$+:G2 TR$B$dI=$N9T$K$J$kMWAG$K$O3+;O%?%0$,I,MW$G$9$,!"=*N;%?%0$O>o$K>JN,2DG=$G$9!#(JTR$B$O!"I=$NOH$r3g$kMF$lJ*$G$9!#0J2<$NFs$D$NB0@-$rDI2C$G$-$^$9!#(J $BI=$NOH$rDj5A$9$kMWAG$OFs$D$"$j$^$9!#8+=P$7$K;H$&(JTH$B$H9`L\$K;H$&(JTD$B$G$9!#$3$N;H$$J,$1$,%f!<%6%(!<%8%'%s%H$K8+=P$7$H9`L\$H$r0[$J$C$?3h;z$GI=<($9$k$3$H$r2DG=$K$7!"2;@ $BI=AH$OIaDL!"@u$$Ib$-D&$j$GI=<($5$l!"30OH$, e$,$C$F$$$F!"OH$N0l$D0l$D$,$3$N@9$j>e$,$C$?I=LL$KF~$j$^$9!#FbMF$,$"$kOH$K$@$18D!9$NOH@~$,0z$+$l$^$9!#(J $B0J30$N6uGr$O!"OH@~$r0z$/$Y$-BP>]$K$O$J$j$^$;$s!#(J $BI=AH$NBg$-$5$r<+F0D4@0$9$k%"%k%4%j%:%`$O!"$=$l$>$l$NOH$KI,MW$J:G>.I}$H:GBgI}$r7W;;$9$Y$-$G$9!#$3$l$O3FNs$KI,MW$J:G>.I}$H:GBgI}$r7h$a!"$=$l$K$h$C$FI=A4BN$GI,MW$J:G>.I}$H:GBgI}$r7h$a$k$?$a$G$9!#(J $BOH$,J#?t$NNs$r$^$?$0$H$-$O!"3F!9$NNsI}$r9g$o$;$F9=@.$9$k$3$H$K$J$j$^$9!#(J
$B#1$D$NJ}K!$H$7$F$O!"$3$l$i$NNs$N4V$GOH$N:G>.I}$H:GBgI}$rJ?Ey$KG[J,$7$^$9!#(J
$BJL$NJ}K!$G$O!"J#?t$NNs$r$^$?$,$i$J$$B>$NOH$N9=@.$K=>$&$h$&$JG[J,$r=E$s$8$^$9!#(J $B%f!<%6%(!<%8%'%s%H$NCf$K$O8@MU$NHO0OFb$G9T$r2~$a$k$3$H$,I,MW$+!"K>$^$7$$$+$b$7$l$J$$$b$N$,$"$j$^$9!#(J
$B$=$N$h$&$J%1!<%9$G$O$3$l$,8+$+$1>e$N>c32$r0z$-5/$3$7$?$H$$$&Js9p$,$"$j$^$9!#(J $BF~$l;R$K$5$l$?I=$G$O!"I=$N:G>.I}$H:GBgI}$,!"$=$NCf$KF~$kOH$N:G>.I}$H:GBgI}$K$J$j$^$9!#(J
$B$$$A$P$s30B&$NI=$KI,MW$JI}$,$o$+$l$P!"I=$NNsI}$r3d$jEv$F$k$3$H$,$G$-$^$9!#(J
$B$3$l$K$h$C$FF~$l;R$K$5$l$?I=$NI}!"$5$i$K$=$NCf$K$"$kI=$NNsI}$r3d$jEv$F$k$3$H$,$G$-$k$h$&$K$J$j$^$9!#(J
$B $BI}$H9b$5$r<($9%T%/%;%kCM$O%9%/%j!<%s%T%/%;%k$r;2>H$9$k$?$a!"%l!<%6!<%W%j%s%?$N$h$&$JHs>o$K9b$$2rA|EY$N5!4o$GIA $B$3$l$i$OCJMnJ,$1$r$7$^$;$s!#J8>OMWAG$OJ8;zAH$r7h$a$k$b$N$G!"0lHLE*$KF~$l;R2DG=$G$9!#B>$NJ8>OMWAG$rF~$l$k$3$H$,$G$-$^$9$,!"$^$H$aMWAG$rF~$l$k$3$H$O$G$-$^$;$s!#(J $B$3$l$i$O$9$Y$F3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#$?$H$($P(J $BJ8>OMWAG$O=g=x@5$7$/F~$l;R$K$7$J$1$l$P$J$j$^$;$s!#
Text level elements must be properly nested - the following
is in error:
$BMxMQ$G$-$k%U%)%s%H$,@)8B$5$l$F$$$k>l9g$d2;@<=PNO$G$O!"6/D4ItJ,$r6hJL$7$FI=8=$9$kBe$o$j$NJ}K!$,;HMQ$5$l$k$Y$-$G$9!#(J $BCm0U!'(JHTML$B$NMh$k$Y$-HG$G$O!"(JSTRIKE$B$O(JHTML 3.0$B$N(J"S"$B$KCV$-49$($i$l$k$+$b$7$l$^$;$s!#(J $B$9$Y$F3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#(J FORM$BMWAG$NCf$KF~$l$i$l$k$N$O(JINPUT,SELECT,TEXTAREA$B$N;0$D$@$1$G$9!#(JINPUT$B$r;H$C$F!"0l9T$N5-F~Ms$d%Q%9%o!<%I5-F~Ms$d%A%'%C%/>#$d%i%8%*%\%?%s!"Aw?.%\%?%s$d INPUT$BMWAG$OMF$lJ*$G$O$J$$$N$G!"=*N;%?%0$O=P$F$-$^$;$s!#(J $BCm0U!!(JNote: $B2hA|:BI8$N;HMQ$OJ8;zNs$N$_$rI=<($9$k%F%-%9%H%V%i%&%6$d2;@<7?%V%i%&%6$G$O$[$H$s$I$N>l9gLdBj$r0z$-5/$3$7$^$9!#(J SELECT$B$O!"J#?t$NIJ=q$+$i0l$DA*$V$+J#?tA*Br$G$-$k8%N)$rDj5A$9$k$N$K;H$$$^$9!#(JSELECT$BMWAG$K$O3+;O%?%0$H=*N;%?%0$,I,MW$G!"FbMF$K$O8%N)$NIJL\$rDj5A$9$k0l$D0J>e$N(JOPTION$BMWAG$,F~$j$^$9!#J#?t$NIJ=q$+$i0l$D$rA*Br$9$k>l9g$O0lHLE*$K3]<4<08%N)$H$7$FI=<($5$l!"J#?t$NIJ=q$+$iJ#?tA*Br$9$k>l9g$O0lHLE*$K0lMwI=$H$7$FI=<($5$l$^$9!#(J $BNc!!(JExample:
SELECT$B$NB0@-!!(JSELECT attributes:
$BDI2C$G$-$kB0@-!!(JOPTION attributes:
TEXTAREA$BMWAG$O3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#MWAG$NFbMF$O!"J8>O$HJ8;z $BNc!!(JExample:
$B%f!<%6%(!<%8%'%s%H$O!"=q$-9~$^$l$?FbMF$rAw?.$7$F$$$k$H$-!"(J CR$B$d(JLF$B!J%"%9%-!<==?JK!(J13,10$BHV!K$K9T=*;_$rEv$F$O$a$k$3$H$,?dA&$5$l$^$9!#(J
$BB>$NJ8;z%;%C%H$r07$&$3$H$,$G$-$k$H$$$&$3$H$r%5!<%P$,A0$b$C$F<($7$?$N$G$J$$8B$j!"Aw?.$5$l$?%G!<%?$N$?$a$NJ8;z%;%C%H$O!"9q:]I8=`2=5!9=%i%F%s(J1$BJ8;z%3!<%I$G$"$k$Y$-$G$9!#(J A (Anchor), IMG,
APPLET, FONT,
BASEFONT, BR
and MAP.
$BIE$OF~$l;R$K$9$k$3$H$O$G$-$^$;$s!#>o$K3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#(J
$BD61[=qN`$NO":?$rDj5A$7!"$^$?D61[=qN`$NO":?@h$H$7$F;H$o$l$kHVCOI=<($H$b$J$j$^$9!#Nc$($P(J $B
and also to define named locations for use as targets for hypertext
links, e.g.
$B2hA|$rA^F~$7$^$9!#(J
IMG $B$O6u$NMWAG$J$N$G!"=*N;%?%0$O=P$F$-$^$;$s!#(J
$B2hA|$O$=$N;~$N9T$KBP$7$F?bD>$KCV$+$l$k$+!":8$+1&$K2s$j9~$^$;$k$3$H$,$G$-$^$9!#(J
$BJ8>ON.$79~$_$N4IM}$N$?$a$K(J CLEAR $BB0@-$r;}$D(J BR $B$r8+$F$/$@$5$$!#(J IMG$BMWAG$K$O0J2<$NB0@-$,$"$j$^$9(J $B%V%i%&%6$NCf$K$O:8$d1&$KG[CV$5$l$k2hA|$KBP$7$F0l;~E*$J6uGr$r$D$/$k$b$N$,$"$k$3$H$KCm0U$7$F$/$@$5$$!#(J
$B7k2L$H$7$F!"0[$J$k%Y%s%@$+$i=P$5$l$F$$$k%V%i%&%64V$GF1$8F0:n$r4|BT$9$k$3$H$O$G$-$^$;$s!#(J
$BJ8>ON.$79~$_$N@)8f$N$7$+$?$O(JBR$B$r8+$F$/$@$5$$!#(J $B$3$3$K(JISMAP$B;HMQK!$NNc$,$"$j$^$9(J $B%/%j%C%/$5$l$?0LCV$O!" $B%T%/%;%kCM$O%9%/%j!<%s%T%/%;%k$r;2>H$9$k$?$a!"%l!<%6!<%W%j%s%?$N$h$&$JHs>o$K9b$$2rA|EY$N5!4o$GIA $B3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#(J
$B$3$NMWAG$O!"A4$F$N(J Java $BBP1~%V%i%&%6$K$h$C$F07$o$l$^$9!#(J
$B$3$l$K$h$C$F!"(J HTML $BJ8=q$K(J Java $B%"%W%l%C%H$rKd$a9~$a$k$h$&$K$J$j$^$9!#(J
APPLET $B$O%"%W%l%C%H$KJQ?t$rEO$9$?$a$K7k$SIU$$$F$$$k(JPARAM$BMWAG$r;H$$$^$9!#(J
PARAM $BMWAG$N8e$K$/$k(J APPLET $BMWAG$NFbMF$K$O!"(JJava $B$r07$o$J$$%f!<%6%(!<%8%'%s%H$N$?$a!"%"%W%l%C%H$NBe$o$j$K$J$k$b$N$rMQ0U$7$F$*$/$Y$-$G$9!#(J
$B$3$l$O(J DTD $B$G(J %text $B $B$3$3$K4JC1$J(JJava$B%"%W%l%C%H$NNc$,$"$j$^$9(J $B$3$3$K(JPARAM$BMWAG$r;H$&JL$NNc$,$"$j$^$9(J
PARAM$BMWAG$O%"%W%l%C%HFC@-JQ?t$r;XDj$9$kM#0l$NJ}K!$G$9!#%"%W%l%C%H$O(J getParameter()$B%a%=%C%I$G$NJQ?t$KBP$9$kMxMQ é$B$d(J¹$B$J$I$H$$$C$?(JSGML$B;z $BCm0U!!(JNote: PARAM$BMWAG$O(JAPPLET$BMWAG$NFbMF$N:G=i$KCV$+$l$k$Y$-$G$9!#$3$l$O(JSGML$B:.9gFbMF7ABV$K$*$1$k@lLgE*;v9`$N0Y$N(J DTD$B$N0lIt$H$7$F$O;XDj$5$l$F$$$^$;$s!#(J $B3+;O%?%0$H=*N;%?%0$,I,MW$G$9!#(J
$B$3$l$G $B%f!<%6%(!<%8%'%s%H$NCf$K$O!"M%@h=g$K%3%s%^$G6h@Z$i$l$?3h;zL>$N0lMw$rA0$N$b$N$rC5$7$F$-$^$9!#(J
FACE $B$O(J HTML 3.2 $B$K$O$"$j$^$;$s!#(J
$B0J2<$K3h;z$NBg$-$5$r@dBP;XDj$7$?7k2L$r<($7$^$9(J size=1
size=2
size=3
size=4
size=5
size=6
size=7
$B0J2<$K4pK\E*$J3h;z$NBg$-$5$r(J3$B$H$7$?>e$GAjBP;XDj$7$?7k2L$r<($7$^$9(J $B4pK\E*$J3h;z$NBg$-$5$r(J6$B$H$7$FF1$8;XDj$r$7$?7k2L$G$9(J $B3h;z$N4pK\E*$JBg$-$5$r@_Dj$7$^$9!#(JBASEFONT$B$O6uMWAG$J$N$G!"=*N;%?%0$O=P$F$-$^$;$s!#(JSIZE$BB0@-$O(J1$B$+$i(J7$B$^$G$N@0?t$rCM$K $B6/@)2~9T$rF~$l$^$9!#$3$l$O6uMWAG$J$N$G!"=*N;%?%0$O=P$F$-$^$;$s!#(JCLEAR $BB0@-$r;H$C$F!"2s$j9~$^$;$?2hA|$NN>OF$KM>Gr$r$H$k$3$H$,$G$-$^$9!#(J<BR CLEAR=LEFT>$B$GD>A0$N2s$j9~$_2hA|$N:8B&$KM>Gr$r@_$1!"(J <BR CLEAR=RIGHT>$B$G2s$j9~$_2hA|$N1&B&$KM>Gr$r@_$1!"$=$7$F(J<BR CLEAR=ALL>$B$G$=$N$h$&$J2hA|$N:81&N>B&$KM>Gr$r@_$1$^$9!#(J MAP $BMWAG$O!"K,Ld $B$3$3$K2hA|<0M6F3%9%$%C%ANs$N4JC1$JNc$,$"$j$^$9(J MAP $BMWAG$K$OB0@-$,(J1$B$D$"$j$^$9!#CO?^$NL>A0$r$D$1$k(J NAME $B$G$9!#(J
$B$3$l$O(J URL $B4z$D$-<1JL;R$K$h$jCO?^$r;2>H$9$k$?$a$K!"(J IMG $BMWAG$N(J USEMAP $BB0@-$K$h$C$F;H$o$l$^$9!#(J
NAME $BB0@-$NCM$,BgJ8;z!&>.J8;z$r6hJL$9$k$3$H$KCm0U$7$F$/$@$5$$!#(J AREA $BMWAG$O6uMWAG$J$N$G!"=*N;%?%0$O=P$F$-$^$;$s!#(J
SHAPE $B$H(J COORDS $B$H(J HREF $B$H(J NOHREF $B$H(J ALT $B$N(J5$B$D$rB0@-$K
$B2hA|>e$N(Jxy$B:BI8$O:8>eC<$+$iB,$C$?%T%/%;%k?t$GI=$o$5$l$^$9!##xCM$H(J y $BCM$,!J%T%/%;%k?t$G$J$/!K%Q!<%;%s%HId9f$D$-$GM?$($i$l$k>l9g$O!"$=$NCM$O!"2hA|$N9-$5$H9b$5$KBP$9$kI4J,N($H2r
Where x and y are measured in pixels from the left/top
of the associated image. If x and y values are given with a
percent sign as a suffix, the values should be interpreted as percentages
of the image's width and height, respectively. For example:
HREF $BB0@-$O!"D6O":?$N9T@h$H$J$k(J URL $B$rM?$($^$9!#(J
$B2!%\%?%s$H$7$FF/$+$J$$NN0h$rDj5A$7$?$$$H$-$O!"(J NOHREF $BB0@-$r;HMQ$7$^$9!#(J
$B$3$l$O!"4pK\E*$K2!%\%?%s$H$7$FF/$$$F$$$kNN0h$K!"7j$r3+$1$?$$$H$-$K$OJXMx$G$9!#(J 2$B$D0J>e$NNN0h$,=E$J$j9g$&$h$&$J>l9g$K$O!"CO?^Dj5A$G:G=i$KDj5A$5$l$?NN0h$,!"$C$F!"(JNOHREF$B$N$D$$$?(J AREA $BMWAG$O0lHLE*$K!"(J HREF $BB0@-$N$"$k$b$N$h$jA0$KCV$/$Y$-$@$H$$$&$3$H$K$J$j$^$9!#(J ALT $BB0@-$O!"2!%\%?%s$N>e$r%^%&%9$+B>$N%]%$%s%F%#%s%0%G%P%$%9$,0\F0Cf$K%9%F!<%?%9%i%$%s$KI=<($5$l$k!"0?$$$O2hA|$rI=<($7$J$$%f!<%6%(!<%8%'%s%H$N$?$a$NIJ=q$-$r9=@.$9$kJ8>O$rMQ0U$7$^$9!#(J
$B2;@ $B$3$l$O%U%!%$%k$,(J HTML 3.2 DTD $B$K=`5r$7$F$$$k$3$H$r3N$+$a$k$?$a$K!"(J nsgmls $B$N$h$&$J(J SGML $B%Q!<%5!<$H$H$b$K;HMQ$9$k$3$H$,$G$-$^$9!#(J
DTD $B$,%U%!%$%k!X(J HTML32.dtd $B!Y$H$7$F!"%i%F%s#1 $B$3$l$O#8%S%C%H9q:]I8=`2=5!9=%i%F%s#1J8;z%;%C%H$r;H$$$^$9!#(J
$BJ8;z?t$d%?%0L>$N$h$&$JFC@-$N>e8BCM$O!"(JHTML 2.0$B$N$b$N$+$i$O$+$J$jA}2C$7$F$$$^$9$,!"%f!<%6%(!<%8%'%s%H$O6KC<$KD9$$$b$N$r2!$7IU$1$i$l$J$$$h$&$K$9$k$3$H$,?dA&$5$l$^$9!#(J .J8;z(J u $B!J=E%"%/%;%s%H5-9fIU!K(Jsmall u, grave accent -->
<!ENTITY uacute CDATA "ú" -- $B>.J8;z(J u $B!J1T%"%/%;%s%H5-9fIU!K(Jsmall u, acute accent -->
<!ENTITY ucirc CDATA "û" -- $B>.J8;z(J u $B!J6J@^%"%/%;%s%H5-9fIU!K(Jsmall u, circumflex accent -->
<!ENTITY uuml CDATA "ü" -- $B>.J8;z(J u $B!J%&%`%i%&%HIU!K(Jsmall u, dieresis or umlaut mark -->
<!ENTITY yacute CDATA "ý" -- $B>.J8;z(J y $B!J1T%"%/%;%s%H5-9fIU!K(Jsmall y, acute accent -->
<!ENTITY thorn CDATA "þ" -- $B%"%$%9%i%s%I$N>.J8;z(J thorn$B!!(Jsmall thorn, Icelandic -->
<!ENTITY yuml CDATA "ÿ" -- $B>.J8;z(J y $B!J%&%`%i%&%HIU!K(Jsmall y, dieresis or umlaut mark -->
W3C HTML Editorial Review Board $B$N%a%s%P!$NB?$/$N?M!9$K$*Ni?=$7>e$2$^$9!#(J
The META element can be used to include name/value pairs
describing properties of the document, such as author, expiry date,
a list of key words etc. The NAME attribute specifies the
property name while the CONTENT attribute specifies the
property value, e.g.
<META NAME="Author" CONTENT="Dave Raggett">
The HTTP-EQUIV attribute can be used in place of the
NAME attribute and has a special significance when
documents are retrieved via the Hypertext Transfer Protocol (HTTP). HTTP
servers may use the property name specified by the HTTP-EQUIV attribute
to create an RFC 822 style header in the HTTP response. This can't be
used to set certain HTTP headers though, see the HTTP specification for
details.
<META HTTP-EQUIV="Expires" CONTENT="Tue, 20 Aug 1996 14:25:27 GMT">
Expires: Tue, 20 Aug 1996 14:25:27 GMT
$BO":?(J
LINK
LINK provides a media independent method for defining relationships with other documents and resources. LINK has been part of HTML since the very early days, although few browsers as yet take advantage of it (most still ignore LINK elements).
LINK elements can be used in principle:
for document specific navigation toolbars or menus
to control how collections of HTML files are rendered into printed documents
for linking associated resources such as style sheets and scripts
to provide alternative forms of the current document
<!ELEMENT LINK - O EMPTY>
<!ATTLIST LINK
href %URL #IMPLIED -- $BO":?$7$?AG:`$N(JURL$B!!(J98.1.9URL for linked resource --
rel CDATA #IMPLIED -- $B@5=gO":?%?%$%W!!(Jforward link types --
rev CDATA #IMPLIED -- $B5U=gO":?%?%$%W!!(Jreverse link types --
title CDATA #IMPLIED -- $B=u8@E*I8BjJ8;zNs!!(Jadvisory title string --
>
Specifies a URL designating the linked resource.
The forward relationship also known as the "link type". It specifies a named relationship from the enclosing document to the resource specified by the HREF attribute. HTML link relationships are as yet unstandardized, although some conventions have been established.
An advisory title for the linked resource.
The link references the top of a hierarchy, e.g. the first or cover page in a collection.
The link references a document serving as a table of contents.
The link references a document providing an index for the current document.
The link references a document providing a glossary of terms that are relevant to the current document.
The link references a copyright statement for the current document.
The link references the previous document in a guided tour.
The link references a document offering help, e.g. describing the wider context and offering further links to relevant documents.
This is aimed at reorienting users who have lost their way.
The link references a page for searching material related to a collection of pages
<LINK REL=Contents HREF=toc.html>
<LINK REL=Previous HREF=doc31.html>
<LINK REL=Next HREF=doc33.html>
<LINK REL=Chapter REV=Contents HREF=chapter2.html>
$BK\J8MWAG(J
The BODY element
This contains the document body. Both start and end tags for
BODY may be omitted. The body can contain a wide range
of elements:
BACKGROUND,
BGCOLOR, TEXT, LINK,
VLINK and ALINK.
$B$3$l$i$r;H$C$FJI;f$rE=$C$?$j!"GX7J?'$K2C$(J8>O$dD6O":?$N?'$r@_Dj$7$?$j$9$k$3$H$,$G$-$^$9!#(J
These can be used to set a
repeating background image, plus background and foreground colors for
normal text and hypertext links.
<!ENTITY % body.content "(%heading | %text | %block | ADDRESS)*">
<!ENTITY % color "CDATA" -- a color specification: #HHHHHH @@ details? -->
<!ENTITY % body-color-attrs "
bgcolor %color #IMPLIED
text %color #IMPLIED
link %color #IMPLIED
vlink %color #IMPLIED
alink %color #IMPLIED
">
<!ELEMENT BODY O O %body.content>
<!ATTLIST BODY
background %URL #IMPLIED -- $BJ8=q$NGX7J$H$J$k@8CO!!(Jtexture tile for document background --
%body-color-attrs; -- bgcolor, text, link, vlink, alink --
>
<body bgcolor=white text=black link=red vlink=maroon alink=fuchsia>
Specifies the background color for the document body.
See below for the syntax of color values.
Specifies the color used to stroke the document's text.
This is generally used when you have changed the background
color with the BGCOLOR or BACKGROUND attributes.
Specifies the color used to stroke the text for unvisited hypertext
links.
Specifies the color used to stroke the text for visited hypertext
links.
Specifies the highlight color used to stroke the text for hypertext
links at the moment the user clicks on the link.
Specifies a URL for an image that will be used to tile the document
background.
Colors are given in the sRGB
color space as hexadecimal numbers (e.g. COLOR="#C0FFC0"),
or as one of 16 widely understood color names. These colors were
originally picked as being the standard 16 colors supported with the
Windows VGA palette.
Black = "#000000"
Green = "#008000" Silver = "#C0C0C0"
Lime = "#00FF00" Gray = "#808080"
Olive = "#808000" White = "#FFFFFF"
Yellow = "#FFFF00" Maroon = "#800000"
Navy = "#000080" Red = "#FF0000"
Blue = "#0000FF" Purple = "#800080"
Teal = "#008080" Fuchsia = "#FF00FF"
Aqua = "#00FFFF" $B$^$H$aMWAG!&J8>OMWAG(J
Block and Text level elements
Most elements that can appear in the document body fall into one of
two groups: block level elements which cause paragraph breaks, and text
level elements which don't. Common block level elements include
H1 to H6 (headers), P
(paragraphs) LI (list items), and HR
(horizontal rules). Common text level elements include EM,
I, B and FONT (character
emphasis), A (hypertext links), IMG and
APPLET (embedded objects) and BR (line
breaks). Note that block elements generally act as containers for text
level and other block level elements (excluding headings and address
elements), while text level elements can only contain other text level
elements. The exact model depends on the element.
$B8+=P$7(J
Headings
<!--
$B8+=P$7$K$O(JH1$B!J:G=EMW!K$+$i(JH6$B!J:G$b=EMW$G$J$$!K$^$G(J6$B$D$NCJ3,$,$"$j$^$9!#(J
There are six levels of headers from H1 (the most important) to H6 (the least important).
-->
<!ELEMENT ( %heading ) - - (%text;)*>
<!ATTLIST ( %heading )
align (left|center|right) #IMPLIED
>
<H1 ALIGN=CENTER> ... centered heading ... </H1>
The default is left alignment, but this can be overridden by an
enclosing DIV or CENTER element.
$B1|IU!!(JADDRESS
<!ENTITY % address.content "((%text;) | P)*">
<!ELEMENT ADDRESS - - %address.content>
The ADDRESS element requires start and end tags, and specifies information such as authorship and contact details for the current document. User agents should render the content with paragraph-breaks before and after. Note that the content is restricted to paragraphs, plain text and text-like elements as defined by the %text entity.
<ADDRESS>
Newsletter editor<BR>
J.R. Brown<BR>
8723 Buena Vista, Smallville, CT 01234<BR>
Tel: +1 (123) 456 7890
</ADDRESS>
$B$^$H$aMWAG(J
Block elements
The paragraph element requires a start tag, but the end tag can
always be omitted. Use the ALIGN attribute to set the text
alignment within a paragraph, e.g. <P ALIGN=RIGHT>
These require start and end tags, and contain one or more
LI elements representing individual list items.
These require start and end tags, and contain one or more
LI elements representing individual list items.
These require start and end tags and contain DT
elements that give the terms, and DD elements that give
corresponding definitions.
Requires start and end tags. These elements are rendered with a
monospaced font and preserve layout defined by whitespace and line
break characters.
Requires start and end tags. It is used with the ALIGN
attribute to set the text alignment of the block elements it contains.
ALIGN can be one of LEFT, CENTER
or RIGHT.
Requires start and end tags. It is used to center text lines
enclosed by the CENTER element. See DIV
for a more general solution.
Requires start and end tags. It is used to enclose extended
quotations and is typically rendered with indented margins.
Requires start and end tags. This element is used to define
a fill-out form for processing by HTTP servers. The attributes
are ACTION, METHOD and ENCTYPE.
Form elements can't be nested.
Not a container, so the end tag is forbidden. attributes are
ALIGN, NOSHADE, SIZE and
WIDTH.
Requires start and end tags. Each table starts with an optional
CAPTION followed by one or more TR elements
defining table rows. Each row has one or more cells defined by
TH or TD elements. attributes for
TABLE elements are WIDTH, BORDER,
CELLSPACING and CELLPADDING.
$BCJMn(J
Paragraphs <!ELEMENT P - O (%text)*>
<!ATTLIST P
align (left|center|right) #IMPLIED
>
The P element is used to markup paragraphs. It is a
container and requires a start tag. The end tag is optional as it can
always be inferred by the parser. User agents should place paragraph
breaks before and after P elements. The rendering is user
agent dependent, but text is generally wrapped to fit the space
available.
<P>$B$3$l$O:G=i$NCJMn$G$9!#(JThis is the first paragraph.
<P>$B$3$l$OFsHVL\$NCJMn$G$9!#(JThis is the second paragraph.
The paragraph is rendered flush left.
The paragraph is centered.
The paragraph is rendered flush right.
<p align=center>$B$3$l$OCf1{B7$($K$7$?CJMn$G$9!#(J
This is a centered paragraph.
<p align=right>$B$=$7$F$3$l$O1&4s$;$K$7$?CJMn$G$9!#(J
and this is a flush right paragraph.
The default is left alignment, but this can be overridden by an
enclosing DIV or
CENTER element.
$B0lMw(J
Lists$B=gITF10lMw(J
Unordered Lists
<!ELEMENT UL - - (LI)+>
<!ENTITY % ULStyle "disc|square|circle">
<!ATTLIST UL -- $BHV9f$J$70lMw!!(Junordered lists --
type (%ULStyle) #IMPLIED -- $B%^!<%/$N7A>u!!(Jbullet style --
compact (compact) #IMPLIED -- $BC;=L7?!!(Jreduced interitem spacing --
>
<!ELEMENT LI - O %flow -- $B0lMw9`L\!!(Jlist item -->
<!ATTLIST LI
type (%LIStyle) #IMPLIED -- $B0lMw9`L\$N7A>u!!(Jlist item style --
>
The UL element is used for unordered lists. Both start
and end tags are always needed. The LI element is used for
individual list items. The end tag for LI elements can
always be omitted. Note that LI elements can contain nested
lists. The COMPACT attribute can be used as a hint to the
user agent to render lists in a more compact style.
The TYPE attribute can be used to set the bullet style
on UL and LI elements. The permitted values
are "disc", "square" or "circle". The default generally depends on the
level of nesting for lists.
This list was chosen to cater for the original bullet shapes used by
Mosaic in 1993.
$B=xNs!JHV9fIU$-!K0lMw(J
Ordered (i.e. numbered) Lists
<!ELEMENT OL - - (LI)+>
<!ATTLIST OL -- $BHV9f$D$-0lMw!!(Jordered lists --
type CDATA #IMPLIED -- $BHV9f$N
<OL>
<LI> ... first list item
<LI> ... second list item
...
</OL>
The OL START attribute can be used to
initialize the sequence number (by default it is initialized to 1).
You can set it later on with the VALUE attribute on
LI elements. Both of these attributes expect integer
values. You can't indicate that numbering should be continued from a
previous list, or to skip missing values without giving an explicit
number.
The COMPACT attribute can be used as a hint to the user
agent to render lists in a more compact style. The OL
TYPE attribute allows you to set the numbering style for
list items:
Type $BHV9f$N 1 $B%"%i%S%"?t;z(Jarabic numbers 1, 2, 3, ... a $B>.J8;z%"%k%U%!%Y%C%H(Jlower alpha a, b, c, ... A $BBgJ8;z%"%k%U%!%Y%C%H(Jupper alpha A, B, C, ... i $B>.J8;z%m!<%^?t;z(Jlower roman i, ii, iii, ... I $BBgJ8;z%m!<%^?t;z(Jupper roman I, II, III, ... $BDj5A0lMw(J
Definition Lists
<!-- $BDj5A0lMw!!(JDT$B$OMQ8l!"(JDD$B$O$=$NDj5A(J --
-- definition lists - DT for term, DD for its definition -->
<!ELEMENT DL - - (DT|DD)+>
<!ATTLIST DL
compact (compact) #IMPLIED -- $BC;=L7?!!(Jmore compact style --
>
<!ELEMENT DT - O (%text)*>
<!ELEMENT DD - O %flow;>
<DL>
<DT>$BMQ8l(J1$B!!(JTerm 1<dd>$B$3$l$O:G=i$NMQ8l$NDj5A$G$9!#(JThis is the definition of the first term.
<DT>$BMQ8l(J2$B!!(JTerm 2<dd>$B$3$l$OFsHVL\$NMQ8l$NDj5A$G$9!#(JThis is the definition of the second term.
</DL>
The COMPACT attribute can be used with the
DL element as a hint to the user agent to render
lists in a more compact style.
$B3,AX0lMw(J
DIR
$B$H(J
$B8%N)(J
MENU
<!ELEMENT (DIR|MENU) - - (LI)+ -(%block)>
<!ATTLIST (DIR|MENU)
compact (compact) #IMPLIED
>
These elements have been part of HTML from the early days. They are
intended for unordered lists similar to UL elements. User
agents are recommended to render DIR elements as
multicolumn directory lists, and MENU elements as single
column menu lists. In practice, Mosaic and most other user agents
have ignored this advice and instead render DIR and
MENU in an identical way to UL elements.
$B3d$jIU$1:Q$_J8>O(J
Preformatted Text<!ELEMENT PRE - - (%text)* -(%pre.exclusion)>
<!ATTLIST PRE
width NUMBER #implied
>
Note that the SGML standard requires that the parser
remove a newline immediately following the start tag
or immediately preceding the end tag.
PRE has the same content model as paragraphs,
excluding images and elements that produce changes in font size,
e.g. IMG, BIG, SMALL,
SUB, SUP and FONT.
A few user agents support the WIDTH attribute. It
provides a hint to the user agent of the required width in characters.
The user agent can use this to select an appropriate font size or to
indent the content appropriately.
<PRE>
Higher still and higher
From the earth thou springest
Like a cloud of fire;
The blue deep thou wingest,
And singing still dost soar, and soaring ever singest.
</PRE>
$B$3$l$,
which is rendered as:
Higher still and higher
From the earth thou springest
Like a cloud of fire;
The blue deep thou wingest,
And singing still dost soar, and soaring ever singest.
The horizontal tab character (encoded in Unicode, US ASCII and
ISO 8859-1 as decimal 9) should be interpreted as the smallest
non-zero number of spaces which will leave the number of characters
so far on the line as a multiple of 8. Its use is strongly discouraged
since it is common practice when editing to set the tab-spacing to other
values, leading to misaligned documents.
XMP, LISTING and
PLAINTEXT
<![ %HTML.Deprecated [
<!ENTITY % literal "CDATA"
-- $BA4$F=*N;%?%0$N$_$GI=5-$5$l$F$$$?:"$N!"(J $B8E$$IT0lCW$JJ,@O%b!<%I(J
historical, non-conforming parsing mode where
the only markup signal is the end tag
in full
-->
<!ELEMENT (XMP|LISTING) - - %literal>
<!ELEMENT PLAINTEXT - O %literal>
]]>
These are obsolete tags for preformatted text that predate the
introduction of PRE. User agents may support these
for backwards compatibility. Authors should avoid using them in new
documents!
DIV and CENTER
<!ELEMENT DIV - - %body.content>
<!ATTLIST DIV
align (left|center|right) #IMPLIED -- $B0J9_$NJ8>O$N@0Ns(J
alignment of following text --
>
<!-- CENTER$B$O(JALIGN=CENTER$B$r;}$D(JDIV$B$N>JN,7A$G$9(J
CENTER is a shorthand for DIV with ALIGN=CENTER -->
<!ELEMENT center - - %body.content>
DIV elements can be used to structure HTML documents as
a hierarchy of divisions. The ALIGN attribute can be used
to set the default horizontal alignment for elements within the content
of the DIV element. Its value is restricted to
LEFT, CENTER or RIGHT, and is
defined in the same way as for the paragraph element
<P>.
Note that because DIV is a block-like element it will
terminate an open P element. Other than this, user agents
are not expected to render paragraph breaks before and after
DIV elements. CENTER is directly equivalent
to DIV with ALIGN=CENTER. Both
DIV and CENTER require start and end tags.
$B0zMQ!!(JBLOCKQUOTE
<!ELEMENT BLOCKQUOTE - - %body.content>
This is used to enclose block quotations from other works.
Both the start and end tags are required. It is often rendered
indented, e.g.
They went in single file, running like hounds on a strong scent,
and an eager light was in their eyes. Nearly due west the broad
swath of the marching Orcs tramped its ugly slot; the sweet grass
of Rohan had been bruised and blackened as they passed.
$B=q<0(J
FORM
<!ENTITY % HTTP-Method "GET | POST"
-- as per HTTP specification
-->
<!ELEMENT FORM - - %body.content -(FORM)>
<!ATTLIST FORM
action %URL #IMPLIED -- server-side form handler --
method (%HTTP-Method) GET -- see HTTP specification --
enctype %Content-Type; "application/x-www-form-urlencoded"
>
This is used to define an HTML form, and you can have more than one form
in the same document. Both the start and end tags are required. For very
simple forms, you can also use the ISINDEX
element. Forms can contain a wide range of HTML markup including several
kinds of form fields such as single and multi-line
text fields, radio button groups, checkboxes, and menus.
This specifies a URL which is either used to post forms via email,
e.g. action="mailto:foo@bar.com", or used to invoke a
server-side forms handler via HTTP, e.g.
action="http://www.acme.com/cgi-bin/register.pl"
When the action attribute specifies an HTTP server, the method
attribute determines which HTTP method will be used to send the form's
contents to the server. It can be either GET or
POST, and defaults to GET.
This determines the mechanism used to encode the form's contents.
It defaults to application/x-www-form-urlencoded.
Further details on handling forms are given in RFC 1867.
HR $B2#7S@~(J
horizontal rules
Horizontal rules may be used to indicate a change in topic.
In a speech based user agent, the rule could be rendered as a pause.
<!ELEMENT HR - O EMPTY>
<!ATTLIST HR
align (left|right|center) #IMPLIED
noshade (noshade) #IMPLIED
size %Pixels #IMPLIED
width %Length #IMPLIED
>
HR elements are not containers so the end tag is forbidden.
The attributes are: ALIGN, NOSHADE,
SIZE and WIDTH.
This determines whether the rule is placed at the left, center
or right of the space between the current left and right margins
for align=left, align=center or
align=right respectively. By default, the rule is centered.
This attribute requests the user agent to render the rule in a
solid color rather than as the traditional two colour "groove".
This can be used to set the height of the rule in pixels.
This can be used to set the width of the rule in
pixels (e.g. width=100) or as the percentage between the
current left and right margins (e.g. width="50%"). The
default is 100%. $BI=AH(J
Tables
<!-- horizontal placement of table relative to window -->
<!ENTITY % Where "(left|center|right)">
<!-- horizontal alignment attributes for cell contents -->
<!ENTITY % cell.halign
"align (left|center|right) #IMPLIED"
>
<!-- vertical alignment attributes for cell contents -->
<!ENTITY % cell.valign
"valign (top|middle|bottom) #IMPLIED"
>
<!ELEMENT table - - (caption?, tr+)>
<!ELEMENT tr - O (th|td)*>
<!ELEMENT (th|td) - O %body.content>
<!ATTLIST table -- $BI=AHMWAG(Jtable element --
align %Where; #IMPLIED -- $B2hLLFb$G$NI=$N0LCV(Jtable position relative to window --
width %Length #IMPLIED -- $B2hLLFb$G$NI=$N2#I}(Jtable width relative to window --
border %Pixels #IMPLIED -- $BI=$N30OH(Jcontrols frame width around table --
cellspacing %Pixels #IMPLIED -- spacing between cells --
cellpadding %Pixels #IMPLIED -- spacing within cells --
>
<!ELEMENT CAPTION - - (%text;)* -- $BI=Bj(Jtable or figure caption -->
<!ATTLIST CAPTION
align (top|bottom) #IMPLIED
>
<!ATTLIST tr -- $B9T(Jtable row --
%cell.halign; -- $B2#J}8~@0Ns(Jhorizontal alignment in cells --
%cell.valign; -- $B=DJ}8~@0Ns(Jvertical alignment in cells --
>
<!ATTLIST (th|td) -- $B8+=P$7OH$^$?$O%G!<%?OH(Jheader or data cell --
nowrap (nowrap) #IMPLIED -- $B<+F02~9T$NM^;_(Jsuppress word wrap --
rowspan NUMBER 1 -- $B9T$^$?$.(Jnumber of rows spanned by cell --
colspan NUMBER 1 -- $BNs$^$?$.(Jnumber of cols spanned by cell --
%cell.halign; -- $B2#J}8~@0Ns(Jhorizontal alignment in cells --
%cell.valign; -- $B=DJ}8~@0Ns(Jvertical alignment in cells --
width %Pixels #IMPLIED -- $BOHI};XDj(Jsuggested width for cell --
height %Pixels #IMPLIED -- $BOH9b$5;XDj(Jsuggested height for cell --
>
<TABLE BORDER=3 CELLSPACING=2 CELLPADDING=2 WIDTH="80%">
<CAPTION> ... table caption ... </CAPTION>
<TR><TD> first cell <TD> second cell
<TR> ...
...
</TABLE>
Each table row is contained in a TR element, although
the end tag can always be omitted. Table cells are defined by
TD elements for data and TH elements for
headers. Like TR, these are containers and can be given
without trailing end tags. TH and TD support
several attributes: ALIGN and VALIGN for
aligning cell content, ROWSPAN and COLSPAN for
cells which span more than one row or column. A cell can contain a wide
variety of other block and text level elements including form fields and
other tables.
The TABLE element always requires both start and end tags.
It supports the following attributes:
This takes one of the case insensitive values: LEFT,
CENTER or RIGHT. It specifies the horizontal
placement of the table relative to the current left and right margins.
It defaults to left alignment, but this can be overridden by an
enclosing DIV or
CENTER element.
In the absence of this attribute the table width is automatically
determined from the table contents. You can use the WIDTH
attribute to set the table width to a fixed value in pixels (e.g.
WIDTH=212) or as a percentage of the space between the
current left and right margins (e.g. WIDTH="80%").
In traditional desktop publishing software, adjacent table cells
share a common border. This is not the case in HTML. Each cell is given
its own border which is separated from the borders around neighboring
cells. This separation can be set in pixels using the
CELLSPACING attribute, (e.g. CELLSPACING=10).
The same value also determines the separation between the table border
and the borders of the outermost cells.
This sets the padding in pixels between the border around each cell
and the cell's contents.
The CAPTION element has one attribute ALIGN
which can be either ALIGN=TOP or ALIGN=BOTTOM.
This can be used to force the caption to be placed above the top or
below the bottom of the table respectively. Most user agents default to
placing the caption above the table. CAPTION always
requires both start and end tags. Captions are limited to plain text and
text-level elements as defined by the %text entity. Block level elements
are not permitted.
The TR or table row element requires a start tag, but
the end tag can always be left out. TR acts as a container
for table cells. It has two attributes:
Sets the default horizontal alignment of cell contents. It takes
one of the case insensitive values: LEFT, CENTER
or RIGHT and plays the same role as the ALIGN
attribute on paragraph elements.
There are two elements for defining table cells. TH is
used for header cells and TD for data cells. This
distinction allows user agents to render header and data cells in
different fonts, and enables speech based browsers to do a better job.
The start tags for TH and TD are always needed
but the end tags can be left out. Table cells can have the following
attributes:
This takes a positive integer value specifying the number of
rows spanned by this cell. It defaults to one.
This takes a positive integer value specifying the number of
columns spanned by this cell. It defaults to one.
Specifies the default horizontal alignment of cell
contents, and overrides the ALIGN attribute on the table
row. It takes the same values: LEFT, CENTER
and RIGHT. If you don't specify an ALIGN
attribute value on the cell, the default is left alignment for
<td> and center alignment for <th>
although you can override this with an ALIGN attribute on
the TR element.
Specifies the default vertical alignment of cell
contents, overriding the VALIGN attribute on the table row.
It takes the same values: TOP, MIDDLE and
BOTTOM. If you don't specify a VALIGN attribute value on
the cell, the default is middle although you can override this with a
VALIGN attribute on the TR element.
Specifies the suggested width for a cell content in pixels
excluding the cell padding. This value will normally be
used except when it conflicts with the width requirements
for other cells in the same column.
Specifies the suggested height for a cell content in pixels
excluding the cell padding. This value will normally be
used except when it conflicts with the height requirements
for other cells in the same row.
Tables are commonly rendered in bas-relief, raised up with the outer
border as a bevel, and individual cells inset into this raised surface.
Borders around individual cells are only drawn if the cell has explicit
content. White space doesn't count for this purpose with the exception
of .
The algorithms used to automatically size tables should take
into account the minimum and maximum width requirements for each
cell. This is used to determine the minimum and maximum width
requirements for each column and hence for the table itself.
Cells spanning more than one column contribute to the
widths of each of the columns spanned. One approach is to evenly
apportion the cell's minimum and maximum width between these
columns, another is to weight the apportioning according to the
contributions from cells that don't span multiple columns.
For some user agents it may be necessary or desirable to break
text lines within words. In such cases a visual indication that this
has occurred is advised.
The minimum and maximum width of nested tables contribute to the
minimum and maximum width of the cell in which they occur. Once the
width requirements are known for the top level table, the column widths
for that table can be assigned. This allows the widths of nested tables
to be assigned and hence in turn the column widths of such tables.
If practical, all columns should be assigned at least their minimum
widths. It is suggested that any surplus space is then shared out
proportional to the difference between the minimum and maximum width
requirements of each column.
$BJ8>OMWAG(J
Text level elements
These don't cause paragraph breaks. Text level elements
that define character styles can generally be nested. They can
contain other text level elements but not block level elements.
$B;zBNMWAG!!(JFont style elements
These all require start and end tags, e.g.
This has some <B>bold text</B>.
This has some <B>bold and <I></B>italic text</I>.
$B%f!<%6%(!<%8%'%s%H$O
User agents should do their best to respect nested emphasis, e.g.
This has some <B>bold and <I>italic text</I></B>.
Where the available fonts are restricted or for speech output, alternative
means should be used for rendering differences in emphasis.
Note: future revisions to HTML may be phase out STRIKE
in favor of the more concise "S" tag from HTML 3.0.
$B;z6gMWAG!!(JPhrase Elements
These all require start and end tags, e.g.
This has some <EM>emphasized text</EM>.
$B=q$-9~$_=q<0(J
Form fields
INPUT,
SELECT and
TEXTAREA are only allowed within
FORM elements. INPUT can
be used for a variety of form fields including single line text fields,
password fields, checkboxes, radio buttons, submit and reset buttons,
hidden fields, file upload, and image buttons.
SELECT elements are used for single or
multiple choice menus. TEXTAREA
elements are used to define multi-line text fields. The content of the
element is used to initialize the field.
INPUT text fields, radio buttons, check boxes, ...
INPUT elements are not containers and so the end tag is
forbidden.
<!ENTITY % IAlign "(top|middle|bottom|left|right)">
<!ENTITY % InputType
"(TEXT | PASSWORD | CHECKBOX | RADIO | SUBMIT
| RESET | FILE | HIDDEN | IMAGE)">
<!ELEMENT INPUT - O EMPTY>
<!ATTLIST INPUT
type %InputType TEXT -- what kind of widget is needed --
name CDATA #IMPLIED -- required for all but submit and reset --
value CDATA #IMPLIED -- required for radio and checkboxes --
checked (checked) #IMPLIED -- for radio buttons and check boxes --
size CDATA #IMPLIED -- specific to each type of field --
maxlength NUMBER #IMPLIED
src %URL #IMPLIED -- for fields with background images --
align %IAlign #IMPLIED -- vertical or horizontal alignment --
>
A single line text field whose visible size can be set using the size attribute, e.g. size=40
for a 40 character wide field. Users should be able to type more than
this limit though with the text scrolling through the field to keep the
input cursor in view. You can enforce an upper limit on the number of
characters that can be entered with the maxlength attribute. The name attribute is used to name the field,
while the value attribute can be used
to initialize the text string shown in the field when the document is
first loaded.
<input type=text size=40 name=user value="your name">
This is like type=text, but echoes characters using a character
like * to hide the text from prying eyes when entering passwords.
You can use size and
maxlength attributes to control
the visible and maximum length exactly as per
regular text fields.
<input type=password size=12 name=pw>
Used for simple Boolean attributes, or for attributes that can take
multiple values at the same time. The latter is represented by several
checkbox fields with the same name and
a different value attribute. Each checked
checkbox generates a separate name/value pair in the submitted data, even
if this results in duplicate names. Use the
checked attribute to initialize
the checkbox to its checked state.
<input type=checkbox checked name=uscitizen value=yes>
Used for attributes which can take a single value from a set of
alternatives. Each radio button field in the group should be given the
same name. Radio buttons require an explicit
value attribute. Only the checked radio
button in the group generates a name/value pair in the submitted data. One
radio button in each group should be initially checked using the
checked attribute.
<input type=radio name=age value="0-12">
<input type=radio name=age value="13-17">
<input type=radio name=age value="18-25">
<input type=radio name=age value="26-35" checked>
<input type=radio name=age value="36-">
This defines a button that users can click to submit the form's
contents to the server. The button's label is set from the
value attribute. If the
name
attribute is given then the submit button's name/value pair will be
included in the submitted data. You can include several submit buttons
in the form. See type=image for graphical submit buttons.
<input type=submit value="Party on ...">
This is used for graphical submit buttons rendered by an image
rather than a text string. The URL for the image is specified with the
src attribute. The image alignment can
be specified with the align
attribute. In this respect, graphical submit buttons are treated
identically to IMG elements, so you can
set align to left, right, top, middle or bottom. The x and y values of
the location clicked are passed to the server: In the submitted data,
image fields are included as two name/value pairs. The names are derived
by taking the name of the field and appending ".x" for the x value, and
".y" for the y value.
<p>Now choose a point on the map:
<input type=image name=point src="map.gif">
image fields typically cause problems for text-only and
speech-based user agents!
This defines a button that users can click to reset form fields
to their initial state when the document was first loaded. You can
set the label by providing a value
attribute. Reset buttons are never sent as part of the form's contents.
<input type=reset value="Start over ...">
This provides a means for users to attach a file to the form's
contents. It is generally rendered by text field and an associated
button which when clicked invokes a file browser to select a file
name. The file name can also be entered directly in the text field.
Just like type=text you can use the size
attribute to set the visible width of this field in average character
widths. You can set an upper limit to the length of file names using the
maxlength attribute. Some user agents
support the ability to restrict the kinds of files to those
matching a comma separated list of MIME content types given with
the ACCEPT attribute e.g. accept="image/*"
restricts files to images. Further information can be found in
RFC 1867.
<input type=file name=photo size=20 accept="image/*">
These fields should not be rendered and provide a means for servers
to store state information with a form. This will be passed back to the
server when the form is submitted, using the name/value pair defined by
the corresponding attributes. This is a work around for the statelessness
of HTTP. Another approach is to use HTTP "Cookies".
<input type=hidden name=customerid value="c2415-345-8563">
Used to define the property name that will be used to identify this
field's content when it is submitted to the server.
Used to initialize the field, or to provide a textual label for
submit and reset buttons.
The presence of this attribute is used to initialize checkboxes and
radio buttons to their checked state.
Used to set the visible size of text fields to a given number of
average character widths, e.g. size=20
Sets the maximum number of characters permitted in a text field.
Specifies a URL for the image to use with a graphical submit button.
Used to specify image alignment for graphical submit buttons.
It is defined just like the IMG align
attribute and takes one of the values: top, middle,
bottom, left or right, defaulting
to bottom.
$B9`L\A*BrMs(J
SELECT menus
<!ELEMENT SELECT - - (OPTION+)>
<!ATTLIST SELECT
name CDATA #REQUIRED
size NUMBER #IMPLIED
multiple (multiple) #IMPLIED
>
<!ELEMENT OPTION - O (#PCDATA)*>
<!ATTLIST OPTION
selected (selected) #IMPLIED
value CDATA #IMPLIED -- defaults to element content --
>
SELECT is used to define select one from many or many
from many menus. SELECT elements require start and end tags
and contain one or more OPTION elements that define menu
items. One from many menus are generally rendered as drop-down menus
while many from many menus are generally shown as list boxes.
<SELECT NAME="flavor">
<OPTION VALUE=a>Vanilla
<OPTION VALUE=b>Strawberry
<OPTION VALUE=c>Rum and Raisin
<OPTION VALUE=d>Peach and Orange
</SELECT>
This specifies a property name that is used to identify the menu
choice when the form is submitted to the server. Each selected option
results in a property name/value pair being included as part of the
form's contents.
This sets the number of visible choices for many from many menus.
The presence of this attribute signifies that the users can make
multiple selections. By default only one selection is allowed.
When this attribute is present, the option is selected when the
document is initially loaded. It is an error for more than one option
to be so selected for one from many menus.
Specifies the property value to be used when submitting the form's
content. This is combined with the property name as given by the name
attribute of the parent SELECT element.
TEXTAREA $BJ#?t9T=q$-9~$_OH(Jmulti-line text fields
<!-- $BJ#?t9T=q$-9~$_OH(JMulti-line text input field. -->
<!ELEMENT TEXTAREA - - (#PCDATA)*>
<!ATTLIST TEXTAREA
name CDATA #REQUIRED
rows NUMBER #REQUIRED
cols NUMBER #REQUIRED
>
TEXTAREA elements require start and end tags. The
content of the element is restricted to text and character entities. It
is used to initialize the text that is shown when the document is first
loaded.
<TEXTAREA NAME=address ROWS=4 COLS=40>
Your address here ...
</TEXTAREA>
It is recommended that user agents canonicalize line endings to
CR, LF (ASCII decimal 13, 10) when submitting the field's contents.
The character set for submitted data should be ISO Latin-1, unless
the server has previously indicated that it can support alternative
character sets.
This specifies a property name that is used to identify the textarea
field when the form is submitted to the server.
Specifies the number of visible text lines. Users should be able
to enter more lines that this, so user agents should provide some
means to scroll through the contents of the textarea field when the
contents extend beyond the visible area.
Specifies the visible width in average character widths. Users should
be able to enter longer lines that this, so user agents should provide
some means to scroll through the contents of the textarea field when the
contents extend beyond the visible area. User agents may wrap visible text
lines to keep long lines visible without the need for scrolling.
$BFC
Special Text level Elements$BIEMWAG(J
The A (anchor) element
<!ELEMENT A - - (%text)* -(A)>
<!ATTLIST A
name CDATA #IMPLIED -- $BO":?Hx;XDj!!(Jnamed link end --
href %URL #IMPLIED -- $BO":?;q:`$N(JURL$B!!(JURL for linked resource --
rel CDATA #IMPLIED -- $BA0J}O":?4X78!!(Jforward link types --
rev CDATA #IMPLIED -- $B5U9TO":?4X78!!(Jreverse link types --
title CDATA #IMPLIED -- $B=u8@E*I=BjJ8;zNs!!(Jadvisory title string --
>
Anchors can't be nested and always require start and end tags.
They are used to define hypertext links and also to define
named locations for use as targets for hypertext links, e.g.
The way to <a href="hands-on.html">happiness</a>.
<h2><a name=mit>545 Tech Square - Hacker's Paradise</a></h2>
This should be a string defining unique name for the scope of the
current HTML document. NAME is used to associate a name
with this part of a document for use with URLs that target a named
section of a document.
Specifies a URL acting as a network address for the linked resource.
This could be another HTML document, a PDF file or an image etc.
The forward relationship also known as the "link type". It can be
used to determine to how deal with the linked resource when printing
out a collection of linked resources.
An advisory title for the linked resource.
IMG - inline images
<!ENTITY % IAlign "(top|middle|bottom|left|right)">
<!ELEMENT IMG - O EMPTY -- $BKd9~$_2hA|(JEmbedded image -->
<!ATTLIST IMG
src %URL #REQUIRED -- $BKd9~$`2hA|$N(JURL$B!!(JURL of image to embed --
alt CDATA #IMPLIED -- $B2hA|$NBe$o$j$K$J$kI=<(!!(Jfor display in place of image --
align %IAlign #IMPLIED -- $B=D$^$?$O2#$N@0Ns!!(Jvertical or horizontal alignment --
height %Pixels #IMPLIED -- $B9b$5$r%T%/%;%k$G;X<(!!(Jsuggested height in pixels --
width %Pixels #IMPLIED -- $BI}$r%T%/%;%k$G;X<(!!(Jsuggested width in pixels --
border %Pixels #IMPLIED -- $BO":?OH@~$r;X<(!!(Jsuggested link border width --
hspace %Pixels #IMPLIED -- $B2#M>Gr$r;X<(!!(Jsuggested horizontal gutter --
vspace %Pixels #IMPLIED -- $B=DM>Gr$r;X<(!!(Jsuggested vertical gutter --
usemap %URL #IMPLIED -- $BK,Ld
Used to insert images. IMG is an empty element and so
the end tag is forbidden. Images can be positioned vertically relative
to the current textline or floated to the left or right. See
BR with the CLEAR attribute for control
over textflow.
e.g. <IMG SRC="canyon.gif" ALT="Grand Canyon">
IMG elements support the following attributes:
This attribute is required for every IMG element. It
specifies a URL for the image resource, for instance a GIF, JPEG or PNG
image file.
This is used to provide a text description of the image and
is vital for interoperability with speech-based and text only
user agents.
This specifies how the image is positioned relative to the current
textline in which it occurs:
positions the top of the image
with the top of the current text line. User agents vary in how they
interpret this. Some only take into account what has occurred on the
text line prior to the IMG element and ignore what happens after it.
is the default and aligns the bottom of the image with the baseline.
floats the image to the current left margin, temporarily changing
this margin, so that subsequent text is flowed along the image's
righthand side. The rendering depends on whether there is any left
aligned text or images that appear earlier than the current image in the
markup. Such text (but not images) generally forces left aligned images
to wrap to a new line, with the subsequent text continuing on the former
line.
floats the image to the current right margin, temporarily changing
this margin, so that subsequent text is flowed along the image's
lefthand side. The rendering depends on whether there is any right
aligned text or images that appear earlier than the current image in the
markup. Such text (but not images) generally forces right aligned images
to wrap to a new line, with the subsequent text continuing on the former
line.
Note that some browsers introduce spurious spacing with multiple left
or right aligned images. As a result authors can't depend on this being
the same for browsers from different vendors. See
BR for ways to control text flow.
When the IMG element appears as part of a hypertext
link, the user agent will generally indicate this by drawing a colored
border (typically blue) around the image. This attribute can be used to
set the width of this border in pixels. Use border=0 to
suppress the border altogether. User agents are recommended to provide
additional cues that the image is clickable, e.g. by changing the mouse
pointer.
This can be used to provide white space to the immediate left and
right of the image. The HSPACE attribute sets the width of
this white space in pixels. By default HSPACE is a small
non-zero number.
This can be used to provide white space above and below the image
The VSPACE attribute sets the height of this white space
in pixels. By default VSPACE is a small non-zero number.
When the IMG element is part of a hypertext link, and
the user clicks on the image, the ISMAP attribute causes
the location to be passed to the server. This mechanism causes problems
for text-only and speech-based user agents. Whenever its possible to
do so use the MAP element instead.
Here is an example of how you use ISMAP:
<a href="/cgibin/navbar.map"><img src=navbar.gif ismap border=0></a>
The location clicked is passed to the server as follows. The user
agent derives a new URL from the URL specified by the HREF
attribute by appending `?' the x coordinate `,' and the y coordinate of
the location in pixels. The link is then followed using the new URL. For
instance, if the user clicked at at the location x=10, y=27 then the
derived URL will be: "/cgibin/navbar.map?10,27". It
is generally a good idea to suppress the border and use graphical idioms
to indicate that the image is clickable.
APPLET (Java Applets)
<!ELEMENT APPLET - - (PARAM | %text)*>
<!ATTLIST APPLET
codebase %URL #IMPLIED -- code base --
code CDATA #REQUIRED -- class file --
alt CDATA #IMPLIED -- for display in place of applet --
name CDATA #IMPLIED -- applet name --
width %Pixels #REQUIRED -- suggested width in pixels --
height %Pixels #REQUIRED -- suggested height in pixels --
align %IAlign #IMPLIED -- vertical or horizontal alignment --
hspace %Pixels #IMPLIED -- suggested horizontal gutter --
vspace %Pixels #IMPLIED -- suggested vertical gutter --
>
<!ELEMENT PARAM - O EMPTY>
<!ATTLIST PARAM
name NMTOKEN #REQUIRED -- The name of the parameter --
value CDATA #IMPLIED -- The value of the parameter --
>
Requires start and end tags. This element is supported by all Java
enabled browsers. It allows you to embed a Java applet into HTML
documents. APPLET uses associated PARAM elements to pass parameters to the
applet. Following the PARAM elements, the content of
APPLET elements should be used to provide an alternative to
the applet for user agents that don't support Java. It is restricted to
text-level markup as defined by the %text entity in
the DTD. Java-compatible browsers ignore this extra HTML code. You can
use it to show a snapshot of the applet running, with text explaining
what the applet does. Other possibilities for this area are a link to a
page that is more useful for the Java-ignorant browser, or text that
taunts the user for not having a Java-compatible browser.
Here is a simple example of a Java applet:
<applet code="Bubbles.class" width=500 height=500>
Java applet that draws animated bubbles.
</applet>
Here is another one using a PARAM element:
<applet code="AudioItem" width=15 height=15>
<param name=snd value="Hello.au|Welcome.au">
Java applet that plays a welcoming sound.
</applet>
This optional attribute specifies the base URL of the applet --
the directory or folder that contains the applet's code.
If this attribute is not specified,
then the document's URL is used.
This required attribute gives the name of the file
that contains the applet's compiled Applet subclass.
This file is relative to the base URL of the applet.
It cannot be absolute.
This optional attribute specifies any text
that should be displayed
if the browser understands the APPLET tag
but can't run Java applets.
This optional attribute specifies a name for the applet instance,
which makes it possible for applets on the same page
to find (and communicate with) each other.
height = pixels
These required attributes give the initial width and height
(in pixels) of the applet display area,
not counting any windows or dialogs that the applet brings up.
This attribute specifies the alignment of the applet.
This attribute is defined in exactly the same way
as the IMG element.
The permitted values are: top, middle,
bottom, left and right.
The default is bottom.
hspace = pixels
These optional attributes specify the number of pixels above and
below the applet (VSPACE) and on each side of the
applet (HSPACE). They're treated the same way as the
IMG element's VSPACE and HSPACE
attributes.
<PARAM NAME = appletParameter VALUE = value>
getParameter()
method.
PARAM elements should be placed at the start of the
content for the APPLET element. This is not specified as part of the
DTD due to technicalities with SGML mixed content models.
$B;zBN(J
FONT
<!ELEMENT FONT - - (%text)* -- local change to font -->
<!ATTLIST FONT
size CDATA #IMPLIED -- [+]nn e.g. size="+1", size=4 --
color CDATA #IMPLIED -- #RRGGBB in hex, e.g. red: color="#FF0000" --
>
This sets the font size for the contents of the font element. You
can set size to an integer ranging from 1 to 7 for an absolute font
size, or specify a relative font size with a signed integer value, e.g.
size="+1" or size="-2". This is mapped to an
absolute font size by adding the current base font size as set by the
BASEFONT element (see below).
Used to set the color to stroke the text. Colors are given as RGB
in hexadecimal notation or as one of 16 widely understood
color names defined as per the BGCOLOR attribute
on the BODY element.
Some user agents also support a FACE attribute which
accepts a comma separated list of font names in order of preference.
This is used to search for an installed font with the corresponding
name. FACE is not part of HTML 3.2.
The following shows the effects of setting font to absolute sizes:
The following shows the effect of relative font sizes using
a base font size of 3:
The same thing with a base font size of 6:
$B4pK\;zBN(J
BASEFONT
<!ELEMENT BASEFONT - O EMPTY -- base font size (1 to 7) -->
<!ATTLIST BASEFONT
size CDATA #IMPLIED -- e.g. size=4, defaults to 3 --
>
Used to set the base font size. BASEFONT is an empty
element so the end tag is forbidden. The SIZE attribute is
an integer value ranging from 1 to 7. The base font size applies to the
normal and preformatted text but not to headings, except where these are
modified using the FONT element with a relative font size.
$B2~9T(J
BR
Used to force a line break. This is an empty element so the end tag
is forbidden. The CLEAR attribute can be used to move down
past floating images on either margin. <BR
CLEAR=LEFT> moves down past floating images on the left
margin, <BR CLEAR=RIGHT> does the same for floating
images on the right margin, while <BR CLEAR=ALL> does
the same for such images on both left and right margins.
$BK,Ld
The MAP element provides a mechanism for client-side
image maps. These can be placed in the same document or grouped in a
separate document although this isn't yet widely supported. The
MAP element requires start and end tags. It contains one or
more AREA elements that specify hotzones on the associated
image and bind these hotzones to URLs.
<!ENTITY % SHAPE "(rect|circle|poly)">
<!ENTITY % COORDS "CDATA" -- comma separated list of numbers -->
<!ELEMENT MAP - - (AREA)+>
<!ATTLIST MAP
name CDATA #REQUIRED
>
<!ELEMENT AREA - O EMPTY>
<!ATTLIST AREA
shape %SHAPE rect
coords %COORDS #IMPLIED -- defines coordinates for shape --
href %URL #IMPLIED -- this region acts as hypertext link --
nohref (nohref) #IMPLIED -- this region has no action --
alt CDATA #REQUIRED -- needed for non-graphical user agents --
>
Here is a simple example for a graphical navigational toolbar:
<img src="navbar.gif" border=0 usemap="#map1">
<map name="map1">
<area href=guide.html alt="Access Guide" shape=rect coords="0,0,118,28">
<area href=search.html alt="Search" shape=rect coords="184,0,276,28">
<area href=shortcut.html alt="Go" shape=rect coords="118,0,184,28">
<area href=top10.html alt="Top Ten" shape=rect coords="276,0,373,28">
</map>
The MAP element has one attribute NAME
which is used to associate a name with a map. This is then used by the
USEMAP attribute on the IMG element to
reference the map via a URL fragment identifier. Note that the value of
the NAME attribute is case sensitive.
The AREA element is an empty element and so the end tag
is forbidden. It takes the following attributes: SHAPE,
COORDS, HREF, NOHREF and
ALT. The SHAPE and COORDS
attributes define a region on the image. If the SHAPE
attribute is omitted, SHAPE="RECT" is assumed.
SHAPE=RECT COORDS="0, 0, 50%, 100%"
The HREF attribute gives a URL for the target of the
hypertext link. The NOHREF attribute is used when you want
to define a region that doesn't act as a hotzone. This is useful when
you want to cut a hole in an underlying region acting as a hotzone.
If two or more regions overlap, the region defined first in the map
definition takes precedence over subsequent regions. This means that
AREA elements with NOHREF should generally be
placed before ones with the HREF attribute.
The ALT attribute is used to provide text labels which
can be displayed in the status line as the mouse or other pointing
device is moved over hotzones, or for constructing a textual menu for
non-graphical user agents. Authors are strongly recommended to
provide meaningful ALT attributes to support
interoperability with speech-based or text-only user agents.
HTML3.2$B$N(JSGML$B8x3+%+%?%m%0Nc(J
Sample SGML Open Catalog for HTML 3.2
-- html32.soc: HTML 3.2$BJ8=q8!>Z%+%?%m%0(Jcatalog for parsing HTML 3.2 documents --
SGMLDECL "HTML32.dcl"
PUBLIC "-//W3C//DTD HTML 3.2 Final//EN" HTML32.dtd
PUBLIC "-//W3C//DTD HTML 3.2 Draft//EN" HTML32.dtd
PUBLIC "-//W3C//DTD HTML 3.2//EN" HTML32.dtd
PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML" ISOlat1.ent
HTML3.2$B$N(JSGML$B@k8@(J
SGML Declaration for HTML 3.2
This uses the 8 bit ISO Latin-1 character set. The size limits on
properties like literals and tag names have been considerably increased
from their HTML 2.0 values, but it is recommended that user agents avoid
imposing arbitrary length limits.
<!SGML "ISO 8879:1986"
--
$BD61[=qN`I=5-K!Bh(J3.2$BHG$N(JSGML$B@k8@(J
SGML Declaration for HyperText Markup Language version 3.2
$B9q:]I8=`2=5!9=%i%F%s#1$*$h$SA}2C$7$?(J
$B%?%0L>$dJ8;z?t$J$I$N>e8B$r4^$`(J
With support for ISO Latin-1 and increased limits
for tag and literal lengths etc.
--
CHARSET
BASESET "ISO 646:1983//CHARSET
International Reference Version
(IRV)//ESC 2/5 4/0"
DESCSET 0 9 UNUSED
9 2 9
11 2 UNUSED
13 1 13
14 18 UNUSED
32 95 32
127 1 UNUSED
BASESET "ISO Registration Number 100//CHARSET
ECMA-94 Right Part of
Latin Alphabet Nr. 1//ESC 2/13 4/1"
DESCSET 128 32 UNUSED
160 96 32
CAPACITY SGMLREF
TOTALCAP 200000
GRPCAP 150000
ENTCAP 150000
SCOPE DOCUMENT
SYNTAX
SHUNCHAR CONTROLS 0 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 127
BASESET "ISO 646:1983//CHARSET
International Reference Version
(IRV)//ESC 2/5 4/0"
DESCSET 0 128 0
FUNCTION
RE 13
RS 10
SPACE 32
TAB SEPCHAR 9
NAMING LCNMSTRT ""
UCNMSTRT ""
LCNMCHAR ".-"
UCNMCHAR ".-"
NAMECASE GENERAL YES
ENTITY NO
DELIM GENERAL SGMLREF
SHORTREF SGMLREF
NAMES SGMLREF
QUANTITY SGMLREF
ATTSPLEN 65536
LITLEN 65536
NAMELEN 65536
PILEN 65536
TAGLVL 100
TAGLEN 65536
GRPGTCNT 150
GRPCNT 64
FEATURES
MINIMIZE
DATATAG NO
OMITTAG YES
RANK NO
SHORTTAG YES
LINK
SIMPLE NO
IMPLICIT NO
EXPLICIT NO
OTHER
CONCUR NO
SUBDOC NO
FORMAL YES
APPINFO NONE
>
HTML 3.2$BJ8=q7?Dj5A(J
HTML 3.2 Document Type Definition
<!--
W3C$B$ND61[J8=qI=5-K!Bh(J3.2$BHGJ8=q7?Dj5A$O(JW3C$B2q0w$NEjI<$K$h$jHc=Z$5$l$?!#(J
W3C$B$K$D$$$F$O(Jhttp://www.w3.org/$B$K$F;2>H$N$3$H(J
W3C Document Type Definition for the HyperText Markup Language
version 3.2 as ratified by a vote of W3C member companies.
For more information on W3C look at URL http://www.w3.org/
Date: Tuesday January 14th 1997
Author: Dave Raggett <dsr@w3.org>
HTML 3.2$B$O!"(J '96$BG/Aa!9$K4+9p$5$l$?0F7o$r(JHTML 2.0 (RFC 1866)$B$K(J
$B
$B%i%F%s(J1$BJ8;z
<!-- (C) International Organization for Standardization 1986
$B$3$NCm0U$,A4$F$N%3%T!<$K4^$a$i$l$k$J$i$P!"(J
$B=`5r$9$k(J SGML $B%7%9%F%`$H9q:]I8=`2=5!9=(J 8879 $B$GDj$a$i$l$?(J
$B%"%W%j%1!<%7%g%s$K$*$$$F;HMQ$9$k$?$a$N$"$i$f$k7A<0$K$h$k(J
$BJ#@=$N5v2D$,G'$a$i$l$k!#(J
$B$3$l$O(JHTML$B$G$N;HMQ$K$*$$$F!"(J160$B$+$i(J255$B$^$G$N==?J?t$G(J
$BA4$F$N%3!<%I$r%+%P!<$9$k$?$a$K3HD%$5$l$F$$$k!#(J
Permission to copy in any form is granted for use with
conforming SGML systems and applications as defined in
ISO 8879, provided this notice is included in all copies.
This has been extended for use with HTML to cover the full
set of codes in the range 160-255 decimal.
-->
<!-- $BJ8;z
$B%i%F%s(J1$BJ8;z%3!<%II=!!(JTable of printable Latin-1 Character codes
$B
Acknowledgements
The author would like to thank the members of the W3C HTML Editorial
Review Board, members of the W3C staff, and the many other people who
have contributed to this specification.
$B;29MJ88%(J
Further Reading
Further information on W3C activities and pointers to the
status of work on HTML and HTTP etc. can be found at
http://www.w3.org/.
Further information on HTML in particular can be found at
http://www.w3.org/pub/WWW/MarkUp/.
$BD61[=qN`I=5-K!;EMM=qBh(J2.0$BHG$NDj5A!#(J
ftp://ds.internic.net/rfc/rfc1866.txt$B$+$iF~
HTML $B=q<0$+$i$N%U%!%$%k%"%C%W%m!<%I$r
$B$3$l$O(JHTML$B$NI=AH$N7A<0$rDj5A$9$k$b$N$G!"(JHTML 3.2$B$GDj5A$5$l$?I=AH7A<0$N>e0L%;%C%H$K$J$C$F$$$^$9!#(J
ftp://ds.internic.net/rfc/rfc1942.txt$B$+!"(JW3C$B$N;CDj0F$H$7$F(Jhttp://www.w3.org/pub/WWW/TR/WD-tables$B$GF~
HTML $BJ8=q$rJ,@O$9$k:]$N8lWC$N8!F$$K$D$$$F$N@bL@!#(Jhttp://www.w3.org/pub/WWW/TR/WD-html-lex$B$GF~
Further information of HTTP can be found at:
http://www.w3.org/pub/WWW/Protocols.
http://www.w3.org/pub/WWW/Graphics/Color/sRGB.html$B$+$iF~