Skip to content

logos: optimise SVG images#2139

Open
mina86 wants to merge 1 commit intogit:gh-pagesfrom
mina86:a
Open

logos: optimise SVG images#2139
mina86 wants to merge 1 commit intogit:gh-pagesfrom
mina86:a

Conversation

@mina86
Copy link

@mina86 mina86 commented Mar 3, 2026

The main motivation for this change was unnecessary double point in the icon path. The top point of the right corner of the icon are in fact two separate points. I’ve used Inkscape’s ‘Join selected nodes’ function to merge them. I’ve then rounded coordinates in the path to two decimal points (again using Inkscape) and finally using a simple regex eliminate unnecessary spaces in the d attribute.

Working on that I've noticed that the clip paths don’t actually do anything: the paths do not go over the clip paths. I’ve thus removed the clip paths.

The styles for the path were over-specified. fill-opacity: 1, fill-rule: nonzero and stroke: none are all initial values of the properties, so I’ve stripped them out.

Finally, in the Logo images, the width attribute was specified without a unit. To match the height and the Icon images, I’ve added pt unit.

Cc: @jasonlong

The main motivation for this change was unnecessary double point in the
icon path.  The top point of the right corner of the icon are in fact
two separate points.  I’ve used Inkscape’s ‘Join selected nodes’
function to merge them.  I’ve then rounded coordinates in the path to
two decimal points (again using Inkscape) and finally using a simple
regex eliminate unnecessary spaces in the `d` attribute.

Working on that I've noticed that the clip paths don’t actually do
anything: the paths do not go over the clip paths.  I’ve thus removed
the clip paths.

The styles for the path were over-specified.  `fill-opacity: 1`,
`fill-rule: nonzero` and `stroke: none` are all initial values of the
properties, so I’ve stripped them out.

Finally, in the Logo images, the `width` attribute was specified without
a unit.  To match the `height` and the Icon images, I’ve added `pt`
unit.

Signed-off-by: Michal Nazarewicz <mina86@mina86.com>
@jasonlong
Copy link
Member

Seems fine to me, but also these things haven't been a problem in the past 14 years so... 🤷🏼. I'll leave it to the current maintainers to decide.

@mina86
Copy link
Author

mina86 commented Mar 3, 2026

I’ve only noticed because importing it to FontForge results in an ‘Open Contour’ warning.

@dscho
Copy link
Member

dscho commented Mar 8, 2026

Honestly, I don't quite see the point of this improvement... Why change something that served us well for so long? "Don't fix that which ain't broken..."

@mina86
Copy link
Author

mina86 commented Mar 8, 2026

Depends on what you consider ‘broken’. It does result in Open Contour error when importing the file in FontForge. While FF can deal with it, I figured might just as well fix it at the source. But yes, I agree that it’s not a big deal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants