Comments (10)
Do you have problems with Linux as well as Windows? Which LaTeX distribution do you use?
from svg.
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.
from svg.
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 MiKTeX/miktex#532). I will have a closer look tonight.
from svg.
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!
from svg.
(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}
from svg.
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.
from svg.
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.
from svg.
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:
- pdflatex:
Inkscape 1.0.1 (3bc2e813f5, 2020-09-07) Pango version: 1.46.1
for both cases - lualatex:
kscape 1.0.1 (3bc2e813f5, 2020-09-07) Pango version: 1.46.1
[sic] for redirected pipe - xelatex:
Pango version: 1.46.1
only for both cases
So I re-opened the mentioned issue (MiKTeX/miktex#532)
I created a new issue: MiKTeX/miktex#648
from svg.
I'm going to provide a bug fix today. Hopefully, MiKTeX gets adopted soon.
from svg.
svg v2.02j
is now available via CTAN and so for common LaTeX distributions as well
from svg.
Related Issues (20)
- Including some files from matplotlib fails, commandline works HOT 2
- Importing SVG doesn't work on Windows when the filename contains German special characters
- No helpful error message when inkscape conversion fails HOT 5
- Rendering twice removes the output HOT 1
- \includesvg in Beamer causing wrong figure placement HOT 6
- Bug color/colour of text not correct HOT 2
- Inkscape conversion command deprecated for Inkscape 1.2.2 (2022-12-09) HOT 5
- SVG extracted using `svg-extract` looks different from the original SVG HOT 4
- `svg` package takes the bounding box of the original SVG as opposed to the bounding box resulting from the text conversion HOT 2
- Exporting selected layers HOT 3
- Including two files by the same name results in duplication of the first file HOT 1
- Call inkscape --shell with batches of files for faster processing HOT 4
- Handling for package `svg-extract` only options is flawed when used with package `svg` instead
- TeXstudio autocomplete is not supported by svg package HOT 6
- add support for opt-in ImageMagick instead of Inkscape HOT 4
- Compilation fails for specific images
- Text Reference Displays Section Number Instead of Figure Number with \ref HOT 1
- svg-extract incompatibility with filecontents HOT 1
- includesvg incompatible with setkeys{Gin} HOT 16
- Enhanced support for pandoc HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from svg.