public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: [email protected]
Cc: Jürgen Purtz <[email protected]>
Subject: Re: First SVG graphic
Date: Mon, 11 Mar 2019 10:50:52 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Peter Eisentraut <[email protected]> writes:
> I played with this further.  My conclusion is that SVG as a source
> format is not workable.  Aside from the tooling issues that are being
> discussed, which might be solvable, I think it's not the right level of
> abstraction.

It does seem like using SVG as an intermediate format rather than a source
format might be a better idea.

> (We can have some discussion about whether we want to commit the
> intermediate SVG files and what the directory layout should be etc.   I
> didn't bother with that in my patch yet.)

Ideally, we'd treat them much as we do for bison output files:
we'll supply them in tarballs but you'd better have the relevant
tools if you want to build docs from a git pull.  However, that
may be assuming too much about the portability of the tools ...

			regards, tom lane

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], [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