Exporting concise SVG by melwyncarlo · Pull Request #30598 · matplotlib/matplotlib · GitHub

PR summary

Currently all SVG elements are exported as path, which is currently the most viable solution, as other solutions have their pitfalls. But a concise and apt SVG could make things better and is something probably to work on.

This PR closes #17424. (well, not really, just wanted to link it to the issue as per the PR checklist)
It's not the final solution but it solves the problem. There are restrictions involved in this solution (reference):

        # Option-1: (preferred alternative; currently in use over here)
        #   Set attrib['vector-effects'] = 'non-scaling-stroke'
        #   in _get_style_dict()
        #       Issue:
        #           Part of SVG Tiny 1.2 and SVG 2 (active development)
        #           Supported on modern browsers but not all image editors
        #           Does not scale stroke-width on scaling/zooming,
        #           though it zooms well on browsers while viewing.
        #           Does not directly scale stroke-width when exporting to
        #           higher resolution raster images (PNG); requires first
        #           manually scaling the SVG by:
        #               1. scaling the SVG width, height, and viewbox
        #                   e.g.: current width = 480.0, height = 345.6
        #                         viewbox = 0 0 480.0 345.6
        #                         To obtain 4800px x 3456px image, set
        #                         new width = 4800.0, height = 3456.0
        #                         viewbox = 0 0 4800.0 3456.0
        #               2. Applying transform scale() to the figure
        #                   e.g.: (cont'd) scale factor = 4800 / 480 = 10
        #                         so, change:  <g id="figure_1"> to:
        #                         <g id="figure_1" transform="scale(10)">
        # Option-2:
        #   gc.set_linewidth(gc.get_linewidth() / transform_scale_factor)
        #       Issue:
        #           Works well if tranform_matrix consists only of
        #           uniform scaling and translation, i.e.,
        #           transform_scale_factor = abs(transform_matrix[0, 0])
        #           Otherwise, it requires an advanced affine matrix
        #           decomposition algorithm (SVD or Polar) to compute the
        #           transform_scale_factor.
        #           Still does not correct non-uniform stroke-width
        #           caused by shearing/skewing.
        # Option-3: (currently in use in main branch)
        #   Convert all shapes to path, apply transformations to path,
        #   and then draw path. This basically avoids all the above
        #   mentioned pitfalls.

I have performed relevant tests:

P.S.: It's not meant to pass any CI/CD tests, as the solution itself is assumed to be subject to changes.

If we were to merge this, we would have to provide an rcparam to control it (like we do with text in vector backends that let you pick "text + embed the fonts / hope they are available in the viewer" vs "draw text as paths")

with open('pure_svg_mode', 'r') as f: is NOT for merging (release version). It's simply there to perform my comparison tests as mentioned in my Test Code Repository (link in issue description), i.e., to compare between the old method and the new method. It will be deleted.

I believe that we now have a high enough minimum python we can use the match statement.

Oh yes, I will make that change.
I was also wondering if instead of multiple conditions in this draw function, shouldn't they be called from within their respective classes itself? Or is this the right way forward?

Rather than pin to the svg renderer, if we are going to do this then we should duck-type and allow backends to opt-in to providing more specialized rendering calls.

I agree, something to work on.

I'm mildly in favor of this conceptually, but I think the first thing to sort out is how we want to allow backends to provide additional methods that not all have.

I think the path is to add "additional methods that backends may implement for specialization reasons" + an rcparam to globally turn trying to use them on/off. This is not perfectly clear (as say the users asks for specialization and the backend happens to have draw_circle, should that be prefferniatlly used by draw_marker when the marker is definitly a circle?) but I think is a good starting point. This has some (conceptual) overlap with the methods related to blitting.

Unfortunately given that we require changes inside of draw, I don't see an easy way to do this in an extension module first (I can think of terrible ways that involve sub-classing and monkey-patching but that is a bit too messy to advocate for).

I agree this will take time and a lot of revisions.

I thought there was only one SVG backend. Are there others?

I'm not well knowledgeable on the topic of specialisation that you're talking about.

Extension modules for SVG implementation or backends?

Wouldn't markers too internally be simplified into their basic shape classes?

The cairo (internal) and mplcairo (third-party) backends can also render to svg.
mplcairo actually already internally detects circle markers (by checking for whether the path is the same object as the Path.unit_circle() singleton) and partially special-cases them (see block starting at https://github.com/matplotlib/mplcairo/blob/d922884dcaac3a52ec122d378b0e17629b4909b2/ext/_util.cpp#L652).

I think the path is to add "additional methods that backends may implement for specialization reasons"

I'd like to bring backend versioning back to the table. #30559 While it doesn't solve all issues here, it would really help to formally specify variants of the backend API.

I don't think we should really ever require (or suggest that it be required) that backends provide all these draw_foo methods. Something more reasonable may be to add a single pair of can_draw_patch(Patch) -> bool and draw_patch(Patch) methods (and if the backend says that it cannot natively draw the patch, then fall back to the standard Path representation.

I don't think we should really ever require (or suggest that it be required) that backends provide all these draw_foo methods. Something more reasonable may be to add a single pair of can_draw_patch(Patch) -> bool and draw_patch(Patch) methods (and if the backend says that it cannot natively draw the patch, then fall back to the standard Path representation.

Similar happens for text; you can implement draw_text, but if not, then everything goes through draw_path (which is required).

melwyncarlo added 2 commits September 25, 2025 10:08

Issue 17424 Preliminary Solution

f36876c

Merge branch 'matplotlib:main' into issue_17424

3b86436

github-actions Bot added the backend: svg label Sep 25, 2025

tacaswell reviewed Sep 25, 2025

View reviewed changes

github-actions Bot added the status: needs rebase label Aug 27, 2026

+                          draw_path_instead = False
+                          # Below two lines are only for testing/comparing
+                          # and can be removed
+                          with open('pure_svg_mode', 'r') as f:

+                                      common_args = (gc,
+                                          base_transform,
+                                          draw_path_args[2])  # rgbFace
+                                      if isinstance(patch, (Polygon, RegularPolygon,

+                          with open('pure_svg_mode', 'r') as f:
+                              if f.read() == '1':
+                                  from matplotlib.backends.backend_mixed import MixedModeRenderer
+                                  if isinstance(renderer, MixedModeRenderer) and renderer.is_svg_renderer():

Exporting concise SVG by melwyncarlo · Pull Request #30598 · matplotlib/matplotlib · GitHub

Repository navigation

Exporting concise SVG - #30598

Exporting concise SVG#30598melwyncarlo wants to merge 2 commits intomatplotlib:mainmatplotlib/matplotlib:mainfrom melwyncarlo:issue_17424melwyncarlo/matplotlib:issue_17424Copy head branch name to clipboard

Conversation

melwyncarlo commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR summary

Uh oh!

tacaswell Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

melwyncarlo Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

tacaswell Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

melwyncarlo Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

tacaswell Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

melwyncarlo Sep 25, 2025

Choose a reason for hiding this comment

Uh oh!

tacaswell commented Sep 25, 2025

Uh oh!

melwyncarlo commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anntzer commented Sep 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

timhoffm commented Sep 29, 2025

Uh oh!

anntzer commented Oct 1, 2025

Uh oh!

QuLogic commented Oct 1, 2025

Uh oh!

This branch has not been deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Exporting concise SVG#30598
melwyncarlo wants to merge 2 commits into
matplotlib:mainfrom
melwyncarlo:issue_17424

melwyncarlo commented Sep 25, 2025 •
edited
Loading

melwyncarlo commented Sep 25, 2025 •
edited
Loading

anntzer commented Sep 29, 2025 •
edited
Loading