trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gunnar Tapper <>
Subject [DISCUSS] Move documentation to Apache Open Office (AOO)
Date Fri, 11 Nov 2016 20:53:43 GMT

It's not easy to document in asciidoc. Personally, I have flashbacks to
TGAL/TFORM (for you old Tandem folks) that we used in the 80s. Seriously?

I've opened a discussion on the dev community list on this topic. So far,
no one seems to say that you MUST use markup languages for your

>From what I see, we'd been trading off being able to do diffs in source
control vs. having user-visible diffs in the documentation (via change
bars) and a REAL word processor. To me, the tradeoff is simple: use the
real word processor.

In addition, I think it'd be much easier to translate documents and to get
people to update them. Who wants to learn a markup language and all its
intricacies. (Trust me, table handling is a royal pain and so is PDF

I want to be clear that all forms of source control diffs disappear if we
move to AAO: the .odoc files are really zip archives with several files in
them. Also, we might lose the capability to provide the documents in
web-page format; experimentation needed.

What is your opinion on the matter? Would you be more willing to update
documents if using AAO, which is pretty similar to working in Word.


*If you think you can you can, if you think you can't you're right.*

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message