latex embedded in multi markdown, citations

Hello, I’m new to Scrivener and loving it so far. I have a fair amount of experience with LaTeX, and I’m trying to use it with scrivener through MMD. I can’t figure out how to make citations.

I found a video tutorial but it seemed to be for the old Scriv version(no file->multimarkdown settings)

Where/How do I include my .bib file? Or should I just put it in the directory with the produced tex file.

should make this be in the output tex file, but instead, when compiling MMD -> Latex, it generates a file with 0 bytes.

I get errors like this:

-:32: parser error : StartTag: invalid element name

A 2005 paper from Lawrence Livermore National Labs stat ^ unable to parse -

Can you report what MultiMarkdown you are using? There is MMD3 out now and I’m not sure what version Scrivener uses (I’ve replaced the default with the GitHub version of mmd. I recommend MMD3 for Latex, as it has a much cleaner processing model - just uses inputs instead of XSLT, which was difficult to customize.

For my thesis I use citations like this:


which is a Multimarkdown ‘reference’, and converts into

\citet{amir93} which is using the Natbib citation format.

But the approach you describe should be fine - surround the latex code with HTML comments and it should be passed through as pure Latex.

Assuming your copy and paste in the code block is accurate, check to make sure you do not have double-hyphens converting to em-dashes. Your HTML comment syntax looks like <!— instead of <!–, which obviously will not work.

The built-in version of MMD is 2.0.b6, the last release version of 2.x before 3.x started up. Both versions use the same system for passing raw LaTeX through, so that won’t make a difference.

The Scrivener conversion of two hyphens to a dash is one to watch out for with MMD: I’ve previously had mysterious table failure on MMD compile which came down to that same thing.

Thanks, it was scrivener converting double hyphens to dashes. I wish this feature was disabled by default.

I think all us plain-texters would agree. We live in a world of word processor users, though. :slight_smile:

Might be a good idea to throw together a “basically default” preference set that is optimised for folks like us though. Hmm, I’ll do that right now.