Fix #5573: Use SVG in docs #5677
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Something goes wrong in the format parsing |
|
Merging this so that we can see what the built docs look like at http://matplotlib.org/devdocs We should hold of back porting this until we are sure we are happy with it. |
|
For this to take effect on the devdocs we probably need to change either https://github.com/matplotlib/matplotlib/blob/master/.travis.yml#L110 to not build small or |
jenshnielsen
added a commit
to jenshnielsen/matplotlib
that referenced
this pull request
Dec 31, 2015
Borrowed from matplotlib#5677 which is not backported to 2.x
jenshnielsen
added a commit
to jenshnielsen/matplotlib
that referenced
this pull request
Jan 1, 2016
Borrowed from matplotlib#5677 which is not backported to 2.x
|
This was reverted (see #6835.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This looks a lot better on hi-res displays, and I think will be a nice show-off for the style changes in 2.0.
I think what this PR needs is testing on various browsers and some manual looking for things where SVG breaks (though it all looks pretty good to me on spot-checking, and SVG is one of our better-tested backends).