Open karthink opened 6 months ago
This is solved with the latest updates but only for dvisvgm 3.1+ (with currentColor
support). It's difficult to solve for older dvisvgm versions without some extra code. I think we can simply mention this as a known issue and recommend upgrading to dvisvgm 3.1.
That seems like the most appropriate thing to do at this stage.
Where do we place this advisory? The manual?
That's probably the best place
Okay, let's keep this issue open until we add it to the manual.
karthink @.***> writes:
Where do we place this advisory? The manual?
It might also be helpful to produce a warning when the installed dvisvgm version is too old or when dvisvgm is not installed. This way, users can see what is the problem without digging.
-- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
It might also be helpful to produce a warning when the installed dvisvgm version is too old or when dvisvgm is not installed. This way, users can see what is the problem without digging.
dvisvgm 3.1 is new, it's not part of any texlive release yet. Most users will end up seeing this warning with no way to fix it (beyond silencing the warning itself). The coloring error is limited to tikz previews, dvisvgm works fine otherwise, so I think we can wait a couple of years before issuing a warning when we see dvisvgm < 3.1.
karthink @.***> writes:
It might also be helpful to produce a warning when the installed dvisvgm version is too old or when dvisvgm is not installed. This way, users can see what is the problem without digging.
dvisvgm 3.1 is new, it's not part of any texlive release yet. Most users will end up seeing this warning with no way to fix it (beyond silencing the warning itself). The coloring error is limited to tikz previews, dvisvgm works fine otherwise, so I think we can wait a couple of years before issuing a warning when we see dvisvgm < 3.1.
If there is no catastrophic breakage with older dvisvgm, I agree.
-- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
If there is no catastrophic breakage with older dvisvgm, I agree.
The changes we're making to take advantage of newer dvisvgm versions are fully backwards-compatible. Newer is better, but we'll work with whatever's installed.
Unfortunately dvisvgm 3.1+ does not fix the issue of tikz not respecting the specified foreground color.
When the color is specified earlier in the tex document (like with
\color[rgb]{0,0,0.00392157}
), Tikz and circuitikz elements that follow don't respect it. This causes color issues with the LaTeX preview. This file has an example:A simple workaround would be to specify the color for each fragment, but this will break dvipng conversion processes unexpectedly since it cannot handle more than 99
\color
specials in the DVI.