Quote:
Originally Posted by st_albert
I concur with your observations. My take is that the KF7 version of the mobi file simply ignores the width specification (probably doesn't even include them in the kf7's html.). I haven't had time yet to dissect the mobi file to check on its coding, though.
See my post #71 above. I duplicated the image code on the title page , then changed the width of the second image to 20%. On KF7 emulators, both images were the same size, and seemingly < 50% of screen width. On KF8, they were different sizes, but I'm still not sure that the larger was all of 50%. Maybe I need to put a border on the actual image to see what its bounds are.
Albert
|
OK, good. I was starting to wonder if I was losing my mind, or if I'd missed something, to be honest. (The other day, when using Tex's ePUB, I actually got a bit corn-fused for a moment, thinking that images should have been 50% of the screenwidth--when the coding was, 50% of the size of the original image. That had me going for a few minutes. So, I never rule out the possibility/likelihood that I'm brain-farting!)
I looked at your test ePUB/MOBI. I think that the eagle
image is deceptive--it's wider than you think, due to the slanting nature of the wings and extended talons, and the fact that it has some pixels of whitespace to the left of the extended talons. I'll bet you that the eagle is, absolutely, dead spot on 50%. If you look at the portion of the image to the LEFT of the talons--which is a good bit of length, you can see it's deceptive.
(n.b.: I measured the image. The whitespace to the left of the talons is 16pixels. The image itself is only 90px wide. That means that 17.8% of the image's width is the whitespace to the LEFT of the talons.)
So, I'm betting that's 50%, Albert. :-)
ETA: You're a step ahead of me, Albert--I was just going to unpack that mobi and do what you did. We're in agreement on how the coding is being treated. Nice job!
Hitch