Re: First SVG graphic

From: Jürgen Purtz <juergen(at)purtz(dot)de>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: First SVG graphic
Date: 2019-03-09 11:17:33
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-docs

On 08.03.19 18:55, Peter Eisentraut wrote:
> How do you get from the Inkscape SVG files to the what you call
> "optimized SVG" files?
> I loaded the gin_inkscape.svg file into Inkscape, saved it back out as
> "Plain SVG", but the resultant file did not look at all similar to the
> existing gin.svg.
Inkscape supports a lot of different formats. "Plain SVG" and "Optimized
SVG" are two of them - and they differ in some aspects. "Plain SVG" is
in some respect garrulous and generates unnecessary elements:
namespaces, metadata, IDs, XML-entities. "Optimized SVG" avoids them, as
long as you follow the hints described in Conclusion: People
working with Inkscape shall avoid "Plain SVG" and use "Optimized SVG".

Nevertheless Peter points out an important aspect. If you generate
"Optimized SVG" out of the uploaded files, they look different in
comparison to their original version. As mentioned in,
it is possible - and sometimes advised - to manually 'optimize' the
generated "Optimized SVG" file. I used this technique and tried to make
the files good readable for everyone, especially because we are in an
early phase of SVG integration. But apparently I have overstressed this
possibility. You will find the following differences between the
uploaded 'additionally manually optimized' files and the generated
"Optimized SVG" files:

   - newlines

  - <g stroke="black"> element. This is an Inkscape optimization, which
generates a group out of those elements, which are in a sequence and use
- by chance - the same stroke-attribute. This optimization step is
purely formal and in my opinion misuses the meaning of the <g> element
as a cramp for logically related elements, e.g. to resize or transform
them simultaneously.

As an example of such differences I append two files: gin.svg
("Optimized SVG" plus my manually optimizations; the originally uploaded
file) and gin_pure_opt.svg (pure "Optimized SVG").

What is your opinion? Should we renounce the additional manual step and
use only the pure "Optimized SVG" format? This will increase the
'diff-ablility', which may be valuable in the long term. But direct
readability of the files suffers more or less.

Kind regards, Jürgen

Attachment Content-Type Size
gin.svg image/svg+xml 6.4 KB
gin_pure_opt.svg image/svg+xml 5.8 KB

In response to


Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2019-03-09 15:54:11 Re: First SVG graphic
Previous Message PG Doc comments form 2019-03-08 22:39:16 WAL Configuration Grammar Fix