Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dvisvgm 2.10.1 #104847

Closed
2 tasks done
spacekitteh opened this issue Nov 25, 2020 · 2 comments · Fixed by #105490
Closed
2 tasks done

dvisvgm 2.10.1 #104847

spacekitteh opened this issue Nov 25, 2020 · 2 comments · Fixed by #105490
Labels
6.topic: TeX Issues regarding texlive and TeX in general 9.needs: package (update)

Comments

@spacekitteh
Copy link
Contributor

Checklist
Project name

nix search name: texlive-dvisvgm.bin
current version: 2.9.1
desired version: 2.10.1

Notify maintainers

maintainers: @veprbl

Note for maintainers

Please tag this issue in your PR.

@veprbl
Copy link
Member

veprbl commented Nov 25, 2020

@spacekitteh Can you tell a bit about your use case?

@spacekitteh
Copy link
Contributor Author

@veprbl I knew I forgot something! 😄

I'm using emacs + org-mode, and am using the =unicode-math= package with =stix2-otf= along with lualatex. In order to preview equations, the pipeline goes

emacs makes a standalone document for compiling -> dvilualatex -> dvisvgm -> emacs loads resulting svg

/However/, =dvisvgm= 2.9.1 doesn't understand the extended font data that lualatex emits (see the comments in https://tex.stackexchange.com/questions/537281/using-opentype-font-with-dvilualatex-and-dvisvgm), and so produces corrupt output images. This was fixed in 2.10.1, which was recently released and pushed to CTAN.

@veprbl veprbl added the 6.topic: TeX Issues regarding texlive and TeX in general label Nov 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: TeX Issues regarding texlive and TeX in general 9.needs: package (update)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants