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 ability to do changes reviews and so on and you would basically manage binary files in your Git repo. If OpenOffice could pick up a folder (that is the extracted zip of the file format) and you could version control that the situation would be different, but from all I know that is not possible. Maybe you could hack something together that does that though. Like some sort of ignore file for the binaries and a build script that unzips the doc file and then the writer would commit those. Manfred Gunnar Tapper wrote on 2016-11-11 09:57: > 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's a clear preference to use Apache > OpenOffice for documentation. Beyond usability (and therefore more > willingness to document), it also makes translation easier. We have lots > and lots of documentation (http://trafodion.apache.org/documentation.html) > and are trying to get tech writer contributors to engage, which makes word > processor support more important. > > Has anyone used OpenOffice for documentation before? If so, how is it > handled with source control etc? (OpenOffice files are really zip archives > with multiple files in them.) > > Thoughts? > > -- > Thanks, > > Gunnar > *If you think you can you can, if you think you can't you're right.* > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
