We could give it a try. Although I would have to do some archeology in my mails because this rings a bell about potential problems I dimly remember encountering when writing my PhD thesis. It may be the integration of Inkscape and the shell for some OSes outside Linux.
Just my .2 cents PA Enviado desde mi iPhone > El 2 may 2025, a las 18:57, Ihor Radchenko <yanta...@posteo.net> escribió: > > Emin Martinian <emin.martin...@gmail.com> writes: > >> Briefly speaking, the current latex export of SVG files does not work out >> of the box and requires adding --shell-escape to the latex args and also >> installing inkscape. Even with those, I found the process brittle. If we >> are going to require inkscape for SVG handling, it seems cleaner to me to >> just use inkscape to convert SVG to PDF and then use \includegraphics >> instead of relying on something like \includesvg >> <https://github.com/bzg/org-mode/blob/b6dbf8881076191e1351d7cd15e26547a2531fea/lisp/ox-latex.el#L2879>. >> Also, if we go with the path of converting SVG to PDF, we can allow/support >> other conversion programs like rsvg-convert. Finally, if other backend >> exporters want to support SVG, converting SVG to PDF (or other formats) can >> support that in a similar way. > > In other words, should we try to go around \usepackage{svg} and instead > convert svg->pdf ourselves, without forcing users to provide > --shell-escape? Even in LuaLaTeX, where --shell-escape is not neccesary, > svg may not render correctly without inkscape. > > -- > Ihor Radchenko // yantar92, > Org mode maintainer, > 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>
