Hacker News new | comments | show | ask | jobs | submit login

Yes, and it might be good enough for short, simple documents.

For me using a product like PrinceXML gave me the power of HTML/CSS to control the eBook's appearance more precisely. Also, using a Ruby-based build process let me take advantage of source control, ERB/Ruby code and other things. In other words, it made the whole process easier to manage for producing a large document.

I'm interested in whether you looked into using a DocBook tool chain via publican or asciidoc.

The reason I asked was your comment about taking advantage of source control and the implied separation of content from formatting.

The only real advantage that I can see to going with publican[1] or asciidoc[2] is that they're free tools. The main disadvantage is that you'd have to define formatting via XSL.

[1] http://fedoraproject.org/wiki/DocBook

[2] http://www.methods.co.nz/asciidoc/

XSL! Oh no! I'll have to steer clear of that :)

No I didn't. Sorry I'm not familiar with it - can you tell us what the pros/cons of that approach might be vs. what I did?

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact