Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

2003-02-19 Thread Steven Noels
Nicola Ken Barozzi wrote: Of course, slide + Wyona + etc is the final goal Please let's not jump to conclusions ;-) -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog athttp://blogs.co

Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

2003-02-19 Thread Nicola Ken Barozzi
Jeff Turner wrote, On 19/02/2003 15.49: ... So there's a half-formed plan over in Forrest-land to migrate to XHTML 2 as an intermediate format, and make it one of the frontend formats too: http://marc.theaimsgroup.com/?l=forrest-dev&m=104351979527689&w=2 Then why not use html (ihtml), there ar

Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

2003-02-19 Thread Pier Fumagalli
"Jeff Turner" <[EMAIL PROTECTED]> wrote: > So I agree with Diana about moving all docs to the Wiki. It seems the > best long-term solution, avoiding all the problems that a dual wiki/xdoc > system would cause. I disagree on that. IMO the "Wiki" syntax doesn't have the capability to contextualize

Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

2003-02-19 Thread Stephan Michels
On Wed, 19 Feb 2003, Jeff Turner wrote: > On Wed, Feb 19, 2003 at 03:11:44PM +1100, David Crossley wrote: > > Diana Shannon wrote: > > > > Will people be able to do both ways - traditional patch/create > > xdocs in cvs, or via the Wiki? > > With Chaperon integration, the next version of Forrest s

Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

2003-02-19 Thread SAXESS - Hussayn Dabbous
Hy; The mentioning of "Wiki" triggered my curiousity: If we move all docs to Wiki, then how can we maintain different release versions of the docs ? Or will there be only one single document version, that fits for all released cocoon versions ? Or do you propose to connect Wiki with an underlyi