Jean-François B.
Jean-François B.
@dbitouze I did not investigate where the `\subsubsection*` mark-up originates but defining appropriately the `sphinxclasssd-tab-set`, `sphinxclasssd-tab-item` and `sphinxclasssd-tab-content` LaTeX environment could transmogrify the mark-up you show into the one you...
I tried with ```latex % Support **experimental** pour les tab-set de sphinx-design % cf https://github.com/executablebooks/sphinx-design/issues/218 % ATTENTION C'EST FRAGILE CAR IL NE FAUT PAS QUE LE MARK-UP LATEX DE %...
@dbitouze I should probably have proposed ```latex \newenvironment{sphinxclasssd-tab-item}[3]{\sphinxlineitem{#3}}{} ``` following more closely your initial advice with `\sphinxlineitem`. I think `\sphinxlineitem` main purpose is to handle situations with a label but...
Testing `make -C _build/latex all-pdf` after `make latex` with a build of Sphinx own docs configured to use `xelatex` on a TL2019 is a bit disappointing. *note that these builds...
I added the `do not merge` tag. Waiting for feedback that merging this would actually make a significative difference in big projects if they have time to try it out....
To test if your project using `latex_engine='xelatex'` would benefit from this PR, it is not even needed to pull this branch. 1. execute `make latex` 2. cd to the latex...
In this context I am mentioning here the following fact, which does not seem to be worth a "bug report", it is more perhaps that it could be documented somewhere...
Thanks @gmilde for comment. I will probably not push to deviate from `\linewidth` and this may get closed without (effective) change. Leaving open in case further opinions are expressed. I...
@gmilde I strongly believe this is definitely a "bug" in the sense that the when the code was first written it is 99% certain their author did not think about...
> > I strongly believe this is definitely a "bug" in the sense that the when the code was first written it is 99% certain their author did not think...