Quote:
Originally Posted by SBT
My problem with all toolchains I've used so far is that I end up changing pretty basic functionality all the time to deal with strangely structured ebooks and/or strange source material. I want to make an architecture that's sufficiently flexible to lessen the chance of that happening, and that'll ensure I can reuse as much code as possible.
|
I know that you're a hard-core terminal user, but you may want to give
Sigil and the bundled
Python plugin framework (doc link) another try.
Why reinvent the wheel when pretty much all the routines that you need for manipulating/creating .ncx, .opf and .xhtml files are already there?
Theoretically, they'd allow you to assemble a fully working epub2 or epub3 book without using a single Sigil menu option other than the Plugin Runner.
I.e., you could use Sigil to launch your scripts and preview the generated ePubs.
And if you find the provided well-documented Python routines too limited, you could easily extend them with Python scripts or shell scripts.