On 4/29/09, Robert Ledger <rob...@pytrash.co.uk> wrote: > I was thinking that it might be a good idea to provide a parser > interface so that custom wiki implementations could easily > be integrated with core fossil. ... > The <wiki ..> tag could also be used to enable/disable wiki features > such as my proposed <!-- --> pass through or "kkinnell"s <annotation> > markup.
i think that's a great idea. The ability to create a custom wiki parser in JS might also be really interesting. The wiki interface approach might also allow us to layer wiki parsers :). > A strategy would be needed to handle unrecognised wiki parser name, > simplest : treat as verbatim to next </wiki>. Simply pass it through as-is. i assume you mean that by "verbatim", but "verbatim" has a special meaning in some wikis (close to HTML PRE) > I am in the early stages of implementing this, so now is a good time > to be making comments and suggestions, which would be welcome. My personal favourite wiki syntax is google code :). > I intend to start with a Creole parser as it is easier to work with > and test an established standard, however, I might be interested in > working on an advanced custom parser for fossil. If anyone has any > thoughts on this or a wish list of features speak up now (or forever > hold your peace:) i don't know if this would be useful for your cause or not, but late last year i put together a C library for generating PEG-style parsers using composition of Struct objects: http://fossil.wanderinghorse.net/repos/pegc/ someone else used that lib as the back-end for a PEG parser generator implementation for lisp, and the code is believed to work quite well. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
