Skip to content

Commit

Permalink
doc: Fix minor mark-up misses up
Browse files Browse the repository at this point in the history
  • Loading branch information
tk0miya committed Apr 24, 2021
1 parent 778faff commit cb78512
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion doc/latex.rst
Expand Up @@ -158,14 +158,14 @@ Keys that you may want to override include:
Greek or Cyrillic in a document using ``'pdflatex'`` engine.

.. versionchanged:: 4.0.0

- The font substitution commands added at ``2.0`` have been moved
to the ``'fontsubstitution'`` key, as their presence here made
it complicated for user to customize the value of ``'fontpkg'``.
- The default font setting has changed: it still uses Times and
Helvetica clones for serif and sans serif, but via better, more
complete TeX fonts and associated LaTeX packages. The
monospace font has been changed to better match the Times clone.


``'fncychap'``
Inclusion of the "fncychap" package (which makes fancy chapter titles),
Expand Down

3 comments on commit cb78512

@jfbu
Copy link
Contributor

@jfbu jfbu commented on cb78512 Jun 13, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tk0miya I am only realizing now that this change breaks PDF build of document (or at least raises an error). Indeed the latex output looks like

\begin{itemize}
\DUrole{versionmodified,changed}{Changed in version 4.0.0: }\item {} 
\sphinxAtStartPar
The font substitution commands added at \sphinxcode{\sphinxupquote{2.0}} have be

and text before the \item{} causes a LaTeX error.

@tk0miya
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strange. We need to investigate why the header of versionmodified is displayed inside the itemize env.

@jfbu
Copy link
Contributor

@jfbu jfbu commented on cb78512 Jun 13, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

indeed, I created ticket #9330

Please sign in to comment.