Quote:
Originally Posted by theducks
Were you trying to do this as a SINGLE , huge page?
Reading devices wuss out long before Sigil or Calibres viewer will
break your 'project' into task pages (limit each to less than a few dozen pics)
|
Good question but no. I had 14 different "chapter like" pages. Sigil was fine before I started making image links, which in the xhtml are just text links. But the GUI shows a wysiwyg version of each such page, with all those jpegs loaded into memory somehow.
Each such page (of 14 or so, so far, more to come) have something like 5000 words. Sigil was fine with just text. But a boat building book needs lots of images and diagrams. I make blueprint like pages with various open source CAD programs and then export them as jpeg. And then resize the jpegs, with a shell script, to be about 1000 pixels wide or less.
I found a web page somewhere that said epub images were ideally sized at .... something like 1000 pixels wide. Their argument had something to do with hard-coding width to the number of pixels in an IPhone Retina display. Hard coding to specific devices isn't generally a good idea but I had to start somewhere. So I started with that.
Images can always be resized. Down from the original RAWs.
Jutoh does seem to handle big image pages without trouble. Jutoh is a bit of a learning curve. A lot of it works differently than sigil. Today was my first day with Jutoh, after a week of fighting with sigil.
Boat building is complex. When you start off with history and then teach techniques, talk about design and model making and then and only then dive into "how to build this particular boat" it takes lots of words. And images. Web pages come up one at a time.
When a Pad or Phone app reads an epub it's not clear to me how much of the book is loaded into memory at any given time. I haven't tried to read my own book with an app yet.
So far just with editors.