On 3 August 2012 14:02, Natacha Porté <[email protected]> wrote:
> Hello,
>
> on Friday 03 August 2012 at 13:41, Michal Suchanek wrote:
>> I have strong objections about all such makups, none is perfect, all
>> have some annoyances, and they are all mutually incompatible.
>>
>> Changing from one to another does not improve things, however. It only
>> brings incompatible repositories into existence.
>
> You're going much further than I am here. What I have proposed does not
> introduce any incompatibility at all. I have only included the markdown
> engine and used it for inline ("embedded doc") rendering of .mkd and
> .markdown files in the repository.
>
> As I have said elsewhere, I'm not clever enough to imagine a solution to
> introduce markdown into fossil's internal wiki. So I don't propose it. I
> propose the extra embedded doc rendering, and the tools to perform any
> markdown-to-html conversion. When someone comes up with a way to deal
> with the internal wiki, they will have such tools.
Well, then it is less than satisfactory solution.
HTML is formatted in the browser. Hence support for HTML documents
comes for free, with no code required. It is passed through as any
other file type.
The fossil wiki syntax is used in tickets and internal wiki anyway so
documents in that syntax come nearly for free. The only concern is
proper hyperlink resolution so that you can browse the site. Users
need to know the format for the tickets and internal wiki anyway, and
you have cut&paste between docs and and wiki and tickets.
Now enter .mkd files. They need additional code to parse, there is no
such nice integration with the rest of the fossil, and they do not
solve the issue of "I am not familiar with this" for the users
familiar with the other formats.
And given somebody wrote a bbcode parser implementation, moin moin
parser implementation, and a half dozen others which will be allowed
in the fossil proper? Or is parser for any random format to be added?
How large will fossil then become? Who will maintain all this? Is the
parser to be removed again when the original author is no longer
interested and no other maintainer for it steps up?
>> As you did not include a link to your repository of markdown enabled
>> fossil I cannot tell how it addresses compatibility.
>
> I did. In the very first post of this thread.
Sorry, only saw some replies, not the starting post.
Thanks
Michal
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
