7

In my experience, no matter what you do you will end up with variances and idiosyncrasies throughout your documentation. People have different expectations for what level of formality, what level of formatting, and what organization they like. As such, I think what's probably more important than what you choose as your method for formatting is how ...


4

As of 2017, Authorea might be the way to go. It has all the suggested features, and in contrast to the other answers, it is finally an editor that actually supports collaborative commenting. As a plus, authors can choose whether they want to write their paragraphs in Markdown, LaTeX, HTML, or RichText.


3

Ideally, the reviewers don’t get to do any editing, no matter what the workflow. Even if they just want to see a small change like uppercasing a word, it is better if they just put in a comment and you make the changes. Or not, if you have a reason to reject the proposed change. That way you can maintain strict control of your master document. Again, no ...


3

With help from a coworker I was able to fix this by adding the following to the FO stylesheet: <xsl:template match="classname"> <fo:inline hyphenate="false"> <xsl:call-template name="inline.monoseq"/> </fo:inline> </xsl:template> And likewise for other elements that should get this treatment, like methodname and ...


3

While you can structure a list within a sentence this way, it's typically frowned upon. The preferred style would be to preempt the list with a complete thought that describes the list which follows it and treat that list as a break between thoughts. If you choose to have a vertical list you're saying it's important enough to be its own element and therefor ...


2

Etherpad. It has Commenting PLUS change proposals PLUS attribution Output as plaintext (even better than Markdown for the workflow) Collaboration in realtime with color coding Minimal WYSIWYG A local installation for security


1

My first guess would be Markdown. You can include png files in it too. Its syntax is easy to use and very well documented.


1

I have not been able to find any suitable Markup, so I started coding it myself. A very preliminary version is available on GitLab. Any feedback would be VERY welcome.


1

My bestie, when converting Ebooks, is Calibre. I use it mainly to load .epub files on my Kobo (usually converting from .pdf or .doc). You have so many options to control formatting. You can also export to .mobi and view it on your Kindle if you own one (or also just check the given preview). Calibre also has an integrated reader for Ebooks. Hope this can ...


1

The post you referenced has the basics: in FO, you can't change the hyphenation property for just part of a block. You may be able to change the hyphenation dictionary (add the words you don't want to be hyphenated), but this depends on the tools you use. Information for FOP


1

Draft seems to satisfy your requirements. The versioning process is done by drafting (hence the name) but it's almost the same thing.


Only top voted, non community-wiki answers of a minimum length are eligible