Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gSrOo-0006Am-Ox for pgsql-docs@arkaria.postgresql.org; Fri, 30 Nov 2018 22:36:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gSrOn-0002A1-EN for pgsql-docs@arkaria.postgresql.org; Fri, 30 Nov 2018 22:36:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gSrOn-00026v-7o for pgsql-docs@lists.postgresql.org; Fri, 30 Nov 2018 22:36:37 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gSrOk-0002ZS-F0 for pgsql-docs@lists.postgresql.org; Fri, 30 Nov 2018 22:36:36 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1gSrOh-0002RA-NA; Fri, 30 Nov 2018 17:36:31 -0500 Date: Fri, 30 Nov 2018 17:36:31 -0500 From: Bruce Momjian To: =?iso-8859-1?Q?J=FCrgen?= Purtz Cc: pgsql-docs@lists.postgresql.org Subject: Re: First SVG graphic Message-ID: <20181130223631.GA17824@momjian.us> References: <521932ae-c73d-760d-d973-c980a2d4af82@purtz.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 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 +