Quote:
Originally Posted by slowsmile
Hitch...My thanks for confirming that the plugin works on your K2 device.
<SNIP>
Well Hitch the reason might be because I think that we both might have missed something. We have both perhaps assumed that the other was formatting their percentage image line in the same format. But the truth of what I suspect is that you may have been formatting all your test epubs for KP and KP3 in standard image percentage formatting(just using the height/width attributes in an image tag) whereas I have been formatting all my height/width percentage values in the image tag as an inline style viz. in other words -- concerning the the strange and conflicting KP and KP3 problems -- we might have unknowingly been formatting the percentage values in different ways which might well have caused different results or outcomes for each of us on KP and KP3 eInk emulations.
If what I'm saying is true you wont even need to use my plugin to prove this. And I think we are both agreed that if you format an ebook image in standard formatting with percentage values then it will not display on a KF7 device.
I've even prepared a simple epub test file for you as an attachment below to make it easier for you to see this for yourself. This epub contains my image styling (using inline styling with % values in the image tag) just for one image. All you or anyone else has to do is run this epub on KP and KP3 eInk emulations and you will see the image above the title displayed as plain as day(which is what I am seeing). This proves to me that if you format your image using this inline style method then that image will be displayed on all KF7 emulations. Please also note that this styling also works for all KF8 emulations as well.
And if you or anyone else confirms my findings then that also would seem to further indicate that media queries and dual formatting are completely unnecessary for KF7 and KF8 images. All you really have to do is format a single image line using % values for height and width inside an inline style within an image tag and the image will appropriately display on all KP and KP3 eInk emulations and will also display correctly on all KF8 emulations as well.
|
William:
FWIW, I didn't touch your previous "Paco" (ePUB1, let's call it) ePUB. I took the ePUB1 you sent me, dropped it on KP, and that's what I looked at. Now, maybe I've skimmed your post too quickly, but I didn't "format" bupkus. Literally. I took
whatever you had done, in the "Paco" ePUB you sent me, and dropped/viewed it. So, the coding was yours. Maybe I've misunderstood what you mean, in your post, so, moving along:
Now, about inline %: we've tried this coding, using inline %, over the years. And discarded it. I'm not sure I understand why you think it works.
You have it coded as width:50%, which means, unless I left my CSS brain at the station this morning,
50% of the width of the containing block. Do we agree on that?
The coding, for everybody else who didn't have time to view the ePUB:
Code:
<p class="scrivener5"><img alt="" src="../Images/eagle.jpg" style="width: 50%;height: auto;"/></p>
in which the p class "scrivener 5" is defined as:
.scrivener5 {
margin-left: 0em;
text-align: center;
margin-bottom: 0em;
margin-top: 0.5em;
margin-right: 0em;
text-indent: 0em;
}
Because if we agree that the CSS means 50% of the containing block, then I don't understand
why you think that this coding is working. Please see attached images, for screenshots from the emulator (which I think I demonstrated, last night, is working--do we all agree on that?). I've attached:
- Screenshot from the KP2.94, FireHD;
- Screenshot from the KP2.94 Fire HDX;
- Screenshot from the KP2.94 Fire HDX 8.9";
- Screenshot from the KP 2.94 Voyage; and,
- Screenshot from the KP2.94 DX emulation.
Your coding says, 50% of the width of the screen, which is the containing block
because the Scrivener 5 class doesn't constrain the size; you use it to center the image, only (and provide top margin spacing). Right?
Well, Wiliam, that Eagle damn sure ain't half the screen, in the DX. The DX is 824pixels wide, so this SHOULD be ~400px in width--and it's obviously not, given the original image is 90px wide. Is this what
you're seeing, at your end? My best estimation is that the eagle is displaying slightly over its original size. Perhaps, 125-150% of its actual size.
The KF8s all seem to be about right. Do we all agree on that?
What am I missing? I mean that; we all know that I
don't code daily, so I forget stuff. Freely admit it. What's working, in the DX screenshot? I mean, as it happens, the size of the Eagle image, on that screen, for that moment, works, even though it's not obeying the coding, but that's...
coincidence. If it were, say, twice the size, it wouldn't.
So: what do you think is happening here? To me, this isn't working. To me, it's displaying the image at just a bit over full-size. About 125-150pixels. Not half the size of the image, nor half the size of the screen. Hell, I don't know where it derived the size, unless we assume that like all images on KF7, the DX simply blew it up some percentage, attempting to make it fill the screen, as is KF7's wont.
Anyone else have thoughts on this? I mean...if I'm not understanding what I'm seeing, I'm happy to hear them.
Hitch