On 26 February 2018 at 12:16, Tom Lane wrote:
> Craig Ringer writes:
> > Yeah, I think it'd just effectively preserve the status quo by rendering
> > anyone who's willing to add images and designs to the docs unable - or
> > unlikely to be willing - to do so.
>
> This is an entirely reasonable c
Craig Ringer writes:
> On 26 February 2018 at 04:12, Steve Atkins wrote:
>> Writing SVG by hand maybe doesn't seem the best idea.
>> I understand the attraction to people who want to store everything as
>> diffable text, but images of this sort are unlikely to get updated by
>> others, which mean
> On Feb 25, 2018, at 6:45 PM, Craig Ringer wrote:
>
> On 26 February 2018 at 04:12, Steve Atkins wrote:
>
> Writing SVG by hand maybe doesn't seem the best idea.
>
> I understand the attraction to people who want to store everything as
> diffable text, but images of this sort are unlikely t
On 26 February 2018 at 04:12, Steve Atkins wrote:
>
> Writing SVG by hand maybe doesn't seem the best idea.
>
> I understand the attraction to people who want to store everything as
> diffable text, but images of this sort are unlikely to get updated by
> others, which means they're unlikely to b
> On Feb 25, 2018, at 4:00 AM, Jürgen Purtz wrote:
>
> As an addition to my mail from January 2016 concerning graphics
> (https://www.postgresql.org/message-id/568A9148.30303%40purtz.de) I propose
> to use SVG (after switching to XML) - but not an SVG which is generated by
> Inkscape or simil
As an addition to my mail from January 2016 concerning graphics
(https://www.postgresql.org/message-id/568A9148.30303%40purtz.de) I
propose to use SVG (after switching to XML) - but not an SVG which is
generated by Inkscape or similar tools. Those editors generate very ugly
and chatty commands.
