Comment 6 for bug 758667

True, I'm not arguing that in general, except for the fact that we're moving from a format where that's true to a format that doesn't support css. And the way the code is written in essence Calibre is trying to guess from various css settings what is meant to be <sub> or <sup> in mobiml. However in case Calibre guesses wrong I should think that the tag name itself is a valid fallback, since these tags exist in modern html have special meanings which mirror mobiml. Right now if Calibre guesses wrong the information is lost, which is what's happening in this example doc.

Note for the fix I'm trying to include the parameters for the this style of subscript, but I was also thinking to use the tag names as a fallback. I've already implemented the fallback based on tag names, still working on the paramaters for this type of style, as my first cut was a bit naive.