I tested internal links with [[word]] linked to a document in a folder “Glossary”. I added a section layout without separators. I compile Multimarkdown and in a second step with pandoc to a PDF. But the links are not active in the PDF. I want to link a glossary term in the text to the dedicated glossary page with the explanation.
I read a lot and searched here and over the internet. But I’m more confused and I ask myself if that is possible, or only if compiling to HTML?
Thanks for a short answer about the behaviour and suggestions, if there are any
I added a section layout without separators. I compile Multimarkdown and in a second step with pandoc to a PDF.
Curious as to why you are going through both MultiMarkdown and Pandoc here? Does that mean you are creating a TeX file with MMD, and then using Pandoc to turn that into a PDF? Why not just use latexmk at that point; fewer moving parts?
At any rate, I’m not as sure of the specifics of the procedure with Pandoc, but with MMD there is built-in support for making actual glossaries using the semantic tools for doing so. With other file formats, you may need to cobble something together though.
Correct, I wrote a thesis with Typora as my Markdown editor of choice and I was asked by the professor, if I want to publish the thesis as a book.
For publishing I need to write a “second edition” and I needed a revision mode. So I imported the .md files into Scrivener, made some adjustments and started writing.
To the process writing the thesis in Typora I added some latex functionality like the glossary and abbreviation list. I use a Lua filter during the Markdown to PDF compilation with Pandoc. The Lua filter is responsible for converting abbreviations to latex code for glossary entries and latex itself compiles the cross-references between the glossary terms in the text and the explanations in the list, which is part of the thesis before the main content.
My idea is now to migrate the glossary list with the cross reference functionality to Scrivener to avoid the additional compiling with Pandoc in the future.
My idea is now to migrate the glossary list with the cross reference functionality to Scrivener to avoid the additional compiling with Pandoc in the future.
It sounds to me like you already have a good workflow and a result that you like. Using Scrivener to help with the creative/organisational side of that workflow doesn’t mean having to throw it all away and start over with a new system. Scrivener compliments what you’ve already built and developed, much like Typora would.
But more importantly to this here, there is nothing Scrivener can do that will be better than what you have (in this sense of output capability), and in some regards it simply won’t be able to do what you want. It’s just not built to the same level of sophistication as LaTeX, and by proxy, how you can produce LaTeX with Pandoc. That is why it is best to use Scrivener as an ingredient, so that it can augment how these tools work.
Now as for making that easier, go into Compile, make sure “MultiMarkdown” is set at the top, and double-click on your compile Format in the left sidebar. At the bottom of the list you’ll find a Processing tab. This is where you can set your own custom Pandoc command-line, where you can hook into your Lua filters and everything you’ve already built. You should in essence be able to get the same level of automation that Typora provides.
