It's useful to be able to read commit diffs.
AIUI OpenOffice docs are zipped so diffs aren't generated by SVN/Git etc.
Also if the documentation source is all text-based then it's a lot
easier to do searches and scripted edits (e.g. to fix common typos)
On 14 November 2016 at 19:54, Manfred Mo
I have used all those as well and my preference still sits with asciidoc.
Mostly because I have a larger choice of quality output.
If I have the choice overall and write more complex stuff on my own I would
probably go back to LaTeX ;-)
manfred
Martin Desruisseaux wrote on 2016-11-14 11:16:
Le 14/11/16 à 19:10, Manfred Moser a écrit :
> Switching from Asciidoc to OpenOffice seems like a recipe for disaster to me.
> Asciidoc (or asciidoctor) is very capable for PDF creation and is used in
> publishing companies like OReilly.
On my side I used at different time OpenOffice, Asciidoc,
Switching from Asciidoc to OpenOffice seems like a recipe for disaster to me.
Asciidoc (or asciidoctor) is very capable for PDF creation and is used in
publishing companies like OReilly.
And as you mentioned you can use your version control system nicely. With
OpenOffice you would loose the ab
Hi,
I've created a lot of documentation for Trafodion using Asciidoc, which
allows the project to include the documentation with the source. It's OK
but also complicated when wanting to provide PDF versions of the manuals
due to font issues and other things.
Talking with other contributors, there
