Cant find XSLT-Folder


I want to use the MMD->Latex compilation but I think i need some XSLT for customization because i want to have listings in my document with \lstlisting. My problem is, that I cant find the folder with the xslt-files. I read that the path should be ~/Library/Application Support/MultiMarkdown/. But this folder doesnt exist on my mac. I also cant find something with spotlight altough i already used the latex-snippet.xslt file.

You’ll need to download the MMD2 distribution to get that folder. Scrivener comes with its own copy embedded inside the application (and that includes all of the stock xslt files, so that is where the latex-snippet.xslt file came from), so ordinarily you don’t need to install anything to use it, but if you do want to customise stuff, you’ll want an external installation (which compile will use in preference to the embedded copy, if it exists).

If you do work in snippet mode, you might want to try upgrading to MMD3 instead of installing the older MMD2. You’ll need the MMD3 Mac support package installed as well. This will put some helper scripts into the Application Support folder, and cause Scrivener to trigger the new MMD3 system instead. The advantage for you, if I presume correctly, is that it fundamentally works in snippet mode by default now. Only the content gets generated, even if you aren’t in snippet mode. The preamble and all that stuff is now dynamically linked using the \input command.

Thank you very much.

I will think about it but i just had an idea because of my problem with the lstlistings and some other special things i already have implemented in my Latexfiles. So my idea is to just set up notes in Scrivener for each chapter, section and so on and in these notes put plain latex, that means start every note with .
So i can use my original Latex im used to but with Scrivener and its extras. For compiling to a pdf i just need to compile it to Latex and then to PDF. Or is there a method to just save each note as a own .tex file without using MultiMarkdown at all, because i wouldnt need that anymore.
Do you think this could work?

Is your special list environment something you always use? If so, you might just try renewing the appropriate generic commands instead of creating a new one—that way you don’t have to customise the output at all. Maybe that’s not feasible for what you are doing though.

Back to not really using MMD: Putting everything into a comment should work—but really the only benefit you would get there is headers; which granted are nice, but like I say you can do this with title prefix and suffix settings in the compiler and get the same effect without essentially using a huge scripting system to do one small thing:

[size=80]Two-level demonstration of LaTeX style headers using suffix and prefix ‘Title Settings…’[/size]

Also, if you tried to use the graphics or footnote syntax generation features that way, you’d just end up with raw MMD in your file, due to the HTML comments.

The above demo works best with the plain-text compiler, since at that point you are just using Scrivener to create a huge .tex file when you compile.

Well, basically. If these are .tex snippets in a long draft that make up a full .tex file, then using [b]File/Export/Files...[/b] in plain-text mode, and using a batch rename tool to go from .txt to .tex would do the trick. If you’re looking for a way to go from MMD to .tex with lots of little notes—then no there is nothing like that. All of the tools are geared toward compilation, and so are the opposite of making lots of little files. That’s what Export is for, but Export doesn’t execute the MMD script system.