On 13 November 2010 11:43, Stephan Beal <sgb...@googlemail.com> wrote: > On Sat, Nov 13, 2010 at 11:24 AM, Stephan Beal <sgb...@googlemail.com> > wrote: >> >> Here's are full instructions, and they can easily be adapter to other >> JavaScript-based wiki syntax parsers: > > Okay, well, almost... the parser is mis-parsing some bits which it doesn't > mis-parse if i feed it the same day without it running through fossil. > Apparently some bytes are getting changed in a way which is incompatible > with the parser. > i see now that fossil is apparently still marking up [WikiWord|links] in > HTML, and that interferes with the parser. i figured that "all HTML" would > disable wiki links. So formatting which doesn't generate links works, but > fossil will still try to take over any [WikiStyle links]. That explains why > the intra-wiki links worked with fossil, even after being run through the > GoCo parser. > How feasible is an option to allow 100% unprocessed wiki content? > >
You need to implement an option for that (or better make the current HTML option do really HTML). There was some discussion earlier and there are other people who would welcome true HTML in fossil. I would welcome a true wiki with formatting features on par with MediaWIki or markdown but that's another thing. Thanks Michal _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
