Quote:
Originally Posted by Jellby
But if you settle for "show the images at the largest possible size, with no aspect ratio distortion", as phillipgessert says, that's doable and reasonable (except for the bit about not being possible to easily target the screen height, that's a true nuisance).
|
Indeed. Set the width and never mention height, or at worst maybe auto?
Also use "Tablet" on Page settings when doing docx to epub2 conversion in Calibre, assuming the wordprocessor embedded images make sense. Then you can check the CSS afterwards.
Use Sigil if doing a more customised ebook creation. We just do simple stuff so mostly docx to epub2 just works. Sometimes it doesn't quite.
InDesign was really created for paper print publication via PDF, so it's not the best way to make clean epub2. And all Amazon eink, ereader apps and Fire work most predictably with an upload of a nice clean simple epub2 to KDP. That passes Check Book and Epub Check in Calibre, that the system TOC (NCX) works OK on an epub ereader or a proper epub app or Calibre Viewer and all internal links and external links go to expected places.
Not all physical ereaders actually support even internal links, but most do.
We also create a text contents page in the source document using Anchors/Bookmarks at the start of the destinations and simple internal links on the page. This is in addition to the conversion generated TOC / NCX that the reader or app uses from a menu.
Also any heading appearance not meant to be in the TOC/NCX is given a body text level rather than a level. The Wordprocessor paragraph styles should map 1:1 to class="something" in the HTML and then a definition in the CSS. So never put anything in a style property that won't make sense to an ebook CSS.