| 2017-01-15 21:02:17 |
su_v |
description |
I am attaching an 'Optimized SVG' which illustrates my problem. On looking at the code, one sees that much of the size is created by repeating the attributes inside all the elementes of each <g>. My question is: could they not be given to each parent <g>, keeping in the paths, <text> and <tspan> just the information they don't share with their siblings? It would not only slim the file, but make it also more easily editable by hand, at need...
Note: I dare say, this is properly a scour issue--but, as a Windows user, I can access scour only through Inkscape.
Thanks. |
I am attaching an 'Optimized SVG' which illustrates my problem. On looking at the code, one sees that much of the size is created by repeating the attributes inside all the elementes of each <g>. My question is: could they not be given to each parent <g>, keeping in the paths, <text> and <tspan> just the information they don't share with their siblings? It would not only slim the file, but make it also more easily editable by hand, at need...
Note: I dare say, this is properly a scour issue--but, as a Windows user, I can access scour only through Inkscape.
Thanks.
=====
Inkscape 0.92 on Windows 7 64x |
|
