Quote:
Originally Posted by Turtle91
160 MB is immense when it comes to an ebook. Even very large - picture intense - children's books that I've seen are around 20-25MB. I would guess that the size of your image files are the main culprit. You can/should reduce the image size to about 1600px in height and/or use a better image format to compact the size. That is really all the image size/quality you need with today's reading apps/devices. If you absolutely must have the full size images then you could host them on a network server and include links in the ebook.
As far as splitting the ePub into smaller files....yes...definitely! The smaller the file size the faster the device will load and display each new file. Most people will split the html file at a new chapter - 20 Chapters = 20 files plus files for cover, title, acknowledgments, copyright, etc.
You can use a simple search and replace to find new chapter headings...or if you have the html tags set to use the <h1>-<h6> for different headings you can split there.
If you are using Sigil - and I'm pretty sure Calibre has the same or similar functionality - you can use the following search and replace:
search: "<h1" or "<h3>Chapter" etc. (without the quotes)
replace: "<hr class="sigil_split_marker" /><h1" or "<hr class="sigil_split_marker" /><h3>Chapter" etc.
Then you can use the function "Split at Markers (F6)" in Sigil to automatically split at all those marked locations.
Conversely...you can use the "Split at Cursor (Ctrl-return)" to manually split up the document.
Hope that helps!
|
I don't think the total file size is the issue. I have graphic novels over 300MBs that my Kobo and it's various apps happily handle. Overly complex HTML/CSS is a more likely culprit especially at 5600+ pages and converted from a word document.
Unless the images are absolutely massive but with a 5600+ page document there could just be a few hundred 0.5MB images which would be pretty typical e-Reader sized images.