You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hence currently to use dvisvgm driver (for tikz or pgf LaTeX package), one has to either defining \def\pgfsysdriver{pgfsys-dvisvgm.def} or using it as a class option. (LaTeX packages won't throw errors for unknown global/class options.)
Some history:
Commit 10624dc (*** empty log message ***, 2013-08-23) added package option dvisvgm for pgf.sty and the corresponding doc mentioned above. (Yes, the option was added to pgf.sty, but documented for tikz.sty.)
Commit ab8bbb5 (fixed Vertex.lua anchoring problem, 2013-12-18) moved option dvisvgm from pgf.sty to pgfsys.sty.
Proposal:
Add tikz package option dvisvgm (how to treat the same option in pgfsys?)
Revise related doc since graphicx package now supports dvisvgm driver (hence \PassOptionsToPackage{dvisvgm}{graphicx} is another possibility).
Minimal working example (MWE)
% !TeX program = latex\documentclass{article}
\usepackage[dvisvgm]{tikz}
\begin{document}
\end{document}
The text was updated successfully, but these errors were encountered:
Brief outline of the bug
Current state:
tikz.sty
declares no options.dvisvgm
is only known topgfsys.sty
.pgf/tex/latex/pgf/systemlayer/pgfsys.sty
Line 12 in 6e5fd71
dvisvgm
driver (fortikz
orpgf
LaTeX package), one has to either defining\def\pgfsysdriver{pgfsys-dvisvgm.def}
or using it as a class option. (LaTeX packages won't throw errors for unknown global/class options.)Some history:
dvisvgm
forpgf.sty
and the corresponding doc mentioned above. (Yes, the option was added topgf.sty
, but documented fortikz.sty
.)dvisvgm
frompgf.sty
topgfsys.sty
.Proposal:
tikz
package optiondvisvgm
(how to treat the same option inpgfsys
?)graphicx
package now supportsdvisvgm
driver (hence\PassOptionsToPackage{dvisvgm}{graphicx}
is another possibility).Minimal working example (MWE)
The text was updated successfully, but these errors were encountered: