New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is the extra space at the start of LaTeX footnotes intentional ? (may stretch and give bad result) #2351
Comments
Thank you for reporting. I fixed at 6efdd07. (I used |
@tk0miya Thanks. I should have pointed out perhaps that arguably leaving the LaTeX default (no special spacing) was to be advised. Indeed some language modules for (LaTeX) babel customize this: I know in particular of French http://mirrors.ctan.org/macros/latex/contrib/babel-contrib/french/frenchb.pdf, which modifies footnotes to look like |
A possibility would be for the latex builder to insert As a general remark all macros defined in |
@jfbu Thank you for advice. I added the |
@tk0miya Works great, thank you ! |
At master, I'm getting code generated like: dimensions \footnote[8]{\sphinxAtStartFootnote%\begin{enumerate}
\setcounter{enumi}{19}
\item {}
...
\end{enumerate} That |
@jnothman Thank you for reporting. |
Thanks for the fast fix! |
Consider the following
index.rst
:and in conf.py::
I get from
make latexpdf
This may seem a contrived example, but it occurred to me in real life from auto-generated links via intersphinx, and the use of
12pt
font size, and a font with rather big glyphs. In the example above I inserted-
to give a chance for the URL to break. This was the case of the auto-generated link in my real life case.The problem is with the extra space token which comes from the
\footnote
's in the latex file: (tested on current master)Is it intentional not to have
\footnote[1]{%
? without it a space comes from the end of line. If one wants a space there, one should make it un-stretchable\footnote[1]{\mbox{ }%
.Here is without spaces (standard looks of american typography footnotes):
and here is with
\mbox{ }%
:The text was updated successfully, but these errors were encountered: