Great! Yes that seems to have fixed all occurrences that I have.
What is the difference between "+" and "*" here?

Short related question (sorry to hijack this thread):
How could I force the svgs to be produced in a subfolder (e.g. graphics/mytex-1.svg, graphics/mytex-2.svg) instead of the root folder

Other than that, I think this can be closed.

Thanks a lot again for that quick help.

Hello,

thank you so much for the quick solution. I appreciate your help. It almost fixes all the problems. I think what remains broken are paths/menus that span multiple lines:
E.g. when inserting the following line:

```
Go to \directory{C / Program Files / Prog / Loooooooooooooooooooooong / Loooooooooooooooooooooong / Loooooooooooooooooooooong}
```

Maybe we need to hook into first, mid, last of each style instead? But that would probably yield many little svgs right? I think that would be okay for now, if there is no other solution.

Hi!

Any updates on this or an idea how to debug/ give you further info?

I tried opening the produced *.idv in a viewer but it crashes already, so it seems like the produced dvi is indeed corrupt somehow.

Unfortunately, I have no idea where it starts to go wrong (tikz/pgf?,menukeys?,tex4ht?,dvisvgm?).

The tikzpictures drawn by the menukeys package are actually very very simple and work on their own. They are concatenated with text or other tikzpictures by simple hspaces.

Maybe tex4ht can not handle tikzpictures produced by commands correctly? Do I maybe need some custom \Configure to convert everything inside a \menu or \key command together?

Thanks a lot in advance!

Hi again,

my enthusiasm was a bit too early. While the menu commands from the package work, the directory command (which paints a little directory icon in front of a path) fails with:

--- warning --- Improper groups in \special{t4ht+}... idv[2]
pre-processing DVI file (format version 2)
processing page 2
DVI error: stack not empty at end of page

The MWE is:

\documentclass[a4paper,12pt]{article}
\def\pgfsysdriver{pgfsys-dvisvgm4ht.def} % to use the local copy
\usepackage{menukeys}
\renewmenumacro{\directory}{pathswithfolder}
\begin{document}
Hello world.
\directory{C, Users} % fails
\menu{File > Open} % works
\end{document}

I wonder if you can reproduce that.

Yes! linking to Ghostscript finally shows the boxes, too.

I am on macOS. During installation of MacTex you need to click on "Customize", include the Ghostscipt Dynamic Libraries, and afterward set the LIBGS variable for it to be picked up.

Thanks for your help. I think then just the issue of the driver in pgf remains.

I can see that it is on the develop branch since 16 days but I think there was no release yet that includes it (but I might be mistaken).

I think that I get gray boxes in both PDF and HTML. But as you get the Ghostscript errors, this may be some issue with yout TeX distribution, because it should include Ghostscript.

You can try the tikz+ option, which uses native Dvisvgm commands instead of Dvips commands that are used by default. I think this option has some other issues, which is the result why it isn't used by default, but it may work in your case. Try:

make4ht -m draft filename.tex "tikz+"

Hi, and thanks for the quick reply.

When I remove the local copy from your github, kpsewhich says: /usr/local/texlive/2021/texmf-dist/tex/generic/pgf/systemlayer/pgfsys-dvisvgm4ht.def

When I look inside, the contents differ from your github.
If I run the document without this local copy but still with \def\pgfsysdriver{pgfsys-dvisvgm4ht.def} I get:

[ERROR] htlatex: Compilation errors in the htlatex run
[ERROR] htlatex: Filename Line Message
[ERROR] htlatex: /usr/local/texlive/2021/texmf-dist/tex/generic/pgf/libraries/pgflibraryfadings 31 Undefined control sequence.
...
[ERROR] htlatex: /usr/local/texlive/2021/texmf-dist/tex/generic/pgf/libraries/pgflibraryfadings 57 Undefined control sequence.
--- warning --- Ignoring \special{t4ht.html}
...

With the driver from github it succeeds but does not display the gray "background boxes" for the button correctly. Do you see this box in your result? You can e.g. compare it to the PDF version.

Thanks again!

Hi!

I am trying to convert a document where I am using the menukeys package to HTML. It seems to use Tikz internally to draw the menu/key "buttons".
make4ht creates an svg for every usage of such a button but they seem to be broken. For some of them, I get red lines, indicating a parse error. For others, I get the box without the text, since there seem to be additional <g> elements in the <text>.

I tried both drivers from your git repo already
%\def\pgfsysdriver{pgfsys-tex4ht-updated.def}
\def\pgfsysdriver{pgfsys-dvisvgm4ht.def}

The second, pgfsys-dvisvgm4ht.def only creates the text and no boxes but seems to have no errors as far as I could see.

Not sure if this is an error that can be addressed in this package or its helpers but this is the first package in the hierarchy I guess.

An example can be as minimal as:

\documentclass[a4paper,12pt]{article}
\usepackage{menukeys}
\begin{document}
Hello world.
\menu{FOOO}
\end{document}

which compiles fine with e.g. pdflatex.
I am using TL2021.

Thanks in advance for any help!
J