Hi,
How come using the strikethrough syntax in markdown (like this for example) results in a subscript when viewed?
Thanks.
Because that’s not part of the MultiMarkdown specification.
MultiMarkdown v6+ (which is the spec we support) supports some of the CriticMarkup syntax, so a strikethrough could be set via {--bad words--}.
1 Like
Thanks. Never seen that before. Problem is, like many others I’m using DT in conjunction with other applications and this doesn’t seem to be a very wide-spread usage, or am I wrong? This syntax isn’t recognized by either iA Writer, Typora or MacDown.
MultiMarkdown is the natural successor to Gruber’s original specification and has been in use for quite some time.
CriticMarkup is a newer spec but is supported by MultiMarkdown, so we support it too.
We can’t account for other flavors of Markdown, especially proprietary ones.
Well, it’s very confusing IMHO: it must be Google’s fault again, but when I search for “official multimarkdown syntax”, the first results I get refer to this website. I guess the syntax has yet to settle on this, as Gruber’s specs don’t say anything about strikethrough.
I guess the syntax has yet to settle on this, as Gruber’s specs don’t say anything about strikethrough.
That is correct. Gruber’s original spec didn’t account for many things. Fletcher Penney’s work in extending it via MultiMarkdown is what we support.
CriticMarkup is not part of MultiMarkdown.
It is supported by MultiMarkdown.
By extension, we support it too.
As noted on the CriticMarkup site…
Critic Markup is intended to provide basic editorial change tracking in plain text files. The syntax is compatible with Markdown, MultiMarkdown and HTML.
So, if it isn’t Gruber’s specs or MultiMarkdown, what is the name of the “standard” used by the apps I mentioned above (and others) in which strikethrough is defined with double-tildes?
You’d have to check with those app developers, and no - it’s not guaranteed they’re all using the same.
The only other fairly broadly used spec would be GFM (GitHub Flavored Markdown). However, no we don’t support that spec and no, there’s no option to choose a different specification.
PS: You don’t just add a spec. You have to support the spec in development as well. If it was a simple matter to implement, we’d allow choosing Fountain, GFM, etc., etc.
OK thanks.
You’re welcome.
Nice! Thanks a lot.
Also <del>more bad words</del> could be used, depending on the need. 
more bad words
Make a Typinator or TextExpander shortcut for these. E.g., I use ]]- with Typinator. My shortcut creates the beginning / ending <strike></strike> tags and puts the cursor into the middle so I can commence typing after the shortcut.
Extra credit: <strike>also works in this forum</strike>
also works in this forum
Or create the substitution in System Preferences > Keyboard > Text
1 Like
If you want to use GitHub Flavored Markdown (GFM) you can, you just cant use the preview built in to DT. I use GFM all the time but preview documents in the app Marked.
Bluefrog you absolutely kill me sometimes with some of the stuff you write in here.
PS: You don’t just add a spec . You have to support the spec in development as well. If it was a simple matter to implement, we’d allow choosing Fountain, GFM, etc., etc.
Somehow Brett Terpstra manages to support multiple flavors of Markdown just fine in Marked. After all, the only real issue in DEVONthink is the document previewer given that you guys don’t do inline syntax highlighting in the editor. It would be totally possible to allow the user to select which processor library to use. You guys might want to just support MMD and that’s fine, but please don’t act like this is something that is difficult to accomplish.
2 Likes