-

are too small to be usable in the default configuration of some versions of NCSA Mosaic. Since the TITLE in the HEAD element is displayed on the window bar (and should be context-independent), the

...

... Encloses a block of text that is a quote.

). Often displayed as italic.

 ... 

...

Begin a paragraph (the closing

• ...

1. ...

or
).
1. ...
Directory list (should be multi-column, but isn't in most implementations).
2. Begins each item in the above lists. An inline image can be used as a custom bullet (preceding the list item) using the attribute BULLET="URL". (This is not yet a part of standard HTML 2.0.)

   ...

   ...

   Definition list. Can also be useful for writing dialogue (as in a play). Use

   for tighter rendering. There does not actually have to be a

   for each

   or vice versa.

   Begins each item title in DL.

   Begins each item definition in DL. The list item closing tags

, , and are optional. Lists can be nested (i.e. included in an
3. ...
item in a
...
or a
...
list, or inside a
...
item in a

...

list). List items are not supposed to directly contain

-

headings,

---

, or

(though

and

elements can contain a

or

which itself includes them). Hypertext Anchors/Links: ... Creates a link (HREF=) or anchor (NAME=) or both. (Less commonly used attributes are URN=, REL=, REV=, TITLE=, and METHODS=.) Non-HTML resource types referenced in links can be displayed by external viewers. An anchor element MUST contain something other than whitespace, or it won't work on many browsers. It is better if text contained within a link element is not something relatively meaningless like Click Here, but rather something which describes what the link is pointing to: Chelsea's cat Socks. (Remember that not everybody is using a mouse anyway, so the word "Select" is preferable to "Click".) Anchors/links CANNOT BE NESTED, directly or indirectly, so that even code like ......... ...... is forbidden. (In the upcoming HTML3 language, the attribute ID="...", which will be able to be used with most tags, will replace , so that almost any element will be able to be the target of a link.) Inline images: Inserts an image from the URL as part of the surrounding text flow (if any); GIF 87a (.gif) and X Bitmap (.xbm) formats are supported. (JPEG's are supported by Netscape.) ALIGN=TOP These attributes control the placement of short ALIGN=MIDDLE captions alongside an image (but will probably not do what you expect in the middle of text). WIDTH= Specify the width and height of the image in HEIGHT= pixels. Greatly speed display of document in Netscape (not yet part of standard HTML 2.0). ISMAP The image is a clickable imagemap. Be sure to specify meaningful text in the ALT attribute value (for use in non-graphic environments), especially if the image is in a link. If the image is purely decorative, use ALT="" to avoid annoying "[IMAGE]" clutter in Lynx. Using too many and too large inline bitmaps can be very inconsiderate, especially on your home page and other pages that are linked to from outside, (unless they are publicized as picture galleries). Many people are using 14.4k modems, and it is particularly frustrating when with no advance warning you have to wait for a lot of big .GIF's to load -- before you're even able to decide whether or not there is actually anything of interest on the page. In any case, inline images will often be shown with few colors (only 50 in some versions of Mosaic), whereas external images will be shown with the maximum available number of colors -- so it is best to use a small sample (thumbnail) as a link to the full size image. Text flow:
Forces a line break Logical styles: ... Emphasized (often rendered as italic). ... Strong emphasis (often rendered bold). ... Citation of book, article, movie, etc. (often rendered italic). ... Piece of computer source code (often rendered in fixed-width font). ... Example of keyboard entry (user input). ... Literal characters (e.g. computer output). ... Name of variable (often rendered as italic). ... Word to be introduced/defined (not yet part of standard HTML 2.0). Fonts: ... Bold font. ... Italic font. ... Typewriter (fixed-width) font. ... Underlined (not yet part of standard HTML 2.0; can also create confusion with links, which are rendered as underlined on many browsers). It is preferable to use logical styles rather than hard-wired fonts (bold, italic, etc. may not be available in non-graphical environments, anyway). Styles and fonts are NOT guaranteed to be rendered cumulatively (i.e. Text may look the same as plain Text, and the italic text in

RomanText ItalicText

may not be the appropriate size for a H1 heading). The logical style, font, and link/anchor elements generally can contain only each other (and and
), and not lists and high-level tags. The headings

-

,

...

in a

...

list, and

...

in MENU or DIR can also contain only these tags. It is best not to have whitespace after an opening tag of a style, font, or anchor element, or before a closing tag (i.e. Text is preferable to Text ); such whitespace produces displeasing visual results on some browsers. Special Characters (Entities): & or & & < or < < > or > > These three characters should be escaped with the above ampersand entities everywhere in a document where they are not intended to be used with their HTML meanings. Other entities (such as "é" etc.) are available to encode the alphabetic characters in positions 192-255 of the ISO 8859-1 Latin 1 character set for European languages. Numeric entities can be used for characters in the range 160-191 with some hope of success (such as © for the copyright symbol, since not all browsers understand ©). Not all browsers understand   or even treat   as a space -- a safe alternative is (but this will not act as non-breaking on most browsers). The range 127-159 is undefined in ISO 8859-1, and should not be used. A double-quote character must be escaped as " or " inside an attribute value. Characters in URL's are best escaped with %-hex-digits (e.g. %26 for "&"). Comments: