Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Deprecate svgfont support, possibly replacing with woff? #10063

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

Closed
anntzer opened this issue Dec 20, 2017 · 7 comments
Closed

Deprecate svgfont support, possibly replacing with woff? #10063

anntzer opened this issue Dec 20, 2017 · 7 comments
Milestone

Comments

@anntzer
Copy link
Contributor

anntzer commented Dec 20, 2017

Bug report

Bug summary

The svg backend currently exposes the svg.fonttype = svgfont option, which embeds fonts into the svg file using the "svg fonts" feature which appears to be essentially unsupported anywhere and removed from the svg standard (https://caniuse.com/#feat=svg-fonts https://developer.mozilla.org/en-US/docs/Web/SVG/Tutorial/SVG_fonts). The code path was also not working at all on Py3 (#10046).

I would thus suggest deprecating support for svg fonts.

A possibility to still allow embedding the font file into the svg file would be to use the apparently more popular WOFF(2) format, see https://developer.mozilla.org/en-US/docs/Web/Guide/WOFF https://developer.mozilla.org/en-US/docs/Web/CSS/@font-face for the format, http://www.sameratiani.com/2011/10/16/embed-inline-webfonts-in-css.html for embedding the font into the svg file itself, and https://caniuse.com/#search=woff for support. A quick test suggests that this is supported but chrome/firefox, but not by inkscape, but at least inkscape emits a warning and replaces the embedded font by another one, whereas it appears to freeze with the current implementation of svg fonts.

@tacaswell tacaswell added this to the v2.2 milestone Jan 2, 2018
@tacaswell
Copy link
Member

removed from the svg standard

That is indeed a compelling argument.

@github-actions
Copy link

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Apr 28, 2023
@ksunden ksunden modified the milestones: future releases, v2.2.0 Apr 28, 2023
@ksunden
Copy link
Member

ksunden commented Apr 28, 2023

Closed by #10086, just never was properly linked, it was fully removed later (didn't track down exactly when)

@ksunden ksunden closed this as completed Apr 28, 2023
@QuLogic
Copy link
Member

QuLogic commented Apr 28, 2023

It was fully removed in #12245.

@anntzer
Copy link
Contributor Author

anntzer commented Apr 28, 2023

I think we can keep this open to track the possibility of implementing woff(2) support? Feel free to reclose if you disagree.

@anntzer anntzer reopened this Apr 28, 2023
@timhoffm
Copy link
Member

Then, change the title or rather make a new ticket so that one can see the state immediately?

@github-actions github-actions bot removed the status: inactive Marked by the “Stale” Github Action label Apr 29, 2023
@anntzer
Copy link
Contributor Author

anntzer commented Apr 29, 2023

Sure, see #25791.

@anntzer anntzer closed this as completed Apr 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants