View Single Post
Old 11-09-2007, 06:40 PM   #3
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 jbenny View Post
If you don't care about getting things just so, then either format would work. If you want to format things a particular way and also take advantage of a few 1150 specific features (headers and footers for example), then use HTML. The HTML would not require any conversion, unless you used tags not supported by the 1150. The Word document will always get converted.
If it there are bad code there will be error messages in the eBook publisher application to tell you about them. There is full control over html while word get translated to html anyway. Word (doc or rtf) may be a good choice if you need to convert items with curly quotes and other similar items in them without having to code them directly. Header, footers, and TOC fall into that kind of classification. The results will be an html files with a different extension but you can then direct edit the html to fix anything you like.

The main trick to toc, by the way, it to make sure there is a <a name="toc" /> just ahead of the data to make it work.

Dale
DaleDe is offline   Reply With Quote