Writing a de-psfagger

Paulo Ney de Souza pauloney at gmail.com
Thu Jan 23 18:43:30 CET 2020

David, Thanks for pointing the way!

I have one quick follow up question. Is there a way to parse a list like
the one in *.fls

INPUT /usr/local/texlive/2018/texmf-dist/tex/latex/graphics/trig.sty
INPUT /usr/local/texlive/2018/texmf-dist/tex/latex/graphics-cfg/graphics.cfg
INPUT /usr/local/texlive/2018/texmf-dist/tex/latex/graphics-def/dvips.def
INPUT /usr/local/texlive/2018/texmf-dist/tex/latex/psfrag/psfrag.sty
INPUT nm3.aux
INPUT cap1.aux
INPUT cap2.aux
INPUT cap1.tex
INPUT /usr/local/texlive/2018/texmf-dist/fonts/map/fontname/texfonts.map
INPUT /usr/local/texlive/2018/texmf-dist/fonts/tfm/public/cm/cmr17.tfm
INPUT Figuras/p11/minima.eps
INPUT /usr/local/texlive/2018/texmf-dist/tex/latex/amsfonts/umsa.fd

and decide which file are TeX system file and which are user input files?
Is kpsewich a good guidance for that?

Paulo Ney

On Thu, Jan 23, 2020 at 4:54 AM David Carlisle <d.p.carlisle at gmail.com>

> If you run tex first with --recorder you could pick up the file paths
> from its log rather than having to re-implement the logic, handling
> texinputs path is easy enough as you can use kpsewhich or equivalent
> but \graphicspath may be hidden behind arbitrary layers of tex macros,
> so you really need a tex engine or a pretty accurate perl emulation
> such as latexml.
> David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/texhax/attachments/20200123/32c4d5e5/attachment.html>

More information about the texhax mailing list