View Single Post
Old 11-19-2009, 10:05 AM   #12
Mike L
Wizard
Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.Mike L ought to be getting tired of karma fortunes by now.
 
Mike L's Avatar
 
Posts: 1,479
Karma: 3846231
Join Date: Apr 2009
Location: Edinburgh, Scotland
Device: Kindle 3, Samsung Galaxy
One thing you've really got to watch out for, especially with books on programming, is the formatting of code listings.

With printed books, the author will usually take care to ensure that the line breaks within program code occurs at sensible places. But that doesn't always get transferred to the e-book. I've seen cases where program code just flows like normal text, regardless of the semantics of the code or the occurrence of continuation markers. In other cases, the code simply gets truncated, especially on a small-screen device.

Also, some publishers don't realise that code has to be rendered in a fixed-pitch font. This is never a problem with paper books, but is sometimes an issue with e-books.

I'm not saying all programming books suffer from these problems -- just that they are issues you need to watch out for.
Mike L is offline   Reply With Quote