Hi,
> Datum: Fri, 13 Jan 2012 13:50:28 +0100
> Von: "Natacha Porté" <nata...@instinctive.eu>
> on Friday 13 January 2012 at 09:18, tin-pot wrote:
> > I have added the `discount` Markdown implementation into Fossil version
> > 1.21.
> > This is actually pretty simple to do.
>
> Well, no offense, but that was the easy part.
None taken ;-)
> I would be very interested
> in hearing how to handle the hard part (the one I have given up on when
> I was trying to integrate libupskirt): how to make it play nice across
> the distributed nature of fossil, including nodes with older versions
> which do not include the change.
Well, as I had admitted, this is an early stage, and of course it is a
bad idea to simply apply Markdown everywhere in one Fossil instance, and
nowhere in an other.
What I would propose to handle the "hard part" (hope I understand your
point correctly) is:
1. Of course artifacts with different notations (ie "native" markup and
Markdown) must be allowed to coexist in one repository. So we have
to tag them somehow - but I'm too new to Fossil's interna to have
"the right" solution for that; I hope this should not be too hard?
2. A "Native" Item must be recognizable as such without a tag: a missing
tag indicates the fact that it is native; and it must always be
rendered in the "native" way.
3. "Markdown Items" (and possibly other styles) shall be recognized by a
"Markdown-enabled" Fossil executable and rendered accordingly. I see
no fundamental problem here either.
4. What about rendering of "Markdown Items" (or comparable different
notations) by a off-the-shelf Fossil executable? A "native" Fossil
does not know anything about the "tag" for a "Markdown Item" and will
treat it as "native" anyway. I presume this is the "hard part" ...
The best option I see here is to "degrade gracefully" by an arrangement
like this:
- A "Markdown Item" is wrapped into a <pre> HTML element (or something
to that effect) and gets rendered by an off-the-shelf Fossil as plain
text without special formatting - but it sure would be good to have
at least "native" links processed correctly: how to provide for that?
I don't know yet - hints would be greatly appreciated.
As Markdown is _designed_ to be readable in plain-text view, this
should at least not destroy completely the useablity of Markdown
content in a "native" Fossil.
- A "Markdown Item" wrapped and tagged in this way can still be rendered
and edited correctly in a "Markdown-enabled" Fossil: the tagging and
wrapping should take place unnoticed by the user for items that are
designated as Markdown-styled.
Still, in a "native" Fossil, the item can be edited simply as a piece
of unprocessed plain text.
So this leaves me with a general request for proposals, and two specific
questions:
1. How to "tag" a piece of content (wiki page, log message etc.) in
order to signify it's markup stype?
2. How to wrap a piece of content so that a "native" Fossil will keep
its formatting (line breaks, white space) untouched but still renders
at least "native" links in a useable fashion?
Thanks & Greetings
Martin ("tin-pot")
--
"Okay, buzzwords only. Two syllables, tops." -- Laurie Anderson
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
