On Tue, 4 May 2010 11:28:03 -0400 >>>>>> "Richard" == Richard Hipp wrote:
Richard> There is exists no wiki markup that will make everybody Richard> happy. Any choice of wiki markup will leave some users Richard> grumbling that a different choice should have been made. I'm very well aware of it...and not knowledgable enough to know if some kind of plugin system supporting different markup would work. Richard> I am personally very happy with the current wiki markup in Richard> Fossil. It meets my needs very well. And even if someone Richard> where able to come up with a markup that met my needs better, Richard> at this point I have written so much using the current markup Richard> that I have little interest in changing. So, please do not Richard> expect me to spend time working on another wiki markup. I understand your rationale for the current wiki markup and respect it, as well as being thankful for providing fossil at the first place. However, the whole idea of more 'standard' and/or capable wiki is due to desire to extend its usage for all documentation needs one may have while working on the project...and I believe you agree that writing HMTL is not solution for writing e.g. manuals which require more structured markup than the present wiki is capable of. Richard> On the other hand, if you want to hack up Fossil to support Richard> Markdown or whatever other wiki markup suites you, then by all Richard> means have at it. You will not hurt my feelings in the Richard> least. Note that Fossil is self-hosting, so you can very Richard> easily clone the entire source history then add Markdown Richard> support in your private repository. With an inexpensive Richard> shared-hosting account, you can publish your Fossil-clone so Richard> that others who prefer Markdown can use your version of Fossil Richard> rather than the canonical version. And you can do period pulls Richard> against the canonical Fossil repository and merge changes from Richard> it into your branch. And you can do all of this with my Richard> blessings. Thank you for the blessings...too bad I'm not C-coder and even though I would be, I believe that making 'Markdown-fork' with the need for constant merge is not solution either. Richard> Just please don't ask me to do the hacking for you, nor Richard> support your changes after the fact. My question was not request that you do the hacking, but more a quest for something which Joshua is thinking about... Pls. excuse me if my post gave the wrong impression. Now it's clear... Does it also mean you are still the only coder involved in fossil? At the end it seems that it is possible to choose between the option to live with the present limited wiki markup or use other solution(s)... Sincerely, Gour -- Gour | Hlapicina, Croatia | GPG key: F96FF5F6 ----------------------------------------------------------------
signature.asc
Description: PGP signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
