public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Jürgen Purtz <[email protected]>
Cc: [email protected]
Subject: Re: First SVG graphic
Date: Fri, 30 Nov 2018 17:36:31 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<CAF4Au4zQ7Vp_XfNFEbSPeed7pRnz2vdTVS3i8kBsX4ZCV48jDQ@mail.gmail.com>
<[email protected]>
On Fri, Nov 30, 2018 at 06:04:06PM +0100, Jürgen Purtz wrote:
> I take the reactions of the last days as a strong consent to go on with the
> effort to integrate graphics into the documentation and use SVG as the language
> which creates such graphics. Also the proposed parallel handling of two SVG
> files - a rich but tool-specific version (optional and not normative) and a
> poor tool-independent version (mandatory and normative) - for the same graphic
> seems to be accepted. The community agrees that this way is not optimal because
> the use of different SVG-tools will lead to unnecessary problems - but there is
> no consensus about tools.
>
> What shall we do next:
>
> • I will create one or more wiki pages where the procedure is described.
> Everybody can extend this pages or contribute to their discussion sites.
> The pages will be found in the category 'Documentation' and its subcategory
> 'SVG' (to be created).
> • Actually, we have the very simple example 'PageLayout.svg' and an example
> of medium complexity 'gin.svg'. For testing purposes we shall have a third
> one of high complexity and with many different graphical elements. Can
> someone send such an example - as a screenshot or in any other format?
> • I want to engage everybody to identify important issues of PG and visualize
> them (similar to Oleg's proposal). We will have a - possibly long lasting -
> period of experiments with different examples. I think, it's necessary that
> we make our experiences with different tools and proceedings (one person
> creates a graphic, another one contributes changes, using the same or a
> different tool, ...). Those examples shall not be pure academic use cases.
> They shall reflect real situations with the expectation to be included into
> the documentation - one day or another.
> • In the initial phase, it may be helpful to do some centralized clearings on
> the first SVG source files. 'Copy&Paste' is widely used and the first
> examples will have the meaning of a lighthouse.
> • I will contact our web-team to discuss style-guide related issues.
Sounds good. I have many xfig/SVG images in my presentations if you
want to use any of them:
https://momjian.us/presentations
--
Bruce Momjian <[email protected]> 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 +
view thread (64+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: First SVG graphic
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox