This is 2nd level heading

This is a paragraph before a definition list (dl). In principle, such a list should consist of terms and associated definitions. But many authors use dl elements for fancy "layout" things. Usually the effect is not too bad, if you design user style sheet rules for dlwhich are suitable for real definition lists.

recursion

see recursion

recursion, indirect

see indirect recursion

indirect recursion

see recursion, indirect

term

a word or other expression taken into specific use in a well-defined meaning, which is often defined rather rigorously, even formally, and may differ quite a lot from an everyday meaning

Text-level markup

• CSS (an abbreviation; abbr markup used)
• radar (an acronym; acronym markup used)
• bolded (b markup used - just bolding with unspecified semantics)
• big thing (big markup used)
• large size (font size=6 markup used)
• Courier font (font face=Courier markup used)
• red text (font color=red markup used)
• Origin of Species (a book title; cite markup used)
• a[i] = b[i] + c[i); (computer code; code markup used)
• here we have some deleted text (del markup used)
• an octet is an entity consisting of eight bits (dfn markup used for the term being defined)
• this is very simple (em markup used for emphasizing a word)
• Homo sapiens (should appear in italics; i markup used)
• here we have some inserted text (ins markup used)
• type yes when prompted for an answer (kbd markup used for text indicating keyboard input)
• Hello! (q markup used for quotation)
• He said: She said Hello! (a quotation inside a quotation)
• you may get the message Core dumped at times (samp markup used for sample output)
• this is not that important (small markup used)
• overstruck (strike markup used; note: s is a nonstandard synonym for strike)
• this is highlighted text (strong markup used)
• In order to test how subscripts and superscripts (sub and sup markup) work inside running text, we need some dummy text around constructs like x₁ and H₂O (where subscripts occur). So here is some fill so that you will (hopefully) see whether and how badly the subscripts and superscripts mess up vertical spacing between lines. Now superscripts: M^lle, 1^st, and then some mathematical notations: e^x, sin² x, and some nested superscripts (exponents) too: e^x2 and f(x)^g(x)a+b+c (where 2 and a+b+c should appear as exponents of exponents).
• text in monospace font (tt markup used)
• underlined text (u markup used)
• the command cat filename displays the file specified by the filename (var markup used to indicate a word as a variable).

Some of the elements tested above are typically displayed in a monospace font, often using the same presentation for all of them. This tests whether that is the case on your browser:

• This is sample text inside code markup
• This is sample text inside kbd markup
• This is sample text inside samp markup
• This is sample text inside tt markup

This is a text paragraph that contains some inline links. Generally, inline links (as opposite to e.g. links lists) are problematic from the usability perspective, but they may have use as “incidental”, less relevant links. See the document Links Want To Be Links.

Character test

The following table has some sample characters with annotations. If the browser’s default font does not contain all of them, they may get displayed using backup fonts. This may cause stylistic differences, but it should not prevent the characters from being displayed at all.

Char.	Explanation	Notes
ê	e with circumflex	Latin 1 character, should be ok
—	em dash	Windows Latin 1 character, should be ok, too
Ā	A with macron (line above)	Latin Extended-A character, not present in all fonts
Ω	capital omega	A Greek letter
−	minus sign	Unicode minus
⌀	diameter sign	relatively rare in fonts