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). 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 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. (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. It slays me that they refuse to believe that Amazon would knowingly not fix that. That's been a bug and glitch for years and years now. 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. 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. 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. 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. Oddly the PW3 makes some of them bigger rather than the same relative screen width or smaller. * 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. IRiver Cover Story (Screen cracked at rear due to battery swelling). But the alternative is a PC download and Adobe DRM and I've not got the Adobe program on Linux, only on an ancient XP gaming machine not used on the Internet. Our books look about the same as on a Kobo eInk or even the PW3 in Publisher mode* The Belinda Borrowbox App for our local Libraries is terrible. The Kindle, Kobo and Google Books Playstore Apps for Android seem OK on Android 8.x. Maybe three different LCD based Binatone eReaders, one was Android 2.x! I've only kept one as a curio. Maybe seven different Kindles (I own three different kinds) inc PW4 and ancient ones with KF7-mobi only. I think I've tested about 15 different models of dedicated ereaders and many apps on Android (4.3" to 10" screens, Android 4.x to 8.x) and two apps on the Palm PDA (which is as abysmal as you'd imagine with 160x160 pixels and older than mobi ebook formats). The Boyue Likebook Mars stock reader is OK for PDFs, but KOReader is needed for decent epub support. Some of the Binatone LCD ereaders and the iRiver Cover Story need the ebook (or Calibre created sub-directories in a specific directory, usually Digital Editions or related for fonts and CSS to work. Lithium and Aldiko Classic seem to work similarly to epub2 on any Kobo or Nook since at least the Touch and Simple Touch. Only prehistoric Kindles (Before KK3 and the DXG and earlier except KK3) don't do the fonts. Virtually every ereader ever, does all of those except embedded fonts. 2) ignores the justification settings in CSSĦ) Ignores left, right, top or bottom paragraph css margins
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |