View Single Post
Old 08-15-2017, 07:48 PM   #75
slowsmile
Witchman
slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.slowsmile ought to be getting tired of karma fortunes by now.
 
Posts: 628
Karma: 788808
Join Date: May 2013
Location: Philippines
Device: Android S5
Hitch and st_albert...I'll try and clarify things.

First thing to understand is that the KP and KP3 weirdness that I'm reporting has nothing whatsoever to do with the new plugin. The problem also has nothing to do with image sizing etc.

Everyone has been saying that KF7 devices cannot display images whose height and width dimensions are in percentage values. After all, if you ask yourself the question, "Why do we need to use dual formatting and media queries for Kindle uploads..." the answer to that question is because KF7 devices cannot display image height/width using percentages values(whereas KF8 devices can). Right?

Now run this very simple test. Open the test epub that I sent Hitch(see my last post for the downloaad) on KP and KP3. Then just answer this simple question: Do you see an image on the KP and KP3 eInk displays ? If you do see an image in the eInk displays then that's the oddity or problem. Read on to find out why this is an oddity.

The test epub just contains one image coded thus:

<p class="scrivener5"><img alt="" src="../Images/eagle.jpg" style="width: 50%;height: auto;"/></p>

Please also note in the above code that I'm using inline styling with percentage values in the test epub. It also appears that everyone is seeing this image too on their KP and KP3 eInk displays too. Right?

Here's the oddity explained: Everyone has been saying that image dimensions defined in percentages within an image tag cannot be displayed on older KF7 devices. But when Hitch and I look at the KF7 displays for the test epub we both see the image(formatted with % dimensions) plain as day on our eInk emulations. Well, according to what everyone's been saying -- you should see no image if your image is using percentage values like this on KF7 devices. But the test epub IS displaying an image formatted as an inline style using percentage image values on KP and KP3 eInk displays and that's not supposed to happen. Right?

So all you have to do to confirm my findings is just open my test epub in KP and KP3 and then just report back here if you see a centered image or not in their eInk displays. And please don't complicate things by dragging in image sizing, positions etc in your observations -- the latter is completely irrelevant to this test. This test is only meant to prove or disprove whether using inline styling(with % dimensions) for ebook images will display and show ebook images on KF7 devices.

And here's the most important thing. If you confirm what I have said above to be right(just confirm if the centered image is there or not in the eInk displays-- that's all I care about!!), then there seems to be absolutely no need to use media queries with dual formatting to ensure proper image display on both KF7s and KF8s. All you have to do is just use a single image line that has been styled using inline styling with % values in your image tag and you image(s) will be appropriately displayed on both KF7 and KF8 devices without a problem.

And don't worry Hitch, I'm not going to change my plugin code because of the above discovery. But as far as I'm concerned, just bear in mind that there is not just one way to format your epub for KF7 and KF8 eInk displays for images. There is also a much easier second way of doing this as I have a already described in the paragraph above.

Hitch...It might also be interesting to know if the image in the test epub also displays properly on your K2 device or not after conversion to Kindle mobi.

Does everyone fully understand the problem or oddity that I'm reporting now? I really hope so...

Last edited by slowsmile; 08-16-2017 at 09:02 AM.
slowsmile is offline   Reply With Quote