Quote:
Originally Posted by JSWolf
Why not just make it real text? One thing I dislike is graphics taking the place of text when there's no good reason for it.
|
JSWolf, for pete's sake just imagine it's an image that is not text based and doesn't have a wingding equivalent and, and, and.... I created it as a simple illustrative example.
But even if it were the exact case, this is the kind of advice that is really crazy-making:
-- Question: How do i solve problem X?
-- Answer: By deciding you no longer want to solve problem X.
The issue I described in my original post was not "I want to make a image of text behave a
certain way" it was "I want to make an image behave a certain way", so telling me not to use text images is a non-sequitur.
@Jellby - I think I'm seeing the difference between our two codes, and I don't really understand what the implications are:
Basically, in your test version the height is defined at the <div> level, not the <img> level, resulting in the correct scaling that you observed. I'm confused, though, why definiing the height at the <img> level would result in squishing, and I'm wondering if there are any other unintended consequences depending on which level the height/width values are assigned. Do you know?
EDIT: Welp, I've found unintended consequences...
Whatever protocol PageEdit is using to parse height/width values defined at the <div> results in the image going off the screen (see test3, attached).
And in the EpubJSReader Sigil plugin it cuts off part of the right-hand side of the image (see test4).