Closed deining closed 3 years ago
Do you have problems with Linux as well as Windows? Which LaTeX distribution do you use?
Do you have problems with Linux as well as Windows?
I encountered the issue with on Windows 10 system.
Afterwards I checked inkscape's version output on Linux, too. I would strongly assume that you encounter the same issue on a Linux system. I haven't verfied that, though.
Which LaTeX distribution do you use?
I'm using MikTeX, latest version.
As I couldn't replicate your problem with TeX Live both on Linux and Windows, I am pretty sure that this is a specific issue with MiKTeX (maybe related to https://github.com/MiKTeX/miktex/issues/532). I will have a closer look tonight.
As I couldn't replicate your problem with TeX Live both on Linux and Windows
I just checked. And yes, I can confirm that my MWE runs flawlessfly on Linux (TexLive).
I am pretty sure that this is a specific issue with MiKTeX
You are right. This also means that this issue is most likely not related to the multiline version output of inkscape v1.x.
(maybe related to MiKTeX/miktex#532)
Not sure. Originally, my installlation was indeed on a path containing spaces. I now reinstalled inkscape, choosing a location without spaces. This didn't cure the problem, though.
I will have a closer look tonight.
Thanks and good luck!
(maybe related to MiKTeX/miktex#532)
Not sure. Originally, my installlation was indeed on a path containing spaces. I now reinstalled inkscape, choosing a location without spaces. This didn't cure the problem, though.
I did not mean potential spaces in the path but how MiKTeX treats an additional line when calling \@@input|"inkscape -V"
as TeX Live only reads the first line and expands to Inkscape 1.0.1 (3bc2e813f5, 2020-09-07)
without Pango version
at all as you can see here:
\documentclass{article}
\usepackage[T1]{fontenc}
\begin{document}
\begingroup
\makeatletter
\@makeother\|%
\endlinechar=\m@ne%
\everyeof{\noexpand}%
\edef\foo{%
\xdef\noexpand\foo{\noexpand\@@input|"inkscape\space-V" }%
}%
\meaning\foo
\foo
\endgroup
\meaning\foo
\end{document}
The example also works in MiKTeX (20.10 portable) and gives Inkscape 1.0.1 (3bc2e813f5, 2020-09-07)Pango version: 1.46.1
I could not replicate the problem with the following MWE:
\listfiles
\documentclass{minimal}
\usepackage{svg}
\begin{document}
\noindent\includesvg[width=\textwidth]{test}%
\end{document}
So maybe updating your MiKTeX installation would solve your issue? If this is not the case, please provide me the output log file for the given MWE either right here or via e-mail.
I could not replicate the problem with the following MWE:
I realized just now that the error only occurs when using xelatex
. I can run your MWE successfully using latex
, pdflatex
and lualatex
, but not using xelatex
.
Hopefully you can reproduce the issues using xelatex
from MikTeX.
So maybe updating your MiKTeX installation would solve your issue?
No, I don't think that my xelatex
installation is outdated.
This is XeTeX, Version 3.14159265-2.6-0.999992 (MiKTeX 20.10) (preloaded format=xelatex 2020.10.21)
If this is not the case, please provide me the output log file for the given MWE either right here or via e-mail.
Here comes the log file, as requested.
Puh, that's a tough one. There are in fact two issues. The first concerns Inkscape. Currently, the info for Pango is passed via stderr
and not stdout
. Running this MWE with TeX Live shows this clearly
\listfiles
\documentclass{minimal}
\usepackage[T1]{fontenc}
\begin{document}
\begingroup
\makeatletter
\@makeother\|%
\@makeother\&%
\catcode\endlinechar=10%
\everyeof{\noexpand}%
\edef\parseversion{%
\xdef\noexpand\pipestdout{\noexpand\@@input|"inkscape\space-V\space2>&1" }%
\xdef\noexpand\pipenormal{\noexpand\@@input|"inkscape\space-V" }%
}%
\texttt{\meaning\parseversion}
\parseversion
\endgroup
\texttt{pipestdout}: \pipestdout
\texttt{pipenormal}: \pipenormal
\end{document}
Regardless of the format used (pdflatex, lualatex, xelatex) the result is the same:
Using a standard pipe only returns Inkscape 1.0.1 (3bc2e813f5, 2020-09-07)
whereas redirecting stderr
to stdout
shows Inkscape 1.0.1 (3bc2e813f5, 2020-09-07) Pango version: 1.46.1
I created an issue for this: https://gitlab.com/inkscape/inbox/-/issues/3882
But there is another issue with MiKTeX. Depending on the format used, the result is different:
Inkscape 1.0.1 (3bc2e813f5, 2020-09-07) Pango version: 1.46.1
for both caseskscape 1.0.1 (3bc2e813f5, 2020-09-07) Pango version: 1.46.1
[sic] for redirected pipePango version: 1.46.1
only for both cases~So I re-opened the mentioned issue (https://github.com/MiKTeX/miktex/issues/532)~ I created a new issue: https://github.com/MiKTeX/miktex/issues/648
I'm going to provide a bug fix today. Hopefully, MiKTeX gets adopted soon.
svg v2.02j
is now available via CTAN and so for common LaTeX distributions as well
Minimal working example
Compilation of MWE fails:
Reason for failure:
Autodectection of inkscape version fails since version output of
inkscape
(v1.01) now has two lines, indicatingpango
version as well:This can be easily fixed by specifiying
inkscapeversion=1
as option which causes auto-detection to be skipped.I'm reporting this error anyway since it might confuse newcomers.
Environment