Martin Gieseking

Thanks for the feedback and for taking the time to dig into the sources. First of all, there's no need to apologize. I'm always glad if people suggest useful improvements...

Of course, this feature would be an optional extension and not enabled by default. I usually try to keep the functionality compatible with previous releases. :-)

This issue must be fixed in LuaTeX because the format of the font definition `fnt: AppleColorEmoji:mode=harf;language=dflt; at 10pt` is not supported by dvisvgm. Unfortunately, I can't be of much help...

This seems reasonable too. Unfortunately, it's also not that easy to implement because it would require a lot of changes to the current code base. Maybe it's easier to post-process...

I probably won't implement this feature as part of dvisvgm in the near future. However, it doesn't seem to be too complicated create the desired output with an XSLT script....

It's indeed not easy to detect words and word boundaries from plain DVI data since spaces are realized by explicit movements of the virtual cursor which determines the position of...

This seems to be a bug in the dvisvgm backend of LaTeX/XeLaTeX. It creates a `pdf:image` special to reference the PNG file which dvisvgm doesn't support. Here's a excerpt of...

Unfortunately, DVI is a linear format, i.e. several commands that describe or annotate the content of a page may affect preceding and following pages as well. Thus, it's necessary to...

I have to look more closely into the sources, but I guess you're right. It's probably the fontforge library that writes the current date/time into the TTF header which also...

Thank you for your feedback and the detailed feature request. Actually, separating the font data from the page SVGs is on my to-do list for a long time. Since the...