View Single Post
Old 10-21-2020, 03:03 PM   #10
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 79,796
Karma: 146391129
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Quoth View Post
Indesign was meant for paper (and by implication PDFs which really are only proofs of paper). The epub support is a fudge and produces ghastly stuff.

Far better to use a Wordprocessor. Use Styles. Totally trivial to set top margin, left, right, first line and bottom.

Then Sigil or Calibre to convert a docx to epub.

Then the above example is totally automatic converting docx to epub if the margins are set in pt. The convention is 12pt = 1em. Almost all rendering engines use that if the CSS is in points.
In some cases, it's easier to output a text version of the book and edit that. If the formatting is not too complex, it will be easy enough to edit that to be well formatted ePub.

What I don't get is why publishers try to duplicate the look of the pBook but still manage to botch the eBook formatting. For example, paragraph spaces. They don't exist in the pBook and left justify does not exist in the pBook.
JSWolf is offline   Reply With Quote