Nicolas Goaziou writes: > Hello, > > Christian Moe <m...@christianmoe.com> writes: > >> Here's a simple CSS workaround that might or might not work well for >> you, and won't work for non-HTML backends, but at least requires minimal >> hacking: > > [...] > > Good to know. > > Anyhow, does my proposal make sense? > > > Regards,
Hi, Sorry, catching up on mail. Also, I misunderstood your proposal when you wrote it -- I thought it was a suggestion for what the user could do. But now I realize it's a proposed change to the HTML backend itself. You wrote: > `html' back-end can redefine what > a paragraph is, instead of following Org's own definition. More > explicitly, an HTML paragraph can be defined as a cluster of elements > not separated by any blank line and containing at least an Org > paragraph. Hence: > #+attr_html: :width 10% > [[./img1.png]] > Paragraph > #+attr_html: :width 10% > [[./img2.png]] > consists of two paragraphs in Org, but would be seen as a single > paragraph by HTML, and exported as such. > Implementation is simple using pseudo-elements. `latex' back-ends does > it already for tables and math snippets. However, I'm no HTML > specialist, so there may be drawbacks I cannot foresee. I'm no expert either. But FWIW, it does make sense to me, and seems intuitive from an HTML-centric view, since IMG elements in HTML are basically inline. I think users would expect to have to put blank lines around an image if they want it wrapped in a paragraph, and should expect to get in trouble if they did not put blank lines around a captioned figure. Yours, Christian
