Cover of the Polish edition of my bookAs some of you may know, I've written 1.08333 books in my native language - a 620 page book for intermediate / semi-advance programmers called something close to "Understanding Programming" or "To Understand Programming" (it was surprisingly well received and it even got an award from the Polish Information Processing Society), and a chapter in a reverse engineering book that had 12 authors (I've also served as a mix of a project manager and technical editor in this case). Anyway, for a long time I wanted to bring the first book to English, and I even got it translated to English and shown it to some publishers. However at that time I didn't really have the energy/time to follow up on it, and it was in great need of some serious editing.

In early 2018 I started thinking about the second edition of the book - what should I change? Update? Add? Or perhaps remove / move to an appendix? While there were several options, there was one thing I was sure about - I want to release both the Polish and English version at the same time.

This leads us to the main question: what software / technical stack do you recommend to write / edit a book in?

It seems to be a strange question, given that I already have experience in the topic both from an author's perspective, as well as an editor's perspective. However the software stack I've used previously was a weird merge between what I wanted to use and what the publisher wanted me to use - this meant that we had to convert the rich text first from the word processor I and my proofreaders/editors used (Google Docs), to a word processor the publisher's proofreaders/editors used, and later to the application the DTP folks used. This sole process introduced A LOT of typos for some reason (especially at the DTP phase) and also meant that none of the fixes made at any of the last two stages were ever ported to Google Docs.

So I'm asking the question above since I basically want to change the software stack I will use for the second edition / English version (and since I'm going self-publishing way I have full flexibility here).

Now here's the thing - my needs are actually pretty weird. I.e. here's what I would expect from a perfect stack for my use-case:

• The author should be able to write/modify the text, while at the same time proofreaders should be able to add suggestions / comments.
• The rich text should not operate on styles like "bold", "italic", "font: monospace", but rather on style classes like "code", "normal text", "command", "filesystem path", etc (so when I when I decide that e.g. filesystem paths should not be monospace, but for example italic, I can do that for the whole book with one style class change).
• It should be a WYSIWYG editor as far as rich text / tables / graphics are concerned (it doesn't have to show the same layout as the target ones - well, that's even possible in the first place).
• It should be automatically compilable to PDF (for printing), PDF (for screen display), EPUB, MOBI, and HTML, with separate styles/layout configs (i.e. there should be no need to manually tweak the source text to fix random bugs in DTP - this should all be fixable in style/layout configuration which should be agnostic to the source text).
• Added bonus is being able to display the English / Polish version side by side while editing.

Yeah, I know, that's probably too much to ask for ;)

But if you have any hints or tips on what software should I look at, please let me know! I will be grateful :)
(Please let me know even if you have an idea that ticks only some of these boxes.)

Thanks!

P.S. I want the book to be published in 2019, but I still have to work out some other details. And finish some other projects. I'll keep you updated on the progress of things in case you're interested.

Comments:

2018-12-17 15:55:23 = ttbhz
{
most of these features are implemented i Adobe InDesign. But in other hand, while its great for text editing on DTP level, it's not so good for writing anything in it. and of course its not free/opensource.
}
2018-12-17 18:13:02 = Piatkosia
{
Latex? ;)
}
2018-12-17 20:56:57 = aablis
{
LaTeX may be suitable for you. I believe it has most (if not all) of the things you expect. Pandoc is a nice tool to convert document. formats. Also, you can write most of the stuff in markdown, which is much simpler than LaTeX, while still using LaTeX-specific commands.
}
2018-12-18 23:57:41 = Max
{
groff or LaTeX for formatting

Private git repo for modifications, comments, editing - you could create branches, merge varoius versions with corrections.

But the main question is: who are your users? Are.they technical? Will they manage using all those different pieces of your ideal stack?

It's worth looking at OpenBSD's mandoc - maybe it will suit your needs. Here's nice summary of various formats: https://undeadly.org/cgi?action=article&sid=20170304230520 (at the very bottom) Avoid markdown.
}
2018-12-20 06:20:00 = eric
{
How about asciidoctor?
}
2019-02-24 16:19:15 = Jurgen
{
Maybe this is a stupid suggestion, but Collabora has a cloud version of LibreOffice - that you can install on your local server or you can use a hosted solution. I have a small setup running at oCloud.de - if you like, I can give you a small account so you can try it out. It allows you to have a nextcloud setup (so edit files locally with LibreOffice, or edit them in the online edition).

You can perfectly use styles in there
Haven't tried collaborating in real time, but I think it's possible.
It stores to PDF in different formats, and has a great toolkit for ebook formats and publishing
Not sure about side by side editing, but obviously you can open both windows side by side.

Jurgen (at gaeremyn point be)
}

Add a comment:

Nick:
URL (optional):
Math captcha: 9 ∗ 4 + 5 =