Generic items#
These are the things that don’t quite fit into other groupings.
Inline Markup#
One of the nice things about markup languages is the ability to have inline
markup. This makes the presentation much nicer. The bold text shouldn’t
be too overbearing. It is very common to have inline code
as well. It is
important to ensure that the inline code doesn’t have a line height that is
greater than the regular prose; otherwise the spacing looks weird.
It is also possible to use explicit roles to do things like a subscript,
a superscript, emphasis, strong, and
literal
.
Hyperlinks#
It is a website, so it’ll have hyperlinks like http://www.python.org (inline), or Python [4] (external reference), example (internal reference), Python web site (external hyperlinks with embedded URI), 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).
reStructuredText has character-level inline markup too. It’s ugly to write, but
someone might be using it, so here’s an example: reStructured
Text.
It is also possible to link to documented items, such as
api_sample.RandomNumberGenerator
.
Interpreted text#
The default role for “interpreted text” (AKA single backticks) is Title Reference. There are other reference syntaxes as well: PEP 287 and RFC 2822.
If the --pep-references
option was supplied, there should be a live link to
PEP 258 here.
GUI labels#
According to the RST demo, GUI labels (like this label) are a way to indicate that some action is to be taken by the user. Like inline code literals, GUI labels should not run over line height.
Long inline code wrapping#
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).
A very long “word”: LoremipsumdolorsitametconsetetursadipscingelitrseddiamnonumyeirmodtemporinviduntutlaboreetdoloremagnaaliquyameratseddiamvoluptuaAtveroeosetaccusametjustoduodoloresetearebum
A very long path: /my/network/directory/where/all/my/fancy/files/reside/but/I/tend/to/hide/them/in/very/long/subdirectories/to/keep/them/very/hard/to/find/even/for/myself.exe
Math#
This is a test. Here is an equation: \(X_{0:5} = (X_0, X_1, X_2, X_3, X_4)\). Here is another:
You can add a link to equations like the one above (1) by using
:eq:
.
References#
Footnotes#
Citations#
This citation has some code blocks
in it, maybe some bold and
italics too. Heck, lets put a link to a meta citation [13] too.
This citation will have one backlink.
Here’s a reference to the above, [12] citation.
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, 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 [4]”.
Targets may be indirect and anonymous. Thus this phrase may also refer to the Targets section.
Target Footnotes#
Centered text#
You can create a statement with centered text with .. centered::
This is centered text!
Rubric#
A rubric is like an informal heading that doesn’t correspond to the document’s structure.
—https://docutils.sourceforge.io/docs/ref/rst/directives.html#rubric
Wikipedia says it is something different:
A rubric is a word or section of text that is traditionally written or printed in red ink for emphasis.
This is stylized as docutils tells us to stylize it, since it is used for footnote headers (see end of https://docs.python.org/3/reference/lexical_analysis.html)
This is a rubric