I would think the solution is rather simple / has been done before:

I once implemented inline support for TWC using this type of syntax:

§§§
your markdown here
§§§

based on @ShowDown 
<https://web.archive.org/web/20141021031548/http://showdown.tiddlyspace.com:80/>,
 
see docs at @MarkdownTutor 
<https://web.archive.org/web/20151101000000*/markdowntutor.tiddlyspace.com>

It could easily be generalized into this:

§§§commonmark
your commonmark-markdown here
§§§

or even
 
§§§md-cm
your commonmark-markdown here
§§§

if we wanted it thusly.

best -tb

On Tuesday, 12 December 2017 16:42:00 UTC+1, Jeremy Ruston wrote:
>
> Mario said:
>
> we would make commonmark [1] markdown [2] a 100% subset [3] of the 
> TiddlyWiki syntax?
>
>
> I’d be very interested if that were possible. It would potentially allow 
> us to dispense with the current Markdown parser, which has significantly 
> limited capabilities compared to native wikitext.
>
> I also agree with Josiah’s point that a worthy longer term goal is to make 
> TiddlyWiki a meta-markup system that allows end users to create their own 
> markup parse rules. However, the complexity of the CommonMark specification 
> suggests to me that it wouldn’t be possible to create a practical parser 
> entirely declaratively. In other words, I think the complexities of 
> arbitrary markup may well require arbitrary computational capabilities to 
> parse.
>
> But, of course, even if we couldn’t create a 100% spec compliant 
> CommonMark parser declaratively, it would still be a very useful thing to 
> have.
>
> Best wishes
>
> Jeremy
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b29449a6-5174-42dc-af0a-ae3588eaa421%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to