-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Latest SVGO is creating SVG files that some renderers can’t handle #1164
Comments
What renderer do you use? Probably, it's not fully compliant, since browsers render it ok. Have you tried option like described in #1137 (comment)? |
FYI importing an SVG file optimized with SVGO 1.3 + standard setting did not work, using the following config did work :-)
|
@GreLI @wbervoets To be completely honest, I don’t know what’s the rendering engine here, but this issue is fixed with what @wbervoets suggested above too. So: {
"plugins": [
{ "convertPathData": { "noSpaceAfterFlags": false } },
{ "mergePaths": { "noSpaceAfterFlags": false } }
]
} |
@viljamis I was trying to import the SVG into Android Studio 3.5 (which converts it to Android VectorDrawable xml format). |
SVGO version:
I'm submitting a:
[x] bug report
[ ] feature request
[ ] support request
Current behavior:
It seems like the latest version of SVGO is creating SVG files that some renderers can’t handle.
A little backstory to explain the situation:
Our team relies on SVGO automation in our design system to optimize SVG icons used. In addition to developers, those icons are used by the design team as well inside vector based tools such as Sketch.
Using the latest version of SVGO the icons look like this when opened in Sketch app (left side we have an icon optimized with SVGOMG using SVGO v1.0.3 and on the right using SVGOMG that has been updated to the latest v1.3.0):
Expected behavior:
SVG files produced should work in any vector based design tool in addition to browsers.
Steps to reproduce:
Other information:
There’s a possibly related issue in SVGOMG repository as well: jakearchibald/svgomg#167
The text was updated successfully, but these errors were encountered: