earlier replies
Replying to @isaac32767
by "hand", I mean with some PHP scripts. e.g. the TOC is generated by parsing my source files, etc.
1
Curious to know what format your source files are in.
1
HTML, a file for each chapter and section, with Microformats to indicate chapter names for building the ToC...
1
PHP for conditional rendering of content for the epub vs print editions, e.g. "on page X" vs hyperlink, and to get images to flow properly
1
Instead of jumping through hoops to generate the XML, consider authoring in XML in the first place.
1
I'm not going to maintain individual XML files for the ncx/opf files. Those need to be generated automatically from my content.
1
I'm not talking about those files. I'm talking about the content files you generate them *from* 1/2
1
There are a lot of off-the-shelf workflows for converting XML to any user doc format you could name. So if you *start* in XML ... 2/2
1
I'm starting in HTML which is what Prince uses to generate the print PDF. That part works great.
1
In other words, you're using a legacy workflow. Moving on from it may not be practical, but you should at least consider it.
1
Replying to @isaac32767
What's legacy about that? It's an actively developed tool, and I was following their rec's: princexml.com

Nov 1, 2017 · 7:24 PM UTC

1
Replying to @aaronpk
I suppose "legacy" can be a subjective word. Most of us consider FORTRAN a legacy language, but a lot of scientists still use it.
1