fletcher
commented
10 years ago I don't think this is something that needs to go in the main MMD source. It can be readily handled by a perl/sed/awk type script, or by simply leaving off the extension when creating the MMD document to begin with.
On 3/21/14 12:03 PM, Tom Torsney-Weir wrote:
Some journal templates don't work with pdflatex so we can't use png, pdf, etc images. You have to use eps images with the standard latex graphicx package. Latex can automatically detect which image format to use and automatically find the correct image based on which version of latex is running. However, the |\includegraphics| statement cannot have an extension in the image reference. So, for example every reference to |\includegraphics{images/image.png}| would need to change to |\includegraphics{images/image}|. Then pdflatex will search for a png file and regular latex will search for an eps file.
Would it be possible to change the latex generation code to support this? I don't mind creating a pull request with this implemented but wanted to get feedback first.
— Reply to this email directly or view it on GitHub https://github.com/fletcher/MultiMarkdown-4/issues/63.
Fletcher T. Penney fletcher@fletcherpenney.net
Some journal templates don't work with pdflatex so we can't use png, pdf, etc images. You have to use eps images with the standard latex graphicx package. Latex can automatically detect which image format to use and automatically find the correct image based on which version of latex is running. However, the
\includegraphicsstatement cannot have an extension in the image reference. So, for example every reference to\includegraphics{images/image.png}would need to change to\includegraphics{images/image}. Then pdflatex will search for a png file and regular latex will search for an eps file.Would it be possible to change the latex generation code to support this? I don't mind creating a pull request with this implemented but wanted to get feedback first.