| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Jürgen Purtz <juergen(at)purtz(dot)de> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: First SVG graphic |
| Date: | 2019-03-09 15:54:11 |
| Message-ID: | 20190309155411.mn5hqlhjbhhrdb4u@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Sat, Mar 9, 2019 at 02:17:33PM +0300, Jürgen Purtz wrote:
> 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.
Uh, so really there is plain SVG, "Optimized SVG", and readable SVG. I
am thinking you should store just "Optimized SVG", and provide a shell
script to convert to readable SVG for those that want it.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-03-09 16:49:31 | Re: First SVG graphic |
| Previous Message | Jürgen Purtz | 2019-03-09 11:17:33 | Re: First SVG graphic |