View Single Post
Old 08-06-2017, 07:00 PM   #6
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...

Quote:
??? I'm confused. I guess I haven't actually stared at the DX emulation in 2.94 (or whatever the current number is), but are you saying that the % CSS that you've written, for KF8, is "working" correctly in the DX emulation? Because I can absolutely, positively say that in real life, on real devices, man, that dog don't hunt, as they say in the South. Crap, now I'll have to go look at that...
To clarify -- the way I tested the above was that I first ran a test epub through my new plugin that only had one smaller image below the title. Then I just manually changed the normal KF8 version width size(inside the epub) from 25% to 50% to make any differences stand out. This means that the KF8 display will be double the size of the KF7 display and very noticeable. Then I tested the epub on the old Kindle Previewer and on the newer KP 3 and when I switched to KF7 emulation -- hey presto -- the KF8 version(which is using % values) was displayed on both these Kindle test apps...

@st_albert...I also really don't hold anyone responsible for perhaps not knowing that KF8 % images may now be displayed on KF7s. This is a bad way to go. To my way of thinking, Hitch and the folks on this forum are all pretty knowledgeable about Kindle requirements, formatting etc. And if anyone is responsible I would say that it's probably the Kindle team for not telling anybody about this possible change(think about the non-existent Kindle LITB info for instance).

For some more clarity, here are the media queries and code that my plugin inserts at the end of the main html stylesheet and in the html respectively on a normal plugin test run:

Spoiler:

In the CSS:

@media amzn-mobi {
.kf8only {
display: none;
}
.mobionly {
display: inline;
}
}
@media not amzn-mobi {
.kf8only {
display: inline;
}
.mobionly {
display: none;
}
}

In the html:

<p class="scrivener8"><img alt=" " class="mobionly" height="100" src="../Images/Image1.jpeg" width="105"/></p>

<p class="scrivener8"><img alt=" " class="kf8only" src="../Images/Image1.jpeg" style="width: 25%;height: auto;"/></p>


Everyone also seems to be assuming that the old KP and new KP 3 apps are telling the truth ie that they were both correctly emulating the KF7. Perhaps that's also a bad assumption. Perhaps its the fault of both KP's apps which may not be emulating the KF7 imaging accurately or correctly. That's why, IMHO, we will only really know the truth by testing the epub, after a plugin run, on an actual KF7 device.

Last edited by slowsmile; 08-06-2017 at 07:57 PM.
slowsmile is offline   Reply With Quote