Quote:
Originally Posted by salamanderjuice
You can customize KCC to various screen sizes, really what that does is it just resizes the images to be a better resolution fit for the device so it doesn't have to resize them on the fly. This is only really a problem for really high res images on old devices IME. I think ePub manga/graphic novel is not quite the same as FXL story book stuff and doesn't care as much for a given resolution. The code is very simple and it's literally just showing 1 full screen image a page. Here's an example of a typical "page":
(snippage for length)
Simple! This is from a Kindle unpack'd ePub. Kobo epubs are basically the same.
The viewport doesn't have to be specific to the device resolution at all and I've read the same book on devices with varying resolutions.
|
Okay, so...you create a book that is just a concatenation of images, yes? One image per page/screen? I guess that'll work. It's not searchable, of course, but then again, presumably, it wouldn't be. it doesn't have a text layer, so that solves all the pixel x-y stuff that FXL (from ePUB) brings to the table.
So...I guess my question would be,
which one (which set of pixel dimensions for the final, for which device?) are you using to sell at KDP? And have you uploaded and tested this yet, to see what you get in MOBI or KFX or whatever format KDP will workflow this into?
Hitch