Quote:
Originally Posted by phillipgessert
I do. I just run it through pandoc first. I think you’re kinda shadow boxing here, so I am going to clarify just one more time. I want to get rid of the code I don’t want. Sometimes I forget to first isolate the code I do. Context: author comes to me with an InDesign file from a designer that can’t be bothered to make the ebook. InDesign file is a mess, with lots of arbitrarily named paragraph and character styles, applied inconsistently and with lots of in-text overrides that mean nothing. Clean up the InDesign file within reason and export an ePub. Every paragraph has a class. Most mean nothing. Random spans everywhere. Most* mean nothing. I don’t like working with markup like that, and I’m sure you don’t either. Easiest way I know of to get a clean slate from that is to first run it through pandoc. InDesign > ePub > pandoc > epub > the actual work. We are actually in agreement.
*Save 3: bold, italic, and bolded italic; which I kick myself for having to redo by forgetting to isolate those first.
|
Solution to the problem...
Take the ePub direct from InDesign and using Calibre's Editor or Sigil, replace the spans for bold, italic, and bold italic and then run through Pandoc. That should do it.