And add <type>TextColor and <type>TeXextras for <type>=hint, important,
note, tip for variants which do not trigger for sphinxheavybox but
still uses sphinxlightbox (suitably enhanced).
Similar named TeXcolor and TeXextras options for \sphinxbox.
This exposed names at ``sphinx.builders.html.sphinxcontrib.serializinghtml``,
etc, which offers no benefit. This was originally broken in commit
9dfbfbf16b, four years ago.
- Refactor usage of ``inventories.cache`` in ``load_mappings()``
- Iterate once over ``cached_vals``
- Avoid a line continuation character in ``_resolve_reference()``
If pygments fails to lex a source string as the specified highlight
language, Sphinx prints a warning. Previously, that warning did not
include the actual source text, although it does include location
information.
However, in some cases the location information may be missing, there
may be multiple highlighted literals on the same line, or the rST is
automatically generated somehow. In such cases, it can be difficult
to determine the source text that led to the error.
With this change, the source text is included in the warning.
Before, the apply method was one big 400-line chunk. This just splits it
up into more manageable chunks by introducing a ``_NodeUpdater`` auxiliary
class holding logic for updating various types of references.
Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>
Internally replace "strokepath" operation for drawing the border
(which mandated constant border-width) by only "fillpath" operations.
This also allowed to significantly simplify some other aspects of the
code related to box-decoration-break=slice.
The internally used color name for the (optional) shadow of
code-blocks had changed at one place but not another, so
using pre_box-shadow-TeXcolor option of 'sphinxsetup'
with latex_elements was broken since.
It is however undecided if the slice style should suppress the
horizontal shadow forcefully. It does not so far.
This commit has removed the \spx@ShadowFBox macro which got so
simple that its meaning could be put directly into \FrameCommand
definition.
Sorry about this, the \expanded was added to pdflatex in 2019 only
(but was available earlier to lualatex). This is in contrast
with \unexpanded which has been available for more than 15 years.
On a system with LaTeX package pict2e unavailable it would lead
to an infinite loop. Caused by forgotten update of a macro name
which has changed meaning.
