Related to setting up to run @nontroppo 's Scrivomatic, it seems while pandocomatic successfully installed, the most recent version of paru couldn’t be used because it wasn’t compatible with the 184.108.40.206 version of Ruby built in to my M1 Macbook Air. Evidently the most recent version of paru, paru-1.0.2.gem, requires Ruby 2.7.6 or higher; version 0.4.3 of paru was then automatically installed instead. Is this a problem for using Scrivomatic? Specifically, is it a problem not having the most recent version of paru installed?
An excerpt of this terminal session is reproduced below, where in it complains about the oldness of the built-in Ruby:
ERROR\: Error installing paru\:
The last version of paru \(\>= 0\) to support your Ruby & RubyGems was 0.4.3. Try installing it with \`gem install paru -v 0.4.3\`
paru requires Ruby version \>= 2.7.6. The current ruby version is 220.127.116.11.
I didn’t mention in my OP that I was able to successfully compile the workflow scrivener sample-project, consistent with V0.4.3. of paru working fine, as you suggested above. (I was not able to compile the .tex file in TeXShop to produce a pdf unfortunately however. I might post about that problem separately.)
It seems that I should eventually invest the time to properly install the latest ruby via the method you describe in the Scrivomatic instruction on GitHub. In the mean time, I think your suggestion somewhere to also try Quarto seems promising. Ultimately it would make sense to both have Scrivomatic and Quarto-VSCode as separate, alternative ways of producing output from Scrivener. (Oh, and also just using the pandoc from the terminal as you also describe.)
Yes, this is going to most likely be a problem with LaTeX packages, you can post in the forum.
Indeed, I think apart from the fact that the metadata is different the great benefit of using pandoc-flavoured markdown is the flexibility to. Quarto is also committed to ensure that the source remains the same, and it is the compilation that modifies the final form, very much similar to Scrivener in principle. In theory we can drive Quarto directly from Scrivener, no immediate need for VSCode (though I think perusing your markdown intermediate is informative when tweaking your final output). One small detail is that for web / book output, Quarto uses the one-file one-chapter model. This is not immediately compatible with scriveners one-file one-project output. However, making a small script to split the document up it trivial; and the command csplit can even do this without needing any scripting.
Update: In the thread above I mentioned that I hadn’t been able to compile the .tex file produced by Scrivomatic, but now I’ve managed to. There were a couple issues related to character encoding settings and fonts in TeXShop on my M1 MacBook Air. I may post on this topic separately.