Just wondering if there is any way to tag a certain document in Scrivener so it will be exported as say an Abstract.
LaTeX has support for specific chapters that dont influence the normal chapter ordering, such as the \begin{abstract} etc tags.
If not, then has any consideration been given to allowing for this via the custom meta-data feature that already exists in Scrivener?
With MultiMarkdown you can insert LaTeX at will. I do this quite a bit myself to amplify what MMD itself does not address. The concept itself is extremely simple: put your LaTeX code into an HTML comment. That will signal the MMD engine to pass it straight through to the LaTeX output without escaping the syntax.
[code]
[Your text]
[/code]
I’m not sure how that would be useful, could you explain what you had in mind? Now if I were to suggest a feature that compliments this technique, it would be compile-time Replacements, not custom meta-data, or inline annotations, with their capability of using custom delineation in the Footnotes and Comments pane. If you set your markers to now you can use inline annotations as a “print raw LaTeX here” feature.
The Scapple user manual in fact does something very much like that, it actually combines the two concepts. Replacements and inline annotations work together to build custom LaTeX calls. Check out the that project from our support page if you haven’t. It has a lot of useful tricks for extending what MMD can do without getting too messy in the text editor.
Ah yeah, i know about the escape clauses (and i use compile time renames to convert some tags already). But the problem is that the LaTeX output assumes all documents in the Scrivening should be a part, and so adds \part tags before it, like so:
[code]\part{Abstract}
\label{abstract}
\begin{abstract}
Abstract goes here
\end{abstract}[/code]
Sadly that causes LaTeX to have a little hissy fit as to what the order of compilation is. Currently im getting around it by only compiling the Abstract in on the final run and manually deleting the \part tag, but that isn’t ideal as i sent a paper off today minus an abstract (thankfully the editor was understanding).
What i was getting at with the metadata, is the ability to set what type of ‘part’ the document is. So one part might be an Abstract and so take the \begin{abstract} tags, while another might have a bibliography, so therefore take \begin{thebibliography}. Ideally the metadata could just have a Key which takes a generic \part{title} if empty, but allows for custom specification.
I’ll leave Ioa to respond on custom metadata.
This may be a grandmother egg sucking tutorial, but if you set the abstract document to ‘compile as is’ you won’t get a standard title and label for the document in the MMD-generated tex file, just the hand-crafted \begin{abstract}.
Excellent! I didn’t realise that, and it is a great help as then i can pop that in for the bibliography as well.