Quote:
Originally Posted by jswinden
I suggest saving the documents as unformated HTML then letting Sigil apply the formatting. MS Word always turned simple HTML into a raging mess that was nearly impossible to read if you let it hardcode the formatting, but it did okay if you let it create generic, non-formatted HTML. I'm talking about the convoluted CSS garbage Word creates. I assume the same is true for most any document editor like Word, Pages, etc. And the same is likely true of creating ePubs directly with those editors. The CSS will be total garbage and difficult to edit. Start with a blank slate and use Sigil to add a bit of formatting where needed.
|
To be fair the code is quite ugly a lot of spans to clean up but it has made a pretty good start a lot of unnecessary white space too but fairly easy to chop into shape. It doesn't import the fonts which is a shame so there is a fair bit of work to be done but it's not entirely a mess. It's probably a bad idea to get too far into the book before transferring to Sigil but after a few pages most of your styles are in and you just need to refine them and then apply to the rest of the content. I'm actually re editing from a pdf file created by indesign. The epub from indesign just caused pretty much all the ereader software i have to choke.
I've been using affinity designer to edit the pdf file and transfer to pages. The pdf export from pages is actually pretty good. it's epub which is tricky.