Sorry to post here, it's just the last thread I could find. What is the status of being able to go from WikiText to basic Markdown?
This is the only thing keeping me up at night when I'm using TW. On Thursday, August 15, 2013 at 12:13:58 PM UTC-7, Yitzhak Bar Geva wrote: > > Sounds fine to me. I'm not waging a campaign on behalf of MMD, or > Scrivener in particular, even though they are really good. The central > issue is compatibility/convertibility. > > > On Thu, Aug 15, 2013 at 9:38 PM, Jeremy Ruston <[email protected] > <javascript:>> wrote: > >> There's a lot of posts about MarkDown and TW5 at the moment, so I'll >> reply here with as much detail as I can, and then review the other threads. >> >> The situation is that: >> >> 1) TW5 wikitext is currently a blend of: >> a) classic TW syntax for most basic formatting >> b) MarkDown syntax for a few bits of basic formatting (code blocks, and >> allowing HTML tags) >> c) GitHub Flavoured MarkDown for a few other bits of basic formatting >> (strikethrough, fenced code blocks) >> d) new syntax for TW5's tiddler operations: transclusion, lists, widgets, >> macros >> >> 2) My declared aim is to simplify things by adopting MarkDown-esque >> syntax for all basic formatting syntax, extending it with TW5 specific >> syntax for tiddler operations >> >> My motivation in adopting (more) MarkDown is to take advantage of its >> familiarity to many users, and to permit the kind of interoperability that >> Yitzhak describes. >> >> I'm familiar with MultiMarkDown. Much of MMD is oriented around page >> media (footnotes etc), and isn't directly relevant within TW5, but there's >> definitely some interesting stuff there. I'm not sure what I think of MMDs >> table implementation. >> >> So, I think that the best way to interoperate with Scrivener will be by >> restricting content tiddlers to a common core of MarkDown syntax. If one >> wanted to publish that content both via TW5 and Scrivener, I'd expect to >> have to wrap it in separate templates for each target. >> >> Best wishes >> >> Jeremy >> >> >> >> >> >> >> On Thu, Aug 15, 2013 at 7:07 PM, PMario <[email protected] <javascript:>> >> wrote: >> >>> On Thursday, August 15, 2013 4:10:10 PM UTC+2, Yitzhak Bar Geva wrote: >>>> >>>> TW5's wikitext is lovely. It's convenient, expressive and all the >>>> superlatives, but off the beaten track. Scrivener supports MultiMarkdown. >>>> My problem (and I believe I'm not alone) is that I want to push the same >>>> content out over different media and keep them synchronized. >>>> >>> >>> Hi, >>> As I wrote at github issues [1], I think Markdown[3] should be a valid >>> subset of TiddlyWiki markup. ... but ... >>> >>> As you point out, Scrivener supports MultiMarkdown [2] which says at its >>> homepage: >>> >>> MMD is a superset of the Markdown [3] syntax, originally created by John >>>> Gruber. It adds multiple syntax features ... >>>> >>> >>> So it adds "syntax features" that are needed by Scrivenger. I personally >>> like Github and its GFM (Github Flavored Markdown) and pandoc [5] (for >>> printing) that also adds its own usefull features and can handle a lot of >>> syntax flavors. ..... >>> >>> With this list, I just want to point out, that there are several >>> different usefull Markdown dialects out there. So IMO TiddlyWiki should >>> include the minimum set of Markdown syntax that is still useable for >>> "simple text". The rest can be plugins. >>> >>> IMO even Markdown as John Gruber designed it, should be a plugin, >>> because this initial definition has some shortcommings, that all the other >>> flavors tried to fix. We should not include them :) >>> >>> What do you guys think? >>> >>> have fun! >>> mario >>> >>> [1] >>> https://github.com/Jermolene/TiddlyWiki5/issues/124#issuecomment-22705113 >>> [2] http://fletcherpenney.net/multimarkdown/ >>> [3] http://daringfireball.net/projects/markdown/syntax >>> [4] https://help.github.com/articles/github-flavored-markdown >>> [5] http://johnmacfarlane.net/pandoc/ >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "TiddlyWikiDev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> >>> To post to this group, send email to [email protected] >>> <javascript:>. >>> Visit this group at http://groups.google.com/group/tiddlywikidev. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> >> >> -- >> Jeremy Ruston >> mailto:[email protected] <javascript:> >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "TiddlyWikiDev" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/tiddlywikidev/8OkKo-hn2Fs/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/tiddlywikidev. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Best, > Yitzhak Bar Geva > On LinkedIn <http://il.linkedin.com/pub/yitzhak-bar-geva/3/759/3ab> > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/9cd3b65d-c33e-45ff-8edb-62b443734dd9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
