Best workflow for programming book
I wish to write a book on assembly language programming that will be available in both electronic and print versions. I currently sell one (another computer architecture) on Lulu. I used LaTeX to write the book and learned last year that there is no reasonable way to convert it to epub. So I sell it both in pdf and paperback. (This is a 568-page book. I'm taking on a big project here, so I want to plan carefully.)
One of the big problems with pdf is that this severely limits the market. As far as I know, Lulu is the only place that will sell both paperback and pdf. Amazon, Apple, and Kobo will not accept books in pdf.
It seems like the most universal format for an ebook is xhtml, the basis of epub. The problem, of course, it that epub (on current readers) does not do a good job of supporting math, line drawings, and computer code listings. This means that I would need to "dumb down" the look of these elements in my book.
Has anyone had good luck producing a technical book (math, line drawings, etc.) in epub? If so, what workflow tools did you use? At this point would it be better to simply stay with pdf?
BTW, I do use smaller, uniform (no binding gutter) margins on the pdf version of my current book, which does improve readability on mobile devices. It has the advantage of preserving pagination between the electronic and print versions, thus making it easier for instructors to refer to the book when students have the two different formats.
|