-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Images not included with Xelatex and new version of graphicx #5848
Comments
But we probably would want to keep the functionality of |
It is on macOS Mohave. Reinstalling MacTex seems to fix the problem. |
Struggling with the same problem (thank you for the workaround!), version 52372. Not only Catalina, can be reproduced with e.g., TinyTex on Linux. The reinstallation probably downgrades the version of the package. |
For those who reinstalled to solve this, what happens when you upgrade Tex ( The guaranteed workaround is just to make a modified latex template removing |
We need two pieces of information:
|
Looks like we can solve the problem without grffile by adding curly braces around the image filename if it contains periods: e.g.
|
This issue is relevant also to LuaLaTeX. See also ho-tex/oberdiek#73. |
Hm. The solution recommended in the comment on issue #2074 doesn't work.
I get
Back to the drawing boardd. |
Upstream issue for grffile: https://github.com/ho-tex/oberdiek/issues/73 |
Okay, now that I've read https://github.com/ho-tex/oberdiek/issues/73 I can see that
I think the thing to do is:
Change 1 will break things for those who have dots in filenames (not just between the filename and tex extension), but this is presumably not that common. Hopefully it won't be long before the upstream issue is fixed. |
This package is needed for proper handling of image filenames containing periods (in addition to the period before the extension). Unfortunately, grffile breaks in the latest texlive update. Until a fix is released (see ho-tex/oberdiek#73) it seems best to remove this from the default template. This may cause problems if you have filenames with periods. The workaround is to put `\usepackage{grffile}` in header-includes, and be sure you're using an older version of texlive packages. See #5848. We will leave that issue open to remind us to check upstream, and restore grffile when it's possible to do so.
The issue is due to graphicx rather than grffile: latex3/latex2e#204 |
Based on #5862 it seems that removing grffile is still needed for now. |
the basic plan is that
should work in the core graphics code, with
also working for backward compatibility (the braces are simply discarded) This is implemented in the core latex release unquote branch working on a <2019-10-01> Patch level 2 latex release hopefully in a day or so. https://github.com/latex3/latex2e/tree/unquote grffile package had some other (mostly unused) facilities but it was overwhelmingly used for spaces and multiple dots in filenames. spaces already work in the core (it was that change that broke grffile trying to patch to add the same feature) and multiple dots are working on that branch and will work in the main release once a few more issues sorted out, days not months. Sorry about the inconvenience but the pressure to support spaces (and non ascii characters) in filenames throughout the latex filehandling code became overwhelming really. Most of the changes are in the core latex filehandling, not on the graphics package.
if you really need the existing grfflile |
if you want something that works now then I suspect that
will work, that undoes all the latex 2019 filehandling changes so you can't use non ascii characters or spaces (in \input or \includegraphics) but it does make things work as before.. https://tex.stackexchange.com/a/512877/1090 Although I haven't actually tried either of the fixes suggested there with pandoc. |
@davidcarlisle thanks for commenting here! It's good to know that we won't need to restore |
latex2e 2019-10-01 patch level 2 went to ctan yesterday so should appear in distributions soon, the following forms should all work just using graphicx (not grffile)
I plan to update grffile (to do nothing by default) once that has propagated to mirrors. |
Terrific! |
Using MacTex distribution and graphicx version higher than 51733
the problem exist only for Xelatex engine.
In the tex file generated by Pandoc, if the line
\usepackage{graphicx,grffile}
is replace by
\usepackage{graphicx}
everything is OK
The text was updated successfully, but these errors were encountered: