View Single Post
Old 02-16-2013, 04:28 PM   #5
CWatkinsNash
IOC Chief Archivist
CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.CWatkinsNash ought to be getting tired of karma fortunes by now.
 
CWatkinsNash's Avatar
 
Posts: 3,453
Karma: 31292382
Join Date: Dec 2010
Location: Nashville, TN, USA
Device: Nook STR Glowlight, Sony T1, Acer Iconia A200
I agree with mr ploppy that they really aren't mutually exclusive. But for a clearer response than the poll can indicate:

- Yes, I know how to create ebooks. (In code view.)
- No, I do not look at the code unless the presentation on my reader indicates that there is something wrong with the code.
- I fix the code if I can clearly see that it's broken or just wrong before even looking at it.

So my knowledge of the "guts" of an ebook does not cause me to care about the code unless, as I said, I can clearly see it does not display properly. It has to cause a readability issue before I'll even bother glancing at the code. And if I only need to shrink the margins, I'll just do a calibre quickie. I don't care if it makes the code "worse" - I just care that I can read the book.
CWatkinsNash is online now   Reply With Quote