Martin Gieseking

The issue seems to have been fixed in LLVM: https://bugs.llvm.org/show_bug.cgi?id=38168

I currently can't reproduce the issue because I don't have a Windows 7 system available. According to [this webpage](https://miktex.org/kb/prerequisites-2-9), the recent MiKTeX releases require at least Windows 10, so Windows...

If you don't specify a page color in the LaTeX file, the PDF doesn't contain any background information either and the background gets transparent, even if most PDF viewers display...

I can't reproduce this at the moment. `\pagecolor{white}` adds an opaque, white rectangle to the SVG which precedes all other graphic elements: ```svg ... ``` If I open the SVG...

I get the same result from your PDF file because it doesn't contain a background color. According to the metadata, you created the file with XeLaTeX. It seems `xcolor` doesn't...

I've just had a closer look into the involved tools. `xelatex` produces an XDV file that contains a `background` special which dvisvgm recognizes. So, when converting this file with dvisvgm,...

If you process a DVI/XDV file, dvisvgm converts text components to `text` elements as you can see in your SVG example. Most SVG renderers don't handle them properly, though. Therefore,...

What does dvisvgm print to the console when you call it that way?

> Hm. The fonts seem properly installed. pdflatex has no problems producing the PDF. Right, there probably was a change in the specification of XDV opcode `XFontDef` which used to...

Yes, @muzimuzhi is absolutely correct. dvisvgm uses TeX's length units in the message output, i.e. 1pt = 1/72.27 in. SVG's points, however, are slightly bigger. TeX therefore calls them "big...