Booktype: An Open Source, Cross-Platform Approach To E-Book Publishing

Despite Apple's protestation that the iBooks Author EULA was misinterpreted, the idea of a book publishing system that could be used to grab copyright of the prepared text is annoying — like the sort of EULAs that seem to give photo-sharing sites unlimited re-use rights of hosted personal photos. New submitter rohangarg points out a publishing system which shouldn't have such problems, and is nicely cross-platform besides: "A new open-source digital writing and publishing platform has been launched by non-profit group Sourcefabric. Booktype allows for collaborative editing and writing of books that can be easily outputted to on-demand print services and eReaders such as the Amazon Kindle, Nook, iPad, and more with a few simple clicks. Booktype source can be found here." The online demo also leads to some downloadable examples (as PDFs).

Comments

Re:LaTeX?

[Simon Brooke]

Very few people can actually use LaTeX. It's an exceptionally user-hostile approach to writing text. Yes, I know some people still use vi, but that doesn't make vi a good word processor. Similarly, LaTeX has exceptional strengths for creating particular sorts of highly technical documents, but for the sorts of documents most people write it is overcomplicated and just gets in the way.

Most people don't want to learn a new language before they can write a simple document. Even if they do want to learn a new language, Markdown is good enough for most people's uses - you can produce damn nice looking documents and, yes, books with it (my toolchain is text piped through a sed script which renders the markdown into rough HTML, through JTidy which cleans that up, through Prince which translates the HTML into nicely rendered PDF, and thence to print. I could use LaTeX - I have used LaTeX - but except for very complicated technical documents it just isn't worth it.

Re:LaTeX?

[0123456]

What are the short comings of HTML for this then?

Most ebook formats are just wrapped HTML.

Re:LaTeX?

[fyngyrz]

E-Book publishing must deal with non-constant "page" sizes. Even on individual devices - when a tablet reader rotates 90 degrees, the book contents must reflow to deal with the new "page" width. Furthermore, users now expect to be able to change fonts and font sizes at will while reading. Rendering needs to be done in the reader software, not during file preparation.

Tailor-made for HTML. You can specify paragraphs, sections, underline, bold, italic, embed images, hyperlinks... all with reflow and user-specified fonts and sizes and colors.

RANT: That was the original intent of HTML: That the user had control over the look and feel, and the author provided content. It's only been in the last few years that websites started screwing up the whole idea of content following browser resizing -- one of the worst design mistakes made, IMHO, because it wastes the user's expensive desktop space in favor of the designer's "idea." If you're any good, you'll design so you get "that look" at a particular size, then the user can find that and stay there if they want to, rather than being stuck with a hard-coded 1024x window or something like that. You can do some pretty clever things along this line with CSS, but hardly anyone does.

It's gotten to the point where if your content reflows the way it should, a lot of people think you're doing it "wrong." Amazing, really. /RANT