Quote:
Originally Posted by Hatgirl
It's a legitimate workaround. But we shouldn't have to be finding workarounds, we should just be able to write code that complies with the W3C specs and have it bloody work  |
Since mobi does not understand CSS
at all, whatever you do with CSS must be converted into mobi-speak, and if it doesn't it's entirely the converter's fault, and a different converter might work differently.
If you don't like Calibre output (which I understand), maybe you can find something else that just processes the CSS and "flattens" it. It's quite likely there are other legitimate CSS construct (selectors, precedence...) that confuse KindleGen, and flattening the CSS would be a desirable pre-convert step.