Inline Markup & References¶
Hint
The contents of this page originate from https://sphinx-rtd-theme.readthedocs.io/en/stable/demo/demo.html
Paragraphs contain text and may contain inline markup: emphasis, strong emphasis, inline literals,
standalone hyperlinks (http://www.python.org) 4, external hyperlinks (Python), internal cross-references (example),
external hyperlinks with embedded URIs (Python web site), footnote references
(manually numbered 1, anonymous auto-numbered 3, labeled auto-numbered 2, or symbolic *),
citation references (12), substitution references (
), and inline hyperlink targets
(see Targets below for a reference back to here). Character-level inline markup is also possible
(although exceedingly ugly!) in reStructuredText.
Also with sphinx.ext.autodoc, which I use in the demo, I can link to test_py_module.test.Foo.
It will link you right to my code documentation for it.
The default role for interpreted text is Title Reference. Here 11 are some explicit interpreted text roles:
a PEP reference (PEP 287); an RFC reference (RFC 2822); a subscript; a superscript;
and explicit roles for standard inline markup.
GUI labels are a useful way to indicate that Some action is to be taken by the user.
The GUI label should not run over line-height so as not to interfere with text from adjacent lines.
Key-bindings indicate that the read is to press a button on the keyboard or mouse,
for example MMB and Shift-MMB. Another useful markup to indicate a user action
is to use menuselection this can be used to show short and long menus in software.
For example, and menuselection can be seen here that breaks is too long to fit on this line.
.
Let’s test wrapping and whitespace significance in inline literals:
This is an example of --inline-literal --text, --including some--
strangely--hyphenated-words. Adjust-the-width-of-your-browser-window
to see how the text is wrapped. -- ---- -------- Now note the
spacing between the words of this sentence (words
should be grouped in pairs).
If the --pep-references option was supplied, there should be a live link to PEP 258 here.
References¶
Footnotes¶
- 1(1,2)
A footnote contains body elements, consistently indented by at least 3 spaces.
This is the footnote’s second paragraph.
- 2(1,2)
Footnotes may be numbered, either manually (as in 1) or automatically using a “#”-prefixed label. This footnote has a label so it can be referred to from multiple places, both as a footnote reference (2) and as a hyperlink reference (label).
- 3
This footnote is numbered automatically and anonymously using a label of “#” only.
- *
Footnotes may also use symbols, specified with a “*” label. Here’s a reference to the next footnote: †.
- †
This footnote shows the next symbol in the sequence.
- 4
Here’s a referenced footnote, with a reference to an existent footnote: 5.
- 5
This is another footnote
Citations¶
- 11
This is the citation I made, let’s make this extremely long so that we can tell that it doesn’t follow the normal responsive table stuff.
- 12(1,2)
This citation has some
code blocksin it, maybe some bold and italics too. Heck, lets put a link to a meta citation 13 too.- 13
This citation will have two backlinks.
Here’s a reference to the above, 12.
Here is another type of citation: citation
Targets¶
This paragraph is pointed to by the explicit “example” target. A reference can be found under Inline Markup & References, above. Inline hyperlink targets are also possible.
Section headers are implicit targets, referred to by name. See Targets.
Explicit external targets are interpolated into references such as “Python”.
Targets may be indirect and anonymous. Thus this phrase may also refer to the Targets section.
Driverless