On Fri, Aug 3, 2012 at 12:19 PM, Michal Suchanek > ...not to decide that but I have to agree. Once you let in markdown > people used to some other wiki syntax would argue they have needlessly > hard time and there would be no end to the stream of requests to > include yet another. >
Hi Michal, For what it's worth (i'm summarizing here because i suspect that you missed the past 37302 threads on this topic ;)... Yes, you are absolutely correct (IMO) on each of your points. The fact is, however, that MD support has probably been the single most-requested feature (possibly as a side-effect of github?) in terms of fossil's wiki support. That gives it a bit more weight, in my opinion (even though i don't personally like MD). That said: in several of my fossil wikis i store Google Code format in the wiki and render it client-side. My only point there is that it _is_ currently possible to integrate any wiki format(s) you want to as long as you can render them client-side, and if you are using multiple formats you need a way of differentiating them (so you know which rendered to use), e.g. via a naming convention or a special markup tag in the first line, or similar. Here's an example which uses GoCo format exclusively: http://fossil.wanderinghorse.net/wikis/cson/ (That doesn't look much like Fossil as you know it, but it is a custom UI implemented on top of the JSON API.) -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
