update docs about :confval:latex_keep_old_macro_names

This commit is contained in:
jfbu 2017-02-18 12:07:44 +01:00
parent 43fd43932d
commit 3a090886b0

View File

@ -1605,22 +1605,23 @@ These options influence LaTeX output. See further :doc:`latex`.
.. confval:: latex_keep_old_macro_names .. confval:: latex_keep_old_macro_names
If ``True`` (default) the ``\strong``, ``\code``, ``\bfcode``, ``\email``, If ``True`` the ``\strong``, ``\code``, ``\bfcode``, ``\email``,
``\tablecontinued``, ``\titleref``, ``\menuselection``, ``\accelerator``, ``\tablecontinued``, ``\titleref``, ``\menuselection``, ``\accelerator``,
``\crossref``, ``\termref``, and ``\optional`` text styling macros are ``\crossref``, ``\termref``, and ``\optional`` text styling macros are
pre-defined by Sphinx and may be user-customized by some pre-defined by Sphinx and may be user-customized by some
``\renewcommand``'s inserted either via ``'preamble'`` key or :dudir:`raw ``\renewcommand``'s inserted either via ``'preamble'`` key or :dudir:`raw
<raw-data-pass-through>` directive. If ``False``, only ``\sphinxstrong``, <raw-data-pass-through>` directive. If ``False``, only ``\sphinxstrong``,
etc... macros are defined (and may be redefined by user). Setting to etc... macros are defined (and may be redefined by user).
``False`` may help solve macro name conflicts caused by user-added latex
packages. The default is ``False`` as it solves macro name conflicts caused by
user-added latex packages. For example ``fontspec v2.6`` defines its own
``\strong`` macro.
.. versionadded:: 1.4.5 .. versionadded:: 1.4.5
.. versionchanged:: 1.6 .. versionchanged:: 1.6
Default was changed from ``True`` to ``False``.
For ``'xelatex'`` engine, the default is ``False`` because LaTeX package .. deprecated:: 1.6
``fontspec v2.6`` defines its own ``\strong`` macro. This setting will be removed at Sphinx 1.7.
.. confval:: latex_elements .. confval:: latex_elements