Subject: Re: First SVG graphic
To: pgsql-docs@lists.postgresql.org
References: <aaa54502-05c0-4ea5-9af8-770411a6bf4b@purtz.de>
 <521932ae-c73d-760d-d973-c980a2d4af82@purtz.de>
 <CAF4Au4zQ7Vp_XfNFEbSPeed7pRnz2vdTVS3i8kBsX4ZCV48jDQ@mail.gmail.com>
From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= <juergen@purtz.de>
Message-ID: <c256ba4f-4064-094a-d1c2-4d8f7ffa4f23@purtz.de>
Date: Fri, 30 Nov 2018 18:04:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: 
 <CAF4Au4zQ7Vp_XfNFEbSPeed7pRnz2vdTVS3i8kBsX4ZCV48jDQ@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------A5CC9B6E04B53B31A257D013"
Content-Language: en-GB
Precedence: bulk

This is a multi-part message in MIME format.
--------------A5CC9B6E04B53B31A257D013
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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.


Kind regards, Jürgen


--------------A5CC9B6E04B53B31A257D013
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>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 <b>different SVG-tools</b> will
      lead to unnecessary problems - but there is no consensus about
      tools.<br>
      <br>
      What shall we do next:<br>
    </p>
    <ul>
      <li>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).</li>
      <li>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?</li>
      <li>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.</li>
      <li>In the initial phase, it may be helpful to do some centralized
        clearings on the first SVG source files. 'Copy&amp;Paste' is
        widely used and the first examples will have the meaning of a
        lighthouse.</li>
      <li>I will contact our web-team to discuss style-guide related
        issues.</li>
    </ul>
    <p><br>
      Kind regards, Jürgen<br>
      <br>
    </p>
    <br>
  </body>
</html>

--------------A5CC9B6E04B53B31A257D013--