View Single Post
Old 11-27-2015, 11:55 AM   #108
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,557
Karma: 93980341
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
There's generally a huge difference in terms of complexity between hand-written CSS and machine-generated CSS, such as would be output from a program like Word or Adobe InDesign: in the latter case you'd get dozens of styles and attributes output which would ensure that your finished book looked as close as possible to the way you'd designed it.

But if (as I am) you're happy to use device defaults for font selections, text size, etc, CSS can be simple and clean. There really are immense benefits to separating the formatting from the semantic content of the book, because it puts all the formatting specification together in one place, rather than having to go through the entire book and change things in multiple places.
HarryT is offline   Reply With Quote