Le 19/06/2015 03:44, Paul Foxworthy a écrit :
Hi Ron,
Up to a point I agree we should be planning for scalability and success. I
totally agree we should plan from the beginning for internationalisation,
and if a toolset doesn't support that, we should avoid it.
I am strongly in favour of good logical markup, so that we can generate a
range of different destinations. DITA is one specific way to achieve good
logical markup, but not the only one.
DocBook *does* support i18n. For instance, the OpenStack project is using
DocBook. Their i18n efforts use the Transifex (transifex.com) online
service, which is free for open source projects. See
https://wiki.openstack.org/wiki/Documentation/Translation.
Here Eric Raymond explains AsciiDoc completes Docbook
http://www.tldp.org/HOWTO/html_single/DocBook-Demystification-HOWTO/#AEN183
BTW did you know that Groovy documentation is done with AsciiDoc (actually
AsciiDoctor) http://www.groovy-lang.org/documentation.html not bad hé
The message you quoted was an Oracle employee assuming professional tech
writers and investing in commercial software like Oxygen. For DITA to be
viable for us, I would argue it must be usable by developers with open
source tools. We can't expect people to invest any money in order to
document OFBiz. Even with free tools, expecting people to directly edit XML
in Eclipse or whatever is a still a barrier that will restrict
contributions from non-developers. Maybe that limitation is acceptable if
the results will be good enough, but "scalability" in theory is no good to
us if nobody contributes in practice.
I have been using Oxygen for years, until they suppressed their Academic
license, the annual license passed from 16 euros to 200 :/
The free tools in Eclipse are enough for my work with OFBiz, and I even
encounter less edition issues (yes Oxygen sucks sometimes, believe me)
Jacques
I have not contributed one line of documentation to OFBiz, and I am very
familiar with IDEs and XML. So I am not the best person to judge these
things. I will be interested in the experience of people doing a proof of
concept. I will be very interested in the experience of people who don't
know much about XML.
I don't need to be persuaded that DITA is good, or that it produces good
results. I would like to explore whether or not it's *useable* by
non-specialists with a little knowledge and training.
Cheers
Paul Foxworthy
