Hi, I am using the *old* exporter (the packaged version in Debian Wheezy), I don't know if this behaviour keeps happening with the new one. I have come up with a minimal case that exhibits this problem — Might be my fault for using this feature wrongly, but it *feels* as a parser error.
The problem happens only when outputting HTML, using «OPTIONS: LaTeX:dvipng» in my document preamble, and in a list context. The full test document is: /------------------------------------------------------------ | #+TITLE: Testing inline math within lists for HTML exporter | #+OPTIONS: LaTeX:dvipng | #+INFOJS_OPT: tdepth:2 sdepth:2 ftoc:nil ltoc:nil | #+LINK_UP: index.html | #+LINK_HOME: index.html | #+STYLE: <link rel="stylesheet" type="text/css" href="css/sistop.css" /> | | * Foo | - Foo bar baz $(100-3 + 128) \times 4KB = 900KB$ bar foo foo baz bar | baz bar bar baz. Foo baz. | - Quux foo bar bar foo a $(100-3 + 128 + (128 \times 128) ) \times 4KB | = 66436KB$, bar foo quux bar foo baz baz. | - Foo bar. Bar baz foo foo baz bar $(100-3 + 128 + (128 \times 128) + | (128 \times 128 \times 128) ) \times 2KB = 8455044 \approx 8GB$, foo | foo bar baz. \------------------------------------------------------------ What happens here? I think the parser fails to see where the math mode ends. The LaTeX snippet is generated correctly (that is, the image in ltxpng/ is generated correctly, but the output to the "alt" attribute of the <img> tag is cut at the first newline. I'm pasting here just the generated <ul>: /------------------------------------------------------------ | <ul> | <li>Foo bar baz <img src="ltxpng/test_f3cfc88d233452ff173621df43ec8460f406305a.png" alt="$(100-3 + 128) \times 4KB = 900KB$"/> bar foo foo baz bar | baz bar bar baz. Foo baz. | </li> | <li>Quux foo bar bar foo a <img src="ltxpng/test_75d5a4164cf14c1532c7111fb0ae8a88e1c5a9c9.png" alt="$(100-3 + 128 + (128 \times 128) ) \times 4KB | </li> | <li>Foo bar. Bar baz foo foo baz bar <img src="ltxpng/test_2497b2e44469a088aef26cf377e3ed761fe649f0.png" alt="$(100-3 + 128 + (128 \times 128) + | foo bar baz. | </li> | </ul> \------------------------------------------------------------ Now, it gets more interesting: If this list is succeeded by a heading that appears on the TOC (that is, level one or level two), there is an interaction I cannot explain with infojs, and the whole document is displayed blank in the browser. So, is there a recommendation there I am missing? Is this bug still present in the new exporter? Are there maintenance releases still expected for the old exporter that could address/fix this? Note that the document renders correctly under LaTeX. Thanks a lot!