View Single Post
Old 05-04-2015, 05:14 AM   #20
skreutzer
Software Developer
skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.skreutzer considers 'yay' to be a thoroughly cromulent word.
 
skreutzer's Avatar
 
Posts: 190
Karma: 89000
Join Date: Jan 2014
Location: Germany
Device: PocketBook Touch Lux 3
Quote:
Originally Posted by Hitch View Post
As far as machine-readability, @skreutzer, were that true, we'd be using XML and XSLT. We're not. That should tell us all something, I'd think. However, if that were the goal, I'd argue for XML, simply because it's already well-established and in large document-archival systems, already in place (like medical records, etc.).
Well, if you construct EPUBs, the XHTML is XML, the NCX is XML, the OPF is XML. I don't know how you would generate an XHTML-TOC automatically, but XSLT would be a more flexible way to do that for programmers than to implement it in static code. But we don't need to furtherly discuss this, because, XML formats being plain-text files too, are for most people not easy to read and write and also inflict even more overhead of typing it, that's exactly why someone would consider to use Markdown and generate an EPUB full of XML files from it.

Last edited by skreutzer; 05-04-2015 at 05:18 AM.
skreutzer is offline   Reply With Quote