MultiMarkdown in Editorial
I found out that some features of MultiMarkdown are not supported in Editorial, as well as a bug:
- Within Code delimiter (```),
<>are not escaped. i.e. HTML codes within code block will still be HTML codes, not plain text.
Does not support:
- MMD metadata block (e.g. title is ignored)
- superscript & subscript (e.g. if MultiMarkdown is not selected, there's an option to select superscript. But once MMD is enabled, MMD styled superscript and subscript is not supported)
- Inline footnote
- ``this kind of smart quote'' will not resulted in “this”
- Code class (e.g. "```tex" should becomes
- Math class (it doesn't have
<span class="math">...enclosing the math)
- Within Code delimiter (```),
Glad someone's nudging @omz to support MORE of MultiMarkdown. I wonder, however, which MultiMarkdown engine is being used. If it's a "standard" one then it's different from a home-grown one.
if you open the Python console in Editorial and type the following:
import markdown, markdown2 markdown.version # 2.2.0 markdown2.__version__ # 2.2.1
I am not sure if these versions include the functionality that you mention above or not.
Thanks @ccc and how would you know which of these Editorial is using (by default)? I would also wonder - if this is relevant - which settings are being used as well.
Editorial doesn't use Python for its own Markdown preview. The library for MultiMarkdown is peg-multimarkdown (if MultiMarkdown is not enabled, I use sundown). I have to admit that I haven't updated the Markdown conversion libraries I'm using in a while...
I suspected that you did not use Python for Markdown preview. The most recent update in either of those two repos (peg and sun) is three years ago so I doubt you are very far out of sync with them ;-).
I'm a fresh user of Editorial and I bought the app because I've read it supports Multimarkdown. Imagine my disappointment when I open a file with lots of footnotes (written on my MacBook with Multimarkdown Composer Pro) and in Preview just see the source code for the footnotes … Could have stayed with Notebooks 8 just as well. :-(
@jotteerr Have you enabled Multimarkdown in the settings? What does your footnote syntax look like?
@omz Yes, MultiMarkdown is enabled. Example for the syntax:
[^This is a footnote.]
As far as I know, this is part of the MMD syntax since v. 4.
It would be great if you could find a way to handle this with Editorial.
The way footnotes work in Editorial at the moment is with labels like
[^fn1]and definitions of the footnote somewhere else (e.g. at the bottom of the section/document), like
[^fn1]: This is the footnote text
(The labels don't have to be numbers.)
@omz I've understood that. But I don't think it's worth editing more than 50 footnotes to a rather cumbersome format, I have to look at other editors instead. It's a pity because Editorial looks promising otherwise and because I already paid for it, but for me footnotes are a killer feature.
"a rather cumbersome format"
According to the MMD syntax guide, that's the official format. An identifier goes inline in your text and the actual text of the note goes at the end.
Ah, I do see here than "inline" footnotes are also allowed by MultiMarkdown. Mea culpa.
@omz I'd just like to add a voice for inline footnotes support. They're really essential for trying to write scholarly work in markdown.
I also wanted to note that inline footnotes would be a fantastic help for me!
Support for inline footnotes is the only thing holding me back from purchasing the app at this time.