Juan Manuel Macías <maciasch...@posteo.net> writes: >> May you please explain in more detail how these new header arguments fit >> into other available LaTeX code block parameters? In particular, when >> exporting to .png/.svg/.html or when :imagemagick header argument is >> provided. > > Sure! `:pdf-process' simply applies a local value to > org-latex-pdf-process. It does not affect the export to png in its > version without imagemagick process, since this option depends on > org-create-formula-image, which in turn depends on > org-preview-latex-default-process. It also does not affect the export to > html, which depends on org-babel-latex-htlatex. It should work in all > other cases, including imagemagick, which ultimately depend on > org-latex-pdf-process.
Would it make sense to make :pdf-process work for png previews as well? > As for `:full-to-pdf' (I don't know if standalone-to-pdf would be a > better name), the expected result is a pdf file. Therefore it is > incompatible with exporting to png, svg or conversion with imagemagick. > For it to work, it is enough to provide these 2 args: ":file foo.pdf > :full-to-pdf yes." Maybe just :standalone? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
