Quote:
Originally Posted by theducks
Most Readers (devices)?
The Kindle  , I-whatever 
I don't think ADE is the big Kahua any more 
|
Yeah, this is why it took me so long to realize anything was amiss; everything's been looking peachy keen on my Kindle! Between the small caps issue, this empty line rendering issue, and their product pricing schemes, I've come to the categorical conclusion that the folks at adobe are fascists, whose sole joy in in life is causing me aggravation.
More seriously, I'm still not clear on why the original code was failing. why wasn't the bottom margin on the heading3 style working? Also, while the new code fixes the problem of the overlaping text, it's really not a precise solution, since it's adding 1 more line height to the bottom margin. It's easy enough to reduce the heading3 margin in the css stylesheet to compensate, but in principle the new div isn't doing what i wanted (which is simply to function as a clearing element for the preceding floats).
EDIT: for the record, I really fundamentally disagree with the view that people should be coding in workarounds to to accommodate the rendering flaws of ADE. That's like saying that Webster's should add "peice" to the dictionary to accommodate all the people don't know the "i before e" rule. If epub is going to be html based, then it should accept standardized html code, not require users to unstandardized their coding. It's annoying that it took me so long to figure this out, but that's not Sigil's fault or Calibre's fault... it's ADE's fault. Just like being confused by the word "piece" when you've always spelled it "peice" isn't Webster's fault for not including an "alternate spelling", it's your fault for not knowing how to spell.