Joined
·
135 Posts
This will be a long read. So I apologize if I did not write this in a more concise or efficient read.
I sometimes write books which have tons of pictures inside. I used to do the fixed layout (FL) approach for these books as it n can sometimes be easier to achieve. The downsides are that FL books do not normally get accepted in most channels who prefer or insist on reflowable (RF) .epubs (especially these days since .mobi is being phased out).
FL books look great on certain devices and appears closer to a actual print book or fixed .pdf. The fonts are however part of the image and one basically has one large rasterized page which may be off-putting to some readers, especially when it comes to un-scaleable fonts. The upside of FL is that one can have very nice looking layouts on a page (similar to print), with photos or graphs having their own captions and precise positioning on the page.
Some customers may prefer RF ebooks due to the fonts being scalable and images flowing as the device is turned landscape as well as some other benefits. Other customers will prefer FL books for various reasons. It is however hard to tell/predict which the overall client base would prefer.
A recipe book may arguably work better as FL. But now does that mean these books will be excluded from most channels who prefer reflowable .epubs?
The potential solution I have come up with was that I learnt to "code" my fixed layout books to work in reflowable channels. Basically the book consists out of imaged pages to work in a reflowable form. I have purchased one of my books at KOBO to test to see if it really got accepted as well as how it works. It opened as expected. Whether customers will complain about a fixed layout experience in a reflowable channel remains to be seen.
I have delisted the book and will be deciding whether I redo it as reflowable .epub or whether to keep the hybrid of reflowable and fixed layout. I am however still stuck between deciding which is the better option for me.
I have been spending months making a book reflowable that I would normally make fixed layout in less than a day. I have used Kindle Create (reflowable) with 90% satisfaction as to what I will find acceptable. If .kcb and .kpf was not Amazon exclusive, I would have preferred using this method to create fixed layout books. I am however thus forced to use their reflowable .epub option.
Here are two of the biggest problems I am having with reflowable .epubs:
1) When an image is higher in pixels (portrait). These portrait images sometimes jump to the next page due to the text that go before or after them. In landscape mode on a device, these images sometimes also appear too small due to its pixel height not being 100% suitable for landscape mode. I can live with this. What bugs me is that the text before or after these images, will sometimes leave a big white gap. I have sliced some portrait images to split into sections when possible. This works great for some images. But one cannot slice images that are supposed to be seen as one unit.
2) The other problem I am having is when text appear on pages when they perhaps shouldn't. In KC I design my books to have text above, and image below as much as I can. I am 95% happy with the layout in KC's previewer. The provide 3 options to preview the book in (mobile, ipad & kindle). As soon as I preview the book in Kindle Previewer 2 or 3, Calibre, Icecream reader etc. it always displays differently. Text would start on different parts of the page than expected. In the KC previewer, the text doesn't jump to a page when I do not want it to, except when I increase or decrease the previewer's font size setting. Is this normal and is the nature of reflowable .epubs? My guess is that one cannot please all devices. I would like to have my book appear good on the most common reading device outside of Amazon.
The ideal would have been to force text you want to always start on the top of a specific page.
Would be great to hear the take of people here having come across some of these same problems. Thanks guys
I sometimes write books which have tons of pictures inside. I used to do the fixed layout (FL) approach for these books as it n can sometimes be easier to achieve. The downsides are that FL books do not normally get accepted in most channels who prefer or insist on reflowable (RF) .epubs (especially these days since .mobi is being phased out).
FL books look great on certain devices and appears closer to a actual print book or fixed .pdf. The fonts are however part of the image and one basically has one large rasterized page which may be off-putting to some readers, especially when it comes to un-scaleable fonts. The upside of FL is that one can have very nice looking layouts on a page (similar to print), with photos or graphs having their own captions and precise positioning on the page.
Some customers may prefer RF ebooks due to the fonts being scalable and images flowing as the device is turned landscape as well as some other benefits. Other customers will prefer FL books for various reasons. It is however hard to tell/predict which the overall client base would prefer.
A recipe book may arguably work better as FL. But now does that mean these books will be excluded from most channels who prefer reflowable .epubs?
The potential solution I have come up with was that I learnt to "code" my fixed layout books to work in reflowable channels. Basically the book consists out of imaged pages to work in a reflowable form. I have purchased one of my books at KOBO to test to see if it really got accepted as well as how it works. It opened as expected. Whether customers will complain about a fixed layout experience in a reflowable channel remains to be seen.
I have delisted the book and will be deciding whether I redo it as reflowable .epub or whether to keep the hybrid of reflowable and fixed layout. I am however still stuck between deciding which is the better option for me.
I have been spending months making a book reflowable that I would normally make fixed layout in less than a day. I have used Kindle Create (reflowable) with 90% satisfaction as to what I will find acceptable. If .kcb and .kpf was not Amazon exclusive, I would have preferred using this method to create fixed layout books. I am however thus forced to use their reflowable .epub option.
Here are two of the biggest problems I am having with reflowable .epubs:
1) When an image is higher in pixels (portrait). These portrait images sometimes jump to the next page due to the text that go before or after them. In landscape mode on a device, these images sometimes also appear too small due to its pixel height not being 100% suitable for landscape mode. I can live with this. What bugs me is that the text before or after these images, will sometimes leave a big white gap. I have sliced some portrait images to split into sections when possible. This works great for some images. But one cannot slice images that are supposed to be seen as one unit.
2) The other problem I am having is when text appear on pages when they perhaps shouldn't. In KC I design my books to have text above, and image below as much as I can. I am 95% happy with the layout in KC's previewer. The provide 3 options to preview the book in (mobile, ipad & kindle). As soon as I preview the book in Kindle Previewer 2 or 3, Calibre, Icecream reader etc. it always displays differently. Text would start on different parts of the page than expected. In the KC previewer, the text doesn't jump to a page when I do not want it to, except when I increase or decrease the previewer's font size setting. Is this normal and is the nature of reflowable .epubs? My guess is that one cannot please all devices. I would like to have my book appear good on the most common reading device outside of Amazon.
The ideal would have been to force text you want to always start on the top of a specific page.
Would be great to hear the take of people here having come across some of these same problems. Thanks guys