Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Date: Mon, 1 Dec 2003 11:14:29 +0100 (CET)
From: Stephan Michels <stephan@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: wiki syntax support
In-Reply-To: <AF82F63E-23E4-11D8-8C4A-000393CFE402@apache.org>
Message-ID: <Pine.LNX.4.44.0312011107350.1924-100000@vern.chem.tu-berlin.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE


On Mon, 1 Dec 2003, Bertrand Delacretaz wrote:

> Le Lundi, 1 d=E9c 2003, =E0 10:35 Europe/Zurich, Nicola Ken Barozzi a =E9=
crit
> :
>
> > Jan.Materne@rzf.fin-nrw.de wrote:
> >> ...Maybe in future Forrest can be configured which wiki format to use
> >> ...
> >
> > It can be done now.
> >
> > We have
> >
> >   .cwiki - JSPWiki format
> >
> > IMHO we should also have a couple more syntaxes:
> >
> > *.mwiki - MoinMoin (used in http://wiki.apache.org/)
> > *.ewiki - Email Wiki (using the format that is used in email
> >                       messages, like *strong*, _underlined_, etc)
> >
> > If someone wants to tackle it, I'll be happy to add it to Forrest.
> >
> > Suggestion: just change the cwiki grammar to the new format, and when
> > it's ok, send it here. I'll take care in doing the other changes
> > needed, like different extension supportl.
>
> Small warning though: being based on a "traditional" parser grammar,
> the chaperon-based wiki stuff gives parsing errors if the input files
> do not respect the wiki grammar. This can be very confusing for
> non-technical document writers.
>
> In the wiki world (AFAIK), the accepted behaviour in such cases is to
> process the page as well as possible. You won't get the format you
> meant but at least there's no confusing error message.
>
> Stephan Michels once said he was working on more free-form grammars for
> Chaperon [1] but I don't know if this has happened.

And I'm still working ;-) I currently develop a wiki-like documentation
system for my prof., so I improve the parser in this way. For example
I added some recovery strategies for invalid documents.

But there is still much work for a single person.

Stephan.