Take the 2-minute tour ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.

(I had a feeling this was a duplicate, but couldn't find an older question about it. Forgive me if I'm just bad at searching.)

Consider the minimal example

\documentclass{article}
\usepackage{mathtools}
\usepackage{unicode-math}
\setmathfont{lmmath-regular.otf}
\begin{document}
\begin{equation*}
  \int f(x) \, \mathrm{d}x
\end{equation*}
\end{document}

When compiled with lualatex the space between the integral sign and f(x) is too large, larger than what I get if I compile with xelatex (or if I'm not using unicode-math).

  • With lualatex:

enter image description here

  • With xelatex:

enter image description here

  • Without unicode-math:

enter image description here

I'm using a recently updated TeXlive 2011, and the same thing happens with Asana-Math.otf or xits-math.otf as math font. Can this be corrected somehow?

share|improve this question
    
Happens the same to me. –  egreg Nov 30 '11 at 21:10

1 Answer 1

up vote 7 down vote accepted

Looks something wrong with italic correction of integrals in the absence of super or subscripts, adding an empty superscript \int^{} f(x) fixes the spacing. Odd enough, adding empty subscript \int_{} f(x) makes it even closer! I'd report this to luatex bug tracker.

share|improve this answer
1  
After tracking down the bug tracker, it seems you've reported this already, about a year ago: tracker.luatex.org/view.php?id=488 –  Torbjørn T. Dec 1 '11 at 0:05
    
Or, that issue doesn't say anything about unicode-math, so it is somewhat different. Should I make a new issue, or just add a comment to that one? –  Torbjørn T. Dec 1 '11 at 7:53
    
I think it is the same issue, I totally forgot about it :) –  Khaled Hosny Dec 1 '11 at 9:59
    
In TL2012, this issue has disappeared in ConTeXt, but still exists in unicode-math. Maybe unicode-math needs to be updated? Or the newest ConTeXt contains this hack you mentioned to get around the engine bug? –  Siyuan Ren Jan 22 '13 at 14:27
    
@C.R.: most likely ConTeXt has a workaround for it. –  Khaled Hosny Jan 22 '13 at 14:30

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.