Today as I was answering a question I noticed that $\oiint$ doesn't work in Physics SE. Is it some kind of a bug or am I missing something obvious?

  • 2
    $\begingroup$ Possible related post on meta.math: meta.math.stackexchange.com/q/9973 $\endgroup$ – dmckee --- ex-moderator kitten May 10 '15 at 21:10
  • 3
    $\begingroup$ It seems people have managed in various creative ways! $\endgroup$ – Qmechanic May 10 '15 at 21:25
  • $\begingroup$ @Qmechanic That is utterly unbelievable! $\endgroup$ – Gonenc May 10 '15 at 21:30
  • $\begingroup$ @Qmechanic - IMO, the OP of that question deserves being upvoted for the sheer effort he/she put in there! (I have, FWIW). $\endgroup$ – 299792458 May 11 '15 at 9:07

I've noticed this as well. As stated in the answer to the Math Meta post dmckee linked, MathJax simply does not support this symbol. You could consider it a bug in MathJax if you want - or more accurately, a feature request - but it's not something for Stack Exchange to handle. So the place to report this would be on the MathJax website.

Unless and until this is implemented in MathJax, I would recommend just using \oint, which gets the point across. It's quite common anyway for physicists to use a single integral symbol regardless of how many dimensions the integration region has.


This was reported as issue #566 of the MathJax github page back in 2013, but I just re-raised it to see what they'd say. The devs indicated that they are working on the fonts for MathJax v3.0, which should arrive next year, and this might solve the problem.

In the meantime, they suggested that we add a custom macro to the MathJax configuration for this site, i.e. something of the following form:

You could use the equivalent of


to allow \oint, \oiint, and \oiiint to work with their respective unicode characters, with sizing reasonably for displaystyle, and being the proper TeX class to allow limits to be placed appropriately (though the lower limit will be a bit too far to the right, because with won't get the proper italic correction).

This seems excessive to me - there's no need to be hauling around that much specific TeX in the html header for every page on the site over such a seldom-used symbol. If people want to have that solution, they can just use the unicode directly:


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .