psfrag is used to alter parts of .eps files within a subsequent \includegraphics. For pdfs, it works only with LaTeX and not with pdfLatex compilation, but pdfLatex will still result in a full document, just without the psfrag alterations.
When it is used in chirun, it results in an error of "TypeError: sequence item 10: expected str instance, @nameuse found".
MWE (Found as MWE PSfrag Fails on the chirun LTI, requires a .eps containing the letter 'a'):
The correct execution of this code would replace the letter 'a' in the drawing.eps with a letter 'b'. An incorrect pdfLatex compilation ignores the psfrag and leaves the 'a' in the diagram. The current Chirun process will crash on finding \psfrag.
Theoretically, we would divert the psfrag and subsequent includegraphics to a LaTeX compiler which can interpret them correctly and use the resulting pdf as the image. Awkwardly, it is possible to use psfrag far before the altered image, including many other latex elements such as text and maths in between the commands, and a psfrag applies to all images within its captured area (ie enclosing in a figure or {} will limit its scope, but putting it at the start of the document will apply to every image in the document). I don't know that there is an effective universal assumption that will help with this.
psfrag is used to alter parts of .eps files within a subsequent \includegraphics. For pdfs, it works only with LaTeX and not with pdfLatex compilation, but pdfLatex will still result in a full document, just without the psfrag alterations.
When it is used in chirun, it results in an error of "TypeError: sequence item 10: expected str instance, @nameuse found".
MWE (Found as MWE PSfrag Fails on the chirun LTI, requires a .eps containing the letter 'a'):
The correct execution of this code would replace the letter 'a' in the drawing.eps with a letter 'b'. An incorrect pdfLatex compilation ignores the psfrag and leaves the 'a' in the diagram. The current Chirun process will crash on finding \psfrag.
Theoretically, we would divert the psfrag and subsequent includegraphics to a LaTeX compiler which can interpret them correctly and use the resulting pdf as the image. Awkwardly, it is possible to use psfrag far before the altered image, including many other latex elements such as text and maths in between the commands, and a psfrag applies to all images within its captured area (ie enclosing in a figure or {} will limit its scope, but putting it at the start of the document will apply to every image in the document). I don't know that there is an effective universal assumption that will help with this.