LaTeX: fix nits with some mark-up in doc and code comment

This commit is contained in:
Jean-François B 2023-03-19 19:09:08 +01:00
parent c951f5f639
commit cf6273a6b1
3 changed files with 4 additions and 4 deletions

View File

@ -1117,10 +1117,10 @@ Do not use quotes to enclose values, whether numerical or strings.
``importantBgColor``, ``tipBgColor``
.. |notetextcolors| replace:: ``noteTextColor``, ``hintTextColor``,
``importantTextColor``, ``tipTextColor``
``importantTextColor``, ``tipTextColor``
.. |notetexextras| replace:: ``noteTeXextras``, ``hintTeXextras``,
``importantTeXextras``, ``tipTeXextras``
``importantTeXextras``, ``tipTeXextras``
.. |warningbdcolors| replace:: ``warningBorderColor``, ``cautionBorderColor``,
``attentionBorderColor``, ``dangerBorderColor``,

View File

@ -925,7 +925,7 @@ will be set to white}%
padding=\fboxsep,% but done here out of habit
border-radius=\fboxsep,%
box-shadow=none,%
% As xcolor is perhaps not loaded we can not use border-TeXcolor=VerbatimColor
% As xcolor is perhaps not loaded we can not use background-TeXcolor=VerbatimColor
% which would not be compatible with \definecolor syntax.
border-TeXcolor={RGB}{32,32,32},% the default VerbatimBorderColor
background-TeXcolor={gray}{0.95},% the default VerbatimColor

View File

@ -97,7 +97,7 @@
\@setminipage
}%
\color@begingroup % workaround upstream framed.sty bug
\csname ifspx@topic@withtextcolor\endcsname
\ifspx@topic@withtextcolor
\color{sphinxtopicTextColor}%
\fi
\spx@topic@TeXextras