Configuration file settings override the built-in defaults, and
command-line options override all.
Some settings override also an associated setting; [10]
others append values from the various sources. [11]
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 may have nothing to do with 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. [11]
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.py
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 [12] 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.
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. [11]
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. [11]
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]:
Enable the promotion of a lone top-level section title
to document title (and subsequent section title to document
subtitle promotion; docutils.transforms.frontmatter.DocTitle).
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).
Note: This setting defines a "search path" (similar to the PATH variable for
executables). However, the term "path" is already used in the
stylesheet_path setting with the meaning of a file location.
Default:
the working directory of the process at launch
and the directory with default stylesheet files
(writer and installation specific).
Use the --help option to get the exact value.
List of paths to CSS stylesheets (comma-separated). Relative paths are
expanded if a matching file is found in the stylesheet_dirs.
If embed_stylesheet is False, paths are rewritten relative to
the output_path (if specified) or the current work directory.
Only lines above and below the table and a thin line after the head.
captionbelow:
Place the table caption below the table (new in Docutils 0.17).
In addition, the HTML writers process:
colwidths-auto:
Delegate the determination of table column widths to the back-end
(leave out the <colgroup> column specification).
Overridden by the "widths" option of the "table" directive.
colwidths-grid:
Write column widths determined from the source to the HTML file.
Overridden by the "widths" option of the "table" directive.
The maximum length (in characters) for one-column field names. Longer
field names will span an entire row of the table used to render the field
list. 0 indicates "no limit". See also option_limit.
The maximum length (in characters) for one-column options in option lists.
Longer options will span an entire row of the table used to render
the option list. 0 indicates "no limit".
See also field_name_limit.
Append an empty anchor element with a href to the section to
section headings. See responsive.css for an example how this can be
styled to show a symbol allowing users to copy the section's URL.
Name of an installed S5 theme, to be copied into a ui/<theme>
subdirectory, beside the destination file (output HTML). Note
that existing theme files will not be overwritten; the existing
theme directory must be deleted manually.
Overrides also theme_url. [10]
Embed the stylesheet(s) in the header of the output file. The
stylesheets must be accessible during processing. Currently, this
fails if the file is not available via the given path (i.e. the
file is not searched in the TeX input path).
See also embed_stylesheet [html writers].
LaTeX code that will be inserted in the document preamble.
Can be used to load packages with options or (re-) define LaTeX
macros without writing a custom style file.
Use legacy functions \DUtitle and \DUadmonition with a
comma-separated list of class values as optional argument. If False, class
values are handled with wrappers and admonitions use the DUadmonition
environment. See Generating LaTeX with Docutils for details.
Per default the LaTeX writer uses \hyperref for hyperlink
references to internal or implicit targets.
Specify an alternative reference command name, e.g., "ref" or "pageref"
to get the section number or the page number as reference text.
The separator between section number prefix and enumerator for
compound enumerated lists (see compound_enumerators).
Generally it isn't recommended to use both, numbered sub-sections and
nested enumerated lists with compound enumerators. This setting avoids
ambiguity in the situation where a section "1" has a list item
enumerated "1.1", and subsection "1.1" has list item "1". With a
separator of ".", these both would translate into a final compound
enumerator of "1.1.1". With a separator of "-", we get the
unambiguous "1-1.1" and "1.1-1".
If embed_stylesheet is False (default), the stylesheet files are
referenced with \usepackage (values with extension .sty or no
extension) or \input (any other extension).
LaTeX will search the specified files in the TeX input path.
Some values change the behaviour of the LaTeX writer:
Note: This setting defines a "search path" (similar to the PATH variable
for executables). However, the term "path" is already used in the
stylesheet_path setting with the meaning of a file location.
% Linux Libertine (free, wide coverage, not only for Linux)
\setmainfont{Linux Libertine O}
\setsansfont{Linux Biolinum O}
\setmonofont[HyphenChar=None]{DejaVu Sans Mono}
The optional argument HyphenChar=None to the monospace font
prevents word hyphenation in literal text.
Path [13] to a configuration/mapping file for additional ODF options.
In particular, this file may contain a mapping of default style names to
names used in the resulting output file.
See section How to use custom style names in the
ODT Writer documentation for details.
Specify the thickness of table borders in thousands of a centimetre.
The Table styles section in the ODT Writer documentation describes
alternatives for additional customisation of the table style.
buildhtml.py generates HTML documents from reStructuredText source
files in a set of directories and their subdirectories.
All visited directories are scanned for "docutils.conf" files which are
parsed after the standard configuration files. Path settings [13] in
these files are resolved relative to the respective directory.
List of glob-style patterns [9] (colon-separated).
Matching directories are skipped. Values are appended. [11]
Patterns are expanded similar to path settings [13] and matched
against the absolute path of to-be-processed directories.
Example: a directory is pruned if it contains a "docutils.conf" file
with the lines
[buildhtml application]
prune: '.'
The default patterns skip auxiliary directories from Python or
popular version control tools anywhere [8].
List of glob-style [9] patterns (colon-separated).
Files with matching filename are treated as source documents.
Values in configuration files overwrite the default and are
overwritten by the command line option.
Writer component name.
One of "html", "html4", "html5", "latex", "xelatex", "odt", "xml",
"pseudoxml", "manpage", "pep_html", "s5", an alias,
or the import name of a plug-in writer module.
Path to an additional configuration file.
The file is processed immediately (if it exists) with
settings overriding defaults and earlier settings.
Filesystem path settings [13] contained within the config file will be
interpreted relative to the config file's location (not relative to the
current working directory).
Multiple --config options may be specified;
each will be processed in turn.
Formerly, Docutils configuration files contained a single "[options]"
section only. This was found to be inflexible, and in August 2003
Docutils adopted the current component-based configuration file
sections as described above.
Up to version 2.0, Docutils will still recognize the old "[options]"
section, but complain with a deprecation warning.
To convert existing config files, the easiest way is to change the
section title: change "[options]" to "[general]". Most settings
haven't changed. The only ones to watch out for are these:
Up to Docutils 0.21, the input_encoding default value was None and
the actual input encoding detected from a Unicode byte order mark (BOM)
or an encoding declaration in the source.
The default input encoding changed to "utf-8" in Docutils 0.22.
Currently, auto-detection can be selected with an input_encoding value
None (rsp. an empty string in a configuration file).
However, this feature is deprecated and will be removed in
Docutils 1.0. See the inspecting_codecs package for a replacement.