I am working on ironing all the kinks out of my Scrivener-Zotero citation workflow, following this basic setup: Markdown/Pandoc :: Better BibTeX for Zotero Everything seems to be working except for when I want to include a Zotero BibTex citation within a Scrivener footnote. When I compile a Scrivener document into .md format, the footnotes include a “\” that prevents them from being converted by Pandoc. Here’s an example:
[^fn1]: This is a discursive footnote with a citation. \[@worsterPassionNatureLife2008 71\]
Is there some compile setting that will prevent those “\” from being added?
I had a similar problem. It appears to be a known bug on Windows. The workaround is to use inline notation when the note contains Markdown formatting, including [ ].
Thanks. I guess that means it may get fixed in a later update. But for now, can you clarify what inline notion I should use in the footnote to make it work?
Inline notation refers to the alternative form of notation that Scrivener provides, via the “Inline Annotation” and “Inline Footnote” features, available in the Insert menu and via shortcut. Since these are directly in the text, they benefit from all of the features available to the main text editor, which in some cases can mean using them to do things the sidebar notes cannot do, such as using styles or offering cross-reference links between items.
But in this case, it specifically avoids a bug in the sidebar text conversion code.
Yes, this is a higher priority fix, but it will be a little while yet before we can return to Scrivener development, unfortunately.
Thank you. I see now. I thought I needed to use some sort of Markdown inline syntax, like single backticks. But yes, using Scrivener’s “Inline Footnote” feature seems to work. I’ll use those for now. Thanks very much!
Yeah, the problem is how thorough the conversion is. It’s a deliberate feature, as I noted in the other thread, an optional one enabled by a switch, but really intended for those that don’t use any Markdown and would want any of Markdown’s markup, including the backtick, to be escaped with backslashes so they print verbatim.
The typical way to pass-thru markup when working this way is with a style intended for that purpose. You can make a style be treated as raw markup, in the Styles compile format option tab—but in this case that doesn’t work given the aforementioned limitation of being unable to use styles inside of comment and footnote sidebar boxes.
Anyway, glad the inline approach works well for you. In the future, when you see this fix pop up in the change logs, note the Edit ▸ Transformations menu, which has options for bulk conversion of inline to inspector, and vice versa (which indeed might be useful for you right now to fix any existing notes that contain brackets).