Quote:
Originally Posted by KmC
It's not a simple DocBook-EPUB because the source XML is in a specific kind of XML (based on the NLM [National Library of Medicine] tag library), and thus we would need someone to develop the XSLT specifically for us.
|
Since it already is in XML, there is no need to introduce some bloated middleman program which could introduce its own errors (InDesign will make some assumptions with the code, and may potentially cause much more work. Plus as Toxaris said, InDesign does not export EPUB correctly in many cases).
I would say the best bet is working directly from the XML -> (Transformation) -> XHTML. From there, you could insert the XHTML into an EPUB using Sigil, and do any other needed tweaks from there (hopefully the Transformation can be created to minimize/eliminate the work to be done).
As long as these XML files all use the same classes, then you can create one master CSS file which can then be used in all books.
As long as all these documents are tagged in a very consistent way, this should be the best bet.
Quote:
Originally Posted by KmC
It seems that it would be cheaper, easier, faster, and wouldn't require anyone to take evening classes in xProc.
Am I missing something? (I VERY well could be)
|
Would it be possible to give samples of any XML files wanting to be converted?