Hi there
In the release notes to DEVONthink To Go 4.1 Lagrange I read that DTTG has a new Markdown parser.
What about the Desktop DEVONthink? Does it uses teh same new parser?
Thanks for clarifications!
Hi there
In the release notes to DEVONthink To Go 4.1 Lagrange I read that DTTG has a new Markdown parser.
What about the Desktop DEVONthink? Does it uses teh same new parser?
Thanks for clarifications!
Not yet.
I see. Do we need to worry about any incompatibility between iOS and macOS?
I guess if you use MD features available only for DTTG, the MD files will display differently in DT. Not surprisingly.
Is there somewheer some details how DTTG and DTK parsers differ, plus what extras The DTTGH parser offeres?
In the manual I found that MathJax, Mermaid and Prism are supported – but I think they are supported in DTK as well.
MathJax, Mermaid and Prism are JavaScript libraries. They have nothing to do with Markdown or MD parsers. You can use any, all, or none of them with any self-respecting MD parser by adding them in a script element.
If there’s a button in preferences to enable these libraries, the MD parser just adds the necessary code when rendering to HTML.
The real differences between DT and DTTG parsers should be in MD syntax itself. AFAICT, DTTG supports GitHub flavored MD now, while DT is at MultiMarkdown.
And in the end the difference is just temporary.
Nevertheless: It would be nice to have a clear description telling us what the brand new MD renderer does support. I couldn’t find anything more detailed than “it combines the best features of …”, not telling me what these features are. But then I did perhaps look at the wrong place? Couldn’t find detailed release notes either.
MultiMarkdowns Inline Footnotes – [^This is the footnote itself, not the anchor of one.] – do not work anymore. Which is a problem when using file transclusion.
On the other hand with the new parser footnote anchors after an exclamation mark actually result in a footnote. Unlike the MMD parser which thinks that ![ is always the beginning of an image link and does not check if a ^ follows.
The next release should fix this. A complete document would be appreciated to confirm the fix in your case too. Thanks!