Given the following document (attached to this bug report) …
… multimarkdown exporter generates this (also attached):
Problems:
markdown_beta16.zip (22.4 KB)
markdown_beta16_mmd.zip (262 Bytes)
Also, (non-inline) footnotes are exported as:
Bold and Italics should be converted when using the “Rich text to MMD” Option. Does it work?
Indeed they are. I stand corrected on that part.
About the [] brackets, internal links are exported in [] brackets by design.
When you export and not compile the internal links are removed.
When you compile the Internal links are exported in [] only if the linked documents are also compiled.
There is one problem with link generation though. With the Markdown-based outputs, the default condition is for no RTF links to be converted to Markdown. This is in keeping with its long-standing behaviour of ignoring hyperlink syntax, along with 99% of the rest of the formatting, in the Markdown workflows.
What this output (no general conversion but links are converted) would be expected from is when a separate Convert links to MultiMarkdown setting is enabled in the general options area (below the independent option to convert tables and lists). This setting was added to the Mac a bit ago, at the request of those that generally do not want RTF conversion, but found the notion of having links converted handy.
Yes, this is using MultiMarkdown link reference syntax, which allows for the following forms:
[code]Refer to [Some Section].
Refer to [Some Section][].
Refer to [a section I’d like to talk about][Some Section].
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.[/code]
You can use parentheses, but only if you also format it as a proper link to an anchor point, and thus be capable of anticipating how MMD is going to turn your title into an ID, or by supplying your own custom ID, demonstrated in the second example below.
[code]
Refer to something with a raw link.
Refer to another thing.
But there is no need to use HTML anchors with [custom ID references either][customid].
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.[/code]
is it therefore supposed to be the case that inspector footnotes are not exported as footnotes when compiling to MMD?
Inspector footnotes will compile to syntax, but they are one of those features you can independently switch off, in the General Options compile overview tab.
General Options-? compile overview? I don’t seem to see this tab. This is under "file->options->general…? But I don’t see any tab for “compile” or “overview”
Is it under “compile?” But under compile-> options button, I don’t see anything that looks like the option you describe:
You’re in the right place, at the very top of that list is an option to remove footnotes. So if you do not need or want MMD syntax generated for your footnotes, that is how you could strip them out.
Ah I see what you mean.
I may have misworded what I meant:
The problem I’ve been encountering is inspector footnotes get exported through MMD as “links” to scrivener files rather than as MMD footnotes themselves. Inline footnotes, when exported via MMD, workout fine and appear as MMD footnotes.
Thanks, I’m pretty sure that is construction dust. Markdown in general is a work in progress at the moment—but this specific bug is not unique to it. You will find the same result when compiling to the standard (not MMD) HTML selection, for example:
<a href="scrivcmt://71C00557-AA98-43BA-8350-7ED33300752A">test footnote.</a>