9 Paragraphs contain text and may contain inline markup: *emphasis*,
10 **strong emphasis**, ``inline literals``, standalone hyperlinks
11 (http://www.python.org), external hyperlinks (Python_), internal
12 cross-references (example_), external hyperlinks with embedded URIs
13 (`Python web site <http://www.python.org>`__), footnote references
14 (manually numbered [1]_, anonymous auto-numbered [#]_, labeled
15 auto-numbered [#label]_, or symbolic [*]_), citation references
16 ([CIT2002]_), substitution references (|example|), and _`inline
17 hyperlink targets` (see Targets_ below for a reference back to here).
18 Character-level inline markup is also possible (although exceedingly
19 ugly!) in *re*\ ``Structured``\ *Text*. Problems are indicated by
20 |problematic| text (generated by processing errors; this one is
23 The default role for interpreted text is `Title Reference`. Here are
24 some explicit interpreted text roles: a PEP reference (:PEP:`287`); an
25 RFC reference (:RFC:`2822`); a :sub:`subscript`; a :sup:`superscript`;
26 and explicit roles for :emphasis:`standard` :strong:`inline`
29 .. DO NOT RE-WRAP THE FOLLOWING PARAGRAPH!
31 Let's test wrapping and whitespace significance in inline literals:
32 ``This is an example of --inline-literal --text, --including some--
33 strangely--hyphenated-words. Adjust-the-width-of-your-browser-window
34 to see how the text is wrapped. -- ---- -------- Now note the
35 spacing between the words of this sentence (words
36 should be grouped in pairs).``
38 If the ``--pep-references`` option was supplied, there should be a
39 live link to PEP 258 here.