There is exists no wiki markup that will make everybody happy. Any choice of wiki markup will leave some users grumbling that a different choice should have been made.
I am personally very happy with the current wiki markup in Fossil. It meets my needs very well. And even if someone where able to come up with a markup that met my needs better, at this point I have written so much using the current markup that I have little interest in changing. So, please do not expect me to spend time working on another wiki markup. On the other hand, if you want to hack up Fossil to support Markdown or whatever other wiki markup suites you, then by all means have at it. You will not hurt my feelings in the least. Note that Fossil is self-hosting, so you can very easily clone the entire source history then add Markdown support in your private repository. With an inexpensive shared-hosting account, you can publish your Fossil-clone so that others who prefer Markdown can use your version of Fossil rather than the canonical version. And you can do period pulls against the canonical Fossil repository and merge changes from it into your branch. And you can do all of this with my blessings. Just please don't ask me to do the hacking for you, nor support your changes after the fact. On Tue, May 4, 2010 at 9:54 AM, Gour <g...@gour-nitai.com> wrote: > On Sun, 29 Nov 2009 12:07:06 -0500 > >>>>>> "Joshua" == <jos...@letterblock.com> wrote: > > Hello list, > > I know I may be beating the dead horse, but... > > Joshua> I recognize that the improvement I and others are asking for > Joshua> may be non-trivial to implement, so while I think markdown (the > Joshua> particular format, not the general class of) is an obvious > Joshua> choice because it allows those who prefer plain HTML to just > Joshua> keep writing HTML without change, if something else is easier > Joshua> to integrate or otherwise preferable I'll happily embrace it. > > Here is avid darcs user familiar enough with several DVCS (bzr, hg, > git), but except fossil there is none appealing enough to replace > darcs. > > Having some 'standard' wiki markup is one of the things I researched > as soon as I visited fossil site today (after having short enocunter > in Sept '09). > > For a long time I was thinking to use reST/Sphinx for my projects' > docs, but gaving up on some Python technology (Django) and decided to > use Haskell, I've returned back to Markdown considering there is > excellent implementation in Pandoc (http://johnmacfarlane.net/pandoc/) > which supports some nice extensions as well. > > The usage of Markdown/Pandoc for end-user docs is quite appropriate > considering that one can convert Markdown markup into > HTML/LaTeX/ConTeXt etc. which would make Markdown excellent choice for > wiki format in Fossil. > > I saw (at the end of the thread), there fossil-creole markup, but just > wonder if there is still some live in the dead-horse of > Markdown-as-fossil-wiki-format? > > > Sincerely, > Gour > > -- > > Gour | Hlapicina, Croatia | GPG key: F96FF5F6 > ---------------------------------------------------------------- > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- --------------------- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
