Quote:
Originally Posted by WillAdams
|
Or ...... conversations such as this illustrate why software like tei2epub never seems to gain very much traction.
A classic case of, "if Aunt Edna had had testicles, we'd be calling her Uncle Edward."
A universal xml schema must exist before any xml-based book creation/rendering system could possibly become universally relevant. And a universal xml schema will never exist because humans never agree on things. So xml-based book creation/rendering would always be doomed to individual factions pushing their own schema/agenda--very much like the situation we already have with the epub-ish format. Same/same with little-to-nothing gained (other than disruption and change-for-the-sake-of-change).
The whole thing is cart-before-the horse anyway. If you (@OP
you ) want to bring a change of this sort about, then create (or support) a Wordprocessor program (which can export beautiful, entirely comprehensive and utterly semantic xml--WITHOUT FAIL) that is sooo intuitive to use, and is feature-rich (yet gracefully simple) that authors wouldn't dare use anything else to create their masterpieces.
Because until authors are in love with the front-end of this magical piece of software that transforms their visionary work into the gobbledygook (which they care not a fig about, so long as it doesn't alter their vision of how their work should
appear) that ebook creators need, then this is all for naught. They
have their preferered tools, and aren't going to change just so all the behind-the-scenes gobbledygook makes more geeks happy.
Plain and simple: a smooth, efficient transition from manuscript to consistently rendered (yet intuitively marked-up ebook) entails nothing short of knocking Word/Adobe off their pedestals. I'm not opposed to it,
per se. I'm just not going to hold my breath.