View Single Post
Old 11-08-2007, 03:37 PM   #104
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,449
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
To summarize your response, zml cannot support setting presentational aspects. And you dont intend it too, ever. And since you aren't open sourcing it, there's no chance it will pick up features like that in the future.

HTML+CSS can support both structural and presentational aspects. They give the author more control and more freedom. As such, IMO they are a much better match for a *general* ebook format.

Look at it this way:

zml is forcing restrictions on authors. Indeed your whole attitude is that authors dont know whats good for them and you're going to tell them that.

HTML+CSS encourages authors to represent things semantically, but if they really want to add presentational aspects, it allows them to do so.

To me the second approach is simply superior. If you want to encourage authors/digitizers to use only structural markup, a better approach would have been to write an authoring tool that supports only structural elements, via the GUI and allows authors to "edit the source" for advanced features. Something like LyX does for LaTeX.
kovidgoyal is offline