Quote:
Originally Posted by slowsmile
OMG...Why are people still talking about my plugin and dual formatting?
In my last post I specifically said and advised in the first paragraph in my last post:
So why is everybody still talking about dual formatting and sizing?
Hitch said:
No Hitch -- I'm saying directly the opposite of your comment above. Have you run the test epub that I sent you in my last email? If you had done that then you would have seen it. The epub only contains one image line(its NOT dual formatted for KF7 and KF8) which has been formatted using % height/width values. If you look at that epub in KF7 emulations then you will see the image -- and that shouldn't happen(because % values should not display on KF7 devies). Got it?
Hitch said:
Perhaps it was a misunderstanding like you say. But my take on this is that if you format % values in the standard way(using height width as attributes in an image tag) then it will not display or it will display the wrong size -- I haven't tested this so I could be wrong. But if you're using inline styling in an image tag for % height/width then that's certainly not the same as using the standard method of declaring the height/width values in an image tag. Assuming that these two methods will give the same result is also quite a dangerous assumption. And my observations when I use the inline styling method for height/width with % dimensions are that it does display correctly as a percentage of the screen width when you use inline styling for the height/width dimensions. In the test epub I sent you(which uses inline styling with percentage dimensions) I have observed that the image displays at 50% of screen size -- which is correct(Don't forget that the image of the hawk will have a larger but unseen white canvass boundary around it as well).
Hitch...All I'm really doing is passing on some observations about KF7 formatting oddities to you because I know that you like hearing about Kindle problems/oddities. I've done this deliberately because you were generous enough to fully test my new plugin for me. But I never thought that this discussion would turn into such a long discussion and create so much confusion. I hope that what I've been saying is clearer now.
To be honest with you, I really don't care that much about this oddity that I'm reporting. I'm just happy that the plugin works OK...  |
William:
I don't think you read my post. My observations have NOTHING to do with your plugin. The image from your test2.ePUB, that you think is showing correctly, isn't.
Period. It's not remotely 50% of the screen. I discussed, in pixel-detail, the white space on the left side of the image, too.
I used YOUR coding, inline. I tested YOUR ePUB. It's not displaying correctly in KF7. That's it, William. It has nothing to do with the plugin.
ETA:
Please go back, William, and read my post 72:
https://www.mobileread.com/forums/sh...8&postcount=72 . The first paragraph of my response talks about the plugin--but the rest is ALL about nothing but KF7 and how the images display.
View the KF7 image, of which I've taken a screenshot, in that post. Not even you can assert that that image is remotely 400+ pixels wide, which is what it would have to be, if it were obeying the instruction, the inline instruction, that you're saying works. It doesn't. It's not an anomaly. You're seeing something incorrectly.
Hitch