As I understand from your conversation is that one of your problems is that you are not allowed to setup a dynamic server.
But what about setting up a dynamic server in the "background" where a CMS is installed and allows emails as "input" and "commiters and contributers" can manage the documentation (WYSIWYG or on the command line). At OSCOM we are starting an Interop/Cross-CMS project, which has the following very basic setup: http://www.oscom.org/projects/interop/interop.jpg I am currently writing some code, such that Wyona can update and commit to CVS via ssh and can publish static HTML (generated via Cocoon) via ssh to some common Web Server. Would that help you somehow? Michael Bertrand Delacretaz wrote: > On Monday 10 June 2002 09:53, Steven Noels wrote: > >>. . . >>I was thinking of something along these lines for Forrest however, where >>non-Cocoon documentors (Xerces, Axis, etc) probably don't have an >>instance of Cocoon running on their workstation. >> > > If Cocoon is not available, what might help is something we > discussed here a while ago [1]: including mailto URLs in documents (on every > paragraph?) that allow users to send comment to -dev mailing lists with > headers that identify the message purpose: > > mailto:[EMAIL PROTECTED]?subject=[DOC-COMMENT]somefile.xml-para231 > > not sure about the syntax, but it's the idea. > > -Bertrand > > [1] > http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=102144573329536&w=2 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
