Quote:
Originally Posted by Quoth
I'd regard any App that < item below> as bad:
1) can't do embedded fonts
2) ignores the justification settings in CSS
3) ignores Page Break before
4) Has no NCX
5) Links not supported
6) Ignores left, right, top or bottom paragraph css margins
7) Ignores first line indent.
(snippage for space)
* Curiously the KK3 (only 167 dpi) in KF8-Publisher mode seems to render a bit more accurately like a 300 dpi Kobo than the PW3, especially with images. Oddly the PW3 makes some of them bigger rather than the same relative screen width or smaller. The KK3 even in KF7-mobi mode is better than the DXG because the KK3 has more built in fonts in FW and the stock DXG serif font is not very pretty IMO.
|
O.M.G, do not get me started on my PPW and PPW family eInk rant, about images that are meant to be larger than 50% of the width of the screen (49%, actually) and 100% of the width of the screen. I reported this problem to KDP in...2014? 2015? Foolishly, at first, I thought it was a Kindle Previewer 2.9xx problem but then I suddenly had this hunch and sure as scat, the issue exists on the real devices, too.
In all of those, if you have any image meant to be 55% of the width of the screen,
KABLAMMO!, it will be 100% of the width of the screen. That's been a bug and glitch for years and years now.
Try explaining
that to irate customers. (sigh). It slays me that they refuse to believe that Amazon would knowingly not fix that. "Not Amazon," they say, "it must be you. YOU must not know what you're doing."
(I have a guy right now that refuses to believe that Amazon's rendering engine won't "fix" all the issues I'm showing him, around Cambria Math. He's adamantly convinced that b/c KP3 shows it working, that despite the screenshots I've shown him, coming from my eInks, that it WILL work via ET, once it's been through the PW. He refuses to believe that the PW (publishing workflow) won't magically fix the bizarro-world view of the Cambria Math unicode characters WILL display in the eInks, which are KF8, mind you, not KFX/ET. He's certain that b/c I sideloaded the MOBIs that we produced, as tests, that that's what is causing the issue, and that Amazon's magic rendering engine/publishing workflow will MAKE the CM unicode work on all not-KF7 devices (not including KCR and/or the LookInside). [sigh and more sigh].
Hitch