trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Varnau <>
Subject RE: [DISCUSS] Apache OpenOffice instead of AsciiDoctor
Date Fri, 15 Jul 2016 16:58:48 GMT
Wouldn't the change make it much harder for people to review changes in the
docs?  Github would not give visual diffs.
So every reviewer would have to have openoffice, not just every author.
Even if they have it, pulling the docs and comparing seems like a hard


> -----Original Message-----
> From: Atanu Mishra []
> Sent: Friday, July 15, 2016 9:52 AM
> To:
> Subject: RE: [DISCUSS] Apache OpenOffice instead of AsciiDoctor
> Hi Gunnar,
> All for making things simpler. Which this should.
> I assume this means moving away from the asciidoc format. Will there be a
> (big) migration effort?
> Thanks,
> Atanu
> -----Original Message-----
> From: Gunnar Tapper []
> Sent: Friday, July 15, 2016 9:41 AM
> To:
> Subject: [DISCUSS] Apache OpenOffice instead of AsciiDoctor
> Hi,
> As you may have seen and/or experienced, it's not easy to work on our
> documentation since you have to setup the build environment, run maven
> builds, etc. And don't get me started on how clumsy it is to update
> documentation.
> I propose that we rethink the whole Asciidoctor approach and move to
> Apache
> OpenOffice instead, which is, of course, open source with a real word
> processor. IMO, the use of Asciidoctor creates a huge barrier to
> documentation creation. It is very, very cumbersome.
> In this model, we'd check in the OpenOffice source into the source tree.
> The publication would be a little more manual in that you'd have to
> generate the web pages and PDF files from within OpenOffice but I think
> that's an OK tradeoff. And, we can probably figure out a way to script
> such
> actions down the line.
> Thoughts?
> --
> Thanks,
> Gunnar
> *If you think you can you can, if you think you can't you're right.*

View raw message