View Single Post
Old 03-06-2009, 12:15 PM   #18
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
Quote:
Originally Posted by Steve Jordan View Post
Yes, ePub is essentially XML... however, many of the component files, such as the individual chapters, the title page, dedication page, etc, are just HTML pages within the ePub package. They can be opened and read on any browser or web page editor. I build the whole thing manually with Dreamweaver at the moment, but I hope that won't always be the case.
The pages in the book is really XHTML, not just XML. XML would need a special definition to understand how to parse it and possibly a special tool. Just saying XML doesn't say anything about how to parse the file. XHTML is a particular implementation of XML that has been defined. The metadata is mostly XML based and you need to be very careful if you touch any of that.

ePUB needs pages that are XHTML, just sloppy old HTML with all its shortcuts won't cut it.

Dale
DaleDe is offline   Reply With Quote