Helmut Denk wrote:
docbook would probably be adequate. its very good for
making a book-like, structured document.
Which is pretty much what we're doing.
if you have to maintain more distributed information
http://dita.xml.org is a better choice.
Possibly. I'll have to look at it a bit more. It looks terribly
abstract, and I can't really figure out what it is or does. We're just
writing a user guide here. That's it. I want something with a simple
(enough) model that is a good semantic fit for how I think about the
structure of a user guide. Docbook and latex do a pretty good job at this.
but both dita and docbook are in some way
old-fashioned ... xslt/fo is an over-complex
technology IMO.
Possibly. But that's the tool's problem. We don't have to deal with that
stuff.
an approach that seems more modern to me is:
http://princexml.com/
which means xml/xhtml + css.
Which schema would we use in this case? Make one up? Use docbook's?
This tool could be useful for the source -> pdf transformation, but does
it handle the source -> html transformation?
a fantastic tool for editing docbook, dita
and xhtml is:
http://www.oxygenxml.com
the grails-documentation may also be a
candidate to look at.
Do you know what they are using there? I couldn't figure it out from the
source.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
