Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.
@noah, almost certainly, there's some extra step to load new fonts that isn't being performed when you preview. Perhaps try editing a question that already has \mathrm, and seeing if preview works in that case.
I can't reproduce Noah's bug, but it's consistent with weird jsMath behavior people have reported lately. Perhaps there's some sort of a race condition that prevents certain packages from loading sometimes. jsMath does seem to be sensitive to the order in which I load various things (things that I wouldn't expect to matter).
When doing mathematics with underscores or asterisks in it, you need to escape the formula with backquotes (outside the dollar signs).
Looks fine to me (firefox 3.6 on linux). The p under the Q is ever-so-slightly lower than that on the Z, but not unpleasingly so. I could send you a screenshot if you like.
This is what I see:
Comparing the two, I think that another difference is in the rendering of the Z and Q themselves.
@buzzard: There is no bluff. I misunderstood your point. When you wrote “it looks like the p fell off” I thought it was a cute way of saying the p was missing or something. Usually, when things go bump in the night the first thing you think of is the backquotes (or lack thereof), hence my post. If you had been more specific, I would of course have answered differently. Anyway, what I see is again quite different than what either you or Andrew sees, but not outrageously wrong:
On Opera on Linux, I see:
which is clearly gibberish!
I don't have iceweasel installed, it's a rebranding of firefox so I don't see why it should be so different, plus you see it on firefox as well.
Looking at your screenshot, the subscript 'p's don't look any smaller than the non-subscript ones. It's a little hard to see, though, so I may be wrong.
My screenshot was firefox on mac. Maybe the available fonts influence the result?
I think I found a hack. I replaced "\mathbf{Q}_p" by "\mathbf{Q}{}_p". That fixed the dropping p for me.
I just installed the TeX-Illustrator fonts (for the obvious purpose of using Computer Modern inside Illustrator), but now jsmath is messed up. Here's an example from http://mathoverflow.net/questions/23437/are-the-q-catalan-numbers-q-holonomic/23930#23930:
Any ideas? I hadn't wanted to installed the jsmath fonts locally for the sake of keeping my experience in sync with "new users" on mathoverflow. I'm using OS X 10.6.
jsMath wraps math in a span of class "typeset" and then has lots of internal spans with classes like "cmsy10" (or other font families). There's a css rule that says that such a thing should use the font family "jsMath-cmsy10". Perhaps the cmsy10 TeX-Illustrator font is somehow taking the place of jsMath-cmsy10, but isn't exactly the same. The ≺ character appears two steps before the - character in jsMath-cmsy10, so you would expect this kind of problem if you used an almost-but-not-quite-the-same font.
If you weren't using jsMath fonts before and don't want to use them, you can always click the jsMath box in the lower right hand corner of your browser, click "options", then click the "use image fonts" radio button. That will save a cookie which tells jsMath to always use image fonts.
Thanks Anton, I'd forgotten I could override the font mode.
The math preview doesn't seem to be working in Chrome. Is anyone else having this problem?
The math preview doesn't seem to be working in Chrome. Is anyone else having this problem?
Yes. I don't know what's going on. The live preview doesn't work in Chrome (on linux), but does work in Firefox. It works in both on another machine running Windows XP. The weird thing is that the one-shot preview works fine, so it's clear that jsMath is working properly. Hmmm ... maybe the modified wmd.js isn't getting loaded for some reason?
Edit: indeed, it looks like the custom version of wmd.js (which incorporates jsMath processing) isn't loading properly. I don't understand why. More Edit: it sometimes works and sometimes doesn't.
Some lines of math are also jutting out of the margins in Chrome for some reason. (A little, uh, math overflow, if you will.) I'm using Vista.
Some lines of math are also jutting out of the margins in Chrome for some reason. (A little, uh, math overflow, if you will.) I'm using Vista.
That's some weird interaction between jsMath and webkit browsers. I can't do anything about that. It doesn't seem to happen with MathJax.
Odd. It looks fine to me in firefox on the mac, but looking at the source, I notice that formulas containing underscores are not surrounded by backticks. Possibly that is part of the problem.
I've noticed that when I come to the main site by way of a search engine the jsmath is blocked somehow. This is all in Firefox.
Hi Yiftach, sorry you haven't received a response yet. Perhaps you could try a more modern browser, e.g. Firefox, Safari, Opera or Chrome? You might also try clearing the browser cache in Explorer in case it's has somehow mis-cached the javascript that renders the LaTeX.
@Evan: the problem is that _phrases between underscores_ get converted to italics, like this, before the math processor gets a chance to look at them. The accepted workaround is to tell markdown to leave the underscores alone by enclosing your math in backticks, like this:
`$\operatorname{Foo}_{bar}$`
Another alternative, assuming you don't have any markdown syntax in the paragraph, is to enclose the paragraph in P tags, like this:
<p>
I really like using $\operatorname{Foo}_{bar}$ as an operator.
</p>
Charles Rezk mentioned a \varprojlim problem on April 16 in this thread, but I'd like to point out that when I looked at this question, $\varinjlim$ rendered correctly in preview, but threw up an error when being displayed after submission. However, when I look at the edit history now, the old version seems to render fine.
I had replaced the \varinjlim commands in the old version with \underset{i}{\lim_{\longrightarrow}}, since I had seen the \underrightarrow problem before. Unfortunately, the bug (whatever it is) does not seem to manifest consistently. Now I get jbl's error message when I look at the edit history (with the same browser as before).