So embarking on an old fashioned word based document is really not the way to go. I assume the reasoning behind this decision to use XML, etc. is to allow for a more collaborative environment and give greater control over maintenance.
What, then, would be the best way to contribute to the documentation efforts ? Assume that I have no XML authoring tools or the like ... just a desire to give something back !! Alan ~-----Original Message----- ~The documentation is primarily web-based, yes. When we take ~the time after ~v2.1 release to look at Apache Forrest for documentation, we ~can use Cocoon ~to generate other document formats, e.g., PDF. I could also look at ~producing a PDF of the final documentation. The documentation ~for James is ~all in XML files using Apache provided DTDs. See src/xdocs in the CVS ~repository. ~ --- Noel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
