Configuration file settings override the built-in defaults, and
command-line options override all.
Some settings override also an associated setting; [11]
others append values from the various sources. [12]
Configuration files are used for persistent customization;
they can be set once and take effect every time you use a component,
e.g., via a front-end tool.
By default, Docutils checks the following places for configuration
files, in the following order:
/etc/docutils.conf: This is a system-wide configuration file,
applicable to all Docutils processing on the system.
./docutils.conf: This is a project-specific configuration file,
located in the current directory.
The Docutils front end has to be executed from the directory
containing this configuration file for it to take effect (note that
this directory may differ from the location of the source files).
~/.docutils: This is a user-specific configuration file,
located in the user's home directory.
If more than one configuration file is found, all will be read and
later entries will override earlier ones. [12]
For example, a "stylesheet" entry in a user-specific configuration file
will override a "stylesheet" entry in the system-wide file.
The default implicit config file paths can be overridden by the
DOCUTILSCONFIG environment variable. DOCUTILSCONFIG should
contain a colon-separated (semicolon-separated on Windows) sequence of
config file paths to search for; leave it empty to disable implicit
config files altogether. Tilde-expansion is performed on paths.
Paths are interpreted relative to the current working directory.
Empty path items are ignored.
In addition, configuration files may be explicitly specified with the
--config command-line option. These configuration files are read after
the three implicit ones listed above (or the ones defined by the
DOCUTILSCONFIG environment variable), and its entries will have
priority.
Configuration files are UTF-8-encoded text files. The configparser
module from Python's standard library is used to read them.
From its documentation:
A configuration file consists of sections, each led by a [section]
header, followed by key/value entries separated by a specific string
(= or : by default).
[…] Leading and trailing whitespace is removed from keys and values.
[…] Configuration files may include comments, prefixed by specific
characters (# and ; by default).
The following conventions apply to Docutils configuration files:
Configuration file entry names correspond to internal runtime
settings. Underscores ("_") and hyphens ("-") can be used interchangeably
in entry names; hyphens are automatically converted to underscores.
Entries with non-applicable or misspelled entry names are silently ignored.
For boolean settings (switches), the following values are
recognized (case-independent):
True:
"true", "yes", "on", "1"
False:
"false", "no", "off", "0", "" (no value)
Lists are specified either comma- or colon-separated:
Below are the Docutils runtime settings, listed by config file section.
Sections correspond to Docutils components (module name or alias; always
in lowercase letters).
[applications], application dependencies, and the section
specific to the Application (front-end tool) in use
("[... application]").
Since any setting may be specified in any section, this ordering
allows component- or application-specific overrides of earlier
settings. For example, there may be Reader-specific overrides of
general settings; Writer-specific overrides of Parser settings;
Application-specific overrides of Writer settings; and so on.
If multiple configuration files are applicable, the process is
completed (all sections are applied in the order given) for each one
before going on to the next. For example, a "[pep_html writer]
stylesheet" setting in an earlier configuration file would be
overridden by an "[html4css1 writer] stylesheet" setting in a later
file.
Individual configuration sections and settings are described
in the following sections.
Some knowledge of Python is assumed for some attributes.
Prefix prepended to all auto-generated identifier keys generated within
the document, after id_prefix. Ensure the value conforms to the
restrictions on identifiers in the output format, as it is not subjected to
the identifier normalization.
A trailing "%" is replaced with the tag name (new in Docutils 0.16).
Default:
"%" (changed from "id" in Docutils 0.18).
Option:
--auto-id-prefix (hidden, intended mainly for programmatic use).
Include a time/datestamp in the document footer. Contains a
format string for Python's time.strftime().
Configuration file entry examples:
# Equivalent to --date command-line option, results in
# ISO 8601 extended format datestamp, e.g. "2001-12-21":
datestamp: %Y-%m-%d
# Equivalent to --time command-line option, results in
# date/timestamp like "2001-12-21 18:43 UTC":
datestamp: %Y-%m-%d %H:%M UTC
# Disables datestamp; equivalent to --no-datestamp:
datestamp:
A system message level threshold; non-halting system messages at
or above this level will produce a non-zero exit status at normal
exit. Exit status is the maximum system message level plus 10 (11
for INFO, etc.).
The threshold at or above which system messages are converted to
exceptions, halting execution immediately. If traceback is set, the
exception will propagate; otherwise, Docutils will exit.
Prefix prepended to all identifier keys generated within the document.
Ensure the value conforms to the restrictions on identifiers in the output
format, as it is not subjected to the identifier normalization.
See also auto_id_prefix.
Default:
"" (no prefix).
Option:
--id-prefix (hidden, intended mainly for programmatic use).
Sets the document language, also used for localized directive and
role names as well as Docutils-generated text.
A typical language identifier consists of a 2-letter language code
from ISO 639 (3-letter codes can be used if no 2-letter code
exists). The language identifier can have an optional subtag,
typically for variations based on country (from ISO 3166
2-letter country codes). Avoid subtags except where they add
useful distinguishing information. Examples of language tags
include "fr", "en-GB", "pt-br" (the same as "pt-BR"), and
"de-1901" (German with pre-1996 spelling).
The language of document parts can be specified with a
"language-<language tag>" class attribute, e.g.
.. class:: language-grc for a quote in Ancient Greek.
The text encoding [13] for output.
The special value "unicode" can be used with
the Publisher convenience functions publish_string() and
publish_from_doctree() to skip encoding and return a str instance
instead of bytes.
This setting is ignored by the ODF/ODT Writer which always usues UTF-8.
Default:
"utf-8".
Option:
--output-encoding (shortcut -o removed in Docutils 0.22).
Path to a file where Docutils will write a list of files that
were required to generate the output, e.g. included files or embedded
stylesheets. [1] The format is one path per line with
forward slashes as separator, the encoding is UTF-8.
Set it to "-" in order to write dependencies to stdout.
This option is particularly useful in conjunction with programs like
make using Makefile rules like:
Base directory, prepended to a filesystem path starting with "/" when
including files with the "include", "raw", or "csv-table"
directives.
Also applied to the "uri" attribute of an <image> or <figure> starting
with "/" when it is converted to a local filesystem path.
Not applied to absolute Windows paths and file: URIs.
Example:
The HTML server for a documentation project serves files from the
"DocumentRoot" /var/www/html/.
Image files are stored in a dedicated directory /var/www/html/pictures/.
With root-prefix=/var/www/html, the rST "image" directive
.. image:: /pictures/mylogo.png
works for LaTeX output and HTML output with embedded images as well as
for HTML output with images included via URI reference.
Include a "View document source" link in the document footer. The URL will
be relative to the output_path (if specified) or the current work directory.
When processing a document tree with the Visitor pattern, raise an
error if a writer does not support a node type listed as optional.
For transitional development use.
Default:
None (disabled).
Option:
--strict-visitor (hidden, for development use only).
List of "classes" attribute values (comma-separated).
Values are appended. [12]
Matching elements are removed from the document tree
(by the StripClassesAndElements transform).
The document title as metadata which does not become part of the
document body. Stored as the document's title attribute.
For example, in HTML output the metadata document title
appears in the title bar of the browser window.
Enable or disable Python tracebacks when system messages with
a severity above the halt_level and other exceptions occur.
Useful for debugging, and essential for issue reports.
Exceptions are allowed to propagate, instead of being
caught and reported (in a user-friendly way) by Docutils.
Enable directives inserting the contents of external files,
such as "include" directive or the "raw" and "csv-table"
directives with option "url" or "file".
A "warning" system message (including the directive text) is inserted
instead. (See also raw_enabled for another security-relevant setting.)
Maximal number of characters in an input line or "substitution"
definition. To prevent extraordinary high processing times or memory
usage for certain input constructs, a "warning" system message is
inserted instead.
Enable the "raw" directive. A "warning" system message
(including the directive text) is inserted instead. See also
file_insertion_enabled for another security-relevant setting.
Allows character level inline markup without escaped whithespace and is
especially suited for languages that do not use whitespace to separate words
(e.g. Japanese, Chinese).
List with language tag and a string of four typographical quote
characters (primary open/close, secondary open/close) for use by
the SmartQuotes transform.
Values are appended. [12]
Example:
Ensure a correct leading apostrophe in 's Gravenhage in Dutch (at the
cost of incorrect opening single quotes) and set French quotes to double
and single guillemets with inner padding [3]:
Parser for Markdown (CommonMark) with rST-compatibility extensions
provided by the 3rd party package myst-docutils.
See MyST with Docutils and MyST's Sphinx configuration options.
(Some settings are not applicable with Docutils,
docutils --parser=myst--help shows available options.)
Enable the promotion of a lone top-level section title
to the document title (and subsequent section title
to document subtitle) by the DocTitle transform.
Scramble email addresses to confuse harvesters. In the reference
URI, the "@" will be replaced by %-escapes (as of RFC 1738). In
the visible text (link text) of an email reference, the "@" and
all periods (".") will be surrounded by <span> tags.
Furthermore, HTML entities are used to encode these characters in
order to further complicate decoding the email address. For
example, "abc@example.org" will be output as:
Remove extra vertical whitespace between items of bullet lists and
enumerated lists, when list items are all "simple" (i.e., items
each contain one paragraph and/or one "simple" sub-list only).
With the "html5" writer, the setting can be overridden for individual
lists using the "class" directive (values "compact" and "open").
Remove extra vertical whitespace between items of field lists that
are "simple" (i.e., all field bodies each contain at most one paragraph).
With the "html5" writer, the setting can be overridden for individual
lists using the "class" directive (values "compact" and "open").
Embed stylesheet(s) in the HTML output. The stylesheet files
must be specified by the stylesheet_path setting and must be
accessible during processing.
See also embed_stylesheet [latex writers].
The format of mathematical content ("math" directive and role) in
the output document. Supported values are (case insensitive):
HTML:
Format math in standard HTML enhanced by CSS rules.
Requires the math.css stylesheet (in the system
stylesheet directory)
A stylesheet_path
can be appended after whitespace. The specified
stylesheet(s) will only be referenced or embedded if required
(i.e. if there is mathematical content in the document).
Self-contained documents (no JavaScript, no external downloads).
MathML is part of the HTML5 standard [5] and
supported by all major browsers (since January 2023 also by Chrome).
Docutil's latex2mathml converter supports a considerable